It would be interesting to see as a comparation a similar test but with HDDs. Let's say taking a few models with 640GB or higher plates, make a 40GB partition at the beginning then do the same job and watch how many bad sectors popup in time. We could compare the reliability of old vs new technology when it comes to real usage.
I was thinking that as well.Originally Posted by sergiu
Your not aloneI was thinking that as well.
-
Hardware:
Did you shutdown the drive after the SE?
Yes, toolbox just issues the ATA secure erase command, which is the same as hdderase.
I will check with my cohorts, but I am fairly sure that SE should stop a lifetime throttle. Lifetime throttle is all about the number of writes over a period of time. Get them too high and it slows down to prolong the life.
I tried rebooting a number of times and had to create a new partition after each secure erase, so it would certainly seem that the SE worked, but the drive remained throttled.
Let's see if I can reproduce it with another onslaught from Anvil's app.
For transparency it would be very helpful if the 230 SMART attribute could be made available in a fw update. Ideally it should indicate “lifetime throttling was active for last write” AND “lifetime throttling is currently active”
More info about write limits on a daily basis (or whatever time frame it uses) to avoid throttling would also be very helpful.
Ryder I have noticed something strange. When I run a SE from the Toolbox it states it has completed when finished, however I can still access files on the drive. It is only after I reboot that the drive appears as an un-partitioned space with no data on it.
Does the SE command somehow delay itself until re-boot?
I've noticed in Tony's troubleshooting guide that he states a SE has to be done via Linux in IDE mode. I assume he is referring to a hdderase.
Why use hdderease if it is the same as the toolbox SE process?
Reply With Quote
Bookmarks