Weird Kernel behavior

[DusteD]

Hi, first i want to tell about my system (the relevant parts)
My harddrive configuration is as follows:
On the motherboards ide controller, primary master is a 250 gb system harddrive.
This drive is partitioned as:
32 gb windows 32 bit
32 gb nothing
181,x gb linux
9xx mb swap

Then i have this ide raid controller (qtec) wich is not supported by linux, on it sits:
primary master: 250 gb
secondary master: 250 gb
striped (raid-0)

The disks are assigned as follows:
hda = stripe0 disk of the array
hdc = stripe1 disk of the array
hde = system disk

The problem is, that linux does not see theese as one drive (the stripe) it simply sees
them as two unpartitioned drives, thus leeding to the following problem:

When i boot linux, the first thing that meets me is this:

ide: failed opcode was: unknown
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
ide0: reset: success
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
ide0: reset: success
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 980446940
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
ide0: reset: success

The system actually boots after a while, and everything seems to work (exept ofcause the ide raid)
But i am however worried about this behaviour, and would like to tell the kernel to back off that drive, as it surely have no idea what to do with it.

Ive checked the following files:
/boot/grub/devices.map
/boot/grub/menu.lst
/etc/fstab
and none of them mention anything about hda, or hdc.
How come it tries to read on a drive that it have no buisness with anyway ?
Btw, im running kernel version 2.6.15-1-486 if that is of any help

Please, anyone, if you can help me get rid of this erratic behaviour, answer,
and no i dont mind recompiling the kernel if there are options in there that can help me.

[antidrugue]

You could add an option like that to /boot/grub/menu.lst

hda=noprobe hdc=noprobe

As many options as you like.

If you use Etch, you'll find a section like that in /boot/grub/menu.lst

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

Just add your boot parameters there:

# defoptions=hda=noprobe hdc=noprobe

And run

update-grub

[DusteD]

Thank you very much, that did the trick!