Stefan Becuwe wrote: > I've given up on cloning SuSE 9 Pro images. They should be replaced > anyway ;-) I successfully created an image from a "plain" openSuSE 10.2. > The Grub error has disappeared. PXE boot goes fine. At the end it says > > Imaging completed > Terminated > I have been done for 1 seconds. Reboot me already! > > So I reboot... > > [...] > RAMDISK: Compressed image found at block 0 > No filesystem could mount root, tried: minix iso9660 > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > > > When I compare boot.msg from the golden client "plain" openSuSE 10.2 with > the newly installed one, I notice that I don't see the SCSI subsystem > being initialized. Moreover, it indicates it has only tried minix and > iso9660... So it's clear it has to go wrong ... but why? > > >> Could you post the file /etc/systemconfig/systemconfig.conf in your >> image? You can find it in >> /var/lib/systemimager/images/<your_image>/etc/systeconfig/systemconfig.conf >> on your image server. > > [BOOT] > ROOTDEV = /dev/sda2 > BOOTDEV = /dev/sda2 > DEFAULTBOOT = systemimager > > [KERNEL0] > LABEL = systemimager > PATH = /boot/vmlinuz-2.6.18.2-34-default > INITRD = /boot/symsets-2.6.18.2-34-default.tar.gz > APPEND = root=/dev/sda2 console=ttyS0,9600 resume=/dev/sda1 splash=silent >
Stefan, it seems that SystemImager doesn't correctly detect the initrd to be used during the first client reboot. Could you post the output of the following commands (in your golden client)? # file /boot/* # file -z /boot/* Thanks, -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
