ha haha
2005-Jun-28 22:01 UTC
How to figure out underlying failed disk(parttions) and sector(s) position ???
Hi, with being exposed to more and more failed hard disks reports, I've accumulated several questions of the logged messages in /var/log/messages file: like how to identifying failed disks(partitions), where is the exact failed sector(s) on the hard disk, and why badblocks reports OK to the reported disk failure. Let me explained the above with the following several example. scenario #1, a PATA hard disk failed.. Host: host1 ..... Jun 21 16:55:09 host1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jun 21 16:55:09 host1 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=234304234, high=13, low=16200426, sector=196487120 Jun 21 16:55:09 host1 kernel: end_request: I/O error, dev 03:0b (hda), sector 196487120 ..... The case #1, showed that /dev/hda failed in a simple way, but some stuff are not obvious: Q1: which failed partition? "dev 03:0b" looks like /dev/hda11, but no quick document explains it, /dev/hda11 is just a guess based on the follwing. -- maybe "/dev/hda11" is a better string to log if my guess is true? root at host1# ls -alF /dev/hda11 brw-rw---- 1 root disk 3, 11 Sep 15 2003 /dev/hda11 Q2: which sector failed? looks like it is sector 234304234 in LBA mode, and relative to the whole disk /dev/hda(relative to sector 0 of /dev/hda); while it is the sector 196487120 when relative to /dev/hda11 (sector 0 of /dev/hda11 partition, which may be Gigabytes offset from the beginning of underlying disk). Is this a reasonable guess? Q3: what does the "high=13, low=16200426" means? Q4: Does linux kernel disk driver tries to relocate the failed sector --mapping access to it to some other good sector first, before failling and logging errors to /var/log/messages? Q5: "badblocks -s -v -n ..." sometimes can not find any disk problems even there were reported disk I/O problems in /var/log/messages? what does that mean? Thanks a lot... ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com
evilninja
2005-Jul-01 00:38 UTC
How to figure out underlying failed disk(parttions) and sector(s) position ???
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ha haha schrieb:> Jun 21 16:55:09 host1 kernel: end_request: I/O error, > dev 03:0b (hda), sector 196487120afaict, this message comes from drivers/block/ll_rw_blk.c, so not really ext2 specific and should probably go to lkml (mind to send a patch?) i think the reiserfs folks had somethnig simliar in the works for reiserfs-specific error messages but i can't remember the name of the (mail)thread.> Q3: what does the "high=13, low=16200426" means?again not ext2 spcific, as this is from drivers/ide/ide-lib.c. - -- BOFH excuse #47: Complete Transient Lockout -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCxJBsC/PVm5+NVoYRAkdFAJ455ZWjNo9XulUZy2wJl+6H4AMqZwCg1fZ0 zzlr1OYCyAiLMJXG1Fyi5Cc=09yx -----END PGP SIGNATURE-----
Apparently Analagous Threads
- figure out underlying failed disk(parttions) and sector(s) position ???
- Problem in e2fsck ? read error in journal inode
- root fs not mounting ext3
- syslinux 6.03 bug related to rev shadow and scroll bar with vshift
- BIG Bug on Linux EXT3 file system, or "/bin/ls" problem?? Please Help!!!