grub and cciss - how?

[Jef_4]

lets try this again - Opera hates these forums... or vice-versa.... are they always this flaky?

Setting up a batch of DL380 G3's with the 5i controller... Try as I might, I can't seem to get grub to see the disks on it (well, techincally, disk, as it's a RAID 0+1 setup).

I have a devices.map like so:
(fd0) /dev/fd0
(hd0) /dev/cciss/c0d0

(doesn't work with just (hd0), either - already tried that)

and some relevant (?) sections of the menu.lst:

## default kernel options
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/cciss/c0d0 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

title Debian GNU/Linux, kernel 2.4.21-uni
root (hd0,0)
kernel /boot/vmlinuz-2.4.21-uni root=/dev/cciss/c0d0p1 ro
savedefault

etc, with several more kernel options....

Running grub, this is the result:

grub> root (hd0,0)

Error 21: Selected disk does not exist


Anyone have any good resources for setting this thing up? I've read that grub may not really like RAID, but I've also seen some indications that people are doing it... just not really being specific on HOW.

Oh, just in case, we are using Debian 3.0r1 as the OS.

The only reason I'm trying grub is because Ghost breaks LILO, and I have to fix it with a boot floppy. Someone suggested that grub played better with Ghost, so I'm willing to try it.

As an aside, has anyone had luck with Ghost and getting a working LILO upon installation of an image?

Thanks.

[Stuart Browne]

The only things I can think of are driver version (doubtful, as this is pre driver), and boot controller order.

I've not had enough experience playing with DL series or the on-board 5i.

Here's a grub.conf from an ML with a SA6402 (U320, it's big brother *grin*):
----------------------------------------------
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.18-14)
root (hd0,0)
kernel /vmlinuz-2.4.18-14 ro root=LABEL=/
initrd /initrd-2.4.18-14.img

----------------------------------------------
So from what I can tell, your config file is ok.

The '(hd0,0)' reference is for BIOS referenced fixed disk 0, partition 0 (i.e. DOS' C:). If your system BIOS is using something other than the 5i for it's primary boot device, the sort of issue you are describing could occur.

[Vitaly Karasik_1]

below is part of my grub.conf (RHEL 2.1), generated by Anaconda (RH installer).

title Red Hat Linux (2.4.9-e.3smp)
root (hd0,0)
kernel /vmlinuz-2.4.9-e.3smp ro root=/dev/cciss/c0d0p2 hda=ide-scsi
initrd /initrd-2.4.9-e.3smp.img


Regards,
Vitaly

[Huc_1]

Not sure this will help but it is perhaps usefull

I found this LG article, explains grubs well

http://www.linuxgazette.com/issue64/kohli.html

J-P

[Jef_4]

Thanks for the answers... I appreciate it. But after a good night's sleep, I came in and am now having success with things :)

I was following the docs on the GNU site, as well as supplied with the debian grub package to install grub from the OS. Everything installed fine, but it appears that there is a problem seeing the drives from within the OS when running the grub shell, even with the proper devices.map.

So, now that I am back into the office, I decided to reboot and see what happened. Even tho from the OS grub couldn't see things, it can when booting. Go figure.

So, just tweaking my drive/partition settings, and everything looks good now. Next is trying to Ghost the darn thing.

Thanks again for taking the time to reply!

[Huc_1]

thanks, for your feedback.

Just one thing As I notice your are a new memnber to theses forums, most people reply to theses forums on volontary base and a way to let the replier know to what degree the answers they gave is usefull is to assign them points depending on the value to you of the answers.

Now get me right you are not oblige to do this it
it is just a feedback mechanism ... we get rewarded by hat at certain level of points.

but mostly whe are pleased to be of help and a thanks does that.

J-P

[Jef_4]

Weird - I assigned points to everyone, but it stills shows them as being unassigned... may be a browser issue -- I'll take a closer look at it.

thanks again!