I'm using SystemImager 4.0.2-1 and SystemConfigurator 2.2.11-1. The following files are attached: /var/lib/systemimager/images/centos5/etc/systemimager/autoinstallscript.conf and /var/lib/systemimager/images/centos5/etc/systemconfig/systemconfig.conf /var/lib/systemimager/scripts/centos5.master
-----Original Message----- From: Andrea Righi [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 2:47 AM To: Shariq Minhas Cc: sisuite-users Subject: Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i Shariq Minhas wrote: > I tried again and this time it recognizes the hard drive but cannot mount the > root filesystem (which is on a logical volume group). The error states that > VolGroup00 cannot be found. > > When installing the client image, I did see output from system imager stating > that VolGroup00 had been created successfully. The grub menu also shows up > fine. OK, so boot-loader is working fine. Which version of systemimager / systemconfigurator are you using? Could you post your /var/lib/systemimager/images/<YOUR_IMAGE>/etc/systemimager/autoinstallscript.conf and /var/lib/systemimager/images/<YOUR_IMAGE>/etc/systemconfig/systemconfig.conf? -Andrea > > > > -----Original Message----- > From: Andrea Righi [mailto:[EMAIL PROTECTED] > Sent: Saturday, February 23, 2008 3:16 AM > To: Shariq Minhas > Cc: sisuite-users > Subject: Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock > CentOS5 and Perc5i > > Shariq Minhas wrote: >> Hi Andrea, >> >> I tried again and managed to get past the error this time. The trick was to >> specify all the kernel boot parameters in a local.cfg file when running >> si_prepareclient. > > That actually means ignoring the ramdisk_blocksize and ramdisk_size > parameters and fallback to the defaults. Interesting... I'll add a > comment in the troubleshooting guide. > >> Now I have a different problem in that the imaging apparently finishes >> cleanly and asks for a reboot. However, on rebooting it cannot read the >> hard disk anymore and kernel panic occurs again. > > Probably your boot-loader was not correctly installed. > > Which versions of SystemImager / System Configurator are you using? Which > distribution are you trying to image? Which versions of grub/lilo/... do > you have in your image? > > -Andrea >
systemconfig.conf
Description: systemconfig.conf
centos5.master
Description: centos5.master
autoinstallscript.conf
Description: autoinstallscript.conf
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
