Hi Jeff,

I have just installed the systemimager-3.6.3 on IBM-HS20 blade server, running RH4/U2 and when trying to restore the created image, I am experiencing exactly the same. 
You description was really helpful but you have not covered the situation if  boel_binaries tar ball does not include the modules. 
Can you assist me please to get those modules or to create one if necessary? 
My image server is exactly the same machine as the client I am willing to restore.  Is it possible to copy the modules from my /usr/lib directory to "/my_modules" and also update the boel tar ball?  

I appreciate your kind assistance. Thank you.

[EMAIL PROTECTED] standard]# find /lib -name mptbase.*
/lib/modules/2.6.9-22.EL/kernel/drivers/message/fusion/mptbase.ko
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/message/fusion/mptbase.ko
[EMAIL PROTECTED] standard]# find /lib -name mpt*
/lib/modules/2.6.9-22.EL/kernel/drivers/message/fusion/mptscsih.ko
/lib/modules/2.6.9-22.EL/kernel/drivers/message/fusion/mptctl.ko
/lib/modules/2.6.9-22.EL/kernel/drivers/message/fusion/mptbase.ko
/lib/modules/2.6.9-22.EL/kernel/drivers/message/fusion/mptlan.ko
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/message/fusion/mptscsih.ko
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/message/fusion/mptctl.ko
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/message/fusion/mptbase.ko
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/message/fusion/mptlan.ko
[EMAIL PROTECTED] standard]# find /lib -name scsi_mod*
/lib/modules/2.6.9-22.EL/kernel/drivers/scsi/scsi_mod.ko
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/scsi/scsi_mod.ko
[EMAIL PROTECTED] standard]# find /lib -name sd_mod*
/lib/modules/2.6.9-22.EL/kernel/drivers/scsi/sd_mod.ko
/lib/modules/2.6.9-22.ELsmp/kernel/drivers/scsi/sd_mod.ko
[EMAIL PROTECTED] standard]#
[EMAIL PROTECTED] standard]# tar ztvf boel_binaries.tar.gz |grep mptbase
[EMAIL PROTECTED] standard]#
[EMAIL PROTECTED] standard]# lsmod
Module                  Size  Used by
radeon                125957  2
parport_pc             27905  0
lp                     15405  0
parport                37641  2 parport_pc,lp
autofs4                22085  0
i2c_dev                14273  0
i2c_core               25921  1 i2c_dev
sunrpc                139173  1
md5                     8001  1
ipv6                  240097  20
dm_mirror              28449  0
dm_mod                 58949  1 dm_mirror
button                 10449  0
battery                12869  0
ac                      8773  0
joydev                 14209  0
uhci_hcd               32729  0
hw_random               9557  0
tg3                    85061  0
ext3                  118729  8
jbd                    59481  1 ext3
mptscsih               41469  0
mptbase                57629  1 mptscsih
sd_mod                 20545  10
scsi_mod              116429  2 mptscsih,sd_mod
[EMAIL PROTECTED] standard]#


Regards
Babak Karvandi



Jeff Johnson wrote:
Iban,

    I'm guessing your scsi modules have not loaded. Watch your boot 
process to see if the scsi hba ever registers and posts the devices 
attached. If it doesn't show up then you need to have the driver module 
for it. There are different ways to accomplish this depending on the 
version of systemimager, kernel major release (2.4 vs 2.6) and of 
course 
the brand and model of scsi hba you are using.

    Basic question. Does the scsi drive (sda) appear at bios post time 
as being present? That is the nice way of asking if the drive is 
plugged 
in. I am sure you have checked that but it is worth asking just in 
case.

    The Adaptec scsi hbas are pretty straightforward. The aic7xxx 
driver 
for the older  ultra160 cards based on the aic78xx/77xx chips. The 
aic79xx for the ultra320 based on aic7902/aic79xx. These drivers are 
the 
same in both 2.4 and 2.6 kernels. The LSI Logic scsi hbas can be a 
little tricky since their drivers are not among the other scsi modules. 
They exist in the drivers/message/fusion directory and are named 
mptbase 
and mptscsih. They are paired and must both be loaded (mptbase first).

    If the drivers exist in your boel_binaries tar ball and are not 
being loaded you might have to drop them into your initrd "/my_moudles" 
directory and driect them to be loaded with the INSMOD_COMMANDS script 
in that directory. If you do this be sure the load order is correct:

1. scsi_mod
2. sd_mod
3. scsi hba driver modules

Using the LSI as an example you would want the scsi_mod.o (or .ko is 
using 2.6), sd_mod.o (.ko), mptbase.o (.ko) and mptscsih.o (.ko) in the 
/my_modules directory and then edit INSMOD_COMMANDS to read:

insmod scsi_mod.o
insmod sd_mod.o
insmod mptbase.o
insmod mptscsih.o

**change .o to .ko in all examples if you systemimager boot kernel is 
2.6 based.

I hope that helps...

--Jeff


Ibán Cabrillo wrote:
> hello,
>     I try to install, a few pc's by PXE. The tftp, dhcp and pxe 
daemon 
> work fine, but when the init script of systemimager try to 
patitioning 
> the disk appears the next error:
>
> >>/script/myscritp.sh
> get_arch
> Partitioning /dev/sda
> Old Patition table for /dev/sda
> Error : could not stat device /dev/sda
> parted -s -- /dev/sda mklabel msdos
> killing all running procces
>
> I've used systemimager 3.4.1-1 and Peter Mueller kernel on a Fedora 
> because the original kernel from systemimager didn't support my 
> network card.
> Any idea about this Problem??
> Thanks
>

-- 
Best Regards,

Jeff Johnson
Vice President
Engineering/Technology
Western Scientific, Inc
[EMAIL PROTECTED]
http://www.wsm.com

9445 Farnham Street - San Diego, CA 92123
Tel 800.443.6699  +001.858.565.6699
Fax +001.858.565.6938

"Abra Capocus" - Bugs Bunny



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting 
language
that extends applications into web and mobile media. Attend the live 
webcast
and join the prime developer group breaking into this new coding 
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to