There certainly is. DL the 1.7 destructive flasher here..
http://www.ocztechnologyforum.com/f...-Agility-Solid2-Onyx-1-7-Destructive-updaters.. and totally disregard that utility.
In fact.. I can't even remember how many original Vertex drives I've seen that will reach 0% and then start all over again at 100%. There are even a couple of old threads over their that had people panicking about that particular utility and even the author himself chimed in to explain that the algorithms used(while based on the smart data) will only give estimates based on GB written over a particular timespan and then average them out for the expected lifespan numbers. So, if you use the piss outta the drive for 2 weeks and then watch the expected life fall?.. you can see it level out and go right back up if you let it sit idle(such as an unused spare would be) for the next month.
Now don't get me wrong here.. you very well may need to back that data up and take extra precaution.. but out of hundreds I've seen post with concerns?.. only a handful(less than that actually) have actually died after these types of utilities pointed to that possibility.
D-flash will reset the smart data and you can surely go on about your business knowing that you have only scratched the surface for what amount of PE/c that drive will have left. Hope that helps reduce the concern.
PS. I have 10 of those drives and they have been beaten SEVERELY during testing and huge vid ripping/encoding sessions(like 100GB PER session at times). Even though I have no absolute way to know how much data some of the drives have written so far(due to d-flashes wiping the smart data clean).. I can conservatively say that some will have near 20TB worth of writes so far. And they will continue to write at least 2-3 times more when you consider that the PE/c ratings are only based on the MINIMUM amount of PE/c available.. not the actual amount that can be written. Look at extreme forums testing and you will see that aside form some controller panic locks and other failures?.. PE/c is not even a valid concern unless these things are put into 24/7 servers where data sets are huge and constant.