It is different hardware and I though that might be the issue since the client to be issued is a newer Dell server. However, I did not use the --my-modules option when creating the golden client image and when I try to use the same CentOS5 kernel to image the client from scratch, it works fine.
I'm curious, do the contents of the /dev directory from the golden client also get copied over to the client being imaged? ________________________________________ From: Andrea Righi [EMAIL PROTECTED] Sent: Sunday, February 24, 2008 2:18 PM 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'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 Everything seems ok here. Actually I'm using a very similar configuration for my CentOS5 image (with root over a LVM logical volume). Do you have a different hardware in your golden client respect to the clients you're trying to image? A possible problem could be that the initrd in the centos5 image doesn't have the module to recognize the disk device. -Andrea ------------------------------------------------------------------------- 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
