How to isolate bad blocks/sectors?
The following is _reliably_ reported to the syslog every time I run
"parted /dev/hdg print"
Apr 6 11:44:36 creaky kernel: hdg: read_intr: status=0x59 { DriveReady
SeekComplete DataRequest Error }
Apr 6 11:44:36 creaky kernel: hdg: read_intr: error=0x40 {
UncorrectableError }, LBAsect=16778710, sector=16778710
Apr 6 11:44:36 creaky kernel: end_request: I/O error, dev 22:00 (hdg),
sector 16778710
parted goes on to report:
Disk geometry for /dev/hdg: 0.000-42934.992 megabytes
Disk label type: mac
Minor Start End Filesystem Name Flags
1 0.000 0.031 Apple
2 0.031 0.057 Macintosh
3 0.058 0.093 Macintosh
4 0.094 0.191 Macintosh
5 0.191 0.441 Macintosh
6 0.441 0.691 Patch Partition
7 0.691 4096.691 hfs MC_Kits
8 4096.691 8192.691 hfs Linux_Kits
9 8192.691 12288.691 hfs Delivery
10 12288.691 16384.691 hfs Development
11 16384.691 29384.691 ext2 linux_dev_1
12 29384.691 42934.987 ext2 linux_dev_2
Information: Don't forget to update /etc/fstab, if necessary.
My questions are:
- Where on the disk does this bad sector lie? partition table proper?
file system tables? data region?
- How can I isolate this bad sector?
Getting a disk error when reading the partition table makes me more than
a little nervous.
FWIW: the following commands yield the syslog errors:
---------------------
parted /dev/hdg9 print
Apr 6 12:13:42 creaky kernel: hdg: read_intr: status=0x59 { DriveReady
SeekComplete DataRequest Error }
Apr 6 12:13:42 creaky kernel: hdg: read_intr: error=0x40 {
UncorrectableError }, LBAsect=16778710, sector=78
Apr 6 12:13:42 creaky kernel: end_request: I/O error, dev 22:09 (hdg),
sector 78
---------------------
parted /dev/hdg11 print
Apr 6 12:16:55 creaky kernel: invalidate: busy buffer
---------------------
parted /dev/hdg12 print
Apr 6 12:18:58 creaky kernel: invalidate: busy buffer
Apr 6 12:18:58 creaky last message repeated 21 times
Apr 6 12:18:58 creaky kernel: attempt to access beyond end of device
Apr 6 12:18:58 creaky kernel: 22:0c: rw=0, want=13875504, limit=13875503
---------------------
Thanks,
--rich
Reply to: