Skip to contentSkip to conversation

BadBlocks. Need assistance.

linux-lvm Beppe 2 participants 2 messages Apr 24, 2003

lore
Share & tools
lore

Beppe

author
#0 lore raw

Hi all,

I have run in to trouble.
I have 4 disks 3*76.34GB and 1*31.87GB setup as one vg(/dev/vg_pub/pub) with ext3.

One day, the performance went down radically, so i check the log seeing..

Apr 13 13:59:56 fukke kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 13 13:59:56 fukke kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=33063360, sector=33063360
Apr 13 13:59:56 fukke kernel: end_request: I/O error, dev 03:40 (hdb), sector 33063360
Apr 13 13:59:58 fukke kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 13 13:59:58 fukke kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=33063360, sector=33063360
Apr 13 13:59:58 fukke kernel: end_request: I/O error, dev 03:40 (hdb), sector 33063360

continuous......with different sectors....

I umount it and run fsck.ext3 -f -c -v /dev/vg_pub/pub e2fsch reports:(e2fsck 1.32 (09-Nov-2002))
Pass 1: Checking inodes, blocks, and sizes
Group 64's block bitmap (2097152) is bad. Relocate<y>? yes

Bad block 0 used as bad block indirect block?!?

This inconsistency can not be fixed with e2fsck; to fix it, use dumpe2fs -b to dump out the bad block list and e2fsck -L filename to read it back in again.
Continue<y>?

doing as it says.
dumpe2fs -b /dev/vg_pub/pub > ./badblocks.txt
fsck.ext3 -f -c -v -L ./badblocks.txt /dev/vg_pub/pub
ending up with the same suggestion, do a dumpe2fs -b and e2fsck -L filename.

What will happend if i move the extend with pvmove to a new disk. e2fsck can't fix the disk AFAI tried or?

Logical Volume Manager 1.0.7
kernal 2.4.20 with LVM patch.

grateful for help.

regards,
::Beppe

#1 lore raw
Quoted 34 lines

Hi all,

I have run in to trouble.
I have 4 disks 3*76.34GB and 1*31.87GB setup as one vg(/dev/vg_pub/pub) with ext3.

One day, the performance went down radically, so i check the log seeing..

Apr 13 13:59:56 fukke kernel: hdb: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }
Apr 13 13:59:56 fukke kernel: hdb: dma_intr: error=0x40 { 
UncorrectableError }, LBAsect=33063360, sector=33063360
Apr 13 13:59:56 fukke kernel: end_request: I/O error, dev 03:40 (hdb), 
sector 33063360
Apr 13 13:59:58 fukke kernel: hdb: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }
Apr 13 13:59:58 fukke kernel: hdb: dma_intr: error=0x40 { 
UncorrectableError }, LBAsect=33063360, sector=33063360
Apr 13 13:59:58 fukke kernel: end_request: I/O error, dev 03:40 (hdb),

sector 33063360

continuous......with different sectors....

I umount it and run fsck.ext3 -f -c -v /dev/vg_pub/pub e2fsch reports:(e2fsck 1.32 (09-Nov-2002))
Pass 1: Checking inodes, blocks, and sizes
Group 64's block bitmap (2097152) is bad. Relocate<y>? yes

Bad block 0 used as bad block indirect block?!?

This inconsistency can not be fixed with e2fsck; to fix it, use dumpe2fs -b to dump out the bad block list and e2fsck -L filename to read it back in again.
Continue<y>?

Quoted 7 lines

doing as it says.
dumpe2fs -b /dev/vg_pub/pub > ./badblocks.txt
fsck.ext3 -f -c -v -L ./badblocks.txt /dev/vg_pub/pub
ending up with the same suggestion, do a dumpe2fs -b and e2fsck -L filename.

What will happend if i move the extend with pvmove to a new disk. e2fsck can't fix the disk AFAI tried or?

You should use dd_rescue to move the data to a new (tested) disk. Then you can run fsck on the new disk safely. There is no need to run pvmove etc...

Also, test all your drives with the IBM/Hitachi Drive Fitness Test before continuing. It is available from:

http://www.hgst.com/hdd/support/download.htm

//Anders

Quoted 10 lines

Logical Volume Manager 1.0.7
kernal 2.4.20 with LVM patch.

grateful for help.

regards,
::Beppe

Quoted 5 lines

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

--------
PGP public key: https://tnonline.net/secure/pgp_key.txt