[Sisuite-users] System Imager 3.5.1 RHEL4 Question
I've been working with Ole Holm Nielsen RHEL4 write up (excellent work!) but have hit a bit of a snag. In system imager 3.4.X there was the option to mkautoinstalldiskette which seems to have disappeared in 3.5.1. Since we only image about 30 nodes simultaneously here having floppy control over which nodes are imaged versus which aren't has been a nice feature that I've grown accustomed too. PXE boot gets difficult as the 30 nodes that are imaged change bi monthly resulting in new sets of mac addresses, etc. etc. Am I just missing a new executable that has replaced the mkautoinstalldiskette or has that feature been removed from 3.5.1? Thanks, Seth Haines BIT Systems Systems Engineer --- 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
RE: [Sisuite-users] systemimager via pxe
Title: [Sisuite-users] systemimager via pxe webmail, sorry for my format. Because I found it so useful (and hard to find!) I am mirroring the NIFLHEIM paper on how to get PXE working with systemimager. I tried to put the link in WIKI but I am very unfamiliar with it, so maybe it is not easy to get to. Here is the link: http://world.anarchy.com/~peter/systemimager/2002.09.18_NIFLHEIM_Cluster_Uses_SystemImager.pdf Regards, P From: [EMAIL PROTECTED] on behalf of jonathanSent: Mon 9/5/2005 7:34 AMTo: sisuite-users@lists.sourceforge.netSubject: [Sisuite-users] systemimager via pxe Hi,i am trying to get something working using systemimager, but I don't ifI can make this with this software.Well, I want to configure a machine as an image serveur with manyclients images stored on it. The clients update the remote image dailyor weekly. If a client crash, we just have to reboot the machine, bootvia the pxe, receive an IP from the Image/DHCP server, and download thelast remote image (selecting the good one) via tfpft or something else,and finally boot normaly with local kernel and datas.From now, i have installed systemimager server and client, create aremote image, and I have just succeed to boot correctly via pxe, butusing the remote kernel from the image.The getimage script has correctly made my client image on the server,generating a /var/lib/systemimager/scripts/GX150.master script. Isupposed this script may be used to restore the image on the client butI don't if I'm right, and how to do this.Most help I have found on the official systemimager website, and alsofrom many others websites, are showing documentation for booting from adiskette, CD or a lilo bootloader. But almost nothing describing how toget systemimager working from a pxe boot.thanks a lot for helping me.johnPs: sorry for my poor english...---SF.Net email is Sponsored by the Better Software Conference EXPOSeptember 19-22, 2005 * San Francisco, CA * Development Lifecycle PracticesAgile Plan-Driven Development * Managing Projects Teams * Testing QASecurity * Process Improvement Measurement * http://www.sqe.com/bsce5sf___Sisuite-users mailing listSisuite-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/sisuite-users
RE: [Sisuite-users] System Imager 3.5.1 RHEL4 Question
Title: [Sisuite-users] System Imager 3.5.1 RHEL4 Question Webmail.. I believe the problem is the default kernel modules grew too big for diskette... can anyone else confirm? Regards, P From: [EMAIL PROTECTED] on behalf of Seth HainesSent: Thu 9/8/2005 8:41 AMTo: sisuite-users@lists.sourceforge.netSubject: [Sisuite-users] System Imager 3.5.1 RHEL4 Question I've been working with Ole Holm Nielsen RHEL4 write up (excellentwork!) but have hit a bit of a snag. In system imager 3.4.X there wasthe option to "mkautoinstalldiskette" which seems to have disappearedin 3.5.1. Since we only image about 30 nodes simultaneously herehaving floppy control over which nodes are imaged versus which aren'thas been a nice feature that I've grown accustomed too. PXE boot getsdifficult as the 30 nodes that are imaged change bi monthly resultingin new sets of mac addresses, etc. etc. Am I just missing a newexecutable that has replaced the mkautoinstalldiskette or has thatfeature been removed from 3.5.1?Thanks,Seth HainesBIT SystemsSystems Engineer---SF.Net email is Sponsored by the Better Software Conference EXPOSeptember 19-22, 2005 * San Francisco, CA * Development Lifecycle PracticesAgile Plan-Driven Development * Managing Projects Teams * Testing QASecurity * Process Improvement Measurement * http://www.sqe.com/bsce5sf___Sisuite-users mailing listSisuite-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/sisuite-users
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
Re: [Sisuite-users] Smart Array 6i cciss not loading
Thanks for the reply Seth ... I was beginning to think there was no one on the list. The floppy/cd boots correctly and bombs exactly as you show below. - from the shell at that point a lsmod does not show cciss loaded. - /dev/cciss... does not exist. - I would attempt to load ccisss.o if I could find it - I presume it's in the initrd ? There was an item on May 2, 2005 Subject [Sisuite-users] Re: cciss disk problem DL360 where Steve Grandinetti responded : The device support for the SmartArray device wasn't loaded, either via the loadable module, or via static support in your kernel. By default, typically, the SmartArray support is via loadable module. There is a 'discover' task that runs as part of the BOEL env. startup, that identifies which h/w is present and loads the appropriate modules. If indeed your SmartArray support is dynamically loaded, it's possible that the 'discover' utility didn't identify the SmartArray devices. If you continue to have trouble in this area, you can statically build in the support by modifying the ./patches/linux.i386.config file, changing the following two config variables from CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m to CONFIG_BLK_CPQ_DA=y CONFIG_BLK_CPQ_CISS_DA=y And rebuild the kernel. - The real issue is to have the new array detected correctly and the module loaded. In the meantime how does one rebuild the kernel ? 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/08 11:16 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading 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
Re: [Sisuite-users] Smart Array 6i cciss not loading
David, I manually ran a modprobe cciss from the BOEL command line in order to insure than an lsmod would show the cciss module loaded, it seemed to work in my case, resulting in the /dev/cciss/host0/target0/disc directory structure that was I referring to in my pervious mail. In this case the cciss module is contained with /lib/modules/.../kernel/drivers/devices/block/cciss.ko or something along those lines. It's extremely small as previously mentioned. What I've been playing around with is swaping out different kernels and initrd.img files from the pxe boot. Haven't had much luck as most of them halt on boot in a kernel panic because none of the normal file system structure is there. What we need is the ability to recompile the BOEL kernel with an up to date cciss driver, or figure out some what to recompile a redhat kernel with support for systemimager. Under the /usr/share/systemimager/boot/i386/standard you'll find the boel tar.gz. I've just now exploded it on a working RedHat box and started playing around with its contents. This tar.gz gets called during the pxe boot process and produces the file system that you see when the shell out occurs during an error. Since I'll be pxe booting, or CD booting, the size of the kernel/initrd.img doesn't matter to me one bit, so going with another kernel that will interact with systemimager may be the better of the two solutions above. To rebuild the boel kernel we need the source, and I currently do not know where to obtain it, and neither does google at this point. Maybe it's in the systemimager cvs repository and I just haven't looked hard enough yet. I'll let you know what I find. Thanks, Seth On 9/8/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Thanks for the reply Seth ... I was beginning to think there was no one on the list. The floppy/cd boots correctly and bombs exactly as you show below. - from the shell at that point a lsmod does not show cciss loaded. - /dev/cciss... does not exist. - I would attempt to load ccisss.o if I could find it - I presume it's in the initrd ? There was an item on May 2, 2005 Subject [Sisuite-users] Re: cciss disk problem DL360 where Steve Grandinetti responded : The device support for the SmartArray device wasn't loaded, either viathe loadable module, or via static support in your kernel. By default,typically, the SmartArray support is via loadable module. There is a 'discover' task that runs as part of the BOEL env. startup, thatidentifies which h/w is present and loads the appropriate modules. Ifindeed your SmartArray support is dynamically loaded, it's possible that the 'discover' utility didn't identify the SmartArray devices.If you continue to have trouble in this area, you can statically buildin the support by modifying the ./patches/linux.i386.config file, changing the following two config variables fromCONFIG_BLK_CPQ_DA=mCONFIG_BLK_CPQ_CISS_DA=mto CONFIG_BLK_CPQ_DA=yCONFIG_BLK_CPQ_CISS_DA=yAnd rebuild the kernel.- The real issue is to have the new array detected correctly and the module loaded. In the meantime how does one rebuild the kernel ? Thanks David K LivingstoneCN Signals and Communications10229 127 Avenue floor 2Edmonton, AB, T5E 0B9Ph : 780 472-3959 Fax : 780 472-3050Email: [EMAIL PROTECTED] Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 11:16 Please respond to sisuite-users To: sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading David,Where does the imaging process bomb? Is it when parted starts tryingto 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/discError: 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 (HPSystemImager Guru) but I never really saw the outcome of thediscussion. 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 SupportPack 7.3, which replaces the tg3 nic card driver (that has potentialto drop packets under heavy load) with the broadcom bcm5700. Thanks,SethOn 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
Re: [Sisuite-users] Smart Array 6i cciss not loading
David, In playing around with the boel tar.gz file there is an interesting file under /usr/share once extracted. Perhaps this was the discovery that Steve was referring to. Performing a search on the pci.1st file shows that the Compaq 6i controller is listed as unknown unknown. I'm curious as to what would happen if changed to block cciss and then re-tarred, but I currently do not have a good understanding of how the boel .tar.gz is even being called in the first place. Maybe someone will a little more system imager experience will post this evening and shed some light on things! Thanks, Seth On 9/8/05, Seth Haines [EMAIL PROTECTED] wrote: David, I manually ran a modprobe cciss from the BOEL command line in order to insure than an lsmod would show the cciss module loaded, it seemed to work in my case, resulting in the /dev/cciss/host0/target0/disc directory structure that was I referring to in my pervious mail. In this case the cciss module is contained with /lib/modules/.../kernel/drivers/devices/block/cciss.ko or something along those lines. It's extremely small as previously mentioned. What I've been playing around with is swaping out different kernels and initrd.img files from the pxe boot. Haven't had much luck as most of them halt on boot in a kernel panic because none of the normal file system structure is there. What we need is the ability to recompile the BOEL kernel with an up to date cciss driver, or figure out some what to recompile a redhat kernel with support for systemimager. Under the /usr/share/systemimager/boot/i386/standard you'll find the boel tar.gz. I've just now exploded it on a working RedHat box and started playing around with its contents. This tar.gz gets called during the pxe boot process and produces the file system that you see when the shell out occurs during an error. Since I'll be pxe booting, or CD booting, the size of the kernel/initrd.img doesn't matter to me one bit, so going with another kernel that will interact with systemimager may be the better of the two solutions above. To rebuild the boel kernel we need the source, and I currently do not know where to obtain it, and neither does google at this point. Maybe it's in the systemimager cvs repository and I just haven't looked hard enough yet. I'll let you know what I find. Thanks, Seth On 9/8/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Thanks for the reply Seth ... I was beginning to think there was no one on the list. The floppy/cd boots correctly and bombs exactly as you show below. - from the shell at that point a lsmod does not show cciss loaded. - /dev/cciss... does not exist. - I would attempt to load ccisss.o if I could find it - I presume it's in the initrd ? There was an item on May 2, 2005 Subject [Sisuite-users] Re: cciss disk problem DL360 where Steve Grandinetti responded : The device support for the SmartArray device wasn't loaded, either viathe loadable module, or via static support in your kernel. By default,typically, the SmartArray support is via loadable module. There is a 'discover' task that runs as part of the BOEL env. startup, thatidentifies which h/w is present and loads the appropriate modules. Ifindeed your SmartArray support is dynamically loaded, it's possible that the 'discover' utility didn't identify the SmartArray devices.If you continue to have trouble in this area, you can statically buildin the support by modifying the ./patches/linux.i386.config file, changing the following two config variables fromCONFIG_BLK_CPQ_DA=mCONFIG_BLK_CPQ_CISS_DA=mto CONFIG_BLK_CPQ_DA=yCONFIG_BLK_CPQ_CISS_DA=yAnd rebuild the kernel.- The real issue is to have the new array detected correctly and the module loaded. In the meantime how does one rebuild the kernel ? Thanks David K Livingstone CN Signals and Communications10229 127 Avenue floor 2Edmonton, AB, T5E 0B9Ph : 780 472-3959 Fax : 780 472-3050Email: [EMAIL PROTECTED] Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 11:16 Please respond to sisuite-users To: sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading David,Where does the imaging process bomb? Is it when parted starts tryingto 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/discError: 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 thediscussion. 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
RE: [Sisuite-users] Smart Array 6i cciss not loading
Does my 2.4 'SI-3.4.1' kernel work with SI-3.5.1 and RHEL4? http://world.anarchy.com/~peter/systemimager/kernel I expect it to have a40% chance of actually working. For your development question, I can answer that. http://wiki.sisuite.org/ leads to - Developer Access The Subversion server is now up and running: http://svn.sisuite.org If you would like to request developer access, send your public ssh key (one with a passphrase, of course) in a gpg encrypted or signed email to dannf_at_dannf.org or [EMAIL PROTECTED]. Once your key is in place, you can perform checkouts like so: Development trunk: svn checkout svn+ssh://[EMAIL PROTECTED]/var/lib/svn/systemimager/trunk/ systemimager/ Regards, P From: [EMAIL PROTECTED] on behalf of Seth HainesSent: Thu 9/8/2005 12:31 PMTo: sisuite-users@lists.sourceforge.netSubject: Re: [Sisuite-users] Smart Array 6i cciss not loading David, I manually ran a "modprobe cciss" from the BOEL command line in order to insure than an lsmod would show the cciss module loaded, it seemed to work in my case, resulting in the /dev/cciss/host0/target0/disc directory structure that was I referring to in my pervious mail. In this case the cciss module is contained with /lib/modules/.../kernel/drivers/devices/block/cciss.ko or something along those lines. It's extremely small as previously mentioned. What I've been playing around with is swaping out different kernels and initrd.img files from the pxe boot. Haven't had much luck as most of them halt on boot in a kernel panic because none of the normal file system structure is there. What we need is the ability to recompile the BOEL kernel with an up to date cciss driver, or figure out some what to recompile a redhat kernel with support for systemimager. Under the /usr/share/systemimager/boot/i386/standard you'll find the boel tar.gz. I've just now exploded it on a working RedHat box and started playing around with its contents. This tar.gz gets called during the pxe boot process and produces the file system that you see when the shell out occurs during an error. Since I'll be pxe booting, or CD booting, the size of the kernel/initrd.img doesn't matter to me one bit, so going with another kernel that will interact with systemimager may be the better of the two solutions above. To rebuild the boel kernel we need the source, and I currently do not know where to obtain it, and neither does google at this point. Maybe it's in the systemimager cvs repository and I just haven't looked hard enough yet. I'll let you know what I find. Thanks, Seth On 9/8/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Thanks for the reply Seth ... I was beginning to think there was no one on the list. The floppy/cd boots correctly and bombs exactly as you show below. - from the shell at that point a lsmod does not show cciss loaded. - /dev/cciss... does not exist. - I would attempt to load ccisss.o if I could find it - I presume it's in the initrd ? There was an item on May 2, 2005 Subject [Sisuite-users] Re: cciss disk problem DL360 where Steve Grandinetti responded : The device support for the SmartArray device wasn't loaded, either viathe loadable module, or via static support in your kernel. By default,typically, the SmartArray support is via loadable module. There is a 'discover' task that runs as part of the BOEL env. startup, thatidentifies which h/w is present and loads the appropriate modules. Ifindeed your SmartArray support is dynamically loaded, it's possible thatthe 'discover' utility didn't identify the SmartArray devices.If you continue to have trouble in this area, you can statically buildin the support by modifying the ./patches/linux.i386.config file, changing the following two config variables fromCONFIG_BLK_CPQ_DA=mCONFIG_BLK_CPQ_CISS_DA=mtoCONFIG_BLK_CPQ_DA=yCONFIG_BLK_CPQ_CISS_DA=yAnd rebuild the kernel.- The real issue is to have the new array detected correctly and the module loaded. In the meantime how does one "rebuild the kernel" ? Thanks David K LivingstoneCN Signals and Communications10229 127 Avenue floor 2Edmonton, AB, T5E 0B9Ph : 780 472-3959 Fax : 780 472-3050Email: [EMAIL PROTECTED] Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 11:16 Please respond to sisuite-users To: sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading David,Where does the imaging process bomb? Is it when parted starts tryingto 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 --
