Re: [sisuite-users] FATAL : Kernel too old

2007-09-17 Thread David . Livingstone
Andrea,

Thanks for the reply.

 I used the standard image and this was successful.

 All our machines are HP Proliant DL/ML servers with Smart Array
 controllers(ie /dev/cciss). We currently have a mix of RHEL3/4 with
 the RHEL3 machines using the 2.4 kernel.

 





[EMAIL PROTECTED] wrote:

 Andrea,

  Thanks for the reply.

  What options do I have ?

 - Try and boot using the standard(included) kernel ?

For this you should try to install the systemimager-boot-standard-3.9.6 in 
your
image server before, to have more chances for your hw to be properly 
recognized.

After the install remember to update your kernel+initrd.img in your 
/tftpboot
and restart the systemimager-bittorrent daemons (only if you're using the 
BT
transport).

A problem you can find with this approach is that in recent kernels the 
IDE disk
naming schema has changed and all these devices are now mapped in /dev/sd* 
(look
for hda - sda transition problem in google for details). So, if you're 
using an
old kernel (actually 2.4 is old in any case), one or more IDE disks and 
you're
not using UUIDs or LABELs in your autoinstallscript.conf probably you can 
find
some problems during the first reboot.

 - Try an boot using a uyok from a similar machine using a 2.6 kernel.
 Will this
work ?

Yes, this is another valid solution, to try with a different boot package 
made
with a 2.6 kernel. The hda - sda problem is still valid.

 - 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.

This would be the cleanest solution, but one of the 2 solutions above is 
surely
quicker.


 Wouldn't virtulization allow you to build both glibc versions on the
 same platform ?


Yes, but since the build server is my laptop: 1) I don't have enough disk 
space
free 2) probably the building process would require an entire night... :-)

-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


Re: [sisuite-users] FATAL : Kernel too old

2007-09-14 Thread Andrea Righi
[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

2007-09-14 Thread Andrea Righi
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] FATAL : Kernel too old

2007-09-14 Thread David . Livingstone
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