Title: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)
Hi Ole:
 
Do you use SystemConfigurator along side SystemImager?  One thing you can try is modify autoinstallscript.conf and add:
 
<boel devstyle="devfs" /> right before the config block ends (right before </config>).
 
Then re-run mkautoinstallscript for the image and try to re-image a new client.  See if that works.
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] on behalf of Ole Holm Nielsen
Sent: Tue 24/05/2005 8:08 AM
To: sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)

We use si_getimage to extract an image from the golden client,
and then we install another client using PXE-booting.  All
this works beautifully until the cloned client tries to
boot from its harddisk, where this message appears:
    "Error loading operating system"
We booted a Live CD and installed a boot loader
on the disk using Grub, and now this slightly modified
cloned client boots correctly.

The error therefore seems to be that the SystemImager
Master script doesn't write the appropriate boot loader
record (or whatever it's called) to disk.  However, I can't
figure out where the Master script is performing this action,
so maybe there's a subtle problem here related to newer
versions of various other tools ?  I wonder if the "parted"
command used in the Master script is supposed to make the
disk bootable ?  The Golden Client's autoinstallscript.conf
seems to look OK:
   <disk dev="/dev/hda" label_type="msdos" unit_of_measurement="MB">
     <!--
       This disk's output was brought to you by the partition tool "sfdisk",
       and by the numbers 4 and 5 and the letter Q.
     -->
     <part  num="1"  size="6000"  p_type="primary"  p_name="-"
flags="boot" />
     <part  num="2"  size="2048"  p_type="primary"  p_name="-"  flags="-" />
     <part  num="3"  size="2047"  p_type="primary"  p_name="-"  flags="-" />
     <part  num="4"  size="*"  p_type="extended"  p_name="-"  flags="-" />
     <part  num="5"  size="*"  p_type="logical"  p_name="-"  flags="-" />
   </disk>


We have a similar setup with an older SystemImager 3.3
and RHEL 3.0 server / Fedora Core 2 clients which works
beautifully.  The Master script on this older version
seems to be virtually identical to the Master script
generated by Systemimager 3.4.1, and the FC2 clients
are indeed able to boot from the cloned disks.

QUESTION: Can anyone help making our disks bootable
while using SystemImager ?

FYI, we're using the Systemimager 3.4.1 RPM packages from
http://sourceforge.net/projects/systemimager/ on a
Redhat RHEL 4.0 server and clients (actually, the client
is currently running the Centos RHEL 4.0 clone).  The
kernel version on both is 2.6.9-5.0.5.ELsmp.

Ole Holm Nielsen
Department of Physics, Technical University of Denmark


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to