Hi Bernard. Thanks for your time, and sorry I haven't replied until
now. I got incredibly busy the last few days before taking a vacation,
and then of course I had to catch up from being away :)
On Jan 15, 2006, at 8:28 PM, Bernard Li wrote:
What OS are you imaging?
This happens to be centos 3.5, but I also image centos 4.2
Are you sure your hardware works with the OS?
Yes! Every system I am trying to image has either already been running
the exact same OS/kernel, or we have identical servers that do. We run
a vendor provided 2.4 based kernel which is mostly monolithic, and so
doesn't use a initrd (uses modules for iptables basically). We are
switching to a 2.6 based one soon, but will need to maintain the 2.4
for a little while.
SystemImager 3.6.3 provides 2 ways to generate a kernel/initrd.img:
1) From the boot-standard package, this is the stock one which
SystemImager builds
Yes, and has worked wonderfully for me on hardware it supports. I
recently upgraded to 3.6.3 and it too works fine on some hardware, but
not this box for example. Whats frustrating about this one is that this
box imaged fine using the older 3.4 systemimager :(. After the upgrade
I can no longer use the old stock 3.4 image (I get errors saying it
can't find the modules it needs). I have also tried Peter Muellers
kernel (which has no initrd).
2) By generating it on the fly using UseYourOwnKernel (triggered by
si_prepareclient), this uses the kernel from /boot (on your OS) and
generate a initrd.img from the template provided in the
initrd_template package
Yes, this would be ideal right? I did this with 3.6.3. First it
wouldn't boot the kernel and I figured out si_prepareclient had
packaged the vmlinux-blah variant of the kernel and not the
vmlinuz-blah one. Then I could boot that kernel but it complained about
the initrd (built with changes to force si_prepareclient to use the
right kernel). Since it usually doesn't use/need an initrd, I tried
with out it and
So you tried both sets of these and both gave you kernel panic? Were
there any other messages besides that message in the topic?
I get the kernel panic with the stock systemimager 3.6.3 boot kernel,
from the rpm or built from a .src.rpm. So At this point I can only
assume it's a bad kernel/driver combo for i20. If you have a newer
kernel I could try, please let me know - I haven't had a lot of luck
building my own.
If I UseMyOwnKernel on a server running the same OS/kernel (but
admittedly this golden client isn't i20 but shouldn't matter as the
driver is nit a module) I get a kernel panic with "No init found". If I
don't use an initrd then I get a panic with
read_super_block: can't find a reiserfs filesystem on (dev 01:00, block
64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 01:00, block
8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 01:00
Can you provide us with the exact model of your SATA hardware and what
modules it is supposed to use? You mentioned that it works in
"production" so I assume you have a Linux distro which works with
that. Find out the module that it loads when running that distro
(well besides i2o, of course)
Well, its compiled into this vendor provided kernel. On an operational
system it reports
# cat /proc/scsi/dpt_i2o/0
Adaptec I2O RAID Driver Version: 2.4 Build 5
Vendor: Adaptec Model: 2015S FW:3B0A
SCSI Host=scsi0 Control Node=/dev/dpti0 irq=26
post fifo size = 255
reply fifo size = 255
sg table size = 56
Devices:
ADAPTEC RAID-10 Rev: 3B0A
TID=533, (Channel=0, Target=0, Lun=0) (online)
The following is the relevant configuration options on i386 for I2O
devices:
linux.i386.config:CONFIG_SCSI_DPT_I2O=m
linux.i386.config:# I2O device support
linux.i386.config:CONFIG_I2O=y
linux.i386.config:# CONFIG_I2O_CONFIG is not set
linux.i386.config:CONFIG_I2O_BLOCK=y
linux.i386.config:CONFIG_I2O_SCSI=m
linux.i386.config:# CONFIG_I2O_PROC is not set
I'm not sure what CONFIG_I2O_CONFIG or CONFIG_12O_PROC does, perhaps
they might help?
If I try compiling my own again, I'll look at this, but don't think
thats my best path here. I think getting the UseYourOwnKernel method to
work would be best.
You are using i386, right?
Yes.
Thanks again for your time.
charles
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
