Stas Oskin wrote: > ---------- Forwarded message ---------- > From: Stas Oskin <[EMAIL PROTECTED]> > Date: 28/04/2008 20:03 > Subject: Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read > superblock CentOS5 and Perc5i > To: [EMAIL PROTECTED] > > > Hi. > > I managed to solve the issue.
Stas, thanks for testing and posting these info. Comments below. > > The whole point was that I actually made an image from a machine > created from image as well. Meaning, I took a post-deployed machine, > made several changes to it, and created a new image from scratch. > > One of the changes it did, was creating the file hardware.lst in the > /var/lib/systemimager/images/IMAGE/etc/systemconfig directory. > > The file contained the following entries: > > 1166 024a scsi sata_svw > 1166 0214 scsi pata_serverworks > 1166 0223 serial ohci-hcd > > One of them was the problematic module. Removing the file allowed the > mkinitrd regeneration to complete. In SystemImager 4.1.x the hardware.lst is always re-generated at end of imaging, so this problem should be already fixed in recent versions (i.e. 4.1.6). > After this case, I have the following issue: > > 1) Is it ok to make an image from imaged server? Yes. > 2) What was the removed file, and was it required in any way? It's used by systemconfigurator to know which modules must be included in the initrd and to create opportune kernel module aliases (see man systemconfigurator). > 3) Is there any way to make the CONFIGRD = YES to work (instead of > hard-coding the kernel version in each post-install script)? You must not hard-code kernel version in post-install script. CONFIGRD=YES must work, if not this means you've found a bug in systemconfigurator, but to fix it we need the full systemconfigurator output as I've requested in a previous email. Otherwise it's too diffucult to understand where systemconfigurator failed. For this I would suggest to enable monitoring (see http://wiki.systemimager.org/index.php/Monitoring) and copy & paste virtual console output. > 4) There is 2 additional files in > /var/lib/systemimager/images/IMAGE/etc/systemconfig directory, > systemconfig.conf.save and systemconfig.conf. The > systemconfig.conf.save has the previous image name DEFAULT/BOOT and > LABEL, but the systemconfig.conf has systemimager for these labels. It > seems to work normally, but could it cause any issues? No, it shouldn't cause any issue. -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
