Re: ST3500320AS Seagate drive disappears
March 6th, 2013, 16:04
Bad sectors can cause a drive to go off line!
Using the forward or jump options you need to check the drive every 5 or 10% just a few lba's at a time and then move on another 5 or 10% until the end of the drive. This gives an idea where real bad sectors are located. If every time you get abort through the rest of the drive it is likely to be a firmware problem, maybe the translator.
Using the forward or jump options you need to check the drive every 5 or 10% just a few lba's at a time and then move on another 5 or 10% until the end of the drive. This gives an idea where real bad sectors are located. If every time you get abort through the rest of the drive it is likely to be a firmware problem, maybe the translator.
Re: ST3500320AS Seagate drive disappears
March 6th, 2013, 19:02
@helpless,
... and that screenshot shows some successful reads, before later hitting a UNC followed by ABRT. To me, your statement of the test you ran, plus the screenshot, disproves the suggestion by Spildit that there is a translator problem which prevents reading "anything past LBA 3,276,957". If that scan started at LBA 100,000,000, then your second MHDD screenshot shows that many LBAs past that one, were readable. I have seen this on many 7200.11 drives - several LBAs on a failing drive (not just one) which trigger this behaviour.
There's lots more I could say, but as Spildit is helping you so much, and so assertively, I'm going to stop here. It's not worth my time trying to put explain further (my gf is complaining about the amount of time I've spent on the laptop in the last few days
), especially as you haven't provided the terminal info nor performed the specific cloning tests, which I suggested. I wish you good luck 
helpless wrote:A new test picture scanning from LBA 100.000.000. is below
... and that screenshot shows some successful reads, before later hitting a UNC followed by ABRT. To me, your statement of the test you ran, plus the screenshot, disproves the suggestion by Spildit that there is a translator problem which prevents reading "anything past LBA 3,276,957". If that scan started at LBA 100,000,000, then your second MHDD screenshot shows that many LBAs past that one, were readable. I have seen this on many 7200.11 drives - several LBAs on a failing drive (not just one) which trigger this behaviour.
There's lots more I could say, but as Spildit is helping you so much, and so assertively, I'm going to stop here. It's not worth my time trying to put explain further (my gf is complaining about the amount of time I've spent on the laptop in the last few days
), especially as you haven't provided the terminal info nor performed the specific cloning tests, which I suggested. I wish you good luck
Powered by phpBB © phpBB Group.