This is a resend from Friday Sept 16th with some of the history deleted - the msg was over the 40 KB limit
and was not posted.
Seth,
- Yes on the std boot pkg for 3.4.1 cciss does not load.
- By editing linux.i386.config as given below and rebuilding it
does work successfully. By doing this I also reduced the overall size
(turned off some hw I don't have) of the boot image soe it easily
fits on a floppy using si_mkautoinstalldiskette.
- suggest changing si_mkautoinstalldiskette and /etc/init.d/rcS to
default to the larger /dev/fd0u1680 so the default boot image fits in 3.4.1
- Yes a "modprobe cciss" also works on the std image.
- 3.4.1 uses linux-2.4.25 which has cciss 2.4.50
I latest 2.4 kernel driver I have is 2.4.54.RH1(from RH ES 3). I might try dropping this
in to see if it cahnges anything. The version with Systemimager 3.5.2 is v2.6.2 and yes
it has significantly changed.
- I gave up on grub long ago and use Lilo which works without a hitch(okay up2date
pukes on a kernel update even though lilo is updated sucessfully).
- One question I have is :
Does the new 3.5.x systemimager work correctly with 2.4.x kernel machines ?
Thanks
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]
| Seth Haines <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 2005/09/16 07:06
|
To: sisuite-users@lists.sourceforge.net cc: Subject: Re: [Sisuite-users] Smart Array 6i cciss not loading |
David,
I finally got a chance to play around with your issue a little bit.
System Imager 3.4.1
HP DL380 G4 with 6i
RHEL3 Update 4 ES install
Sure enough the cciss driver does not load!
I modified the computername.master script to include a single line:
modprobe cciss
Before the partitioning information and that seems to have resolved the drive detection and formatting issues.
Now back to the usual grub issues.
Did your modification to the discovery scripts solve this issue without the necessity of a modprobe?
Also apparently the cciss driver was significantly changed between 3.4.1 and 3.5.1 as the /dev/cciss/ device configuration in the 3.4.1 works with /disc0/disc as opposed to 3.5.1 /host0/target0/disc. I'd much prefer the use of 3.4.1driver in 3.5.1 binaries since in 3.5.1 it at least picks up properly.
Thanks,
Seth
On 9/13/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Thanks Seth,
See other post and yes I am connected to a Cisco switch - all my current installations also take numerous pings before
connectivity.
Also from your first post I am currently running psp-7.20(haven't yet upgraded to 7.3) which as you
mentions replaces tg3 with bcm5700. This becomes a real pain because :
- if you use redhat network to keep your servers up2date then anytime you change the kernel(or kudzu
is run afterward) you have to re-install the support pack/reconfigure your network. I have tried to get Redhat to
incorporate the HP enhancements( push them from rhn) to no avail. I even have a ticket opened with RH where
they claim the bcm5700 driver is to blame and want me to test with the tg3 .... Ok rant over.
| Seth Haines <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 2005/09/12 18:21 Please respond to sisuite-users |
To: sisuite-users@lists.sourceforge.net cc: Subject: Re: [Sisuite-users] Smart Array 6i cciss not loading |
|
David,
With your pings timing out... Are you running a Cisco switch by chance? If so, port fast is probably keeping the port from coming up in time for the ping to succeed. Something to check.
As to your mount issue. When you said that you checked the /dev/cciss directory what did you see listed under the disc0 section? Was there only a /dev/cciss/disc0/disc? Or were there also part1 part2 and part3 block devices? Just curious, because there should be. I assume with only 3 parts you're just running a /boot, swap, and / configuration correct?
This morning I was able to successfully clone a RHEL4 system with 3.5.1 using a fairly modified version of the image.master file (manually creating the block devices and commenting out some of the finish sections) Surprisingly enough grub-install never really completed properly but upon boot everything came up magically. I'm taking this as a saving grace and running with it. Tomorrow I'll be testing out a RHEL4 Update 1 system to see if it has any changes.
Thanks,
Seth
On 9/12/05, [EMAIL PROTECTED] < [EMAIL PROTECTED] > wrote:
Seth/Peter/Anyone !
Unfortunately as you will note from muy first post I'm attempting to load RH EL 3 not 4 on
the DL380 G4 so this will not solve my problem.
I ran into problems when building 3.5.2 on RHEL3 and also when attempting to run si_prepareclient.
I also have a installed base running off of 3.0.0 so I would like as little to change as possible.
So back to trying to get 3.4.1 working on the DL380G4 ...
I have attempted to force recognition of the driver by
modifying the ./patches/linux.i386.config file such that
CONFIG_BLK_CPQ_DA=y
CONFIG_BLK_CPQ_CISS_DA=y
I then remade all the packages(ie rpmbuild -ba /usr/src/redhat/SPECS/systemimager.spec).
I then loaded the resultant boot pkg and made a bootable cd :
- booting from the cd I eventually get the # prompt after the broadcast's fail(remmeber I normally
use a local.cfg from floppy).
- at this point /dev/cciss/disc0/disc ... exists however a parted still results in a No such device ...
- I then attempted to boot again using the same cd but this time also included a floppy with a
local.cfg on it(I had noted fromt he previous boot that the floppy is still referenced for local.cfg)
- This time the local.cfg is read and the ping test is attempted to the image server.
- the ping tests fails but on the subsequent rsync the script is received.
- the script starts to runs and partially works :
- old partition table via parted is displayed
- new partitions are created(1-3 in my case)
- mke2fs -f /dev/cciss/disc0/part3 || shellout works
- tune2fs -L /dev/cciss/disc0/part3 works
- mkdir -p /a/ || shellout works
- mount /dev/cciss/disc0/part3 /a/ -t ext3 -o defaults || shellout FAILS
--> I get "failed: No such device"
- When I am in the shell after the failure I can manually run parted/mkde2fs/tune2fs successfully
but the mount will always fail with "No such device"
Ideas ????
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]
----- Forwarded by David Livingstone/LIVING03/CNR/CA on 2005/09/12 15:18 -----
|
| Seth Haines <[EMAIL PROTECTED] >
Sent by: [EMAIL PROTECTED] 2005/09/08 12:15 Please respond to sisuite-users |
To: sisuite-users@lists.sourceforge.net cc: Subject: Re: [Sisuite-users] Smart Array 6i cciss not loading |
Some more info on this now:
System Imager 3.5.1 uses the 2.6.10_boel_v3.5.2 Kernel. When it talks
to the cciss device boel refers to the /dev as
/dev/cciss/host0/target0/disc, where as the autoinstall script refers
to the cciss device as /dev/cciss/disc0/disc, so no wonder I'm getting
the error on boot saying that No such file or directory exists because
the boel initrd cciss driver creates the wrong /dev structure!
Also potentially of interest is the fact that the RedHat Enterprise
Linux 4.0 cciss driver is around 250 kb give or take 10 kb, where as
the boel is barely pushing 30 kb, something tells me that some
features are going to be missing. The sad part is I've seen system
imager work with a RHEL4 installation, but it was version 3.2.X, you
just had to manually perform a grub-install off the recovery CD once
the image had been put in place. Not exactly perfect.
Here's the current thoughts:
1) I'm wondering whether or not it would be possible to get the make
files for the boel kernel and build a new cciss driver based on the
larger .c file that can be had from the RedHat installation (I'm
thinking no, but it's a hope) I mean there has to be some way to get
the /dev directory to populate with /dev/cciss/c0d0pX the way it
should in order to match the volume labels and grub maps.
2) Editing the autoinstall script to switch all references from
/dev/cciss/disc0/disc to /dev/cciss/host0/target0/disc. A find and
replace may work, but then I'll probably be confronted with grub
issues in the end. This however is an imperfect solution as changing
an autoinstall script after every getimage would be a real pain!
3) Find another product... Ha. Doesn't HP have some Rapid Deployment
package of some kind? Or is that just extremely similar to RedHat's
kickstart?
Thanks,
Seth
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
