Title: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hey Jan:
 
Does Ubuntu use udev?  If so, you can try the following:
 
Edit your image's /etc/systemimager/autoinstallscript.conf, i.e. /var/lib/systemimager/images/<image>/etc/systemimager/autoinstallscript.conf on your imageserver:
 
- add <boel devstyle="devfs" /> right before </config> (udev =/= devfs, but they are treated similarly here)
- mkautoinstallscript --image <image> --force --post-install reboot
- re-image the node
 
What version of SystemConfigurator are you using?
 
There are a few more things we can try if this doesn't work.  It might help if you can post things like device.map, grub.conf during/after the imaging process (i.e. don't reboot after done, and enter the console).
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] on behalf of Jan Groenewald
Sent: Sat 13/08/2005 06:37
To: sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)

Hi

I am installing an Ubuntu image with systemimager. The network boot
works, the dhcp and everything, the files are copied, but the
grub MBR is not installed.

I booted an Ubuntu live CD, and inside the chroot of the image /dev/hda
is not seen at all.

[EMAIL PROTECTED]:/ # systemconfigurator --runboot
Probing devices to guess BIOS drives. This may take a long time.
Could not find device for /boot: Not found or not a block device.
Probing devices to guess BIOS drives. This may take a long time.
Use of uninitialized value in concatenation (.) or string at /usr/lib/systemconfig/Boot/Grub.pm line 160.
Use of uninitialized value in substitution (s///) at /usr/lib/systemconfig/Boot/Grub.pm line 164.
Use of uninitialized value in concatenation (.) or string at /usr/lib/systemconfig/Boot/Grub.pm line 235.
Use of uninitialized value in concatenation (.) or string at /usr/lib/systemconfig/Boot/Grub.pm line 237.
Probing devices to guess BIOS drives. This may take a long time.

Any ideas?

I can temporarily solve it by saving the MBR on the image, and changing
the master script to dd that MBR back to the disk right after the failed
systemconfigurator --runboot.  But if this is a bug I'd like to file it
(or am I doing something wrong?)

regards,
Jan
--
   .~.
   /V\     Jan Groenewald
  /( )\    www.aims.ac.za
  ^^-^^


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to