Title: Re: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)
Hey Ole:
 
I'm now looking into this issue more closely and I was wondering if you can post your /boot/grub/device.map (from the imaged node after running SystemConfigurator)?
 
Thanks,
 
Bernard


From: Ole Holm Nielsen [mailto:[EMAIL PROTECTED]
Sent: Mon 30/05/2005 2:50 AM
To: Bernard Li
Cc: [email protected]
Subject: Re: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)

Hi Bernard,

That's a nice observation, since FC3 and RHEL 4.0 ought to be rather
similar !  When SI 3.4.1 installs my RHEL 4.0 client, the master
script executes "systemconfigurator" which gives this error message
twice:
    df: Warning: Cannot read table of mounted filesystems
This is caused by /etc/mtab being an empty file at this stage.
The "df" command (I believe) is executed by grub-install which
is called by systemconfigurator in /usr/lib/systemconfig/Boot/Grub.pm
line 97.

Also, some weird messages are printed by systemconfigurator:
    Boot::EFI Line 90: config_file has been set to /boot/efi/elilo.conf
    Boot::EFI Line 98: bootloader_exe has been set to
    Boot::EFI Line 102: bootmenu_exe has been set to
The only problem is that EFI isn't installed on this client...
FYI, systemconfigurator is installed from the RPM version 2.2.2-1.

The client's /boot/grub/ directory contains corrupted
files (/boot/grub/stage1 is only 512 bytes...) after the
systemconfigurator command has been run.  I think that
systemconfigurator has a problem with Grub as used in
RHEL 4.0.  I have not been able to get this to work, not
even with your suggestion of using devfs in
autoinstallscript.conf :-(

> RHEL4 doesn't use devfs, it uses udev, however, using this method, I was
> able to use SystemImager with Fedora Core 3, which uses udev.

> Perhaps you can post the error messages associated with grub-install?

Thanks, Ole

Reply via email to