On Sun, 28 Aug 2005, Paul Syred wrote:
Hi All,
[cut]
Upon completion and trying to restart and boot the new image from the hard
disk, I discovered that the grub bootloader was seemingly not present. In
order to try to fix this, I booted with a Knoppix CD, mounted the filesystem
as read/write, then chrooted into the captive filesystem on /mnt/hda1 and
tried to do a grub-install on /dev/hda (the single hard disk).
This seemed to work, and rebooting from the hard disk brought up a grub menu
etc. When the ubuntu image started to load I got a kernel panic and some
messages like;
init: failed to find /dev/null: no such file
init: failed to open /dev/console
I had a look around on the systemimager mailing list archives and it looks
like this is a problem with Ubuntu as this uses udev and seems to require
some extra configuration of the auto install scripts. I am using systemimager
3.2.3-3 for the client and server portions.
I eventually got the client image to boot by adding 'devfs=mount' to the
kernel line in /boot/grub/menu.lst at boot time and then editing this in
permanently once the machine had booted.
Has anyone else had similar problems using Systemimager? - I'm sure there's a
better way of doing this than manually booting each client node using Knoppix
and installing grub properly. Perhaps I'm being really stupid, and have
missed out some configuration steps, and so please let me know how you
yourselves have got this working!
I have ran into the same problem you have described. I believe what's
happening is that when ubuntu (or debian) is first installed on a machine,
it puts down a real /dev directory and devices in there, and when that
machine boots, it uses that /dev/console, /dev/null to start, but then it
soon runs udev and so /dev is now under the control of udev.
When systemimager is used to get the client image, it detects that /dev is
not on a real file system so nothing gets rsynced from /dev, so
during the install, nothing gets put into /dev. I found that both grub
and lilo have problem with this while trying to install the boot loader
in systemconfigurator.
What I did to solve this problem is just to populate /dev in the image
area and this seems to solve all the problems I had with grub/lilo.
Since this is just a quick and dirty hack, I'm sure there is a more
correct way of doing this.
James
-------------------------------------------------------
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
