I installed 14.0 on a system with two disks (actually a disk and a raid array) with the following partitions:

/dev/sda1 - swap
/dev/sda2 - root
/dev/sdb1 - home (a raid array)

I changed to the generic kernel and created initrd.gz using the parameters given by mkinitrd_command_generator.sh :

however the system won't start with the message:
after a lot of tries with adding further modules to initrd.gz I eventually found out that the problem with booting generic is that the raid array is assigned /dev/sda (with only /dev/sda1) and the single drive /dev/sdc (with /dev/sdc1 and /dev/sdc2). Something else (?) gets assigned /dev/sdb but has no partitions. Of course, since the the raid does not have a second partition (nor a root file system), init halts at this point. Note that if I boot with huge, everything falls in place and the system starts without problems.

Two questions:

1- (more important): how can I fix this and boot with generic and initrd.gz ?

2- (curiousity): what causes this mess?

thanks

sorry

Your command for mkinitrd does not have the -R flag to add raid support to the initrd.

XGizzmo,

thanks I overlooked that (thought that the script would quote this too). I will try it tomorrow as currently I only have remote access to the machine.

Well, I've added the -R switch to mkinitrd, but this has not solved it. Now I have an extra error message:

mdadm: No arrays found in config file or automatically
mount: mounting /dev/sda2 on /mnt failed: no such file or directory

In fact I checked the machine's specs again and it turns out that both drives are Raid arrays
/dev/sda 320Gb has swap and root partitions and is on a 3w-xxxx controller
/dev/sdb 1Tb has home partition and is on an aic94xx controller

any other help appreciated!

So what could change the device assignment (hard drives) when going from huge.s o generic kernel?