The latter option conducts a more thorough examination of your drive to look for bad sectors and other such signs of failure. If you want to be a little more particular, you can opt for a quick or extended test. And that's how it works here: if you don't know what type of test to run, click Self Test, and wait for the results. Testing your drive shouldn't be a complicated process - after all, most of it should be automatic. It allows users to test their drives in various ways, and it also offers a few options for formatting/erasing one's storage, among other things.
Being proactive helps, and checking your drives for errors and bad sectors, as well as making periodic backups, is something that may help you in the long run.ĭrive manufacturers often have their own software to offer to help with that, and Seagate SeaTools is an offering from one such manufacturers. However, that does not exclude data loss events from occurring, but it's nice to be proactive. Mission accomplished as far as I'm concerned.Taking care of your drives ensures that they will perform for years to come, and serve you and your data well. It kills the drive as it's scanning for drives to test.Įdit 2: Good news on this, Lenovo has responded back on the original forum topic that they showed the problem to their engineers and they were able to reproduce the problem, and that they are now looking into a fix. In none of the cases did I actually run a test from the SeaTools on the SSD, because it doesn't even get to the point where you can pick a drive to run tests on. I left a note with my laptop repair RMA, but I'm afraid it won't get the higher level attention that it needs without prodding.Įdit: Some additional clarification, this was done to test external Seagate drives. If anyone happens to know of a way of getting this reported to Lenovo engineers, please do speak up. So far, based on the topic for it on Lenovo's forums, there are 3 of us that have encountered this problem, myself having had it happen on 2 separate drives.
I suspect it is a firmware issue on the SSD that reacts poorly to what SeaTools does. I'm talking the partition table is gone and testdisk is unable to bring anything back killed.
Basically, when you run Seagate SeaTools on a Lenovo laptop with an SSD drive starting with MZVLW, it kills the SSD. I'm trying to warn people about this as well as get greater visibility of this issue, as I don't know any way to contact Lenovo engineers about this.
0 kommentar(er)
