Iban,
In the boot ramdisk (initrd.img) there is a top level directory
named "my_moudules". By copying the ata_piix and libata modules into
that directory and then adding the insmod commands to load them into the
file named "INSMOD_COMMANDS found in that same my_mouldes directory. The
file has examples from which to emulate. The embedded init script "rcS"
has a directive to read this file and directory and load the modules
found there before rsyncing the client script and starting the client
imaging process.
The default boot kernel and initrd "should" be finding and loading
these modules without doing any customization. Since it is not working
you may have to get a little "hacky", at least to discover the cause of
the problem or prove that the existing modules do work when manually
loaded. Since the drive is not found the process should shellout and
drop you into an interactive shell. This should occur at a point after
the boel_binaries tar archive has been copied down and extracted. Try
looking in /lib/modules/2.4.25_boel_v3.4.1/kernel/drivers/scsi and see
if the libata.o and ata_piix.o modules are present. If so, manually load
them (libata first I believe) using insmod. You said scsi_mod nad sd_mod
are already loaded so if ata modules are present and will load then you
should see you scsi drive at that point. If so then you just have to get
the module to load during boot when is what I describe in the
"my_moudles" process.
The initrd.img is a compressed (gzip) cramfs image. Getting changes
into is a bit tricky. You could download the systemimager source and
build you own kernel and initrd from that and add the changes you need.
Or you could extract the existing cramfs to a new directory, add in the
bits you need, remake it into a new cramfs image, compress it and
replace your existing initrd.img.
Like I said, a bit "hacky" but it works. Its not worth going through
that effort unless you can verify that the moudles exist and function
correctly when manually loaded. Your problem could be elsewhere.
--Jeff
Ibán Cabrillo wrote:
hello Jeff,
i'm using 2.4.25_boel_v3.4.1 and in the bios the Hdd's appears
correctly. It are two SATA drives, a havae the same machine installed
with fedora C4 ( the golden client ) and this are them lsmod :
Module Size Used by
openafs 556992 2
iptable_filter 6849 0
ip_tables 24897 1 iptable_filter
nfs 197641 1
lockd 63721 2 nfs
parport_pc 31621 1
lp 16585 0
parport 39049 2 parport_pc,lp
autofs4 22725 2
i2c_dev 13377 0
i2c_core 25409 1 i2c_dev
rfcomm 46041 0
l2cap 33857 5 rfcomm
bluetooth 56645 4 rfcomm,l2cap
sunrpc 139781 3 nfs,lockd
dm_mod 59749 0
video 19909 0
button 10577 0
battery 13381 0
ac 8773 0
md5 8001 1
ipv6 265857 16
uhci_hcd 35409 0
ehci_hcd 38093 0
shpchp 96965 0
tg3 94149 0
ext3 133193 5
jbd 61785 1 ext3
ata_piix 13253 6
libata 49220 1 ata_piix
sd_mod 22977 8
scsi_mod 136457 2 libata,sd_mod
after this i think that i need ata_piix and libata because sd_mod and
scsi_mod are load correctly.
then you say that i've to drop them in my initrd "/my_modules", can
you explain me this ?? soory, i don´t understood you.
Thanks.
Jeff Johnson escribió:
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
