Thanks Andrea - here is more additional information
Could you post more details about this point? from the busybox prompt
are you able to see the module of your controller loaded (with lsmod)?
Yes
/dev/sda is present?
Yes
do you get errors when parted tries to create the
partitions?
Not user if it gets there or not...
the last msg on the console is:
mke2fs -q -j /dev/sda2 no device at address while trying to determine
filesystem size
Moreover with UYOK have you tried to use --my-modules?
Try default and as suggested with --my-modules... still no sucesss
Could you post also the output of si_prepareclient from
your golden client? the interesting part is just after:
Appending insmod commands to ./my_modules_dir/INSMOD_COMMANDS...
Here it is:
Signaling xinetd to restart...
Using "parted" to gather information about disk:
/dev/sda
Copying modules to new initrd from: /lib/modules/2.4.21-40.EL...
skipping directory /lib/modules/2.4.21-40.EL/kernel
skipping non-regular file "lib/modules/2.4.21-40.EL/build"
Appending insmod commands to ./my_modules_dir/INSMOD_COMMANDS...
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/scsi/scsi_mod.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/scsi/sd_mod.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/block/diskdumplib.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/scsi/megaraid2.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/fs/jbd/jbd.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/fs/ext3/ext3.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/usb/usbcore.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/usb/host/usb-uhci.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/usb/host/ehci-hcd.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/input/input.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/usb/hid.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/input/mousedev.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/input/keybdev.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/arch/x86_64/kernel/microcode.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/scsi/sg.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/block/floppy.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/net/e1000/e1000.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/fs/autofs4/autofs4.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/acpi/button.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/audit/audit.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/char/drm/radeon.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/block/loop.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/cdrom/cdrom.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/drivers/ide/ide-cd.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/net/ipv4/netfilter/ip_tables.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/net/ipv4/netfilter/iptable_filter.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/fs/fat/fat.o
>> insmod /lib/modules/2.4.21-40.EL/kernel/fs/vfat/vfat.o
Choosing filesystem for new initrd: ext2
Creating new initrd from staging dir: /tmp/.systemimager.7
New initrd mount point: /tmp/.systemimager.8
>> dd if=/dev/zero of=/etc/systemimager/boot/initrd bs=1024 count=22516
22516+0 records in
22516+0 records out
>> mke2fs -b 1024 -m 0 -N 360 -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)
360 inodes, 22516 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
3 block groups
8192 blocks per group, 8192 fragments per group
120 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 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.8 -o loop -t ext2
>> tar -C /tmp/.systemimager.7 -cf - . | tar -C /tmp/.systemimager.8 -xf -
>> umount /tmp/.systemimager.8
>> gzip -f -9 -S .img /etc/systemimager/boot/initrd
>> ls -l /etc/systemimager/boot/initrd.img
-rw-r--r-- 1 root root 7829856 Jan 8 20:57
/etc/systemimager/boot/initrd.img
>> rm -fr /tmp/.systemimager.8
Evaluating initrd size to be added in the kernel boot options
(e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
>> suggested value -> ramdisk_size=32756
Using kernel from: /boot/vmlinux-2.4.21-40.EL
>> ls -l /etc/systemimager/boot/kernel
-rw-r--r-- 1 root root 6699408 Jan 8 20:57
/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. If
PXE-booting, you can copy the files to /tftpboot or the specified
location.
...
Regards,
-Andrea
On 1/8/07, Rene Pineda <[EMAIL PROTECTED]> wrote:
Hi all -
I created an Image of a PowerEdge 2850 using systemimager-server-3.7.5-1,
but I can't reinstall it to the same hardware on another box. I browed the
list and some ppl report similar or exact issues and workarounds, but I
haven't had any success yet.
The main issue seems to be the standard boot cd can't detect the scsi
controller. A build your own kernel does not work either.
Here's my configuration:
Hardware: Dell PowerEdge 2850
OS: RedHat EL (Linux RDEVSE07.immport.org 2.4.21-40.EL #1 SMP Thu Feb 2
22:14:00 EST 2006 x86_64 x86_64
SystemImager Server:
x86systemconfigurator-2.2.2-1.noarch.rpm
systemimager-common-3.7.5-1.noarch.rpm
systemimager-i386boot-standard-3.7.5-1.noarch.rpm
systemimager-server-3.7.5-1.noarch.rpm
systemimager-x86_64boot-standard-3.7.5-1.noarch.rpm
_64 GNU/Linux)
SysteImagerServer (compoenets I installled);
SystemImager Client:
systemimager-common-3.7.5-1
systemimager-i386initrd_template-3.7.5-1
systemimager-x86_64initrd_template-3.7.5-1
systemimager-client-3.7.5-1
systemconfigurator-2.2.2-1
Any help please, including detail steps on how to fix this since I'm new
to SystemImager. Thanks.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
