ST2000LM007 - Weird Read Issue
-
- Official Product Rep
- Posts: 172
- Joined: Tue Feb 07, 2017 2:18 pm
- Location: Netherlands
- Contact:
Re: ST2000LM007 - Weird Read Issue
affirmative, over
http://www.disktuna.com - video & photo repair & recovery service
Re: ST2000LM007 - Weird Read Issue
Got another one
Patient Drive - ST1000LM035, 1RK172-036, WL1..., SBK3, 2 heads
Head 1 is the offender
Patient Drive - ST1000LM035, 1RK172-036, WL1..., SBK3, 2 heads
Head 1 is the offender
Re: ST2000LM007 - Weird Read Issue
I'm also having the same issue with this drive. One head reads fine (files are ok), but head 1 just trow trash out even with all sectors green...
A head swap will be done and I will post the feedback here!
A head swap will be done and I will post the feedback here!
-
- Newbie
- Posts: 1
- Joined: Tue Apr 06, 2021 3:49 pm
Re: ST2000LM007 - Weird Read Issue
this is new and very common issue of LM hdd.
Re: ST2000LM007 - Weird Read Issue
Just to be clear, do these bogus sectors occur in groups of 8?
Re: ST2000LM007 - Weird Read Issue
Here is another Seagate SMR model (ST4000DM004) where the user has experienced insidious data corruption:
https://forum.hddguru.com/viewtopic.php?f=1&t=40740
In this case SMART reported no errors, and no read errors were seen by the OS, but GP Log 0x04 contained 20 Reported Uncorrectable Errors. The only reason that the user was aware of any corruption was because his file system (BTRFS) automatically computes checksums for each file. This is clearly a firmware bug (Seagate weren't too interested in my bug report).
https://forum.hddguru.com/viewtopic.php?f=1&t=40740
In this case SMART reported no errors, and no read errors were seen by the OS, but GP Log 0x04 contained 20 Reported Uncorrectable Errors. The only reason that the user was aware of any corruption was because his file system (BTRFS) automatically computes checksums for each file. This is clearly a firmware bug (Seagate weren't too interested in my bug report).
Re: ST2000LM007 - Weird Read Issue
Basically, what is happening is that if the drive timeout is long enough, it sends back one of the two patterns for bad sectors, rather than reporting them as bad. I have found that if you drop the timeout down to 100ms, it will get reported as unreadable.
Re: ST2000LM007 - Weird Read Issue
Hi Luke!,
It's my understanding that once a sector shows those patterns you mention, the original data in those affected sectors is overwritten with gargabge permanantly. Have you found this to be the case?
It's my understanding that once a sector shows those patterns you mention, the original data in those affected sectors is overwritten with gargabge permanantly. Have you found this to be the case?
Re: ST2000LM007 - Weird Read Issue
No, the data in the original sector is theoretically there and can frequently be recovered with multiple reads or donor heads. The pattern we see is only given if the timeout is long fairly long...if you set it to 100ms, it will likely report an error, rather than provide garbage.
In PC3000, you can manually setup a map that will populate based on sector contents. MRT just added it to their default map, so no configuration is needed.
In PC3000, you can manually setup a map that will populate based on sector contents. MRT just added it to their default map, so no configuration is needed.