[opensuse] Re: badblocks question
On Sun, 29 Jun 2008 12:22:11 +0200, Carlos E. R. wrote:
1. Is there any way with reiserfs to find out which files are affected by the results of a badblocks test? ie, given a list of bad blocks, can I find out the filenames of any files that are going to be unreadable as a result?
Maybe, but I don't know it.
An alternative is to read every file till it fails, then delete and replace the file.
It's about 400,000 files in total. Ouch, that'll take a while. As I mentioned to Larry, doesn't seem to matter now, as it seems the drive has had some sort of physical malfunction. I managed to get only about 67 GB copied off of it before it croaked. I knew I needed a clean-out, but this isn't what I had in mind. :-(
2. Suggestion was made that I could maybe re-zero the drive to revive things. Could I just zero those blocks in the same way, and if so, how?
Better copy everything somewhere else, and then overwrite the entire drive, and reformat it. The overwriting on normal disks triggers the bad sector remapping, but I don't know about usb enclosures. I suppose it happens, the only thing is that you can't interrogate the chipset about it.
Well, ultimately that woudl be the ideal solution, but at that point, I didn't have another drive. But payday was Friday, so I now have a replacement drive, unfortunately just a little too late to pull all the data off the drive. What I'll probably end up doing is disassembling the unit and hooking the drives up to an IDE/SATA interface (depending on what it is internally) to see if there's any chance of recovering anything. Given it's two drives, it's probably just one that's failed, but it'll depend on how the data spans the drives as to whether or not that'll work. But I should be able to interrogate the electronics for the failure in any event. Not a good data week. :-( -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-06-29 at 19:14 -0000, Jim Henderson wrote:
An alternative is to read every file till it fails, then delete and replace the file.
It's about 400,000 files in total. Ouch, that'll take a while.
Yep. Well, actually you did that, in a way... you were trying to copy the data elsewere and it failed.
As I mentioned to Larry, doesn't seem to matter now, as it seems the drive has had some sort of physical malfunction. I managed to get only about 67 GB copied off of it before it croaked.
It could be the firmware trying to relocate bad sectors, going back and forth between two remote disk tracks, and that sounds like "clicks". Who knows!
I knew I needed a clean-out, but this isn't what I had in mind. :-(
No, certainly not.
2. Suggestion was made that I could maybe re-zero the drive to revive things. Could I just zero those blocks in the same way, and if so, how?
Better copy everything somewhere else, and then overwrite the entire drive, and reformat it. The overwriting on normal disks triggers the bad sector remapping, but I don't know about usb enclosures. I suppose it happens, the only thing is that you can't interrogate the chipset about it.
Well, ultimately that woudl be the ideal solution, but at that point, I didn't have another drive. But payday was Friday, so I now have a replacement drive, unfortunately just a little too late to pull all the data off the drive.
Yes, a pity.
What I'll probably end up doing is disassembling the unit and hooking the drives up to an IDE/SATA interface (depending on what it is internally) to see if there's any chance of recovering anything. Given it's two drives, it's probably just one that's failed, but it'll depend on how the data spans the drives as to whether or not that'll work. But I should be able to interrogate the electronics for the failure in any event.
You can run smart tests on it and learn something. Two drives... double the failure rate, at least :-( - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIZ+kCtTMYHG2NR9URAjRmAJ0UTotZU1RDOP+gtseWAP9xYNrhQgCdGBOV Lu+5sqAiqTHZUlFwEQrd3dA= =zOvf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 29 Jun 2008 21:56:35 +0200, Carlos E. R. wrote:
It's about 400,000 files in total. Ouch, that'll take a while.
Yep. Well, actually you did that, in a way... you were trying to copy the data elsewere and it failed.
Yeah. I think in the end the drive just overheated.
As I mentioned to Larry, doesn't seem to matter now, as it seems the drive has had some sort of physical malfunction. I managed to get only about 67 GB copied off of it before it croaked.
It could be the firmware trying to relocate bad sectors, going back and forth between two remote disk tracks, and that sounds like "clicks". Who knows!
Very possible. It just seems to be cycling that now. I'll probably hit the drive with a bulk eraser I've got somewhere in the basement before disposing of it. In the end, it was about 126 GB of space that was unreadable before it took the final crash.
Well, ultimately that woudl be the ideal solution, but at that point, I didn't have another drive. But payday was Friday, so I now have a replacement drive, unfortunately just a little too late to pull all the data off the drive.
Yes, a pity.
Fortunately, one set of files I knew I'd have difficulty replacing did make it (not to the new drive, but to an internal drive on the system), so it's not a total loss.
You can run smart tests on it and learn something.
Yeah, that at least should help prevent another failure.
Two drives... double the failure rate, at least :-(
Yeah, or at least twice the opportunity for a failure. New drive is a single drive, so hopefully that won't be an issue on it. A little concerned at how hot it seems to run, though. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-06-29 at 20:34 -0000, Jim Henderson wrote:
Yep. Well, actually you did that, in a way... you were trying to copy the data elsewere and it failed.
Yeah. I think in the end the drive just overheated.
I think modern drives run hotter, it's becoming an issue.
It could be the firmware trying to relocate bad sectors, going back and forth between two remote disk tracks, and that sounds like "clicks". Who knows!
Very possible. It just seems to be cycling that now. I'll probably hit the drive with a bulk eraser I've got somewhere in the basement before disposing of it. In the end, it was about 126 GB of space that was unreadable before it took the final crash.
Last time I had a disk go bad, with some bad sectors, I was able to recover an image of the disks partitions with dd; only one was really affected, and I had to do it with dd_rescue instead. On each bad sector it seemed as it tried to read, failed, maybe reset, then tried again. I think it tried 10 or 20 times for each sector, each attempt some seconds, and there were more than a few sectors bad. I left it running for half a day or more, but at the end I got an image I could run reiserfsck on it and recover some of the data. And each attempt it did some clicks. The rest of the disk had no problems at all, just some part of the surface gone bad. If the head or the electronics had been affected, nothing could have been recovered, I suppose. And the partitioning of the disk limited the damage to one partition, making the recovery of the rest very easy.
You can run smart tests on it and learn something.
Yeah, that at least should help prevent another failure.
Two drives... double the failure rate, at least :-(
Yeah, or at least twice the opportunity for a failure. New drive is a single drive, so hopefully that won't be an issue on it. A little concerned at how hot it seems to run, though.
Some enclosures are cooler than others. I like ones from "cooler master" named "xcraftlite". They have both esata and usb plugs, so that testing is easier connecting to the sata interface (which I still have to buy). I heard of others with a little fan. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD4DBQFIaAa3tTMYHG2NR9URAmSSAJwPNX46/gumxKKw7xWbFjYFD3ENJgCY/uRY dOgD08Qg5/P8zKd/45xGjg== =XiyY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 30 Jun 2008 00:03:20 +0200, Carlos E. R. wrote:
Yeah. I think in the end the drive just overheated.
I think modern drives run hotter, it's becoming an issue.
That does seem to be the case, yes.
Very possible. It just seems to be cycling that now. I'll probably hit the drive with a bulk eraser I've got somewhere in the basement before disposing of it. In the end, it was about 126 GB of space that was unreadable before it took the final crash.
Last time I had a disk go bad, with some bad sectors, I was able to recover an image of the disks partitions with dd; only one was really affected, and I had to do it with dd_rescue instead. On each bad sector it seemed as it tried to read, failed, maybe reset, then tried again. I think it tried 10 or 20 times for each sector, each attempt some seconds, and there were more than a few sectors bad. I left it running for half a day or more, but at the end I got an image I could run reiserfsck on it and recover some of the data.
And each attempt it did some clicks.
The rest of the disk had no problems at all, just some part of the surface gone bad. If the head or the electronics had been affected, nothing could have been recovered, I suppose. And the partitioning of the disk limited the damage to one partition, making the recovery of the rest very easy.
It seems that the problem is a bit more involved now; it's not even presenting on the USB bus the way it should, so I think the internal electronics are also toast. I could open it up and bypass them, but I also may have the option of returning the drive. Going to let it sit overnight powered off and see if that helps. I'm not real hopeful at this stage, but it is fortunate it was used mostly for backups and I still have most of the data in other locations.
Yeah, or at least twice the opportunity for a failure. New drive is a single drive, so hopefully that won't be an issue on it. A little concerned at how hot it seems to run, though.
Some enclosures are cooler than others. I like ones from "cooler master" named "xcraftlite". They have both esata and usb plugs, so that testing is easier connecting to the sata interface (which I still have to buy).
I heard of others with a little fan.
The new one actually does seem to be running cooler now - I had it laid down flat on top of the other drive (probably not a good idea in retrospect), now it's got plenty of ventilation on either side and it's not running as hot. So that's good news. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Carlos E. R.
-
Jim Henderson