the 2005.1 livecd works correctly. the system is correctly installed. the hard disk is within internal RAID. its name is /dev/cciss/c0d0, and partitions which are successfuly created with fdisk and mounted as swap and ext3 are /dev/cciss/c0d0p1 (swap) and /dev/cciss/c0d0p2 : root@livecd ~ # fdisk -l Disk /dev/cciss/c0d0: 36.4 GB, 36414750720 bytes 255 heads, 32 sectors/track, 8716 cylinders Units = cylinders of 8160 * 512 = 4177920 bytes Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 1 246 1003664 83 Linux /dev/cciss/c0d0p2 247 8716 34557600 83 Linux root@livecd ~ # after several iterations i got this grub.conf file which somehow boots the Proliant: root@livecd ~ # mount /dev/cciss/c0d0p c0d0p1 c0d0p2 root@livecd ~ # mount /dev/cciss/c0d0p2 /mnt/gentoo root@livecd ~ # cat /mnt/gentoo/boot/grub/grub.conf default 0 timeout 30 boot=/dev/cciss/c0d0 device (hd0) /dev/cciss/c0d0 root (hd0,1) splashimage=(hd0,1)/grub/splash.xpm.gz title=Gentoo Linux 2.6.14-r4 kernel /boot/kernel-genkernel-x86-2.6.14-gentoo-r4 ramdisk=8192 doscsi udev initrd /boot/initramfs-genkernel-x86-2.6.14-gentoo-r4 root@livecd ~ # after the 'unclean' boot process (there is something wrong in parts with the display) i got to the point where something (presumably udev) tells me that there is unkown root block device. i get the busybox shell and the /dev/ does not have any reference to the /dev/cciss/ not to any other resembleing device (i.e. scsi). there is however one disfunctional /dev/hda device file and off course the /dev/ide/... cdrom . i had RHEL 3.0 U3 linux running happily on the machine without any problem. unfortunately i did not saved the grub config before reinstall. Reproducible: Always Steps to Reproduce: 1. Install form 2005.1 livecd. 2. configure correctly everything. 3. reboot. Actual Results: failed Expected Results: to reboot properly and the installed system to recognize the /dev/cciss/c0d0 as the livecd does.
What version of udev are you running? Do you have the proper driver for your disks built into your kernel, or as a module? It sounds like your module is just not being loaded.
it could be. i made a 'genkernel all' kernel build. i have never done that before in any other gentoo installation. i have done that exactly for proper loading of all the modules i even did not know Proliant needed. i did not controlled what and how is loaded. i think that the cciss module need to be loaded. however, the grub has problems with detecting the (hd0) as /dev/cciss/c0d0 anyway. it is the root problem. i found on other web page that at least on one occassion the lilo did not help either with detecting it on gentoo. grub device.map did not contained (hd0) entry at all. i had to add it manually. this was fixed at grub bugs page a year ago. do i need to recompile the kernel or initrd or add the cciss module to the /etc/autoload... file?
hello. i have read more on the issue in the gentoo forums. i think that the problem with grub is separate from my own problem where cciss module most probably is not not loaded AFTER boot. however i would say at the moment that if this is to be pursued as a bug it is most likely to be configuration issue within grub and not a bug as such in gentoo. to be frank - this should be closed. if you have good information how to overcome grub installation (grub-install definitely not works) with Compaq Smart Array 5i (cciss) disks than perhaps this should be mention as a warning or something within the gentoo installation handbook. thank for your help!
