|
From: Bruce S. <bw...@re...> - 2010-05-11 20:20:30
|
"badblocks" can scan a disk or partition for read errors. That might tell you if the disk is physically damaged vs. the filesystem being corrupt. Be careful with the options, some will write & destroy data, where others only do a read test. You can always do a fsck to see if that clears up any problems. If the disk is physically damaged, you might be able to recover some files and not others, depending where the bad sectors lie. I actually had luck once by putting the damaged drive in a freezer for awhile, and then connecting and reading it quickly before it warmed up. I had to repeat the freezing multiple times because I could only recover a few files before it warmed up. Is this a good time to lecture on the benefits of a good backup procedure? :-) Also, since you're reformatting from scratch, this might be a good time to consider moving to ext4. I've found it to be much faster. - BS On Tue, May 11, 2010 at 13:52, Chris Grove <dl...@ki...> wrote: > Hi guys, I'm hoping someone out there can point me in the right direction. > I've been using DL for quite a while now and am currently using 1.4. The > other day I had one of my hard drives start to fail so I brought a nice new > 400Gb drive and installed. I partitioned it and used mkfs.ext3 on it and > copied data to it with no problems. Yesterday I decided to move some of my > data around and while doing so I received several I/O errors. When I checked > the Dmesg I found several of the following errors: > attempt to access beyond end of device > hdd1: rw=0, want=8234593600, limit=625137282 > I've goggled this error, but I'm not sure what tools, if any, that DL has to > fix it. Can someone please point me in the right direction. > Thanks in advance, Chris. > ------------------------------------------------------------------------------ > > > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > |