/dev/ataraid directories missing.

[hdok]

Hello,

I have two IBM discs in a raid0 array using the on board promise controller of my P4b533 main board. And a single IBM disc from which I am running gentoo. I would like to be able to mount the windows partitions on the raid0 discs.

I am running a 2.4.20 kernel and have loaded the following modules:
ataraid
raido
md
lvm-mod
pdc202xx_new

The logs in messages have me believing the hardware is recognised just fine (I see a messages that both discs are found) but I cannot mount /dev/ataraid/... because: /dev/ataraid is not there, the directories "ataraid" just have not been created in /dev.

- What should I do to make it work?
In the past there was a tool mkdev or something but cannot find it now.

Because I have found nothing on this in the forums or on google I thought I just drop a note here. There is however a lot of talk on how to get promise raid controllers working and I know mine can function just fine because I have recently switched back from redhat to gentoo (I started missing gentoo ) and in redhat I could mount my windows discs just fine.

Thanx in advance,


PS Have a look at my previous posts to see how long it has been since I returned home

[Helena]

You need to enable the PROMISE FastTrak controller in your kernel config. I don't remember exactly where but I suggest you look under IDE/ATAPI devices or something.

[hdok]

had compiled it as a module:pdc202xx_new

Will recompile the kernel with fasttrack support in it

[hdok]

Have compiled it in the kernel and now it seems to work
Now the next hurdle to take is grub and how to boot my windows partition.
But maybe I will switch to lilo instead seems to be much easier in this case!


Will try to find out why it does not work when I load it as modules, have probably
besides setting them from module to "compiled-in: I might have also set another option
in the kernel config that made it work.

[Helena]

Have compiled it in the kernel and now it seems to work
Now the next hurdle to take is grub and how to boot my windows partition.
But maybe I will switch to lilo instead seems to be much easier in this case!


Will try to find out why it does not work when I load it as modules, have probably
besides setting them from module to "compiled-in: I might have also set another option
in the kernel config that made it work.

It is possible, however you have to create a GRUB boot disk, if I remember well. The installation guide contains further instructions.