On Mon, Apr 13, 1998 at 12:14:33AM +1000, Hamish Moffatt wrote: > On Sun, Apr 12, 1998 at 04:09:50PM +0200, Marcus Brinkmann wrote: > > I have now some bad blocks on my 2-year-old WD Caviar IDE drive. I'm not > > overly concerned, because I have a brand new SeaGate, on where I install > > hamm atm, but I wonder if linux can mark bad blacks as 'used', so that it > > doesn't write on them anymore. Or how do you cope with bad blocks? > > (I also get irq timeouts and drive resets, and then the system hangs. Why?) > > "e2fsck -c /dev/device" will do it. I believe the IRQ timeouts and > drive resets are a symptom of bad blocks, they were when I got some here.
If this really will mark bad blocks, I could have real trouble (and I will follow Ben Pfaffs advise to backup). I'm a bit confused: When I run e2fsck -c on the drive again, will it find the bad blocks already found again? I ran this command, and again I got timeouts. Then I ran the command a second time, and it found (the same?) bad blocks. I think it were the same because the sector numbers have been the same/similar? > Actually, most of the IRQ timeouts and drive resets were caused by > a faulty power supply in that machine. I replaced it, and found > one bad blocks with e2fsck, and the machine has been perfect ever since. > (Up 62 days, exactly 62 days since I replaced that power supply.) I think the power supply is okay... I will run e2fsck -c again, will backup and repartition the drive and will use it. And I will contact WD about the warranty. Thank you for your help, Marcus -- "Rhubarb is no Egyptian god." Debian GNU/Linux finger brinkmd@ Marcus Brinkmann http://www.debian.org master.debian.org [EMAIL PROTECTED] for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]