Bugs item #1274899, was opened at 2005-08-28 02:45 Message generated for change (Settings changed) made by righiandr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1274899&group_id=259
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: systemimager-server Group: v3.2.0 >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Problems with Grub/udev when Imaging Ubuntu Clients Initial Comment: I recently took delivery of three identical P3 machines to be used as client workstations in student accommodation belonging to my college. I am interested in saving time and keeping the images up to date by deployed cloned images using systemimager (www.systemimager.org), but have had a few problems using this method. First I prepared the golden client, ran the prepare client utility, and pulled the image via getimage onto the image server (my own personal ubuntu machine). All of these steps went perfectly. I made an auto install diskette using mkautoinstalldiskette and added a tweaked \local.cfg to this. My DHCP server is not on the same machine as the image server and I needed to set this in the local.cfg file. I then took this diskette and booted the first client node to be imaged with the cd and downloaded the image onto this machine. All the files seemed to copy across perfectly well. 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! Thanks, Paul S. ---------------------------------------------------------------------- Comment By: Erich Focht (efocht) Date: 2005-08-29 11:07 Message: Logged In: YES user_id=338721 Hi Paul, this should be fixed in the current unstable release (3.5.3). Please give that a try. Regards, Erich ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100259&aid=1274899&group_id=259 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
