first, I would like to thank Alan Cox, Mark Hahn,
Horst von Brand, and David B. Rees for their replies.
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?
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
Useless to say, that my boot manager (netboot) complains about not
being able to load the boot block! (although, it's below the 1024 cyl)
When booting from floppy, the kernel has no problems with hda.
DOS sees only 8033 MB of hda.
With LBA mapping enabled, netboot/lilo works again, but kernel
doesn't change his view of drive geometry?!
Did anybody has a clue, why BIOS uses different geometries on
identical configured drives? (b)illness/silliness? I am confused!
ASUS P5A, BIOS v. 1004 (actual)
Comment to the
Dumb question: Which is "better" SCSI or IDE disks? thread:
The bigger the drives become, the easier is SCSI to handle!
(although not without problems, too)
cu
Hans-Peter
-
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/