Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Stas Oskin wrote: > Hi. > > Well, I think I encountered one of these "unexpected issues". > > On the machine I'm currently installing, the script fails with the > following error: > > No module pata_serverworks found for kernel 2.6.18-53.1.14.el5, aborting. > > The used command is: > mkinitrd /boot/initrd-2.6.18-53.1.14.el5.img 2.6.18-53.1.14.el5 > > Any idea what can be done here? Did you run mkinitrd in a post-install script or is it part of the output of systemconfigurator? in the first case use CONFIGRD = YES instead, in the second case post the full output of systemconfigurator. -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 sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Stas Oskin wrote: > By the way, where this line (CONFIGRD = YES) can be added? There are > two sections in the systemconfig.conf, [BOOT] and [KERNEL0] On top of the file, for example: $ cat /var/lib/systemimager/images/IMAGE/etc/systemconfig/systemconfig.conf CONFIGRD = YES [BOOT] ROOTDEV = /dev/hda2 BOOTDEV = /dev/hda DEFAULTBOOT = systemimager [KERNEL0] LABEL = systemimager PATH = /boot/vmlinuz-2.6.22.17-0.1-default INITRD = /boot/initrd-2.6.22.17-0.1-default APPEND = ro vga=0x332 resume=/dev/hda1 splash=silent showopts -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 sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
By the way, where this line (CONFIGRD = YES) can be added? There are two sections in the systemconfig.conf, [BOOT] and [KERNEL0] Thanks. 2008/4/18, Stas Oskin <[EMAIL PROTECTED]>: > Hi. > > Well, I think I encountered one of these "unexpected issues". > > On the machine I'm currently installing, the script fails with the > following error: > > No module pata_serverworks found for kernel 2.6.18-53.1.14.el5, aborting. > > The used command is: > mkinitrd /boot/initrd-2.6.18-53.1.14.el5.img 2.6.18-53.1.14.el5 > > Any idea what can be done here? > > Thanks. > > > > > > This could be easily automated simply adding "CONFIGRD = YES" in > > /etc/systemconfig/systemconfig.conf in the image. Now this is not the > > default and I would like to do more testing with the new > > systemconfigurator version (currently the trunk release) before enabling > > it. Anyway, would it be safe enough? actually, are we able to handle of > > the different "mkinitrd" present in all the distributions with > > systemconfigurator? I think enabling this would probably raise a lot of > > unexpected bugs. > > > > -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 sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Hi. Well, I think I encountered one of these "unexpected issues". On the machine I'm currently installing, the script fails with the following error: No module pata_serverworks found for kernel 2.6.18-53.1.14.el5, aborting. The used command is: mkinitrd /boot/initrd-2.6.18-53.1.14.el5.img 2.6.18-53.1.14.el5 Any idea what can be done here? Thanks. > > This could be easily automated simply adding "CONFIGRD = YES" in > /etc/systemconfig/systemconfig.conf in the image. Now this is not the > default and I would like to do more testing with the new > systemconfigurator version (currently the trunk release) before enabling > it. Anyway, would it be safe enough? actually, are we able to handle of > the different "mkinitrd" present in all the distributions with > systemconfigurator? I think enabling this would probably raise a lot of > unexpected bugs. > > -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 sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Stas Oskin wrote: > By the way, perhaps this initrd regeneration should be automated in > any way? This would make sysimager truly universal out of box. > This could be easily automated simply adding "CONFIGRD = YES" in /etc/systemconfig/systemconfig.conf in the image. Now this is not the default and I would like to do more testing with the new systemconfigurator version (currently the trunk release) before enabling it. Anyway, would it be safe enough? actually, are we able to handle of the different "mkinitrd" present in all the distributions with systemconfigurator? I think enabling this would probably raise a lot of unexpected bugs. -Andrea - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
By the way, perhaps this initrd regeneration should be automated in any way? This would make sysimager truly universal out of box. Regards. 2008/3/29, Stas Oskin <[EMAIL PROTECTED]>: > Hi. > > I wanted to say that the exact same advice helped me too (used Asus > image for Tyan server). > > Thanks, > Stas. > > 2008/2/25, Shariq Minhas <[EMAIL PROTECTED]>: > > > That did the trick! > > > > > > -Original Message- > > From: Shariq Minhas > > Sent: Sunday, February 24, 2008 3:38 PM > > To: [EMAIL PROTECTED] > > Cc: sisuite-users > > Subject: RE: [sisuite-users] Kernel Panic EXT3-fs: unable to read > superblock CentOS5 and Perc5i > > > > Thanks. I'll try this out and let everyone know how it worked. > > > > > > From: Andrea Righi [EMAIL PROTECTED] > > Sent: Sunday, February 24, 2008 2:50 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: > > > 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. > > > > If you need to image clients with different hardware it's correct to not > > use --my-modules, this is only to save some space when you have identical > > clients. > > > > > > > > I'm curious, do the contents of the /dev directory from the golden > client also get copied over to the client being imaged? > > > > > > > It depends, look at the devstyle in autoinstallscript.conf. If > > devstyle="udev" (as it should be with centos5), then the /dev files are > > not copied, since the opportune device files will be created dynamically > > at run-time by udev. Static /dev is only for old kernels / old distro > > that doesn't use udev. > > > > BTW, to fix your problem try to define a post-install script like the > > following (see /var/lib/systemimager/scripts/post-install/README for > > details): > > > > --- > > #!/bin/sh > > rm -f /boot/initrd-2.6.18-8.el5.img > > mkinitrd /boot/initrd-2.6.18-8.el5.img 2.6.18-8.el5 > > --- > > > > Be sure to use the same kernel version you've in your image. > > > > This will simply re-create the initrd at the end of the imaging, and it > > should include all the needed modules, also the module to properly > > recognize the disk. Actually, this should work with totally > > heterogeneous clients. > > > > -Andrea > > > > - > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > > ___ > > sisuite-users mailing list > > sisuite-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Hi. I wanted to say that the exact same advice helped me too (used Asus image for Tyan server). Thanks, Stas. 2008/2/25, Shariq Minhas <[EMAIL PROTECTED]>: > That did the trick! > > > -Original Message- > From: Shariq Minhas > Sent: Sunday, February 24, 2008 3:38 PM > To: [EMAIL PROTECTED] > Cc: sisuite-users > Subject: RE: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock > CentOS5 and Perc5i > > Thanks. I'll try this out and let everyone know how it worked. > > > From: Andrea Righi [EMAIL PROTECTED] > Sent: Sunday, February 24, 2008 2:50 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: > > 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. > > If you need to image clients with different hardware it's correct to not > use --my-modules, this is only to save some space when you have identical > clients. > > > > > I'm curious, do the contents of the /dev directory from the golden client > also get copied over to the client being imaged? > > > > It depends, look at the devstyle in autoinstallscript.conf. If > devstyle="udev" (as it should be with centos5), then the /dev files are > not copied, since the opportune device files will be created dynamically > at run-time by udev. Static /dev is only for old kernels / old distro > that doesn't use udev. > > BTW, to fix your problem try to define a post-install script like the > following (see /var/lib/systemimager/scripts/post-install/README for > details): > > --- > #!/bin/sh > rm -f /boot/initrd-2.6.18-8.el5.img > mkinitrd /boot/initrd-2.6.18-8.el5.img 2.6.18-8.el5 > --- > > Be sure to use the same kernel version you've in your image. > > This will simply re-create the initrd at the end of the imaging, and it > should include all the needed modules, also the module to properly > recognize the disk. Actually, this should work with totally > heterogeneous clients. > > -Andrea > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > sisuite-users mailing list > sisuite-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sisuite-users > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
That did the trick! -Original Message- From: Shariq Minhas Sent: Sunday, February 24, 2008 3:38 PM To: [EMAIL PROTECTED] Cc: sisuite-users Subject: RE: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i Thanks. I'll try this out and let everyone know how it worked. From: Andrea Righi [EMAIL PROTECTED] Sent: Sunday, February 24, 2008 2:50 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: > 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. If you need to image clients with different hardware it's correct to not use --my-modules, this is only to save some space when you have identical clients. > > I'm curious, do the contents of the /dev directory from the golden client > also get copied over to the client being imaged? > It depends, look at the devstyle in autoinstallscript.conf. If devstyle="udev" (as it should be with centos5), then the /dev files are not copied, since the opportune device files will be created dynamically at run-time by udev. Static /dev is only for old kernels / old distro that doesn't use udev. BTW, to fix your problem try to define a post-install script like the following (see /var/lib/systemimager/scripts/post-install/README for details): --- #!/bin/sh rm -f /boot/initrd-2.6.18-8.el5.img mkinitrd /boot/initrd-2.6.18-8.el5.img 2.6.18-8.el5 --- Be sure to use the same kernel version you've in your image. This will simply re-create the initrd at the end of the imaging, and it should include all the needed modules, also the module to properly recognize the disk. Actually, this should work with totally heterogeneous clients. -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Thanks. I'll try this out and let everyone know how it worked. From: Andrea Righi [EMAIL PROTECTED] Sent: Sunday, February 24, 2008 2:50 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: > 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. If you need to image clients with different hardware it's correct to not use --my-modules, this is only to save some space when you have identical clients. > > I'm curious, do the contents of the /dev directory from the golden client > also get copied over to the client being imaged? > It depends, look at the devstyle in autoinstallscript.conf. If devstyle="udev" (as it should be with centos5), then the /dev files are not copied, since the opportune device files will be created dynamically at run-time by udev. Static /dev is only for old kernels / old distro that doesn't use udev. BTW, to fix your problem try to define a post-install script like the following (see /var/lib/systemimager/scripts/post-install/README for details): --- #!/bin/sh rm -f /boot/initrd-2.6.18-8.el5.img mkinitrd /boot/initrd-2.6.18-8.el5.img 2.6.18-8.el5 --- Be sure to use the same kernel version you've in your image. This will simply re-create the initrd at the end of the imaging, and it should include all the needed modules, also the module to properly recognize the disk. Actually, this should work with totally heterogeneous clients. -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Shariq Minhas wrote: > 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. If you need to image clients with different hardware it's correct to not use --my-modules, this is only to save some space when you have identical clients. > > I'm curious, do the contents of the /dev directory from the golden client > also get copied over to the client being imaged? > It depends, look at the devstyle in autoinstallscript.conf. If devstyle="udev" (as it should be with centos5), then the /dev files are not copied, since the opportune device files will be created dynamically at run-time by udev. Static /dev is only for old kernels / old distro that doesn't use udev. BTW, to fix your problem try to define a post-install script like the following (see /var/lib/systemimager/scripts/post-install/README for details): --- #!/bin/sh rm -f /boot/initrd-2.6.18-8.el5.img mkinitrd /boot/initrd-2.6.18-8.el5.img 2.6.18-8.el5 --- Be sure to use the same kernel version you've in your image. This will simply re-create the initrd at the end of the imaging, and it should include all the needed modules, also the module to properly recognize the disk. Actually, this should work with totally heterogeneous clients. -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
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/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
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/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
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//etc/systemimager/autoinstallscript.conf and /var/lib/systemimager/images//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/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
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//etc/systemimager/autoinstallscript.conf and /var/lib/systemimager/images//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 > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
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. -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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Kernel Panic EXT3-fs: unable to read superblock CentOS5 and Perc5i
Shariq Minhas wrote: > Hello, > > I'm trying to image an new (no OS installed) Dell PowerEdge SC1435 > server with a CentOS5 UYOK image. The server has the Perc5i controller > with two mirrored 80GB SATA drives. The imaging keeps failing with the > following error: > > EXT3-fs: unable to read superblock > > and then the kernel goes into panic mode. I've built the client image > with UYOK and CentOS 5 installs fine from scratch on a similar server. > > Any ideas on what can be done to overcome this? > > Thanks in advance. > Probably your UYOK initrd.img has been created using an ext3 filesystem and your kernel doesn't support it. Anyway, if you didn't explicitly force it then this is a bug. It seems a bit strange because I'm not able to reproduce the problem, with CentOS 5 my UYOK initrd.img is correctly created using cpio. Could you try to force the use of cpio instead of ext3? just re-run si_prepareclient with the option "--filesystem cpio". -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
