by Hi,
I hope someone can help me with this:
I have bought a new harddisk, a seagate medalist 4300mb (not the
pro-version). It is an UDMA2-harddisk. The label says it has 8894
cylinders, 15 heads and 63 sectors. The BIOS and linux autodetect
523/255/63. The disk works fine with windows '98. Linux gives me the
following problems:
1. When the kernel reads the partitiontable, it gives the following
error-message, but i does successfully read the partitiontable. When the
partitiontable is reread after running fdisk, I don't see any error
messages.
The error was:
hdb: set_multmode: status=0x51 {DriveReady SeekComplete Error}
hdb: set_multmode: error=0x04 {DriveStatusError}
2. when i write the partitiontable with fdisk, and then restart fdisk,
and look at the partitiontable, fdisk said the following:
partition 2 has different physical/logical ending:
phys=(600,254,19) logical=(90,254,63)
partition 2 does not end on cylinder boundary:
phys=(600,254,19) logical=(90,254,63)
partition 4 has different physical/logical beginnens (non-Linux?):
phys=(254,0,11) logical=(448,0,1)
3. When i run mke2fs i get the following error-message (no matter what
inode-size i specify):
hdb: write_intr: status=0x051 {DriveReady SeekComplete Error}
hdb: write_intr: error=0x10 {SectorIdNotFound}, LBASector=97910975,
sector=141
(and this about 5 times for every sector)
sometimes is see:
ide0: reset: success
4. I do remember seeing this message (but i don't remember when, and i
could not recreate it):
hda: dma disabled
hdb: dma disabled
When i ignore all errors, and install slackware, fsck gives a lot of
error-messages, and it won't boot. When i boot linux with parameters
"hdb=8894,15,63", problem #2 does not occur, but all the other things
still go wrong. I tried to install slackware 3.5 with kernel 2.0.34. I
had the same error with kernel 2.0.35. My motherboard is an Asus P2B-DS,
but i could recreate the error on a p166. I also tried the disk as
master, slave and single, and on the primary and secondary IDE. It all
gave the same effect. Another quantum 6.4gb-disk works fine in the same
system.
Does anybody know what could be wrong ? Is there a bug in the kernel ?
Or is the disk just broken (but then...it works fine with windows '98
and DOS).
I hope someone can help me, otherwise I'm doomed to use win'98 :(
Grtz,