Did you try the -l or -L options to fsck.ext3? You need to add the badblocks to the filesystem so that it won't use them again. I have to do this every once in a while on my old 2 GB disk running 7.0 ;o)
It is a bad sign on such a new disk, though. You may want to check with the manufacturer about getting a new disk. Forrest > -----Original Message----- > From: Marco [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 07, 2002 12:49 PM > To: [EMAIL PROTECTED] > Subject: HARD-DISK bad blocks > > > Hello,after a power-failure I noticed these disk errors > that I guess are uncorrectable but I hope to be wrong: > > Jan 5 21:48:44 linux kernel: end_request: I/O error, dev 03:01 (hda), > sector 106864 > Jan 5 21:48:46 linux kernel: hda: dma_intr: status=0x51 { DriveReady > SeekComplete Error } > Jan 5 21:48:46 linux kernel: hda: dma_intr: error=0x40 { > UncorrectableError }, LBAsect=106932, sector=106864 > Jan 5 21:48:46 linux kernel: end_request: I/O error, dev 03:01 (hda), > sector 106864 > Jan 5 22:07:59 linux kernel: hda: dma_intr: status=0x51 { DriveReady > SeekComplete Error } > Jan 5 22:07:59 linux kernel: hda: dma_intr: error=0x40 { > UncorrectableError }, LBAsect=106932, sector=106864 > Jan 5 22:07:59 linux kernel: end_request: I/O error, dev 03:01 (hda), > sector 106864 > Jan 5 22:07:59 linux kernel: hda: dma_intr: status=0x51 { DriveReady > SeekComplete Error } > Jan 5 22:07:59 linux kernel: hda: dma_intr: error=0x40 { > UncorrectableError }, LBAsect=106932, sector=106864 > Jan 5 22:07:59 linux kernel: end_request: I/O error, dev 03:01 (hda), > sector 106864 > > I guess that it is a phisical damage to the hard-disk's sector number > 106864 > > I'm using Red Hat 7.2 (kernel 2.4.7-10) with ext3 filesystem > (journalled-ordered). > I ran "fsck.ext3 -c" and a lot of bad sectors were discovered, > finally I ran "fsck.ext3 -p -v -c" and fsck reported 220 bad blocks > found > on root partition /dev/hda.Despite of that,I nomore see same errors as > above, > they are only: > > [root@linux etc]# tail -f /var/log/messages > Jan 7 18:08:13 linux gconfd (marco-1275): 21 items remain in > the cache > after cleaning already-synced items older than 300 seconds > Jan 7 18:15:34 linux kernel: hda: timeout waiting for DMA > Jan 7 18:15:34 linux kernel: ide_dmaproc: chipset supported > ide_dma_timeout func only: 14 > Jan 7 18:15:34 linux kernel: hda: status error: status=0x58 { > DriveReady SeekComplete DataRequest } > Jan 7 18:15:34 linux kernel: hda: drive not ready for command > gen 7 19:05:46 linux su(pam_unix)[1988]: session opened for user root > by marco(uid=500) > Jan 7 19:07:24 linux kernel: hda: timeout waiting for DMA > Jan 7 19:07:24 linux kernel: ide_dmaproc: chipset supported > ide_dma_timeout func only: 14 > Jan 7 19:07:24 linux kernel: hda: status error: status=0x58 { > DriveReady SeekComplete DataRequest } > Jan 7 19:07:24 linux kernel: hda: drive not ready for command > > {HDA NOTES:} > {hda: Maxtor 2B020H1, ATA DISK drive} > {hda: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=2491/255/63, > (U)DMA} > > The disk access speed was reduced before running fsck,now it seems > normal > as before power-failure. > Is now a DMA setting problem or is still a DISK problem? > > What you think? Is there any repairing solution? > > -- > 73's! Marco <[EMAIL PROTECTED]> | http://www.qsl.net/ik5bcu > i.p.:44.134.210.32 44.134.210.33 | > AMPRNET:[EMAIL PROTECTED] > AX25:[EMAIL PROTECTED] | GSM:+393297378262 > > > > _______________________________________________ > Seawolf-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/seawolf-list > _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
