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 !
The client (ML370) is running RH3 AS with kernel 2.4.21-20.EL.
The server is a HP Proliant DL380G4 running the latest RH ES 4.
Both have systemimager 3.9.6 loaded.
I was testing by imaging and then loading the client.
Here is entry from the pxelinux.cfg directory on the
server - I used --flavor when creating. The boot messages
for the client were scrolling off the screen however it did
boot using the below specified kernel/initrd. Also one
of the first lines said "PXE 2.11 2004-08-16"
LABEL systemimager
KERNEL /i386/nlstest2_2007/kernel
APPEND initrd=/i386/nlstest2_2007/initrd.img root=/dev/ram
ramdisk_blocksize=1024 ramdisk_size=80000 HOSTNAME=nlstest2
IMAGENAME=nlstest2_2007
Here is the output of the "si_prepareclient --server 192.168.81.35
--exclude /dev/cciss/c0d2"
Using "sfdisk" to gather information about disk:
/dev/cciss/c0d0
Using "sfdisk" to gather information about disk:
/dev/cciss/c0d1
>>> Copying modules to new initrd from: /lib/modules/2.4.21-20.EL...
skipping directory /lib/modules/2.4.21-20.EL/kernel
skipping non-regular file "lib/modules/2.4.21-20.EL/build"
>>> Appending insmod commands to ./my_modules_dir/INSMOD_COMMANDS...
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/scsi/scsi_mod.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/scsi/sd_mod.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/block/cciss.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/fs/jbd/jbd.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/fs/ext3/ext3.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/usb/usbcore.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/usb/host/usb-ohci.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/input/input.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/usb/hid.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/input/mousedev.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/input/keybdev.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/arch/i386/kernel/microcode.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/scsi/sg.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/block/floppy.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/net/e1000/e1000.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/net/e100/e100.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/net/8021q/8021q.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/fs/autofs4/autofs4.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/net/sunrpc/sunrpc.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/fs/lockd/lockd.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/fs/nfsd/nfsd.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/char/softdog.o
>> insmod /lib/modules/2.4.21-20.EL/kernel/drivers/sound/soundcore.o
>>> Choosing filesystem for new initrd: ext2
>>> Creating new initrd from staging dir: /tmp/.systemimager.0
>>> New initrd mount point: /tmp/.systemimager.1
>> dd if=/dev/zero of=/etc/systemimager/boot/initrd bs=1024 count=30292
30292+0 records in
30292+0 records out
>> mke2fs -b 1024 -m 0 -N 752 -F /etc/systemimager/boot/initrd
mke2fs 1.32 (09-Nov-2002)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
768 inodes, 30292 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
4 block groups
8192 blocks per group, 8192 fragments per group
192 inodes per group
Superblock backups stored on blocks:
8193, 24577
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
>> tune2fs -i 0 /etc/systemimager/boot/initrd
tune2fs 1.32 (09-Nov-2002)
Setting interval between check 0 seconds
>> mount /etc/systemimager/boot/initrd /tmp/.systemimager.1 -o loop -t
ext2
>> tar -C /tmp/.systemimager.0 -cf - . | tar -C /tmp/.systemimager.1 -xf -
>> umount /tmp/.systemimager.1
>> gzip -f -9 -S .img /etc/systemimager/boot/initrd
>> ls -l /etc/systemimager/boot/initrd.img
-rw-r--r-- 1 root root 10734119 Sep 13 13:49
/etc/systemimager/boot/initrd.img
>> rm -fr /tmp/.systemimager.1
>> Evaluating initrd size to be added in the kernel boot options
>> (e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
>> suggested value -> ramdisk_size=40532
>>> Using kernel from: /boot/vmlinuz-2.4.21-20.EL
>> ls -l /etc/systemimager/boot/kernel
-rw-r--r-- 1 root root 1243768 Sep 13 13:49
/etc/systemimager/boot/kernel
Starting or re-starting rsync as a daemon.....
done!
This client is ready to have its image retrieved. You must now run
the "si_getimage" command on your imageserver.
Your client has been successfully prepared. Boot kernel (copied from
this Linux distribution) and an initrd.img (generated by the
initrd_template package) can be found in /etc/systemimager/boot.
Automatically create configuration file for systemconfigurator:
>> /etc/systemconfig/systemconfig.conf
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]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
