Re: [sisuite-users] FATAL : Kernel too old
[EMAIL PROTECTED] wrote: I just attempted to PXE boot a HP Proliant ML370 G2 with systemimager 3.9.6 and received the following kernel panic : Freeing unused kernel memory : 164k freed FATAL: Kernel too old Kernel panic : Attempting to kill init ! That's because the glibc into the initrd.img are build using the linux-2.6 headers (our build machine is a Ubuntu 7.04 host), that means your 2.4 kernel is not compatible. See also: http://www.busybox.net/lists/busybox/2005-January/013500.html To resolve you should build systemimager from source using your 2.4 machine, in order to have a compatible version of glibc in your initrd.img. For us this is a very difficult issue to resolve: first of all we should find 2 build machines for each arch (one with 2.4 kernel and another with a 2.6 kernel), and then we should build 2 different versions for each arch of the packages systemimager-initrd_template and systemimager-boot-standard... -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] FATAL : Kernel too old
Andrea Righi wrote: [EMAIL PROTECTED] wrote: I just attempted to PXE boot a HP Proliant ML370 G2 with systemimager 3.9.6 and received the following kernel panic : Freeing unused kernel memory : 164k freed FATAL: Kernel too old Kernel panic : Attempting to kill init ! That's because the glibc into the initrd.img are build using the linux-2.6 headers (our build machine is a Ubuntu 7.04 host), that means your 2.4 kernel is not compatible. See also: http://www.busybox.net/lists/busybox/2005-January/013500.html To resolve you should build systemimager from source using your 2.4 machine, in order to have a compatible version of glibc in your initrd.img. For us this is a very difficult issue to resolve: first of all we should find 2 build machines for each arch (one with 2.4 kernel and another with a 2.6 kernel), and then we should build 2 different versions for each arch of the packages systemimager-initrd_template and systemimager-boot-standard... Added a comment in the troubleshooting guide: http://wiki.systemimager.org/index.php/Troubleshooting#FATAL:_Kernel_too_old For now this is the best we can do... -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] 3.8.2 for ia64
Roger Chevalier wrote: Thanks for the reply Andrea. Works better with the ramdisk_size parameter, but the generic kernel/initrd it did not recognize the scsi card (sym53c8xx module) I did not invetigate why currently (may be you can tell me where to look at?) So I use UYOK, and it works ! I managed to restore a debian etch with LVM2 build on a software RAID1. (3.8.2 si version) I will try a few more configuration. I don't know if someone is interested in the rpm build on ia64 (mostly the boot packages) ? I currently have access to a ia64 server, I will try also to build the 3.9.6, I let you know any feedback. Very good! waiting your feedback... Thanks, -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] FATAL : Kernel too old
Andrea, Thanks for the reply. What options do I have ? - Try and boot using the standard(included) kernel ? - Try an boot using a uyok from a similar machine using a 2.6 kernel. Will this work ? - Build from source on the 2.4 machine. This looks like the cleanest solution. I have downloaded the 3.9.6 tar source however I'm not sure how to build the rpm's. I have looked at the online docs rpmbuild -ta tarball however after looking at the Makefile I see a rpm target which does a rpmbuild -tb. Also my machines are behind a firewall and can only connect to the internet via a proxy. Wouldn't virtulization allow you to build both glibc versions on the same platform ? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Andrea Righi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2007/09/14 02:31 Please respond to [EMAIL PROTECTED]; Please respond to sisuite-users@lists.sourceforge.net To [EMAIL PROTECTED] cc sisuite-users@lists.sourceforge.net Subject Re: [sisuite-users] FATAL : Kernel too old Andrea Righi wrote: [EMAIL PROTECTED] wrote: I just attempted to PXE boot a HP Proliant ML370 G2 with systemimager 3.9.6 and received the following kernel panic : Freeing unused kernel memory : 164k freed FATAL: Kernel too old Kernel panic : Attempting to kill init ! That's because the glibc into the initrd.img are build using the linux-2.6 headers (our build machine is a Ubuntu 7.04 host), that means your 2.4 kernel is not compatible. See also: http://www.busybox.net/lists/busybox/2005-January/013500.html To resolve you should build systemimager from source using your 2.4 machine, in order to have a compatible version of glibc in your initrd.img. For us this is a very difficult issue to resolve: first of all we should find 2 build machines for each arch (one with 2.4 kernel and another with a 2.6 kernel), and then we should build 2 different versions for each arch of the packages systemimager-initrd_template and systemimager-boot-standard... Added a comment in the troubleshooting guide: http://wiki.systemimager.org/index.php/Troubleshooting#FATAL:_Kernel_too_old For now this is the best we can do... -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
[sisuite-users] systemconfigurator and bogus sc-initrd
I am trying to install some nodes using an image captured from a pre-existing system and during the install systemconfigurator keeps creating an initrd file called sc-initrd-2.6.9-55.ELsmp.gz and this does not work out because the correct modules do not get included in this initrd and the resulting system does not boot. I have an initrd file that does work but everytime I edit the grub.conf or menu.lst files in the image, it seems like systemconfigurator overwrites the grub.conf file to reference this bogus sc-initrd-2.6.9-55.ELsmp.gz file instead. How do I get one of two things to happen: 1. how to get systemconfigurator to STOP rewriting my grub.conf file or 2. how to get systemconfigurator to create a CORRECT initrd file containing the appropriate modules needed for this platform? I am in the process of creating a hardware.lst file but the documentation that talks about that file does not mention how to get systemconfigurator to include modules for things like lvm. Any assistance, information, pointers to docs or other suggestions are most welcome. -- Steven DuChene - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] systemconfigurator and bogus sc-initrd
Thanks for the suggestion Ted. I was able to look through the sample.cfg file that is provided with systemconfigurator and get an idea of how to override the creation and use of the sc-initrd thing. -Original Message- From: Ted Arden [EMAIL PROTECTED] Sent: Sep 14, 2007 10:07 AM To: Steven A. DuChene [EMAIL PROTECTED] Subject: Re: [sisuite-users] systemconfigurator and bogus sc-initrd d00de.. just write a post-install script that copies over a known good working grub.conf file as the last thing to do after imaging?? i have had to do a coupla work arounds with sysimager in the past.. some post processing. if you have the vanilla grub.conf file, you may as well just put that into the image via post-process? =ted= On Fri, 14 Sep 2007, Steven A. DuChene wrote: I am trying to install some nodes using an image captured from a pre-existing system and during the install systemconfigurator keeps creating an initrd file called sc-initrd-2.6.9-55.ELsmp.gz and this does not work out because the correct modules do not get included in this initrd and the resulting system does not boot. I have an initrd file that does work but everytime I edit the grub.conf or menu.lst files in the image, it seems like systemconfigurator overwrites the grub.conf file to reference this bogus sc-initrd-2.6.9-55.ELsmp.gz file instead. How do I get one of two things to happen: 1. how to get systemconfigurator to STOP rewriting my grub.conf file or 2. how to get systemconfigurator to create a CORRECT initrd file containing the appropriate modules needed for this platform? I am in the process of creating a hardware.lst file but the documentation that talks about that file does not mention how to get systemconfigurator to include modules for things like lvm. Any assistance, information, pointers to docs or other suggestions are most welcome. -- Steven DuChene - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
