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
|
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
On 9/8/05, Seth Haines <[EMAIL PROTECTED]> wrote:
> David,
>
> Where does the imaging process bomb? Is it when parted starts trying
> to create the partitions and format them?
>
> I'm running into the same problem with some DL380 G4's (RHEL4 Install).
>
> Partitioning /dev/cciss/disc0/disc...
> Old partition tabe for /dev/cciss/disc0/disc
> Error: Could not stat device /dev/cciss/disc0/disc. No such file or directory.
> parted -s -- /dev/cciss/disc0/disc........
> Error: Could not stat device /dev/cciss/disc0/disc. No such file or directory.
>
> I remember seeing some traffic back in mid July from Mark Seger (HP
> SystemImager Guru) but I never really saw the outcome of the
> discussion. I'm starting to go through the archives now to see if
> there is anything I can find.
>
> Incidentally you should consider installing the HP Proliant Support
> Pack 7.3, which replaces the tg3 nic card driver (that has potential
> to drop packets under heavy load) with the broadcom bcm5700.
>
> Thanks,
>
> Seth
>
> On 9/6/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > I curently run Systemimager 3.0.0 on numerous HP Proliant DL380 G3's
> > witthout a problem. They
> > use e1000 nic driver and cciss(Smart Array 5i) diriver when booting from
> > floppy. I have loaded
> > RH EL 3 with the latest updated.
> >
> > I recently acquired newer DL380 G4 servers(Smart Array 6i and tg3 nics) and
> > I ran into numerous problems :
> >
> > 1. The 3.0.0 standard boot floppy does not recognize the Smart Array 6i and
> > therefore no disks
> > are available.
> > 2. The nics are not recognized.
> >
> > I have tried the following :
> >
> > 1. Using Systemimager 3.4.1
> > - After much effort(another story) I finally generated a boot floppy
> > from the std boot pkg however
> > once again the Smart Array 6i(cciss) was not recognized.
> >
> > 2. Downloaded Ole Holm Nielsen's 3.5.2 rpm's(generate for RH 4.0 and posted
> > to this list) and
> > generated a bootable cd(no chance of floppy on this one:). Still no luck
> > with with the
> > cciss driver not loaded. The nic's however are recognized.
> >
> > So the immediate question is what do I have to do to get the Smart Array 6i
> > recognized ?
> > - I have subsequently loaded the machine via RH cd's(RH 3 upadte 5) and the
> > array is
> > working fine. Looked at the cciss code on RH 3 and the kernel source both
> > cciss.c v 2.4.52.RH2 and the latest
> > v2.4.54.RH all have the 6i updates.
> >
> > Other Questions :
> > - I currently use local.cfg on my floppy boots : Can I use local.cfg on a
> > bootable cd and if so how ?
> > - Making a bootable floppy with 3.4.1 was a headace :
> > - the si_mkautoinstalldiskette would exit with zero space on the
> > floppy. No mention is made in the manual on this.
> > I tried :
> > 1. As per the suggestion in si_mkautoinstalldiskette(ie vi the code)
> > I attemted to use /dev/fd0u1680
> > - This worked for "si_mkautoinstalldiskette --floppy
> > /dev/fd0u1680" however on subsequent
> > boot the rc script which attempts to load local.cfg does so
> > using /dev/fd0 and it fails.
> > - si_mkautoinstalldiskette -out-file ddimage will also fail as
> > it hardcodes to 1.44 MB and fails.
> > 2. Took all the comments out of lcoal.cfg and syslinux.cfg and
> > removed message.txt altogether. This
> > then just fit on fd0.
> >
> > 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]
> >
> >
>
-------------------------------------------------------
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
