Thanks for the info and all the replies. I am using the latest 4.1.99 rpms from Bernard's release area.
I was finally able to see what is going on using the si_monitortk application and captured a console log from a couple of my systems. I think the grub install is failing in some unusual way. The call to grub-install is producing a usage message as if it does not like one of the options provided. I see in the usage message that it says the "recheck" option is unreliable and is strongly discouraged but this option is being used when grub-install is being invoked. The following messages about grub appear in the console log file: 2011-7-13 15:7:36 [Boot::Grub :: Line 132] grub supports --no-floppy argument. 2011-7-13 15:7:36 [Boot::Grub :: Line 107] Grub executable set to: /sbin/grub-install. 2011-7-13 15:7:36 [Boot::Grub :: Line 151] bootloader = /sbin/grub-install 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: /boot 2011-7-13 15:7:36 [Boot::Grub :: Line 338] mount: / 2011-7-13 15:7:36 [Boot::Grub :: Line 368] calling /sbin/grub-install --no-floppy --recheck UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 Probing devices to guess BIOS drives. This may take a long time. Format of install_device not recognized. Usage: grub-install [OPTION] install_device Install GRUB on your drive. -h, --help print this message and exit -v, --version print the version information and exit --root-directory=DIR install GRUB images under the directory DIR instead of the root directory --grub-shell=FILE use FILE as the grub shell --no-floppy do not probe any floppy drive --force-lba force GRUB to use LBA mode even for a buggy BIOS --recheck probe a device map even if it already exists This flag is unreliable and its use is strongly discouraged. INSTALL_DEVICE can be a GRUB device name or a system device filename. grub-install copies GRUB images into the DIR/boot directory specfied by --root-directory, and uses the grub shell to install grub into the boot sector. Report bugs to <bug-g...@gnu.org>. 2011-7-13 15:7:37 [Boot::Grub :: Line 319] mount: /boot 2011-7-13 15:7:37 [Boot::Grub :: Line 319] mount: / 2011-7-13 15:7:37 [Boot::Grub :: Line 321] mount: / mounts: UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7 2011-7-13 15:7:37 [Boot::Grub :: Line 247] d = /dev/sda1 2011-7-13 15:7:37 [Boot::Grub :: Line 250] Device: sda; Part: 1 2011-7-13 15:7:37 [Boot::Grub :: Line 252] Biosdev: (hd0) 2011-7-13 15:7:37 [Boot::Grub :: Line 374] Installing GRUB on (hd0,0) 2011-7-13 15:7:37 [Boot::Grub :: Line 377] Grub root set to (hd0,0), bootdev=(hd0) Probing devices to guess BIOS drives. This may take a long time. 2011-7-13 15:7:37 [main :: Line 479] All done. I have modified the following files: /boot/grub/grub.conf /boot/grub/grub.conf /etc/modprobe.conf /etc/modules.conf /etc/sysconfig/network /etc/sysconfig/network-scripts/ifcfg-eth0 Has anyone seen this before? Is there someway I can eliminate this --recheck option from being used with grub-install? Or is it that grub just does not like the "UUID=0b8f2f84-5a03-4a80-b853-a624d496e5e7" device it is given? If I could figure out where the call was being made I would try to fix it. I tried inserting a hard-coded grub-install line into a couple of different places in the autoinstall master script but it seems no matter where I put ti the script complains that the path is not correct (it cannot find the executable). -- Steven DuChene -----Original Message----- >From: Chris Pepper <pep...@reppep.com> >Sent: Jul 13, 2011 10:46 AM >To: sisuite-users@lists.sourceforge.net >Subject: Re: [sisuite-users] Not seeing boel messages on serial console > > Development is going on, but I don't know how close we are to a >packaged release. Check the archives of this list. > > The released versions of SI do not work well on current hardware -- >they don't include current drivers, so don't work on our current nodes, >for instance. > > SALI <https://subtrac.sara.nl/oss/sali> is a current boot image, but >it's not 100% compatible. I got part way through shimming it to work, >and my notes are now in the SALI wiki, but SI should have a usable image >built-in, and the compatibility problems need to be sorted. > >Chris > ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
