hi,
I have a laptop, dell inspiron 4100 with a 30 gb hd.
I erased all existing partitions in order to install win2k and linux.
when I partitioned the hd with the win2k disk and created a 12gb partition everything went fine.
win2k installed without any problem.
BUT when I tried to install linux (I tried so far several different install cd (mepis, vidalinux, yoper, redhat) and live cd as well (knopix, damnsmalllinux, slax, ultimaterescue) I get a bunch of error messages looking more or less as follow:

hda: read_intr: status=0x51 {driveready seekcomplete datarequest error}
hda: read_intr: error=0x01 {addmark not found} lbasect=3, sector=0
dma disabled success
idE0: reset: success

hda: read_intr: status=0x59 {driVeready seekcomplete datarequest error}
hda: read_intr: error=0x01 {addmark not found} lbasect=3, sector=0
dma disabled success
idE0: reset: success

hda: read_intr: status=0x59 {driVeready seekcomplete datarequest error}
hda: read_intr: error=0x01 {addmark not found} lbasect=4, sector=4
dma disabled success
idE0: reset: success

hda: read_intr: status=0x59 {driVeready seekcomplete datarequest error}
hda: read_intr: error=0x01 {addmark not found} lbasect=6, sector=6
dma disabled success
idE0: reset: success

then the disk boot and load the devices but when i run qtparted or cfdisk, the had does not appear.
yet, ifI use a dos or win rescure disk, the partitions are there and kit shows no error at all.
anyone has an idea of how can I fix this problem?

tuxman

and you can boot to W$K without any problems?
if you can check your bios may need to reset to default.
new er drive?

yes win 2k works fine as well as ms-dos disks or dos based utilities.
as a matter of fact I reinstalled win2k without problems.
i checked the bios setting and it does not show any lba imput or setting.

thanks

tuxman

are all these disc's homemade
you may have copy error's
the cdrom drive you are loading from may need to be replaced with a newer one

well, the same disks works on my other pc, so i dont think is a disk failure, most likely something between the linux kernels and the hd, some sort of bad blocks issue.
at least thats my guess but aid like to hear from someone who knows better.

tuxman