First of all, it was a defect drive!
BTW: Why badblocks (-vw) doesn't report those failures?
(only klogd does)
Why sfdisk tries to load the xd module?
If you do not specify a device, sfdisk tries all default devices
(hd[a-h], sd[a-e], xd[ab], ed[a-d]).
At 2nd look, some weirdness remains:
As a lucky guy, I have two of those drives.
Both should behave the same in terms of geometry.
But they don't:
Both drives have identical BIOS setting (CHS):
19481/16/63 mapping: normal
BIOS display: CHS, UDMA 2, 10240 MB
Kernel reports:
<4>hda: FUJITSU MPC3102AT E, 9765MB w/0kB Cache, CHS=1024/255/63
<4>hdc: FUJITSU MPC3102AT E, 9765MB w/0kB Cache, CHS=19841/16/63
The kernel gets BIOS info for the first two disks, probably hda and hdb,
at boot time, but does not have BIOS data for hdc, so a difference is
not surprising.
No doubt the disk itself reports 16383/16/83, and the kernel finds 19841
by looking at the LBA capacity.
Probably the 1024/255/63 is a result of BIOS translation.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/