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
^^-^^
-------------------------------------------------------
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
