I am not sure whether I should have a new thread on this, and I put it here anyway since my error message is almost exactly the same as Jan Groenewald
After rsyncing: Probing devices to guess BIOS drives. This may take a long time. df: warning can't read table of mounted filesystems. 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. After reboot, the grub is installed fine, but DHCP is not configure as systemconfigurator specified, imaged computer is using static IP of the golden client. Golden Client: linux 2.6.11-gentoo-r3, systemconfigurator 2.0.9, systemimager 3.4.1. Imager Server: fc4, systemimager 3.4.1. Initially I have the /boot not found failed since I have /boot in it's own partition, I was able to get it working after change the / /boot order in the master script after reading this list. Thanks a lot. On Sun, 2005-08-14 at 20:27 -0700, [EMAIL PROTECTED] wrote: > Send Sisuite-users mailing list submissions to > sisuite-users@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/sisuite-users > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Sisuite-users digest..." > > > Today's Topics: > > 1. Re: systemconfigurator --runboot fails (chroot does not see /dev/hda) > (Jan Groenewald) > > --__--__-- > > Message: 1 > Date: Sun, 14 Aug 2005 16:23:56 +0200 > To: sisuite-users@lists.sourceforge.net > Subject: Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does > not see /dev/hda) > From: [EMAIL PROTECTED] (Jan Groenewald) > Reply-To: sisuite-users@lists.sourceforge.net > > Hi > > On Sat, Aug 13, 2005 at 02:32:11PM -0700, Bernard Li wrote: > > Does Ubuntu use udev? If so, you can try the following: > Yes, it does. It is on a 2.6 kernel. > > > Edit your image's /etc/systemimager/autoinstallscript.conf, i.e. > > ..<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 > I'll go and try it tomorrow, and get back to you. > > > What version of SystemConfigurator are you using? > ii systemconfigur 2.0.10-1 Unified Configuration API for Linux > (on the client, in which chroot it is running, right) > > I updated systemimager to 3.4 (from the systemimager website, which is > newer than the ubuntu systemimager-* 3.2.3-3 packages. This broke the > booting on the clients, which now didn't see the hda at all to partition > it (missing ide-scsi? I solved that years ago and didn't feel like doing > the mkbootpackage thing all over, I've forgotten how -- I pulled my > boot kernel back from a backup, and reverted to 3.2.3 -- I don't think > that is the problem anyway?). > > > 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). > I've noticed device.map on the golden image: > /dev/hda (hd0) > buthe images, once installed, have only: > /dev/fd0 (fd0) > > grub.conf? Or menu.1st? > [EMAIL PROTECTED]:/etc # locate grub.conf (my golden image; yes, using grub) > /usr/share/kernel-package/kpkg_grub.conf > > > 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?) > I don't think it was an MBR, after looking up grub error 15. It was > rather the device.map file. Is this another udev thing? I can now, > by editing device.map (and I can set up the master script to copy this > into place after the rsync) get a little further: Now grub sees the kernel, > starts to boot, and then: > > (grub sees kernel and initrd.img) > boot > Uncompressing Linux, ok booting the kernel... > audit(123412345124.2341324 something like that) initializing > Starting Ubuntu... > /sbin/init: 426: cannot create /dev/null : Read-only file system > /sbin/init: 427: cannot open dev/console : no such file > Kernel panic: not syncing. Attempted to kill init! > > One rather garbled thread here tells me to edit the grub boot line. > (strange, these should be fine). Also something about devfs=mount in > grub.conf there, so I'll look at that. > http://kerneltrap.org/node/4870 > > I haven't gone further yet, but will report back tomorrow later > (I'm on South African time). > > cheers, > Jan > -- > .~. > /V\ Jan Groenewald > /( )\ www.aims.ac.za > ^^-^^ > > > > --__--__-- > > _______________________________________________ > Sisuite-users mailing list > Sisuite-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > > End of Sisuite-users Digest -- ------------------------------------------------------- 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
