From tallpaul at speakeasy.org Tue Feb 1 00:23:00 2005 From: tallpaul at speakeasy.org (Paul English) Date: Mon, 31 Jan 2005 16:23:00 -0800 (PST) Subject: System freeze after VFS:Mount root (ext2 filesystem) Message-ID: Okay - I went through this document: http://www.stanford.edu/~alfw/PXE-Kickstart/ to do a PXE kickstart. Not bad in that right off the bat it managed to boot off the network. But... It successfully boots off the network, then says: VFS:Mount root (ext2 filesystem) and stops. The machine isn't hung, that's just as far as it gets. On the console (alt-F3) it tells me: Alt-f3 gives me: doing kickstart... setting it up reverse name lookup failed (I checked this one out, it seems to be NBD) url is 10.0.1.1:/data/Kickstart/ks-WB30.cfg file location: nfs://10.0.1.1:/data/Kickstart/ks-WB30.cfg And that is it! Nothing more about failing to mount the nfs directory or anything. It gets the kickstart file and then just stops. Hitting enter no longer makes the cursor move down the screen, but the "alt-F" commands work and control-alt-delete works. At this point it looks like it is saying "I know where ks.cfg is, and I'm about to get it" but never does get it. Any help appreciated, Paul From tallpaul at speakeasy.org Tue Feb 1 01:40:05 2005 From: tallpaul at speakeasy.org (Paul English) Date: Mon, 31 Jan 2005 17:40:05 -0800 (PST) Subject: System freeze after VFS:Mount root (ext2 filesystem) In-Reply-To: References: Message-ID: On Mon, 31 Jan 2005, Paul English wrote: > doing kickstart... setting it up > reverse name lookup failed (I checked this one out, it seems to be NBD) > url is 10.0.1.1:/data/Kickstart/ks-WB30.cfg > file location: nfs://10.0.1.1:/data/Kickstart/ks-WB30.cfg > > And that is it! Nothing more about failing to mount the nfs directory or > anything. It gets the kickstart file and then just stops. Hitting enter no > longer makes the cursor move down the screen, but the "alt-F" commands > work and control-alt-delete works. And with some help from a friend, I solved the problem. nfsd was not configured to start on boot. And /var/log/messages doesn't even get "failed to mount" messages if nfsd isn't running. So the server was sitting there silently and the client was silently failing to mount the nfs directory and get it's ks.cfg file. Thanks all, Paul From marhoy at gmail.com Tue Feb 1 10:06:10 2005 From: marhoy at gmail.com (=?ISO-8859-1?Q?Martin_H=F8y?=) Date: Tue, 1 Feb 2005 11:06:10 +0100 Subject: Problems with Fedora core 3 In-Reply-To: References: <5D339AE687B0C8438185AE62ED06697D0EA312@ukchmail01.mail.quadriga.com> <93072505012806427019ce59@mail.gmail.com> <93072505013107564d3103d1@mail.gmail.com> Message-ID: <93072505020102066a6aeccb@mail.gmail.com> On Mon, 31 Jan 2005 10:42:35 -0600, Jason L Tibbitts III wrote: > >>>>> "MH" == Martin H?y writes: > > MH> But the updated install somehow triggers a bug(?), so that when I > MH> reboot the machine after installing, kudzu reports the ethernet > MH> card, soundcard and sata-controller as "new hardware" which needs > MH> to be configured. > > That's new to me; perhaps the updated kernel detects devices in a > different order, so that kudzu thinks they're all new? This wouldn't > have been a problem before since the kernel in the boot image would > have been the same as the freshly installed one. > > You could try building fresh boot images too, but unfortunately I > can't offer any advice on how to do that. As an experiment, you could > try updating everything but the kernel. (I.e. start from a fresh tree > from the DVD image, pull down the updates and delete the new kernel > packages. Then run the update and try an install.) Hello again, I tried the first approach (updating the boot.iso too), which turned out to be both easy and successful: Everything now works like a charm, and the kudzu-trouble is gone. The commands I used to rebuild all the boot/install-files was: export PATH="$PATH:/usr/lib/anaconda-runtime" export PYTHONPATH=/usr/lib/anaconda buildinstall --pkgorder --version 3 --product \ 'Fedora Core' --release 'Fedora Core 3' --prodpath Fedora \ /disk1/fc3-updated/i386/os where is the pkgorder-file produced by your update-script, and /disk1/fc3-updated/i386/os is of course the path to my updated tree. You could even include this as an option in your update-script. PS: The buildinstall have to be run as root, as it tries to do e.g. some keyboard-things that only root is allowed to. Regards, Martin From Rebecca.R.Hepper at seagate.com Wed Feb 2 17:22:18 2005 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Wed, 2 Feb 2005 11:22:18 -0600 Subject: Genhdlist issue on RH 9 Message-ID: Hello, My NFS server is RH 9 with anaconda & anaconda-runtime 9.0-4 RPMs installed. I want to set up to install Fedora Core 3 systems. The FC3 kickstart worked fine when I used RPMs off the CDs. But then I updated some of the RPMs and I now need to run genhdlist. Based on what I have read, I need to run the following commands: PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder /var/redhat.disks/fc3 i386 Fedora > pkgorder.txt /usr/lib/anaconda-runtime/genhdlist --productpath Fedora --withnumbers --pkgorder pkgorder.txt /var/redhat.disks/fc3 The problem lies in the fact that my version of genhdlist does not support the productpath or pkgorder options. I have the latest anaconda RPMs that I could find that work with RH 9. Is there a way around this or does my server have to be upgraded to Fedora? Regards, Becky From phr at doc.ic.ac.uk Wed Feb 2 18:21:44 2005 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Wed, 2 Feb 2005 18:21:44 +0000 (GMT) Subject: Genhdlist issue on RH 9 In-Reply-To: References: Message-ID: On Wed, 2 Feb 2005 Rebecca.R.Hepper at seagate.com wrote: >My NFS server is RH 9 with anaconda & anaconda-runtime 9.0-4 RPMs >installed. I want to set up to install Fedora Core 3 systems. genhdlist is evil. Whereas it used to be statically compiled so that one could happily copy it cross-distro, now it just seems to have a bunch of GLIBC symbol versioning complaints whenever I try to run it away from the "host" release. This may not be entirely Redhat's fault... - the NSS problem has caused quite some chatter: http://www.google.com/search?q=nss+static+linking >Is there a way around this or does my server have to be upgraded to >Fedora? The least disruptive method I can think of would be to boot another workstation nearby with the FC rescue CD, mount the NFS dir and run genhdlist/pkgorder from there. Cheers, Phil From James.Oden at tekelec.com Wed Feb 2 18:22:15 2005 From: James.Oden at tekelec.com (Oden, James) Date: Wed, 2 Feb 2005 12:22:15 -0600 Subject: Genhdlist issue on RH 9 Message-ID: <58292FA6B3EEFD49AEDAF6597E21E717A466AC@DCEVS2.tekelec.com> > Hello, > > My NFS server is RH 9 with anaconda & anaconda-runtime 9.0-4 RPMs > installed. I want to set up to install Fedora Core 3 systems. > > The FC3 kickstart worked fine when I used RPMs off the CDs. But then I > updated some of the RPMs and I now need to run genhdlist. > Based on what I > have read, I need to run the following commands: > > PYTHONPATH=/usr/lib/anaconda > /usr/lib/anaconda-runtime/pkgorder /var/redhat.disks/fc3 i386 Fedora > > pkgorder.txt > /usr/lib/anaconda-runtime/genhdlist --productpath Fedora --withnumbers > --pkgorder pkgorder.txt /var/redhat.disks/fc3 > > The problem lies in the fact that my version of genhdlist > does not support > the productpath or pkgorder options. I have the latest It was --fileorder in RH9 and think it still is in RHEL3. Don't know about product path, but could download the SRPMS for the fedora one and the RH9 one, do a diff between the two genhdlist.c files and come up with a patch. I am guessing the --productpath is pretty trivial to add back into a RH9 anaconda. Cheers...james From rreed at ops.sgp.arm.gov Thu Feb 3 17:19:14 2005 From: rreed at ops.sgp.arm.gov (Ronald Reed) Date: Thu, 03 Feb 2005 11:19:14 -0600 Subject: initrd.img module loading Message-ID: <1107451153.3008.4.camel@ronnote> Where does the standard initrd.img get the order to load modules into the kernel? I need to create a new initrd for a boot that loads some scsi raid modules in a specific order. -- =========================== Ron Reed RedHat Certified Engineer SGP Computer Department Manager Unix Systems Administrator ARM SGP CART Site (580)388-4053 ron.reed at arm.gov From johnpaulmp at amiindia.co.in Fri Feb 4 04:40:43 2005 From: johnpaulmp at amiindia.co.in (johnpaul) Date: Fri, 4 Feb 2005 10:10:43 +0530 Subject: initrd.img module loading References: <1107451153.3008.4.camel@ronnote> Message-ID: <001201c50a73$b05a1e60$8300000a@johnpaul> Hi Have a look at the loader.c file in the loader2 directory of the anaconda source Regards John ----- Original Message ----- From: "Ronald Reed" To: "Discussion list about Kickstart" Sent: Thursday, February 03, 2005 10:49 PM Subject: initrd.img module loading > Where does the standard initrd.img get the order to load modules into > the kernel? > > I need to create a new initrd for a boot that loads some scsi raid > modules in a specific order. > -- > =========================== > Ron Reed > RedHat Certified Engineer > SGP Computer Department Manager > Unix Systems Administrator > ARM SGP CART Site > (580)388-4053 > ron.reed at arm.gov > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From peter at boku.net Fri Feb 4 04:53:04 2005 From: peter at boku.net (Peter Eisch) Date: Thu, 03 Feb 2005 22:53:04 -0600 Subject: Detecting a previous install Message-ID: Does anyone have an insight for how to include a %pre script where I could test for the existence of a specific directory on the target drive? Is there a variable set by anaconda that describes the target for the install that I could pick up on the %pre? I have not tried it yet, but I could forsee trying to mount every conceivable root filesystem hda, sda, etc. to see if /etc/openssl/certs exists. If it is, my install needs to die a horrible death as we're finding "users" don't seem to grasp the gravity of some things. Does anyone have any insight or experiences? Thanks, peter From phr at doc.ic.ac.uk Fri Feb 4 05:20:31 2005 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Fri, 4 Feb 2005 05:20:31 +0000 (GMT) Subject: Detecting a previous install In-Reply-To: References: Message-ID: On Thu, 3 Feb 2005, Peter Eisch wrote: >Is there a variable set by anaconda that describes the target for the >install that I could pick up on the %pre? Don't know of one. > I have not tried it yet, but I could forsee trying to mount every >conceivable root filesystem hda, sda, etc. to see if /etc/openssl/certs >exists. It's worse than that - you have to create the device nodes. For just the single file existence test, one strategy would be: foreach "Linux" partition as determined by /proc/partitions and fdisk { use debugfs to list the directory of cat the file, and die if appropriate } Gain bonus points for correctly handling LVM-based filesystems. Cheers, Phil From Rebecca.R.Hepper at seagate.com Fri Feb 4 14:34:35 2005 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Fri, 4 Feb 2005 08:34:35 -0600 Subject: Genhdlist issue on RH 9 In-Reply-To: <58292FA6B3EEFD49AEDAF6597E21E717A466AC@DCEVS2.tekelec.com> Message-ID: Thanks for the suggestions. genhdlist is evil :) The easiest route for me was to boot a FC3 system, mount the NFS dir and run my commands. This worked great! "Oden, James" To Sent by: "Discussion list about Kickstart" kickstart-list-bo unces at redhat.com cc No Phone Info Available Subject RE: Genhdlist issue on RH 9 02/02/2005 12:22 PM Please respond to Discussion list about Kickstart > Hello, > > My NFS server is RH 9 with anaconda & anaconda-runtime 9.0-4 RPMs > installed. I want to set up to install Fedora Core 3 systems. > > The FC3 kickstart worked fine when I used RPMs off the CDs. But then I > updated some of the RPMs and I now need to run genhdlist. > Based on what I > have read, I need to run the following commands: > > PYTHONPATH=/usr/lib/anaconda > /usr/lib/anaconda-runtime/pkgorder /var/redhat.disks/fc3 i386 Fedora > > pkgorder.txt > /usr/lib/anaconda-runtime/genhdlist --productpath Fedora --withnumbers > --pkgorder pkgorder.txt /var/redhat.disks/fc3 > > The problem lies in the fact that my version of genhdlist > does not support > the productpath or pkgorder options. I have the latest It was --fileorder in RH9 and think it still is in RHEL3. Don't know about product path, but could download the SRPMS for the fedora one and the RH9 one, do a diff between the two genhdlist.c files and come up with a patch. I am guessing the --productpath is pretty trivial to add back into a RH9 anaconda. Cheers...james _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From mshuler at rackspace.com Fri Feb 4 18:21:57 2005 From: mshuler at rackspace.com (Michael Shuler) Date: Fri, 04 Feb 2005 12:21:57 -0600 Subject: Detecting a previous install In-Reply-To: References: Message-ID: <4203BD45.4010308@rackspace.com> Peter Eisch wrote: > Does anyone have an insight for how to include a %pre script where I could > test for the existence of a specific directory on the target drive? I would suggest that the user should think twice if there is anything on the drive, not just a file or directory. Our standard practice is to only kickstart completely new drives, so anything with an existing partition is bad news. You could make this die, or provide and opt out, as below (which keeps me from having to wipe test boxes before kicking). This works on EL-3 and EL-4beta: %pre # change to tty3 and check for partitions chvt 3 exec < /dev/tty3 > /dev/tty3 2>/dev/tty3 # check clear sleep 2 echo "Checking for existing partitions...\n" FDISK=`which fdisk` if [ `$FDISK -l | grep "^/dev" | wc -l` -ne 0 ] ; then sleep 1 echo "Whoa! This server has data partitions!!\n" while true; do echo "If you wish to continue with kickstart, type -> YES <- :\n" read answer case $answer in YES ) echo "\nContinuing with kickstart...\n" ; sleep 3 ; break ;; * ) echo "\nHuh? Let's try again...\n" ;; esac done else echo "Found no partitions - moving right along...\n" ; sleep 3 fi # move back to tty1 and continue with install chvt 1 exec < /dev/tty1 > /dev/tty1 -- Kind Regards, Michael Shuler From rreed at ops.sgp.arm.gov Mon Feb 7 20:31:04 2005 From: rreed at ops.sgp.arm.gov (Ronald Reed) Date: Mon, 07 Feb 2005 14:31:04 -0600 Subject: initrd.img module loading In-Reply-To: <001201c50a73$b05a1e60$8300000a@johnpaul> References: <1107451153.3008.4.camel@ronnote> <001201c50a73$b05a1e60$8300000a@johnpaul> Message-ID: <1107808264.3039.24.camel@ronnote> I really don't want to rewrite anaconda, just to get one scsi module to load before another one. I have tried the scsihosts= boot option, but the installer just seems to ignore it. I have also tried the expert noprobe boot options with device commands in the kickstart config file (Which worked in 7.1 - 7.3), and the system can not find any drives at that point. What I need to do, is make sure that the aacraid driver is setup as /dev/sda and that the megaraid driver is setup as /dev/sdb during the install. On Thu, 2005-02-03 at 22:40, johnpaul wrote: > Hi > > Have a look at the loader.c file in the loader2 directory of the > anaconda source > > Regards > John > ----- Original Message ----- > From: "Ronald Reed" > To: "Discussion list about Kickstart" > Sent: Thursday, February 03, 2005 10:49 PM > Subject: initrd.img module loading > > > > Where does the standard initrd.img get the order to load modules into > > the kernel? > > > > I need to create a new initrd for a boot that loads some scsi raid > > modules in a specific order. > > -- > > =========================== > > Ron Reed > > RedHat Certified Engineer > > SGP Computer Department Manager > > Unix Systems Administrator > > ARM SGP CART Site > > (580)388-4053 > > ron.reed at arm.gov > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- =========================== Ron Reed RedHat Certified Engineer SGP Computer Department Manager Unix Systems Administrator ARM SGP CART Site (580)388-4053 ron.reed at arm.gov From peter at boku.net Mon Feb 7 21:51:39 2005 From: peter at boku.net (Peter Eisch) Date: Mon, 07 Feb 2005 15:51:39 -0600 Subject: initrd.img module loading In-Reply-To: <1107808264.3039.24.camel@ronnote> Message-ID: I'm not sure what your scope is, but maybe this helps... I had an issue where I needed to forceload drivers where I knew the PCI info was up to date for the devices we were loading on, so I forceloaded the drivers in the initrd.img just as the kernel was being installed. This, of course, had to be done manually on the install cd's initrd. But for the various kernels I ended up with something like this in the spec files for each platform: %post bigmem [ -x /usr/sbin/module_upgrade ] && /usr/sbin/module_upgrade [ -x /sbin/mkkerneldoth ] && /sbin/mkkerneldoth if [ -x /sbin/new-kernel-pkg ] ; then /sbin/new-kernel-pkg --mkinitrd --depmod --install %{KVERREL}bigmem fi /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with cciss \ /boot/ninitrd-%{KVERREL}bigmem.img %{KVERREL}bigmem /bin/mv /boot/initrd-%{KVERREL}bigmem.img /boot/oinitrd-%{KVERREL}bigmem.img /bin/mv /boot/ninitrd-%{KVERREL}bigmem.img /boot/initrd-%{KVERREL}bigmem.img Maybe do the --preloads in the order you need them loaded. Hope this helps, peter On 2/7/05 2:31 PM, "Ronald Reed" wrote: > I really don't want to rewrite anaconda, just to get one scsi module to > load before another one. > > I have tried the scsihosts= boot option, but the installer just seems to > ignore it. I have also tried the expert noprobe boot options with device > commands in the kickstart config file (Which worked in 7.1 - 7.3), and > the system can not find any drives at that point. > > What I need to do, is make sure that the aacraid driver is setup as > /dev/sda and that the megaraid driver is setup as /dev/sdb during the > install. > > On Thu, 2005-02-03 at 22:40, johnpaul wrote: >> Hi >> >> Have a look at the loader.c file in the loader2 directory of the >> anaconda source >> >> Regards >> John >> ----- Original Message ----- >> From: "Ronald Reed" >> To: "Discussion list about Kickstart" >> Sent: Thursday, February 03, 2005 10:49 PM >> Subject: initrd.img module loading >> >> >>> Where does the standard initrd.img get the order to load modules into >>> the kernel? >>> >>> I need to create a new initrd for a boot that loads some scsi raid >>> modules in a specific order. >>> -- >>> =========================== >>> Ron Reed >>> RedHat Certified Engineer >>> SGP Computer Department Manager >>> Unix Systems Administrator >>> ARM SGP CART Site >>> (580)388-4053 >>> ron.reed at arm.gov >>> >>> _______________________________________________ >>> Kickstart-list mailing list >>> Kickstart-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/kickstart-list >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list From jskohli at gmail.com Tue Feb 8 12:18:14 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Tue, 8 Feb 2005 17:48:14 +0530 Subject: Out of Disk Space !! Message-ID: <27ecd449050208041864c97be8@mail.gmail.com> Hi, I am getting this error while installation, using the ks.cfg which partitions the drive into three partitions, / = 1 G swap = 1 G /var = rest of space ( 30 + G) The cd image that i built had modified stage2.img, ( took care of .buildstamp) bootdisks upgraded to kernel 2.6.10..., Only Modified isolinux/initrd.img is used, rest of the files like, stage2.img and hdstg2.img are just repackaged version of what were on Original FC3 Iso's, only changed .buildstamp Now when i booot that CD, the boots up, detects hardware, anaconda starts X The partitions are created and formatted, but then the Install ends with a message. "An error occured while transfering install image to your harddrive . You are probably out of disk space" Where as when i perform fdisk -l on tty2, which shows, all the partitions were created and also on console 6 the formatting was successful and hence lot of space is there. On tty3, the detailed error message is as follows... Error transfering stage2.img: [Errno 2] No such file of directory: '/mnt/sysimage/proc/rhinstall-stage2.img' I did a search on google, and archives, came up with no results. Can any one tell me what i am missing or doing wrong and why it is trying to copy rhinstall-stage2.img from some proc fs instead of stage2.img from CD. I am stuck at this point for too long now, any Pointers, any ideas, will be helpful, that can get me going in forward direction. Thanks.... -- Regards JSK jskohli (AT) gmail (DOT) com From rreed at ops.sgp.arm.gov Tue Feb 8 16:04:31 2005 From: rreed at ops.sgp.arm.gov (Ronald Reed) Date: Tue, 08 Feb 2005 10:04:31 -0600 Subject: initrd.img module loading In-Reply-To: References: Message-ID: <1107878670.2977.27.camel@ronnote> That is an interesting ideal, but I need the modules to load in a certain order during the kickstart. If the megaraid driver gets loaded first, then the external drive array gets setup as /dev/sda and the kickstart installs the external array as the main boot device. The boot prompt command scsihosts= is supposed to let you do that, but it doesn't seem to work. Ron On Mon, 2005-02-07 at 15:51, Peter Eisch wrote: > I'm not sure what your scope is, but maybe this helps... > > I had an issue where I needed to forceload drivers where I knew the PCI info > was up to date for the devices we were loading on, so I forceloaded the > drivers in the initrd.img just as the kernel was being installed. This, of > course, had to be done manually on the install cd's initrd. But for the > various kernels I ended up with something like this in the spec files for > each platform: > > %post bigmem > [ -x /usr/sbin/module_upgrade ] && /usr/sbin/module_upgrade > [ -x /sbin/mkkerneldoth ] && /sbin/mkkerneldoth > if [ -x /sbin/new-kernel-pkg ] ; then > /sbin/new-kernel-pkg --mkinitrd --depmod --install %{KVERREL}bigmem > fi > /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with cciss \ > /boot/ninitrd-%{KVERREL}bigmem.img %{KVERREL}bigmem > /bin/mv /boot/initrd-%{KVERREL}bigmem.img /boot/oinitrd-%{KVERREL}bigmem.img > /bin/mv /boot/ninitrd-%{KVERREL}bigmem.img /boot/initrd-%{KVERREL}bigmem.img > > > Maybe do the --preloads in the order you need them loaded. Hope this helps, > > peter > > > On 2/7/05 2:31 PM, "Ronald Reed" wrote: > > > I really don't want to rewrite anaconda, just to get one scsi module to > > load before another one. > > > > I have tried the scsihosts= boot option, but the installer just seems to > > ignore it. I have also tried the expert noprobe boot options with device > > commands in the kickstart config file (Which worked in 7.1 - 7.3), and > > the system can not find any drives at that point. > > > > What I need to do, is make sure that the aacraid driver is setup as > > /dev/sda and that the megaraid driver is setup as /dev/sdb during the > > install. > > > > On Thu, 2005-02-03 at 22:40, johnpaul wrote: > >> Hi > >> > >> Have a look at the loader.c file in the loader2 directory of the > >> anaconda source > >> > >> Regards > >> John > >> ----- Original Message ----- > >> From: "Ronald Reed" > >> To: "Discussion list about Kickstart" > >> Sent: Thursday, February 03, 2005 10:49 PM > >> Subject: initrd.img module loading > >> > >> > >>> Where does the standard initrd.img get the order to load modules into > >>> the kernel? > >>> > >>> I need to create a new initrd for a boot that loads some scsi raid > >>> modules in a specific order. > >>> -- > >>> =========================== > >>> Ron Reed > >>> RedHat Certified Engineer > >>> SGP Computer Department Manager > >>> Unix Systems Administrator > >>> ARM SGP CART Site > >>> (580)388-4053 > >>> ron.reed at arm.gov > >>> > >>> _______________________________________________ > >>> Kickstart-list mailing list > >>> Kickstart-list at redhat.com > >>> https://www.redhat.com/mailman/listinfo/kickstart-list > >> > >> _______________________________________________ > >> Kickstart-list mailing list > >> Kickstart-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- =========================== Ron Reed RedHat Certified Engineer SGP Computer Department Manager Unix Systems Administrator ARM SGP CART Site (580)388-4053 ron.reed at arm.gov From dan at half-asleep.com Tue Feb 8 16:06:05 2005 From: dan at half-asleep.com (Daniel Segall) Date: Tue, 8 Feb 2005 11:06:05 -0500 (EST) Subject: Out of Disk Space !! In-Reply-To: <27ecd449050208041864c97be8@mail.gmail.com> References: <27ecd449050208041864c97be8@mail.gmail.com> Message-ID: <40875.192.80.55.73.1107878765.squirrel@192.80.55.73> How much stuff are you actually installing? 1g for the entire system is not very much space. I believe a completely trimmed down FC3 will take close to that much now, and that assumes you have taken care of all dependencies and such. Not sure if this is the case, but maybe try making / larger for testing purposes. -Dan > Hi, > > I am getting this error while installation, using the ks.cfg which > partitions the drive into > three partitions, / = 1 G > swap = 1 G > /var = rest of space ( 30 + G) > > The cd image that i built had modified stage2.img, ( took care of > .buildstamp) > bootdisks upgraded to kernel 2.6.10..., > Only Modified isolinux/initrd.img is used, rest of the files like, > stage2.img and hdstg2.img > are just repackaged version of what were on Original FC3 Iso's, only > changed .buildstamp > > Now when i booot that CD, the boots up, detects hardware, anaconda starts > X > The partitions are created and formatted, but then the Install ends > with a message. > > "An error occured while transfering install image to your harddrive . > You are probably > out of disk space" > > Where as when i perform fdisk -l on tty2, which shows, all the > partitions were created > and also on console 6 the formatting was successful and hence lot of > space is there. > > On tty3, the detailed error message is as follows... > > Error transfering stage2.img: [Errno 2] No such file of directory: > '/mnt/sysimage/proc/rhinstall-stage2.img' > > I did a search on google, and archives, came up with no results. > > Can any one tell me what i am missing or doing wrong and why it is > trying to copy > rhinstall-stage2.img from some proc fs instead of stage2.img from CD. > > I am stuck at this point for too long now, any Pointers, any ideas, > will be helpful, that can > get me going in forward direction. > > Thanks.... > > -- > Regards > JSK > jskohli (AT) gmail (DOT) com > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > From peter at boku.net Tue Feb 8 16:16:05 2005 From: peter at boku.net (Peter Eisch) Date: Tue, 08 Feb 2005 10:16:05 -0600 Subject: Out of Disk Space !! In-Reply-To: <27ecd449050208041864c97be8@mail.gmail.com> Message-ID: You probably don't have drivers for that particular kernel that you are now booting from in the stage2.img. Whatever you did to update the boot initrd.img, also do to the stage2.img. peter On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" wrote: > Hi, > > I am getting this error while installation, using the ks.cfg which > partitions the drive into > three partitions, / = 1 G > swap = 1 G > /var = rest of space ( 30 + G) > > The cd image that i built had modified stage2.img, ( took care of .buildstamp) > bootdisks upgraded to kernel 2.6.10..., > Only Modified isolinux/initrd.img is used, rest of the files like, > stage2.img and hdstg2.img > are just repackaged version of what were on Original FC3 Iso's, only > changed .buildstamp > > Now when i booot that CD, the boots up, detects hardware, anaconda starts X > The partitions are created and formatted, but then the Install ends > with a message. > > "An error occured while transfering install image to your harddrive . > You are probably > out of disk space" > > Where as when i perform fdisk -l on tty2, which shows, all the > partitions were created > and also on console 6 the formatting was successful and hence lot of > space is there. > > On tty3, the detailed error message is as follows... > > Error transfering stage2.img: [Errno 2] No such file of directory: > '/mnt/sysimage/proc/rhinstall-stage2.img' > > I did a search on google, and archives, came up with no results. > > Can any one tell me what i am missing or doing wrong and why it is > trying to copy > rhinstall-stage2.img from some proc fs instead of stage2.img from CD. > > I am stuck at this point for too long now, any Pointers, any ideas, > will be helpful, that can > get me going in forward direction. > > Thanks.... From peter at boku.net Tue Feb 8 16:19:03 2005 From: peter at boku.net (Peter Eisch) Date: Tue, 08 Feb 2005 10:19:03 -0600 Subject: initrd.img module loading In-Reply-To: <1107878670.2977.27.camel@ronnote> Message-ID: The order you pass them to mkinitrd is the order in which they'll be loaded. By the time kickstart gets around to doing anything, the kernel has already laid out how devices are mapped. Or are you looking for this in the ks.cfg: bootloader --driveorder=cciss/c0d0,sda,hda --location=mbr peter On 2/8/05 10:04 AM, "Ronald Reed" wrote: > That is an interesting ideal, but I need the modules to load in a > certain order during the kickstart. If the megaraid driver gets loaded > first, then the external drive array gets setup as /dev/sda and the > kickstart installs the external array as the main boot device. The boot > prompt command scsihosts= is supposed to let you do that, but it doesn't > seem to work. > > Ron > > On Mon, 2005-02-07 at 15:51, Peter Eisch wrote: >> I'm not sure what your scope is, but maybe this helps... >> >> I had an issue where I needed to forceload drivers where I knew the PCI info >> was up to date for the devices we were loading on, so I forceloaded the >> drivers in the initrd.img just as the kernel was being installed. This, of >> course, had to be done manually on the install cd's initrd. But for the >> various kernels I ended up with something like this in the spec files for >> each platform: >> >> %post bigmem >> [ -x /usr/sbin/module_upgrade ] && /usr/sbin/module_upgrade >> [ -x /sbin/mkkerneldoth ] && /sbin/mkkerneldoth >> if [ -x /sbin/new-kernel-pkg ] ; then >> /sbin/new-kernel-pkg --mkinitrd --depmod --install %{KVERREL}bigmem >> fi >> /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with cciss \ >> /boot/ninitrd-%{KVERREL}bigmem.img %{KVERREL}bigmem >> /bin/mv /boot/initrd-%{KVERREL}bigmem.img /boot/oinitrd-%{KVERREL}bigmem.img >> /bin/mv /boot/ninitrd-%{KVERREL}bigmem.img /boot/initrd-%{KVERREL}bigmem.img >> >> >> Maybe do the --preloads in the order you need them loaded. Hope this helps, >> >> peter >> >> >> On 2/7/05 2:31 PM, "Ronald Reed" wrote: >> >>> I really don't want to rewrite anaconda, just to get one scsi module to >>> load before another one. >>> >>> I have tried the scsihosts= boot option, but the installer just seems to >>> ignore it. I have also tried the expert noprobe boot options with device >>> commands in the kickstart config file (Which worked in 7.1 - 7.3), and >>> the system can not find any drives at that point. >>> >>> What I need to do, is make sure that the aacraid driver is setup as >>> /dev/sda and that the megaraid driver is setup as /dev/sdb during the >>> install. >>> >>> On Thu, 2005-02-03 at 22:40, johnpaul wrote: >>>> Hi >>>> >>>> Have a look at the loader.c file in the loader2 directory of the >>>> anaconda source >>>> >>>> Regards >>>> John >>>> ----- Original Message ----- >>>> From: "Ronald Reed" >>>> To: "Discussion list about Kickstart" >>>> Sent: Thursday, February 03, 2005 10:49 PM >>>> Subject: initrd.img module loading >>>> >>>> >>>>> Where does the standard initrd.img get the order to load modules into >>>>> the kernel? >>>>> >>>>> I need to create a new initrd for a boot that loads some scsi raid >>>>> modules in a specific order. >>>>> -- >>>>> =========================== >>>>> Ron Reed >>>>> RedHat Certified Engineer >>>>> SGP Computer Department Manager >>>>> Unix Systems Administrator >>>>> ARM SGP CART Site >>>>> (580)388-4053 >>>>> ron.reed at arm.gov >>>>> >>>>> _______________________________________________ >>>>> Kickstart-list mailing list >>>>> Kickstart-list at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/kickstart-list >>>> >>>> _______________________________________________ >>>> Kickstart-list mailing list >>>> Kickstart-list at redhat.com >>>> https://www.redhat.com/mailman/listinfo/kickstart-list >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list From jskohli at gmail.com Tue Feb 8 16:36:21 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Tue, 8 Feb 2005 22:06:21 +0530 Subject: Out of Disk Space !! In-Reply-To: References: <27ecd449050208041864c97be8@mail.gmail.com> Message-ID: <27ecd449050208083619e00c3f@mail.gmail.com> Installing only bare minimum system, to act as gateway and proxy server. All the partitions are correctly formatted. I am using stripped down, buildinstall which only updates, initrd.img and not the other files. Since building stage2.img using buildinstall, requires lot of other packages to be in the install tree, for X and others, which i dont' want to include, as it is for proxy server and very small image. And what kind of drivers ??? On Tue, 08 Feb 2005 10:16:05 -0600, Peter Eisch wrote: > > You probably don't have drivers for that particular kernel that you are now > booting from in the stage2.img. Whatever you did to update the boot > initrd.img, also do to the stage2.img. > > peter > > On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" wrote: > > > Hi, > > > > I am getting this error while installation, using the ks.cfg which > > partitions the drive into > > three partitions, / = 1 G > > swap = 1 G > > /var = rest of space ( 30 + G) > > > > The cd image that i built had modified stage2.img, ( took care of .buildstamp) > > bootdisks upgraded to kernel 2.6.10..., > > Only Modified isolinux/initrd.img is used, rest of the files like, > > stage2.img and hdstg2.img > > are just repackaged version of what were on Original FC3 Iso's, only > > changed .buildstamp > > > > Now when i booot that CD, the boots up, detects hardware, anaconda starts X > > The partitions are created and formatted, but then the Install ends > > with a message. > > > > "An error occured while transfering install image to your harddrive . > > You are probably > > out of disk space" > > > > Where as when i perform fdisk -l on tty2, which shows, all the > > partitions were created > > and also on console 6 the formatting was successful and hence lot of > > space is there. > > > > On tty3, the detailed error message is as follows... > > > > Error transfering stage2.img: [Errno 2] No such file of directory: > > '/mnt/sysimage/proc/rhinstall-stage2.img' > > > > I did a search on google, and archives, came up with no results. > > > > Can any one tell me what i am missing or doing wrong and why it is > > trying to copy > > rhinstall-stage2.img from some proc fs instead of stage2.img from CD. > > > > I am stuck at this point for too long now, any Pointers, any ideas, > > will be helpful, that can > > get me going in forward direction. > > > > Thanks.... > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Regards JSK jskohli (AT) gmail (DOT) com From peter at boku.net Tue Feb 8 16:45:56 2005 From: peter at boku.net (Peter Eisch) Date: Tue, 08 Feb 2005 10:45:56 -0600 Subject: Out of Disk Space !! In-Reply-To: <27ecd449050208083619e00c3f@mail.gmail.com> Message-ID: If you look at 'pivotroot' down in the source, you'll see that stage2.img gets mounted as the new / during the install. Whatever drivers you updated in initrd.img will also need to be updated on the new / image loaded from stage2.img. What Drivers? ... the drivers for whatever controller your target install disk is connected. On 2/8/05 10:36 AM, "Jaswinder Singh Kohli" wrote: > Installing only bare minimum system, to act as gateway and proxy server. > All the partitions are correctly formatted. > > I am using stripped down, buildinstall which only updates, initrd.img > and not the other files. > > Since building stage2.img using buildinstall, requires lot of other > packages to be in the > install tree, for X and others, which i dont' want to include, as it > is for proxy server > and very small image. > > And what kind of drivers ??? > > > On Tue, 08 Feb 2005 10:16:05 -0600, Peter Eisch wrote: >> >> You probably don't have drivers for that particular kernel that you are now >> booting from in the stage2.img. Whatever you did to update the boot >> initrd.img, also do to the stage2.img. >> >> peter >> >> On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" wrote: >> >>> Hi, >>> >>> I am getting this error while installation, using the ks.cfg which >>> partitions the drive into >>> three partitions, / = 1 G >>> swap = 1 G >>> /var = rest of space ( 30 + G) >>> >>> The cd image that i built had modified stage2.img, ( took care of >>> .buildstamp) >>> bootdisks upgraded to kernel 2.6.10..., >>> Only Modified isolinux/initrd.img is used, rest of the files like, >>> stage2.img and hdstg2.img >>> are just repackaged version of what were on Original FC3 Iso's, only >>> changed .buildstamp >>> >>> Now when i booot that CD, the boots up, detects hardware, anaconda starts X >>> The partitions are created and formatted, but then the Install ends >>> with a message. >>> >>> "An error occured while transfering install image to your harddrive . >>> You are probably >>> out of disk space" >>> >>> Where as when i perform fdisk -l on tty2, which shows, all the >>> partitions were created >>> and also on console 6 the formatting was successful and hence lot of >>> space is there. >>> >>> On tty3, the detailed error message is as follows... >>> >>> Error transfering stage2.img: [Errno 2] No such file of directory: >>> '/mnt/sysimage/proc/rhinstall-stage2.img' >>> >>> I did a search on google, and archives, came up with no results. >>> >>> Can any one tell me what i am missing or doing wrong and why it is >>> trying to copy >>> rhinstall-stage2.img from some proc fs instead of stage2.img from CD. >>> >>> I am stuck at this point for too long now, any Pointers, any ideas, >>> will be helpful, that can >>> get me going in forward direction. >>> >>> Thanks.... >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> > From rreed at ops.sgp.arm.gov Tue Feb 8 17:20:24 2005 From: rreed at ops.sgp.arm.gov (Ronald Reed) Date: Tue, 08 Feb 2005 11:20:24 -0600 Subject: initrd.img module loading In-Reply-To: References: Message-ID: <1107883223.2977.50.camel@ronnote> Maybe I am misunderstanding what is being said or I am not making myself clear. This is a fresh kickstart install, with a standard RedHat Enterprise 3.0 boot image and kickstart file. (I am customizing a kickstart CD, but it is the standard bootdisk.img file for the CD boot) When the install starts, it finds the megaraid device first and assigns it as /dev/sda. This makes anaconda format and install to the wrong raid set. I guess I could remake the initrd.img for the install, but I am not sure what options to use to make a new initrd.img for the bootdisk.img so that it still has all the options that it currently has in it, but just load the aacraid driver before it loads the megaraid one. Ron On Tue, 2005-02-08 at 10:19, Peter Eisch wrote: > The order you pass them to mkinitrd is the order in which they'll be loaded. > By the time kickstart gets around to doing anything, the kernel has already > laid out how devices are mapped. > > Or are you looking for this in the ks.cfg: > > bootloader --driveorder=cciss/c0d0,sda,hda --location=mbr > > peter > > On 2/8/05 10:04 AM, "Ronald Reed" wrote: > > > That is an interesting ideal, but I need the modules to load in a > > certain order during the kickstart. If the megaraid driver gets loaded > > first, then the external drive array gets setup as /dev/sda and the > > kickstart installs the external array as the main boot device. The boot > > prompt command scsihosts= is supposed to let you do that, but it doesn't > > seem to work. > > > > Ron > > > > On Mon, 2005-02-07 at 15:51, Peter Eisch wrote: > >> I'm not sure what your scope is, but maybe this helps... > >> > >> I had an issue where I needed to forceload drivers where I knew the PCI info > >> was up to date for the devices we were loading on, so I forceloaded the > >> drivers in the initrd.img just as the kernel was being installed. This, of > >> course, had to be done manually on the install cd's initrd. But for the > >> various kernels I ended up with something like this in the spec files for > >> each platform: > >> > >> %post bigmem > >> [ -x /usr/sbin/module_upgrade ] && /usr/sbin/module_upgrade > >> [ -x /sbin/mkkerneldoth ] && /sbin/mkkerneldoth > >> if [ -x /sbin/new-kernel-pkg ] ; then > >> /sbin/new-kernel-pkg --mkinitrd --depmod --install %{KVERREL}bigmem > >> fi > >> /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with cciss \ > >> /boot/ninitrd-%{KVERREL}bigmem.img %{KVERREL}bigmem > >> /bin/mv /boot/initrd-%{KVERREL}bigmem.img /boot/oinitrd-%{KVERREL}bigmem.img > >> /bin/mv /boot/ninitrd-%{KVERREL}bigmem.img /boot/initrd-%{KVERREL}bigmem.img > >> > >> > >> Maybe do the --preloads in the order you need them loaded. Hope this helps, > >> > >> peter > >> > >> > >> On 2/7/05 2:31 PM, "Ronald Reed" wrote: > >> > >>> I really don't want to rewrite anaconda, just to get one scsi module to > >>> load before another one. > >>> > >>> I have tried the scsihosts= boot option, but the installer just seems to > >>> ignore it. I have also tried the expert noprobe boot options with device > >>> commands in the kickstart config file (Which worked in 7.1 - 7.3), and > >>> the system can not find any drives at that point. > >>> > >>> What I need to do, is make sure that the aacraid driver is setup as > >>> /dev/sda and that the megaraid driver is setup as /dev/sdb during the > >>> install. > >>> > >>> On Thu, 2005-02-03 at 22:40, johnpaul wrote: > >>>> Hi > >>>> > >>>> Have a look at the loader.c file in the loader2 directory of the > >>>> anaconda source > >>>> > >>>> Regards > >>>> John > >>>> ----- Original Message ----- > >>>> From: "Ronald Reed" > >>>> To: "Discussion list about Kickstart" > >>>> Sent: Thursday, February 03, 2005 10:49 PM > >>>> Subject: initrd.img module loading > >>>> > >>>> > >>>>> Where does the standard initrd.img get the order to load modules into > >>>>> the kernel? > >>>>> > >>>>> I need to create a new initrd for a boot that loads some scsi raid > >>>>> modules in a specific order. > >>>>> -- > >>>>> =========================== > >>>>> Ron Reed > >>>>> RedHat Certified Engineer > >>>>> SGP Computer Department Manager > >>>>> Unix Systems Administrator > >>>>> ARM SGP CART Site > >>>>> (580)388-4053 > >>>>> ron.reed at arm.gov > >>>>> > >>>>> _______________________________________________ > >>>>> Kickstart-list mailing list > >>>>> Kickstart-list at redhat.com > >>>>> https://www.redhat.com/mailman/listinfo/kickstart-list > >>>> > >>>> _______________________________________________ > >>>> Kickstart-list mailing list > >>>> Kickstart-list at redhat.com > >>>> https://www.redhat.com/mailman/listinfo/kickstart-list > >> > >> _______________________________________________ > >> Kickstart-list mailing list > >> Kickstart-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- =========================== Ron Reed RedHat Certified Engineer SGP Computer Department Manager Unix Systems Administrator ARM SGP CART Site (580)388-4053 ron.reed at arm.gov From brilong at cisco.com Tue Feb 8 17:47:21 2005 From: brilong at cisco.com (Brian Long) Date: Tue, 08 Feb 2005 12:47:21 -0500 Subject: initrd.img module loading In-Reply-To: <1107883223.2977.50.camel@ronnote> References: <1107883223.2977.50.camel@ronnote> Message-ID: <1107884842.6410.51.camel@localhost.localdomain> On Tue, 2005-02-08 at 11:20 -0600, Ronald Reed wrote: > Maybe I am misunderstanding what is being said or I am not making myself > clear. > > This is a fresh kickstart install, with a standard RedHat Enterprise 3.0 > boot image and kickstart file. (I am customizing a kickstart CD, but it > is the standard bootdisk.img file for the CD boot) > > When the install starts, it finds the megaraid device first and assigns > it as /dev/sda. This makes anaconda format and install to the wrong raid > set. > > I guess I could remake the initrd.img for the install, but I am not sure > what options to use to make a new initrd.img for the bootdisk.img so > that it still has all the options that it currently has in it, but just > load the aacraid driver before it loads the megaraid one. What does it detect the aacraid device as? /dev/sdb? If so, why don't you use the bootloader option mentioned previously to get grub to use sdb as the boot drive? /Brian/ -- Brian Long | | | IT Data Center Systems | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s From rreed at ops.sgp.arm.gov Tue Feb 8 17:53:15 2005 From: rreed at ops.sgp.arm.gov (Ronald Reed) Date: Tue, 08 Feb 2005 11:53:15 -0600 Subject: initrd.img module loading In-Reply-To: <1107884842.6410.51.camel@localhost.localdomain> References: <1107883223.2977.50.camel@ronnote> <1107884842.6410.51.camel@localhost.localdomain> Message-ID: <1107885195.2977.54.camel@ronnote> Yes, the aacraid device get set to /dev/sdb. The accraid device is a mirrored pair of 36GB drives that are inside the hardware. The megaraid device is a Raid 5 group of 4 73GB drives (3 in the array, and 1 hot spare). The megaraid is to be used for NFS file storage and the accraid is to be used for the system drive. Ron On Tue, 2005-02-08 at 11:47, Brian Long wrote: > What does it detect the aacraid device as? /dev/sdb? If so, why don't > you use the bootloader option mentioned previously to get grub to use > sdb as the boot drive? > > /Brian/ -- =========================== Ron Reed RedHat Certified Engineer SGP Computer Department Manager Unix Systems Administrator ARM SGP CART Site (580)388-4053 ron.reed at arm.gov From ebrown at lanl.gov Tue Feb 8 17:58:14 2005 From: ebrown at lanl.gov (Ed Brown) Date: Tue, 08 Feb 2005 10:58:14 -0700 Subject: initrd.img module loading In-Reply-To: <1107885195.2977.54.camel@ronnote> References: <1107883223.2977.50.camel@ronnote> <1107884842.6410.51.camel@localhost.localdomain> <1107885195.2977.54.camel@ronnote> Message-ID: <1107885494.23264.117.camel@edbrown.lanl.gov> The --driveorder option won't change the drive letter assignments, but it will change the drive that grub is installed to. Isn't that what you are after? In your case, you probably want: bootloader --driveorder=sdb,sda --location=mbr -Ed On Tue, 2005-02-08 at 10:53, Ronald Reed wrote: > Yes, the aacraid device get set to /dev/sdb. The accraid device is a > mirrored pair of 36GB drives that are inside the hardware. The megaraid > device is a Raid 5 group of 4 73GB drives (3 in the array, and 1 hot > spare). The megaraid is to be used for NFS file storage and the accraid > is to be used for the system drive. > > Ron > > On Tue, 2005-02-08 at 11:47, Brian Long wrote: > > > What does it detect the aacraid device as? /dev/sdb? If so, why don't > > you use the bootloader option mentioned previously to get grub to use > > sdb as the boot drive? > > > > /Brian/ From ebrown at lanl.gov Tue Feb 8 18:18:55 2005 From: ebrown at lanl.gov (Ed Brown) Date: Tue, 08 Feb 2005 11:18:55 -0700 Subject: initrd.img module loading In-Reply-To: <1107885494.23264.117.camel@edbrown.lanl.gov> References: <1107883223.2977.50.camel@ronnote> <1107884842.6410.51.camel@localhost.localdomain> <1107885195.2977.54.camel@ronnote> <1107885494.23264.117.camel@edbrown.lanl.gov> Message-ID: <1107886735.23264.133.camel@edbrown.lanl.gov> In case it's not immediately apparent, with respect to the OS itself, you would use '--ondisk sdb' in your partition entries. -Ed On Tue, 2005-02-08 at 10:58, Ed Brown wrote: > The --driveorder option won't change the drive letter assignments, but > it will change the drive that grub is installed to. Isn't that what you > are after? In your case, you probably want: > > bootloader --driveorder=sdb,sda --location=mbr > > -Ed > > > On Tue, 2005-02-08 at 10:53, Ronald Reed wrote: > > Yes, the aacraid device get set to /dev/sdb. The accraid device is a > > mirrored pair of 36GB drives that are inside the hardware. The megaraid > > device is a Raid 5 group of 4 73GB drives (3 in the array, and 1 hot > > spare). The megaraid is to be used for NFS file storage and the accraid > > is to be used for the system drive. > > > > Ron > > > > On Tue, 2005-02-08 at 11:47, Brian Long wrote: > > > > > What does it detect the aacraid device as? /dev/sdb? If so, why don't > > > you use the bootloader option mentioned previously to get grub to use > > > sdb as the boot drive? > > > > > > /Brian/ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From rreed at ops.sgp.arm.gov Tue Feb 8 18:27:30 2005 From: rreed at ops.sgp.arm.gov (Ronald Reed) Date: Tue, 08 Feb 2005 12:27:30 -0600 Subject: initrd.img module loading In-Reply-To: <1107885494.23264.117.camel@edbrown.lanl.gov> References: <1107883223.2977.50.camel@ronnote> <1107884842.6410.51.camel@localhost.localdomain> <1107885195.2977.54.camel@ronnote> <1107885494.23264.117.camel@edbrown.lanl.gov> Message-ID: <1107887249.2977.56.camel@ronnote> No, I need the drive letter assignments to be different. Ron On Tue, 2005-02-08 at 11:58, Ed Brown wrote: > The --driveorder option won't change the drive letter assignments, but > it will change the drive that grub is installed to. Isn't that what you > are after? In your case, you probably want: > > bootloader --driveorder=sdb,sda --location=mbr > > -Ed > > > On Tue, 2005-02-08 at 10:53, Ronald Reed wrote: > > Yes, the aacraid device get set to /dev/sdb. The accraid device is a > > mirrored pair of 36GB drives that are inside the hardware. The megaraid > > device is a Raid 5 group of 4 73GB drives (3 in the array, and 1 hot > > spare). The megaraid is to be used for NFS file storage and the accraid > > is to be used for the system drive. > > > > Ron > > > > On Tue, 2005-02-08 at 11:47, Brian Long wrote: > > > > > What does it detect the aacraid device as? /dev/sdb? If so, why don't > > > you use the bootloader option mentioned previously to get grub to use > > > sdb as the boot drive? > > > > > > /Brian/ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- =========================== Ron Reed RedHat Certified Engineer SGP Computer Department Manager Unix Systems Administrator ARM SGP CART Site (580)388-4053 ron.reed at arm.gov From jskohli at gmail.com Wed Feb 9 04:03:20 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Wed, 9 Feb 2005 09:33:20 +0530 Subject: Out of Disk Space !! In-Reply-To: References: <27ecd449050208083619e00c3f@mail.gmail.com> Message-ID: <27ecd449050208200373c6f106@mail.gmail.com> Thanks a lot for your reply I'll get back to you soon, after working on that. Thanks a lot On Tue, 08 Feb 2005 10:45:56 -0600, Peter Eisch wrote: > > If you look at 'pivotroot' down in the source, you'll see that stage2.img > gets mounted as the new / during the install. Whatever drivers you updated > in initrd.img will also need to be updated on the new / image loaded from > stage2.img. > > What Drivers? ... the drivers for whatever controller your target install > disk is connected. > > On 2/8/05 10:36 AM, "Jaswinder Singh Kohli" wrote: > > > Installing only bare minimum system, to act as gateway and proxy server. > > All the partitions are correctly formatted. > > > > I am using stripped down, buildinstall which only updates, initrd.img > > and not the other files. > > > > Since building stage2.img using buildinstall, requires lot of other > > packages to be in the > > install tree, for X and others, which i dont' want to include, as it > > is for proxy server > > and very small image. > > > > And what kind of drivers ??? > > > > > > On Tue, 08 Feb 2005 10:16:05 -0600, Peter Eisch wrote: > >> > >> You probably don't have drivers for that particular kernel that you are now > >> booting from in the stage2.img. Whatever you did to update the boot > >> initrd.img, also do to the stage2.img. > >> > >> peter > >> > >> On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" wrote: > >> > >>> Hi, > >>> > >>> I am getting this error while installation, using the ks.cfg which > >>> partitions the drive into > >>> three partitions, / = 1 G > >>> swap = 1 G > >>> /var = rest of space ( 30 + G) > >>> > >>> The cd image that i built had modified stage2.img, ( took care of > >>> .buildstamp) > >>> bootdisks upgraded to kernel 2.6.10..., > >>> Only Modified isolinux/initrd.img is used, rest of the files like, > >>> stage2.img and hdstg2.img > >>> are just repackaged version of what were on Original FC3 Iso's, only > >>> changed .buildstamp > >>> > >>> Now when i booot that CD, the boots up, detects hardware, anaconda starts X > >>> The partitions are created and formatted, but then the Install ends > >>> with a message. > >>> > >>> "An error occured while transfering install image to your harddrive . > >>> You are probably > >>> out of disk space" > >>> > >>> Where as when i perform fdisk -l on tty2, which shows, all the > >>> partitions were created > >>> and also on console 6 the formatting was successful and hence lot of > >>> space is there. > >>> > >>> On tty3, the detailed error message is as follows... > >>> > >>> Error transfering stage2.img: [Errno 2] No such file of directory: > >>> '/mnt/sysimage/proc/rhinstall-stage2.img' > >>> > >>> I did a search on google, and archives, came up with no results. > >>> > >>> Can any one tell me what i am missing or doing wrong and why it is > >>> trying to copy > >>> rhinstall-stage2.img from some proc fs instead of stage2.img from CD. > >>> > >>> I am stuck at this point for too long now, any Pointers, any ideas, > >>> will be helpful, that can > >>> get me going in forward direction. > >>> > >>> Thanks.... > >> > >> _______________________________________________ > >> Kickstart-list mailing list > >> Kickstart-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/kickstart-list > >> > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Regards JSK jskohli (AT) gmail (DOT) com From Chris.McKenzie at entrust.com Wed Feb 9 23:33:48 2005 From: Chris.McKenzie at entrust.com (Chris Mckenzie) Date: Wed, 9 Feb 2005 18:33:48 -0500 Subject: Kickstart hangs when removing sendmail Message-ID: So I sort of solved it last week. This is an FYI I suppose. Nothing worked, kickstart -sendmail, rpm -e sendmail, etc... I had to actually start sendmail, then kill -killall sendmail, THEN rpm -e sendmail. It's a tatoo, and I just sanded it off. This is followed with the existing Postfix install with support for Postgres. Thanks for the suggestions. - Chris -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Chris Mckenzie Sent: January 31, 2005 2:59 PM To: 'Discussion list about Kickstart' Subject: RE: Kickstart hangs when removing sendmail Thanks for the suggestions guys. We're not installing the RH Postfix. We're using PostgreSQL not MySQL and the Postfix that ships with RH doesn't include support for Postgres. I'm installing Postfix with Postgres support as part of the kickstart %post. My problem is no matter what I try I can't not install sendmail when stick strictly to the %packages portion of the kickstart. %packages --resolvedeps gcc make openssh openssh-clients openssh-server patch perl perl-CGI perl-DBI perl-HTML-Parser perl-libwww-perl perl-URI openssl openssl-perl rdate rpm-build rpmdb-redhat sharutils sudo telnet unzip wget up2date eject -sendmail I know I set --resolvedeps, so something in there wants it (or maybe Anaconda itself simply wants it) If I try ot remove it from %post, it sometimes never returns... rpm -e sendmail --nodeps Note the --nodeps, so I don't get the dependancy errors. Once Postfix is installed, those complaints don't mean a thing, it just works as expected. So I tried the following trickery... RETURN=`rpm -e sendmail --nodeps& 2>&1 > /dev/null` ilimit=60 isleep=1 for ((i=0 ; i < ilimit ; i++)); do RETURN=`rpm -q sendmail | grep "not installed"` if [ "$RETURN" ]; then # Sendmail has finally been removed... echo " -> Sendmail has been removed" break fi done Haven't had time to test it yet, but the idea is if `rpm -e sendmail` never retrurns sometimes, I might as well spawn it as a background process and watch the `rpm -q sendmail` for the removal itself. (I noticed that when I get the hang, a reboot and login shows sendmail not installed) Very frustrating, but I wouldn't care so much if Postfix didn't' need sendmail removed. (their docs claim so, and our testing indiciated some incompatibiltiies) Thanks again for the help. - Chris -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com ] On Behalf Of Edgar Chill?n 'Chillux' Sent: January 28, 2005 12:32 PM To: Discussion list about Kickstart Subject: Re: Kickstart hangs when removing sendmail I dont remember if postfix requires a sendmail as a dependency but if not here is the solution: In the ks.cfg in the package system: @ Base -mdam -sendmail In the %post rpm -ihv postfix If the postfix needs dependencys obviusly you have to install it fist. Regards --- Chris Mckenzie escribi?: > Hi all. > > My kickstart occasionally hangs indefinitely > intermittedly when from my > %post I call: > > rpm -e sendmail > > I subsequently install Postfix, and I absolutely > require Sendmail removed > before hand. > > It's inexplicable. Rpm never returns, the %post just > sits there. > > Any ideas? I can't pipe STDERR, and the damn thing > never returns. When I do > get the hang, I'm already on TTY3, and none of the > other TTYs offer any > clues. > > Thanks!!! > > - Chris > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list ===== -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- Edgar Alberto Chill?n Esc?rcega Mobile: 04455-1951-9194 -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- PublicKeyID: 0x584CF620 [DH/DSS] http://keyserver.noreply.org/ FingerPrint: 1EDE EF26 C6AA 17DC 1A59 97C8 5270 1942 584C F620 -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- _________________________________________________________ Do You Yahoo!? La mejor conexi?n a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From e_chillon at yahoo.com.mx Fri Feb 11 16:11:31 2005 From: e_chillon at yahoo.com.mx (=?iso-8859-1?q?Edgar=20Chill=F3n=20'Chillux'?=) Date: Fri, 11 Feb 2005 10:11:31 -0600 (CST) Subject: Kickstart hangs when removing sendmail In-Reply-To: Message-ID: <20050211161132.8567.qmail@web52208.mail.yahoo.com> I had the same problem, you can not uninstall sendmail if you dont unistall firt the mdam. So in the kikstart you must have to put: -mdam -sendmail Expect to solve your problem. Regards. --- Chris Mckenzie escribi?: > So I sort of solved it last week. This is an FYI I > suppose. > > Nothing worked, kickstart -sendmail, rpm -e > sendmail, etc... I had to > actually start sendmail, then kill -killall > sendmail, THEN rpm -e sendmail. > It's a tatoo, and I just sanded it off. > > This is followed with the existing Postfix install > with support for > Postgres. > > Thanks for the suggestions. > > - Chris > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf > Of Chris Mckenzie > Sent: January 31, 2005 2:59 PM > To: 'Discussion list about Kickstart' > Subject: RE: Kickstart hangs when removing sendmail > > > > Thanks for the suggestions guys. We're not > installing the RH Postfix. We're > using PostgreSQL not MySQL and the Postfix that > ships with RH doesn't > include support for Postgres. > > I'm installing Postfix with Postgres support as part > of the kickstart %post. > > > My problem is no matter what I try I can't not > install sendmail when stick > strictly to the %packages portion of the kickstart. > > %packages --resolvedeps > gcc > make > openssh > openssh-clients > openssh-server > patch > perl > perl-CGI > perl-DBI > perl-HTML-Parser > perl-libwww-perl > perl-URI > openssl > openssl-perl > rdate > rpm-build > rpmdb-redhat > sharutils > sudo > telnet > unzip > wget > up2date > eject > -sendmail > > I know I set --resolvedeps, so something in there > wants it (or maybe > Anaconda itself simply wants it) > > If I try ot remove it from %post, it sometimes never > returns... > > rpm -e sendmail --nodeps > > Note the --nodeps, so I don't get the dependancy > errors. Once Postfix is > installed, those complaints don't mean a thing, it > just works as expected. > > So I tried the following trickery... > > RETURN=`rpm -e sendmail --nodeps& 2>&1 > > /dev/null` > ilimit=60 > isleep=1 > for ((i=0 ; i < ilimit ; i++)); do > RETURN=`rpm -q sendmail | grep "not installed"` > if [ "$RETURN" ]; then > # Sendmail has finally been removed... > echo " -> Sendmail has been removed" > break > fi > done > > Haven't had time to test it yet, but the idea is if > `rpm -e sendmail` never > retrurns sometimes, I might as well spawn it as a > background process and > watch the `rpm -q sendmail` for the removal itself. > (I noticed that when I > get the hang, a reboot and login shows sendmail not > installed) > > Very frustrating, but I wouldn't care so much if > Postfix didn't' need > sendmail removed. (their docs claim so, and our > testing indiciated some > incompatibiltiies) > > Thanks again for the help. > > - Chris > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com > ] On > Behalf Of Edgar Chill?n > 'Chillux' > Sent: January 28, 2005 12:32 PM > To: Discussion list about Kickstart > Subject: Re: Kickstart hangs when removing sendmail > > > I dont remember if postfix requires a sendmail as a > dependency but if not here is the solution: > > In the ks.cfg in the package system: > @ Base > -mdam > -sendmail > > In the %post > rpm -ihv postfix > > If the postfix needs dependencys obviusly you have > to > install it fist. > > Regards > > --- Chris Mckenzie > escribi?: > > Hi all. > > > > My kickstart occasionally hangs indefinitely > > intermittedly when from my > > %post I call: > > > > rpm -e sendmail > > > > I subsequently install Postfix, and I absolutely > > require Sendmail removed > > before hand. > > > > It's inexplicable. Rpm never returns, the %post > just > > sits there. > > > > Any ideas? I can't pipe STDERR, and the damn thing > > > never returns. When I do > > get the hang, I'm already on TTY3, and none of the > > > other TTYs offer any > > clues. > > > > Thanks!!! > > > > - Chris > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > ===== > -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- > > Edgar Alberto Chill?n Esc?rcega > Mobile: 04455-1951-9194 > -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- > > PublicKeyID: 0x584CF620 [DH/DSS] > http://keyserver.noreply.org/ > > FingerPrint: 1EDE EF26 C6AA 17DC 1A59 97C8 5270 > 1942 584C F620 > -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- > > > _________________________________________________________ > > Do You Yahoo!? > La mejor conexi?n a internet y 25MB extra a tu > correo por $100 al mes. > http://net.yahoo.com.mx > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list ===== Saludos. ________________________________ Edgar Alberto Chill?n Esc?rcega Out Sourcer Pfizer S.A. de C.V. Security Consultant - M?xico DF Tel: (55) 59 81 85 00 ext. 9060 Mobile: 04455-1951-9194 PublicKeyID: 0x584CF620 [DH/DSS] http://keyserver.noreply.org/ FingerPrint: 1EDE EF26 C6AA 17DC 1A59 97C8 5270 1942 584C F620 _________________________________________________________ Do You Yahoo!? La mejor conexi?n a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx From jskohli at gmail.com Mon Feb 14 11:50:20 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Mon, 14 Feb 2005 17:20:20 +0530 Subject: Out of Disk Space !! In-Reply-To: <27ecd449050208200373c6f106@mail.gmail.com> References: <27ecd449050208083619e00c3f@mail.gmail.com> <27ecd449050208200373c6f106@mail.gmail.com> Message-ID: <27ecd44905021403505df10b78@mail.gmail.com> Hi, Again same error, but the problem is very strange as i like to relate it to hardware this time. The system is cPCI-6860 Board, with SCSI Controller, mpt drivers are loaded. Two Seagate SCSI disks are attached. Just after printing Starting Anaconda, Fedora Core System Installer... it prints following lines which i guess leads to outta disk space problem.... error -2147483630 reading header: cpio read failed - Success error -2147483630 reading header: cpio read failed - Success or sometimes related to gzlib a little later detects Monitor(SyncMaster) and Graphics Cards ( ATI Mach64) and Mouse Everything goes fine until the system formats and then trying to Transfer the install image to hard drive. The same thing works fine on other systems such as, standard P4 Machine with HT The cPCI Machine has 2 xeon HT processors, ECC 1024M RAM. Earlier it also gave problems with SCSI1 disk, as the system hanged for indefinate time . with the status light of SCSI1 disk glowing, where as SCSI0 was fine. Just upgraded anaconda to version latest from development branch still the cpio/gzlib problem remains. As we have 3 of such systems and all of them exhibiting same problem. where as same CD works fine on other systems. Can it be due to some hardware incompatibility with anaconda. On Wed, 9 Feb 2005 09:33:20 +0530, Jaswinder Singh Kohli wrote: > Thanks a lot for your reply > I'll get back to you soon, after working on that. > > Thanks a lot > > > On Tue, 08 Feb 2005 10:45:56 -0600, Peter Eisch wrote: > > > > If you look at 'pivotroot' down in the source, you'll see that stage2.img > > gets mounted as the new / during the install. Whatever drivers you updated > > in initrd.img will also need to be updated on the new / image loaded from > > stage2.img. > > > > What Drivers? ... the drivers for whatever controller your target install > > disk is connected. > > > > On 2/8/05 10:36 AM, "Jaswinder Singh Kohli" wrote: > > > > > Installing only bare minimum system, to act as gateway and proxy server. > > > All the partitions are correctly formatted. > > > > > > I am using stripped down, buildinstall which only updates, initrd.img > > > and not the other files. > > > > > > Since building stage2.img using buildinstall, requires lot of other > > > packages to be in the > > > install tree, for X and others, which i dont' want to include, as it > > > is for proxy server > > > and very small image. > > > > > > And what kind of drivers ??? > > > > > > > > > On Tue, 08 Feb 2005 10:16:05 -0600, Peter Eisch wrote: > > >> > > >> You probably don't have drivers for that particular kernel that you are now > > >> booting from in the stage2.img. Whatever you did to update the boot > > >> initrd.img, also do to the stage2.img. > > >> > > >> peter > > >> > > >> On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" wrote: > > >> > > >>> Hi, > > >>> > > >>> I am getting this error while installation, using the ks.cfg which > > >>> partitions the drive into > > >>> three partitions, / = 1 G > > >>> swap = 1 G > > >>> /var = rest of space ( 30 + G) > > >>> > > >>> The cd image that i built had modified stage2.img, ( took care of > > >>> .buildstamp) > > >>> bootdisks upgraded to kernel 2.6.10..., > > >>> Only Modified isolinux/initrd.img is used, rest of the files like, > > >>> stage2.img and hdstg2.img > > >>> are just repackaged version of what were on Original FC3 Iso's, only > > >>> changed .buildstamp > > >>> > > >>> Now when i booot that CD, the boots up, detects hardware, anaconda starts X > > >>> The partitions are created and formatted, but then the Install ends > > >>> with a message. > > >>> > > >>> "An error occured while transfering install image to your harddrive . > > >>> You are probably > > >>> out of disk space" > > >>> > > >>> Where as when i perform fdisk -l on tty2, which shows, all the > > >>> partitions were created > > >>> and also on console 6 the formatting was successful and hence lot of > > >>> space is there. > > >>> > > >>> On tty3, the detailed error message is as follows... > > >>> > > >>> Error transfering stage2.img: [Errno 2] No such file of directory: > > >>> '/mnt/sysimage/proc/rhinstall-stage2.img' > > >>> > > >>> I did a search on google, and archives, came up with no results. > > >>> > > >>> Can any one tell me what i am missing or doing wrong and why it is > > >>> trying to copy > > >>> rhinstall-stage2.img from some proc fs instead of stage2.img from CD. > > >>> > > >>> I am stuck at this point for too long now, any Pointers, any ideas, > > >>> will be helpful, that can > > >>> get me going in forward direction. > > >>> > > >>> Thanks.... > > >> > > >> _______________________________________________ > > >> Kickstart-list mailing list > > >> Kickstart-list at redhat.com > > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > >> > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > -- > Regards > JSK > jskohli (AT) gmail (DOT) com > -- Regards JSK jskohli (AT) gmail (DOT) com From jskohli at gmail.com Wed Feb 16 05:07:47 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Wed, 16 Feb 2005 10:37:47 +0530 Subject: Out of Disk Space !! In-Reply-To: <003101c51291$9b34e4e0$fd00a8c0@moacyr> References: <27ecd449050208083619e00c3f@mail.gmail.com> <27ecd449050208200373c6f106@mail.gmail.com> <27ecd44905021403505df10b78@mail.gmail.com> <003101c51291$9b34e4e0$fd00a8c0@moacyr> Message-ID: <27ecd449050215210712e6784d@mail.gmail.com> Hi Moacyr, Out of space and outta luck now.... The above thing doesn't work. It is always giving same error, error -2147483630 reading header: cpio read failed - Success and on conole 3, Error transfering stage2.img: [Errorno 2]: No such file or directory: '/mnt/sysimage/proc/rhinstall-stage2.img' and on console 4, <4> Error -3 while decompressing ! Is there anywhere i can seee, the detailed log file and post it over here, as to help it analyse. This problem might be related to anaconda and my hardware compatibility The installation of RedHat 9 proceeds quite well. I tested it for nearly 5-7 times to give any error remotely of same nature as this, but the hardware worked fine with Redhat 9. I am totally stuck, don't know, what is it to be worked on, Hardware, Linux kernel, or the Anaconda. Any directions here with anything.... ---Hardware Specs--- ----START---- Product Specifications cPCI-6860 6U/8TE system slot CPU board, PCI 2.1 and PICMG? 2.1 hot swap compliant, 64-bit/66MHz PCI interface, PICMG 2.16 and 2.9 (IPMI) compliant Dual low-voltage Xeon CPU 1.6/1,8/2.0GHz with 400MHz FSB or single Xeon CPU up to 2.4GHz, CPU's each with 512k L2 Intel E7500 memory control hub Intel 82801CA I/O control hub Intel 82870P2 PCI/PCI-X 64-Bit hub Intel 21154 PCI/PCI bridge to J1/J2 64-bit/66MHz Up to 7 I/O slots 33MHz or 4 slots 66MHz 1GB/2GB/4GB dual channel DDR200 ECC RAM Two Gigabit Ethernet ports (front/rear/PICMG2.16) (82546 via PCI-X bus), one 10/100BaseTX port (82559ER) Intel PXE remote boot support ATI Rage-XL graphic controller 8MB VRAM, resolution up to 1600x1200x32 One RS232, two USB 1.1, and a PS/2 MS/KB port on FP Award/Phoenix PnP BIOS in Flash HW monitor (W83782D) and Watchdog (1s up to 255min) Product Specifications Transition Module cPCI-R6860 Intel 82870P2 PCI/PCI-X 64-bit hub 2 Gigabit Ethernet ports (82546 via PCI-X bus) Ultra-160 SCSI port (SYS53C1000R) Floppy interface, 2 ATA100 ports, PC Card slot 1 RS232 and 2 USB 1.1 ports, opt. management port VGA and PS/2 mouse/keyboard lead out at RP ----END---- On Mon, 14 Feb 2005 10:35:03 -0200, Moacyr Leite da Silva wrote: > Hi Jaswinder > > Try to run this > > linux ks=floppy allowcddma > > Reference - Installation Error Out Of Disk Space > http://www.fedoraforum.org/forum/archive/index.php/t-1834.html > > I have this problem with some machines. > > My Best Regards, > > Moacyr Leite da Silva > www.akadnyx.com.br > www.opensourceuniversity.com.br > > > ----- Original Message ----- > From: "Jaswinder Singh Kohli" > To: "Discussion list about Kickstart" > Sent: Monday, February 14, 2005 9:50 AM > Subject: Re: Out of Disk Space !! > > > Hi, > > Again same error, but the problem is very strange as i like to relate > > it to hardware this time. > > > > The system is cPCI-6860 Board, with SCSI Controller, mpt drivers are > loaded. > > Two Seagate SCSI disks are attached. > > > > Just after printing Starting Anaconda, Fedora Core System Installer... > > it prints following lines which i guess leads to outta disk space > problem.... > > > > error -2147483630 reading header: cpio read failed - Success > > error -2147483630 reading header: cpio read failed - Success > > or sometimes related to gzlib > > > > a little later detects Monitor(SyncMaster) and Graphics Cards ( ATI > > Mach64) and Mouse > > > > Everything goes fine until the system formats and then trying to > > Transfer the install image > > to hard drive. > > > > The same thing works fine on other systems such as, standard P4 Machine > with HT > > > > The cPCI Machine has 2 xeon HT processors, ECC 1024M RAM. > > > > Earlier it also gave problems with SCSI1 disk, as the system hanged > > for indefinate time . > > with the status light of SCSI1 disk glowing, where as SCSI0 was fine. > > > > Just upgraded anaconda to version latest from development branch still > > the cpio/gzlib > > problem remains. > > > > As we have 3 of such systems and all of them exhibiting same problem. > > where as same CD works fine on other systems. > > Can it be due to some hardware incompatibility with anaconda. > > > > > > On Wed, 9 Feb 2005 09:33:20 +0530, Jaswinder Singh Kohli > > wrote: > > > Thanks a lot for your reply > > > I'll get back to you soon, after working on that. > > > > > > Thanks a lot > > > > > > > > > On Tue, 08 Feb 2005 10:45:56 -0600, Peter Eisch wrote: > > > > > > > > If you look at 'pivotroot' down in the source, you'll see that > stage2.img > > > > gets mounted as the new / during the install. Whatever drivers you > updated > > > > in initrd.img will also need to be updated on the new / image loaded > from > > > > stage2.img. > > > > > > > > What Drivers? ... the drivers for whatever controller your target > install > > > > disk is connected. > > > > > > > > On 2/8/05 10:36 AM, "Jaswinder Singh Kohli" wrote: > > > > > > > > > Installing only bare minimum system, to act as gateway and proxy > server. > > > > > All the partitions are correctly formatted. > > > > > > > > > > I am using stripped down, buildinstall which only updates, > initrd.img > > > > > and not the other files. > > > > > > > > > > Since building stage2.img using buildinstall, requires lot of other > > > > > packages to be in the > > > > > install tree, for X and others, which i dont' want to include, as it > > > > > is for proxy server > > > > > and very small image. > > > > > > > > > > And what kind of drivers ??? > > > > > > > > > > > > > > > On Tue, 08 Feb 2005 10:16:05 -0600, Peter Eisch > wrote: > > > > >> > > > > >> You probably don't have drivers for that particular kernel that you > are now > > > > >> booting from in the stage2.img. Whatever you did to update the > boot > > > > >> initrd.img, also do to the stage2.img. > > > > >> > > > > >> peter > > > > >> > > > > >> On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" > wrote: > > > > >> > > > > >>> Hi, > > > > >>> > > > > >>> I am getting this error while installation, using the ks.cfg which > > > > >>> partitions the drive into > > > > >>> three partitions, / = 1 G > > > > >>> swap = 1 G > > > > >>> /var = rest of space ( 30 + G) > > > > >>> > > > > >>> The cd image that i built had modified stage2.img, ( took care of > > > > >>> .buildstamp) > > > > >>> bootdisks upgraded to kernel 2.6.10..., > > > > >>> Only Modified isolinux/initrd.img is used, rest of the files like, > > > > >>> stage2.img and hdstg2.img > > > > >>> are just repackaged version of what were on Original FC3 Iso's, > only > > > > >>> changed .buildstamp > > > > >>> > > > > >>> Now when i booot that CD, the boots up, detects hardware, anaconda > starts X > > > > >>> The partitions are created and formatted, but then the Install > ends > > > > >>> with a message. > > > > >>> > > > > >>> "An error occured while transfering install image to your > harddrive . > > > > >>> You are probably > > > > >>> out of disk space" > > > > >>> > > > > >>> Where as when i perform fdisk -l on tty2, which shows, all the > > > > >>> partitions were created > > > > >>> and also on console 6 the formatting was successful and hence lot > of > > > > >>> space is there. > > > > >>> > > > > >>> On tty3, the detailed error message is as follows... > > > > >>> > > > > >>> Error transfering stage2.img: [Errno 2] No such file of directory: > > > > >>> '/mnt/sysimage/proc/rhinstall-stage2.img' > > > > >>> > > > > >>> I did a search on google, and archives, came up with no results. > > > > >>> > > > > >>> Can any one tell me what i am missing or doing wrong and why it is > > > > >>> trying to copy > > > > >>> rhinstall-stage2.img from some proc fs instead of stage2.img from > CD. > > > > >>> > > > > >>> I am stuck at this point for too long now, any Pointers, any > ideas, > > > > >>> will be helpful, that can > > > > >>> get me going in forward direction. > > > > >>> > > > > >>> Thanks.... > > > > >> > > > > >> _______________________________________________ > > > > >> Kickstart-list mailing list > > > > >> Kickstart-list at redhat.com > > > > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > > > >> > > > > > > > > > > > > > _______________________________________________ > > > > Kickstart-list mailing list > > > > Kickstart-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > > > > > > -- > > > Regards > > > JSK > > > jskohli (AT) gmail (DOT) com > > > > > > > > > -- > > Regards > > JSK > > jskohli (AT) gmail (DOT) com > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > -- Regards JSK jskohli (AT) gmail (DOT) com From peter at boku.net Wed Feb 16 12:15:23 2005 From: peter at boku.net (Peter Eisch) Date: Wed, 16 Feb 2005 06:15:23 -0600 Subject: Out of Disk Space !! In-Reply-To: <27ecd449050215210712e6784d@mail.gmail.com> Message-ID: The only thing I could think of is that the driver for the controller that the cdrom is connected through isn't included in the drivers in stage2.img. This would keep the sysimage from mounting as anaconda is about to begin the install. Does the install iso have the stage2.img or /mnt/sysimage/proc/rhinstall-stage2.img on it? If that didn't get updated in the shuffle of updates or got lost, that could be a problem. peter On 2/15/05 11:07 PM, "Jaswinder Singh Kohli" wrote: > Hi Moacyr, > Out of space and outta luck now.... > The above thing doesn't work. > It is always giving same error, > error -2147483630 reading header: cpio read failed - Success > > and on conole 3, > Error transfering stage2.img: [Errorno 2]: No such file or directory: > '/mnt/sysimage/proc/rhinstall-stage2.img' > > and on console 4, > <4> Error -3 while decompressing ! > > Is there anywhere i can seee, the detailed log file and post it over > here, as to help it > analyse. This problem might be related to anaconda and my hardware > compatibility > > The installation of RedHat 9 proceeds quite well. I tested it for > nearly 5-7 times to > give any error remotely of same nature as this, but the hardware > worked fine with > Redhat 9. > > I am totally stuck, don't know, what is it to be worked on, Hardware, > Linux kernel, or the > Anaconda. > > Any directions here with anything.... > > > ---Hardware Specs--- > ----START---- > Product Specifications cPCI-6860 > 6U/8TE system slot CPU board, PCI 2.1 and PICMG? 2.1 hot swap > compliant, 64-bit/66MHz PCI interface, PICMG 2.16 and 2.9 (IPMI) > compliant > Dual low-voltage Xeon CPU 1.6/1,8/2.0GHz with 400MHz FSB or single > Xeon CPU up to 2.4GHz, CPU's each with 512k L2 > Intel E7500 memory control hub > Intel 82801CA I/O control hub > Intel 82870P2 PCI/PCI-X 64-Bit hub > Intel 21154 PCI/PCI bridge to J1/J2 64-bit/66MHz > Up to 7 I/O slots 33MHz or 4 slots 66MHz > 1GB/2GB/4GB dual channel DDR200 ECC RAM > Two Gigabit Ethernet ports (front/rear/PICMG2.16) (82546 via PCI-X > bus), one 10/100BaseTX port (82559ER) > Intel PXE remote boot support > ATI Rage-XL graphic controller 8MB VRAM, resolution up to 1600x1200x32 > One RS232, two USB 1.1, and a PS/2 MS/KB port on FP > Award/Phoenix PnP BIOS in Flash > HW monitor (W83782D) and Watchdog (1s up to 255min) > > Product Specifications Transition Module cPCI-R6860 > Intel 82870P2 PCI/PCI-X 64-bit hub > 2 Gigabit Ethernet ports (82546 via PCI-X bus) > Ultra-160 SCSI port (SYS53C1000R) > Floppy interface, 2 ATA100 ports, PC Card slot > 1 RS232 and 2 USB 1.1 ports, opt. management port > VGA and PS/2 mouse/keyboard lead out at RP > ----END---- > > On Mon, 14 Feb 2005 10:35:03 -0200, Moacyr Leite da Silva > wrote: >> Hi Jaswinder >> >> Try to run this >> >> linux ks=floppy allowcddma >> >> Reference - Installation Error Out Of Disk Space >> http://www.fedoraforum.org/forum/archive/index.php/t-1834.html >> >> I have this problem with some machines. >> >> My Best Regards, >> >> Moacyr Leite da Silva >> www.akadnyx.com.br >> www.opensourceuniversity.com.br >> >> >> ----- Original Message ----- >> From: "Jaswinder Singh Kohli" >> To: "Discussion list about Kickstart" >> Sent: Monday, February 14, 2005 9:50 AM >> Subject: Re: Out of Disk Space !! >> >>> Hi, >>> Again same error, but the problem is very strange as i like to relate >>> it to hardware this time. >>> >>> The system is cPCI-6860 Board, with SCSI Controller, mpt drivers are >> loaded. >>> Two Seagate SCSI disks are attached. >>> >>> Just after printing Starting Anaconda, Fedora Core System Installer... >>> it prints following lines which i guess leads to outta disk space >> problem.... >>> >>> error -2147483630 reading header: cpio read failed - Success >>> error -2147483630 reading header: cpio read failed - Success >>> or sometimes related to gzlib >>> >>> a little later detects Monitor(SyncMaster) and Graphics Cards ( ATI >>> Mach64) and Mouse >>> >>> Everything goes fine until the system formats and then trying to >>> Transfer the install image >>> to hard drive. >>> >>> The same thing works fine on other systems such as, standard P4 Machine >> with HT >>> >>> The cPCI Machine has 2 xeon HT processors, ECC 1024M RAM. >>> >>> Earlier it also gave problems with SCSI1 disk, as the system hanged >>> for indefinate time . >>> with the status light of SCSI1 disk glowing, where as SCSI0 was fine. >>> >>> Just upgraded anaconda to version latest from development branch still >>> the cpio/gzlib >>> problem remains. >>> >>> As we have 3 of such systems and all of them exhibiting same problem. >>> where as same CD works fine on other systems. >>> Can it be due to some hardware incompatibility with anaconda. >>> >>> >>> On Wed, 9 Feb 2005 09:33:20 +0530, Jaswinder Singh Kohli >>> wrote: >>>> Thanks a lot for your reply >>>> I'll get back to you soon, after working on that. >>>> >>>> Thanks a lot >>>> >>>> >>>> On Tue, 08 Feb 2005 10:45:56 -0600, Peter Eisch wrote: >>>>> >>>>> If you look at 'pivotroot' down in the source, you'll see that >> stage2.img >>>>> gets mounted as the new / during the install. Whatever drivers you >> updated >>>>> in initrd.img will also need to be updated on the new / image loaded >> from >>>>> stage2.img. >>>>> >>>>> What Drivers? ... the drivers for whatever controller your target >> install >>>>> disk is connected. >>>>> >>>>> On 2/8/05 10:36 AM, "Jaswinder Singh Kohli" wrote: >>>>> >>>>>> Installing only bare minimum system, to act as gateway and proxy >> server. >>>>>> All the partitions are correctly formatted. >>>>>> >>>>>> I am using stripped down, buildinstall which only updates, >> initrd.img >>>>>> and not the other files. >>>>>> >>>>>> Since building stage2.img using buildinstall, requires lot of other >>>>>> packages to be in the >>>>>> install tree, for X and others, which i dont' want to include, as it >>>>>> is for proxy server >>>>>> and very small image. >>>>>> >>>>>> And what kind of drivers ??? >>>>>> >>>>>> >>>>>> On Tue, 08 Feb 2005 10:16:05 -0600, Peter Eisch >> wrote: >>>>>>> >>>>>>> You probably don't have drivers for that particular kernel that you >> are now >>>>>>> booting from in the stage2.img. Whatever you did to update the >> boot >>>>>>> initrd.img, also do to the stage2.img. >>>>>>> >>>>>>> peter >>>>>>> >>>>>>> On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" >> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I am getting this error while installation, using the ks.cfg which >>>>>>>> partitions the drive into >>>>>>>> three partitions, / = 1 G >>>>>>>> swap = 1 G >>>>>>>> /var = rest of space ( 30 + G) >>>>>>>> >>>>>>>> The cd image that i built had modified stage2.img, ( took care of >>>>>>>> .buildstamp) >>>>>>>> bootdisks upgraded to kernel 2.6.10..., >>>>>>>> Only Modified isolinux/initrd.img is used, rest of the files like, >>>>>>>> stage2.img and hdstg2.img >>>>>>>> are just repackaged version of what were on Original FC3 Iso's, >> only >>>>>>>> changed .buildstamp >>>>>>>> >>>>>>>> Now when i booot that CD, the boots up, detects hardware, anaconda >> starts X >>>>>>>> The partitions are created and formatted, but then the Install >> ends >>>>>>>> with a message. >>>>>>>> >>>>>>>> "An error occured while transfering install image to your >> harddrive . >>>>>>>> You are probably >>>>>>>> out of disk space" >>>>>>>> >>>>>>>> Where as when i perform fdisk -l on tty2, which shows, all the >>>>>>>> partitions were created >>>>>>>> and also on console 6 the formatting was successful and hence lot >> of >>>>>>>> space is there. >>>>>>>> >>>>>>>> On tty3, the detailed error message is as follows... >>>>>>>> >>>>>>>> Error transfering stage2.img: [Errno 2] No such file of directory: >>>>>>>> '/mnt/sysimage/proc/rhinstall-stage2.img' >>>>>>>> >>>>>>>> I did a search on google, and archives, came up with no results. >>>>>>>> >>>>>>>> Can any one tell me what i am missing or doing wrong and why it is >>>>>>>> trying to copy >>>>>>>> rhinstall-stage2.img from some proc fs instead of stage2.img from >> CD. >>>>>>>> >>>>>>>> I am stuck at this point for too long now, any Pointers, any >> ideas, >>>>>>>> will be helpful, that can >>>>>>>> get me going in forward direction. >>>>>>>> >>>>>>>> Thanks.... >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Kickstart-list mailing list >>>>>>> Kickstart-list at redhat.com >>>>>>> https://www.redhat.com/mailman/listinfo/kickstart-list >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Kickstart-list mailing list >>>>> Kickstart-list at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/kickstart-list >>>>> >>>> >>>> -- >>>> Regards >>>> JSK >>>> jskohli (AT) gmail (DOT) com >>>> >>> >>> >>> -- >>> Regards >>> JSK >>> jskohli (AT) gmail (DOT) com >>> >>> _______________________________________________ >>> Kickstart-list mailing list >>> Kickstart-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/kickstart-list >>> >> >> > From jskohli at gmail.com Wed Feb 16 17:52:12 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Wed, 16 Feb 2005 23:22:12 +0530 Subject: Out of Disk Space !! In-Reply-To: References: <27ecd449050215210712e6784d@mail.gmail.com> Message-ID: <27ecd449050216095232c2389c@mail.gmail.com> Thanks a lot for your reply, Yes, the stage2.img is there, i try to install it on eServer x Series from IBM works without a hitch. Super fine. But when it comes down to this hardware as i have earlier mentioned. I get this problem. The Hardware is cPCI 6860 Board, you can check the exact specs down under. It is Xeon 2 way , 2 Ghz MPT SCSI controller, with 2 40 Gb, Seagate Cheetah Ultra 160 Drives attached. all on single board. The System is from company called ADLINK. Already stuck b/w rock and a hard place, no way to go, tested everything, every idea, that came over here and there. RH9 Install works fine, no error with that, .... any ideas what it could be. The Kernel or anaconda comapatility with the Hardware. I can provide more information, syslog and ancaonda log. Thanks.. On Wed, 16 Feb 2005 06:15:23 -0600, Peter Eisch wrote: > > The only thing I could think of is that the driver for the controller that > the cdrom is connected through isn't included in the drivers in stage2.img. > This would keep the sysimage from mounting as anaconda is about to begin the > install. Does the install iso have the stage2.img or > /mnt/sysimage/proc/rhinstall-stage2.img on it? If that didn't get updated > in the shuffle of updates or got lost, that could be a problem. > > peter > > On 2/15/05 11:07 PM, "Jaswinder Singh Kohli" wrote: > > > Hi Moacyr, > > Out of space and outta luck now.... > > The above thing doesn't work. > > It is always giving same error, > > error -2147483630 reading header: cpio read failed - Success > > > > and on conole 3, > > Error transfering stage2.img: [Errorno 2]: No such file or directory: > > '/mnt/sysimage/proc/rhinstall-stage2.img' > > > > and on console 4, > > <4> Error -3 while decompressing ! > > > > Is there anywhere i can seee, the detailed log file and post it over > > here, as to help it > > analyse. This problem might be related to anaconda and my hardware > > compatibility > > > > The installation of RedHat 9 proceeds quite well. I tested it for > > nearly 5-7 times to > > give any error remotely of same nature as this, but the hardware > > worked fine with > > Redhat 9. > > > > I am totally stuck, don't know, what is it to be worked on, Hardware, > > Linux kernel, or the > > Anaconda. > > > > Any directions here with anything.... > > > > > > ---Hardware Specs--- > > ----START---- > > Product Specifications cPCI-6860 > > 6U/8TE system slot CPU board, PCI 2.1 and PICMG? 2.1 hot swap > > compliant, 64-bit/66MHz PCI interface, PICMG 2.16 and 2.9 (IPMI) > > compliant > > Dual low-voltage Xeon CPU 1.6/1,8/2.0GHz with 400MHz FSB or single > > Xeon CPU up to 2.4GHz, CPU's each with 512k L2 > > Intel E7500 memory control hub > > Intel 82801CA I/O control hub > > Intel 82870P2 PCI/PCI-X 64-Bit hub > > Intel 21154 PCI/PCI bridge to J1/J2 64-bit/66MHz > > Up to 7 I/O slots 33MHz or 4 slots 66MHz > > 1GB/2GB/4GB dual channel DDR200 ECC RAM > > Two Gigabit Ethernet ports (front/rear/PICMG2.16) (82546 via PCI-X > > bus), one 10/100BaseTX port (82559ER) > > Intel PXE remote boot support > > ATI Rage-XL graphic controller 8MB VRAM, resolution up to 1600x1200x32 > > One RS232, two USB 1.1, and a PS/2 MS/KB port on FP > > Award/Phoenix PnP BIOS in Flash > > HW monitor (W83782D) and Watchdog (1s up to 255min) > > > > Product Specifications Transition Module cPCI-R6860 > > Intel 82870P2 PCI/PCI-X 64-bit hub > > 2 Gigabit Ethernet ports (82546 via PCI-X bus) > > Ultra-160 SCSI port (SYS53C1000R) > > Floppy interface, 2 ATA100 ports, PC Card slot > > 1 RS232 and 2 USB 1.1 ports, opt. management port > > VGA and PS/2 mouse/keyboard lead out at RP > > ----END---- > > > > On Mon, 14 Feb 2005 10:35:03 -0200, Moacyr Leite da Silva > > wrote: > >> Hi Jaswinder > >> > >> Try to run this > >> > >> linux ks=floppy allowcddma > >> > >> Reference - Installation Error Out Of Disk Space > >> http://www.fedoraforum.org/forum/archive/index.php/t-1834.html > >> > >> I have this problem with some machines. > >> > >> My Best Regards, > >> > >> Moacyr Leite da Silva > >> www.akadnyx.com.br > >> www.opensourceuniversity.com.br > >> > >> > >> ----- Original Message ----- > >> From: "Jaswinder Singh Kohli" > >> To: "Discussion list about Kickstart" > >> Sent: Monday, February 14, 2005 9:50 AM > >> Subject: Re: Out of Disk Space !! > >> > >>> Hi, > >>> Again same error, but the problem is very strange as i like to relate > >>> it to hardware this time. > >>> > >>> The system is cPCI-6860 Board, with SCSI Controller, mpt drivers are > >> loaded. > >>> Two Seagate SCSI disks are attached. > >>> > >>> Just after printing Starting Anaconda, Fedora Core System Installer... > >>> it prints following lines which i guess leads to outta disk space > >> problem.... > >>> > >>> error -2147483630 reading header: cpio read failed - Success > >>> error -2147483630 reading header: cpio read failed - Success > >>> or sometimes related to gzlib > >>> > >>> a little later detects Monitor(SyncMaster) and Graphics Cards ( ATI > >>> Mach64) and Mouse > >>> > >>> Everything goes fine until the system formats and then trying to > >>> Transfer the install image > >>> to hard drive. > >>> > >>> The same thing works fine on other systems such as, standard P4 Machine > >> with HT > >>> > >>> The cPCI Machine has 2 xeon HT processors, ECC 1024M RAM. > >>> > >>> Earlier it also gave problems with SCSI1 disk, as the system hanged > >>> for indefinate time . > >>> with the status light of SCSI1 disk glowing, where as SCSI0 was fine. > >>> > >>> Just upgraded anaconda to version latest from development branch still > >>> the cpio/gzlib > >>> problem remains. > >>> > >>> As we have 3 of such systems and all of them exhibiting same problem. > >>> where as same CD works fine on other systems. > >>> Can it be due to some hardware incompatibility with anaconda. > >>> > >>> > >>> On Wed, 9 Feb 2005 09:33:20 +0530, Jaswinder Singh Kohli > >>> wrote: > >>>> Thanks a lot for your reply > >>>> I'll get back to you soon, after working on that. > >>>> > >>>> Thanks a lot > >>>> > >>>> > >>>> On Tue, 08 Feb 2005 10:45:56 -0600, Peter Eisch wrote: > >>>>> > >>>>> If you look at 'pivotroot' down in the source, you'll see that > >> stage2.img > >>>>> gets mounted as the new / during the install. Whatever drivers you > >> updated > >>>>> in initrd.img will also need to be updated on the new / image loaded > >> from > >>>>> stage2.img. > >>>>> > >>>>> What Drivers? ... the drivers for whatever controller your target > >> install > >>>>> disk is connected. > >>>>> > >>>>> On 2/8/05 10:36 AM, "Jaswinder Singh Kohli" wrote: > >>>>> > >>>>>> Installing only bare minimum system, to act as gateway and proxy > >> server. > >>>>>> All the partitions are correctly formatted. > >>>>>> > >>>>>> I am using stripped down, buildinstall which only updates, > >> initrd.img > >>>>>> and not the other files. > >>>>>> > >>>>>> Since building stage2.img using buildinstall, requires lot of other > >>>>>> packages to be in the > >>>>>> install tree, for X and others, which i dont' want to include, as it > >>>>>> is for proxy server > >>>>>> and very small image. > >>>>>> > >>>>>> And what kind of drivers ??? > >>>>>> > >>>>>> > >>>>>> On Tue, 08 Feb 2005 10:16:05 -0600, Peter Eisch > >> wrote: > >>>>>>> > >>>>>>> You probably don't have drivers for that particular kernel that you > >> are now > >>>>>>> booting from in the stage2.img. Whatever you did to update the > >> boot > >>>>>>> initrd.img, also do to the stage2.img. > >>>>>>> > >>>>>>> peter > >>>>>>> > >>>>>>> On 2/8/05 6:18 AM, "Jaswinder Singh Kohli" > >> wrote: > >>>>>>> > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> I am getting this error while installation, using the ks.cfg which > >>>>>>>> partitions the drive into > >>>>>>>> three partitions, / = 1 G > >>>>>>>> swap = 1 G > >>>>>>>> /var = rest of space ( 30 + G) > >>>>>>>> > >>>>>>>> The cd image that i built had modified stage2.img, ( took care of > >>>>>>>> .buildstamp) > >>>>>>>> bootdisks upgraded to kernel 2.6.10..., > >>>>>>>> Only Modified isolinux/initrd.img is used, rest of the files like, > >>>>>>>> stage2.img and hdstg2.img > >>>>>>>> are just repackaged version of what were on Original FC3 Iso's, > >> only > >>>>>>>> changed .buildstamp > >>>>>>>> > >>>>>>>> Now when i booot that CD, the boots up, detects hardware, anaconda > >> starts X > >>>>>>>> The partitions are created and formatted, but then the Install > >> ends > >>>>>>>> with a message. > >>>>>>>> > >>>>>>>> "An error occured while transfering install image to your > >> harddrive . > >>>>>>>> You are probably > >>>>>>>> out of disk space" > >>>>>>>> > >>>>>>>> Where as when i perform fdisk -l on tty2, which shows, all the > >>>>>>>> partitions were created > >>>>>>>> and also on console 6 the formatting was successful and hence lot > >> of > >>>>>>>> space is there. > >>>>>>>> > >>>>>>>> On tty3, the detailed error message is as follows... > >>>>>>>> > >>>>>>>> Error transfering stage2.img: [Errno 2] No such file of directory: > >>>>>>>> '/mnt/sysimage/proc/rhinstall-stage2.img' > >>>>>>>> > >>>>>>>> I did a search on google, and archives, came up with no results. > >>>>>>>> > >>>>>>>> Can any one tell me what i am missing or doing wrong and why it is > >>>>>>>> trying to copy > >>>>>>>> rhinstall-stage2.img from some proc fs instead of stage2.img from > >> CD. > >>>>>>>> > >>>>>>>> I am stuck at this point for too long now, any Pointers, any > >> ideas, > >>>>>>>> will be helpful, that can > >>>>>>>> get me going in forward direction. > >>>>>>>> > >>>>>>>> Thanks.... > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> Kickstart-list mailing list > >>>>>>> Kickstart-list at redhat.com > >>>>>>> https://www.redhat.com/mailman/listinfo/kickstart-list > >>>>>>> > >>>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Kickstart-list mailing list > >>>>> Kickstart-list at redhat.com > >>>>> https://www.redhat.com/mailman/listinfo/kickstart-list > >>>>> > >>>> > >>>> -- > >>>> Regards > >>>> JSK > >>>> jskohli (AT) gmail (DOT) com > >>>> > >>> > >>> > >>> -- > >>> Regards > >>> JSK > >>> jskohli (AT) gmail (DOT) com > >>> > >>> _______________________________________________ > >>> Kickstart-list mailing list > >>> Kickstart-list at redhat.com > >>> https://www.redhat.com/mailman/listinfo/kickstart-list > >>> > >> > >> > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Regards JSK jskohli (AT) gmail (DOT) com From jskohli at gmail.com Thu Feb 17 04:09:13 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Thu, 17 Feb 2005 09:39:13 +0530 Subject: Out of Disk Space !! In-Reply-To: <200502162129.06449.debian@herakles.homelinux.org> References: <27ecd449050208083619e00c3f@mail.gmail.com> <003101c51291$9b34e4e0$fd00a8c0@moacyr> <27ecd449050215210712e6784d@mail.gmail.com> <200502162129.06449.debian@herakles.homelinux.org> Message-ID: <27ecd4490502162009259ca378@mail.gmail.com> I checked the CD Media for errors, worked very fine otherwise. Did a installation from same CD to different hardware piece eServer xSeries Blade thing from IBM, worked like charm. Now since i changed the ROM drive and other things in the machine, either there is some incompatibility b/w the hardware and kernel 2.6.x or anaconda. Since the same CD works on different hardware as mentioned. The hardware is cPCI-6860A based system from ADLINK Technologies, comes with SCSI card from MPT Details over here. http://www.powerbridge.de/daten_e/p_picmg2.16-cpu/cpci-6860/cpci-6860.htm ours is, 2Ghz 2 way LV Xeon processors On Wed, 16 Feb 2005 21:29:06 +0800, John Summerfield wrote: > On Wednesday 16 February 2005 13:07, Jaswinder Singh Kohli wrote: > > It is always giving same error, > > error -2147483630 reading header: cpio read failed - Success > > There's a buif in cpio right there. > The negative number is nonseens, and "cpio read failed - Success" > means that cpio detected an error, presumably in a read operation, and then > then used some function that worked before saving errno or creating a useful > error message. > > The missing information _may_ help you resolve the problem. You could, > perheps, check your media for errors; I can imagine (without investingating) > that at some points cpio gets to read from the install CD/DVD. > > -- > > Cheers > John Summerfield > tourist pics: http://environmental.disaster.cds.merseine.nu/ > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list at redhat.com > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > -- Regards JSK jskohli (AT) gmail (DOT) com From peter at boku.net Thu Feb 17 19:46:38 2005 From: peter at boku.net (Peter Eisch) Date: Thu, 17 Feb 2005 13:46:38 -0600 Subject: Out of Disk Space !! In-Reply-To: <27ecd4490502162009259ca378@mail.gmail.com> Message-ID: Are you installing via USB? If so, do you have the USB drivers in your stage2.img for the kernel that the cdrom is booting? Changing drives isn't as important as know that the controller that the drive is connected through has driver support available. I hate to keep harping on the stage2.img, but after the kernel loads using initrd.img as it's root filesystem and before the installer starts, pivotroot flips in the stage2.img. So everything may boot just fine from the cdrom but the installer can't find the install media because the driver's no longer available after the pivotroot. This pretty much exhausts my ideas and experiences. peter On 2/16/05 10:09 PM, "Jaswinder Singh Kohli" wrote: > I checked the CD Media for errors, worked very fine otherwise. > Did a installation from same CD to different hardware piece eServer > xSeries Blade thing > from IBM, worked like charm. > > Now since i changed the ROM drive and other things in the machine, > either there is some > incompatibility b/w the hardware and kernel 2.6.x or anaconda. > > Since the same CD works on different hardware as mentioned. > The hardware is cPCI-6860A based system from ADLINK Technologies, comes with > SCSI card from MPT > > Details over here. > http://www.powerbridge.de/daten_e/p_picmg2.16-cpu/cpci-6860/cpci-6860.htm > ours is, 2Ghz 2 way LV Xeon processors > > > > > On Wed, 16 Feb 2005 21:29:06 +0800, John Summerfield > wrote: >> On Wednesday 16 February 2005 13:07, Jaswinder Singh Kohli wrote: >>> It is always giving same error, >>> error -2147483630 reading header: cpio read failed - Success >> >> There's a buif in cpio right there. >> The negative number is nonseens, and "cpio read failed - Success" >> means that cpio detected an error, presumably in a read operation, and then >> then used some function that worked before saving errno or creating a useful >> error message. >> >> The missing information _may_ help you resolve the problem. You could, >> perheps, check your media for errors; I can imagine (without investingating) >> that at some points cpio gets to read from the install CD/DVD. >> >> -- >> >> Cheers >> John Summerfield >> tourist pics: http://environmental.disaster.cds.merseine.nu/ >> >> _______________________________________________ >> Anaconda-devel-list mailing list >> Anaconda-devel-list at redhat.com >> https://www.redhat.com/mailman/listinfo/anaconda-devel-list >> > From jskohli at gmail.com Thu Feb 17 19:58:50 2005 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Fri, 18 Feb 2005 01:28:50 +0530 Subject: Out of Disk Space !! In-Reply-To: References: <27ecd4490502162009259ca378@mail.gmail.com> Message-ID: <27ecd4490502171158afe83e5@mail.gmail.com> Thanks for reply, But still nothing USB here except the Keyboard, i'll try out the system wihtout the USB keyboard, in, but the keyboard is working simply very fine, thruout the installation system, till it comes over crashing. But still i will try it again in morning, first thing, and get back. ... Thanks a lot On Thu, 17 Feb 2005 13:46:38 -0600, Peter Eisch wrote: > > Are you installing via USB? If so, do you have the USB drivers in your > stage2.img for the kernel that the cdrom is booting? Changing drives isn't > as important as know that the controller that the drive is connected through > has driver support available. > > I hate to keep harping on the stage2.img, but after the kernel loads using > initrd.img as it's root filesystem and before the installer starts, > pivotroot flips in the stage2.img. So everything may boot just fine from > the cdrom but the installer can't find the install media because the > driver's no longer available after the pivotroot. > > This pretty much exhausts my ideas and experiences. > > peter > > On 2/16/05 10:09 PM, "Jaswinder Singh Kohli" wrote: > > > I checked the CD Media for errors, worked very fine otherwise. > > Did a installation from same CD to different hardware piece eServer > > xSeries Blade thing > > from IBM, worked like charm. > > > > Now since i changed the ROM drive and other things in the machine, > > either there is some > > incompatibility b/w the hardware and kernel 2.6.x or anaconda. > > > > Since the same CD works on different hardware as mentioned. > > The hardware is cPCI-6860A based system from ADLINK Technologies, comes with > > SCSI card from MPT > > > > Details over here. > > http://www.powerbridge.de/daten_e/p_picmg2.16-cpu/cpci-6860/cpci-6860.htm > > ours is, 2Ghz 2 way LV Xeon processors > > > > > > > > > > On Wed, 16 Feb 2005 21:29:06 +0800, John Summerfield > > wrote: > >> On Wednesday 16 February 2005 13:07, Jaswinder Singh Kohli wrote: > >>> It is always giving same error, > >>> error -2147483630 reading header: cpio read failed - Success > >> > >> There's a buif in cpio right there. > >> The negative number is nonseens, and "cpio read failed - Success" > >> means that cpio detected an error, presumably in a read operation, and then > >> then used some function that worked before saving errno or creating a useful > >> error message. > >> > >> The missing information _may_ help you resolve the problem. You could, > >> perheps, check your media for errors; I can imagine (without investingating) > >> that at some points cpio gets to read from the install CD/DVD. > >> > >> -- > >> > >> Cheers > >> John Summerfield > >> tourist pics: http://environmental.disaster.cds.merseine.nu/ > >> > >> _______________________________________________ > >> Anaconda-devel-list mailing list > >> Anaconda-devel-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/anaconda-devel-list > >> > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Regards JSK jskohli (AT) gmail (DOT) com From nicolas.catania at hp.com Tue Feb 22 17:53:40 2005 From: nicolas.catania at hp.com (niko) Date: Tue, 22 Feb 2005 09:53:40 -0800 Subject: kickstart file BNF syntax Message-ID: <16923.29092.477981.172119@localhost.localdomain> Hi, Recently I migrated a machine from AS2.1 to EL3. During that exercise, I realized that kickstart files from 2.1 and 3 are not compatible (e.g different syntax for the mouse directive). I would like to make that migration process easier. Does anyone know where I can find the complete syntax description (BNF would be nice) for KS files for each release? Thanks Niko -- Nicolas Catania HP Change & Configuration Software Operation +1 408 447-4564 nicolas.catania at hp.com From rreed at ops.sgp.arm.gov Tue Feb 22 18:38:15 2005 From: rreed at ops.sgp.arm.gov (Ronald Reed) Date: Tue, 22 Feb 2005 12:38:15 -0600 Subject: initrd.img module loading In-Reply-To: <1107887249.2977.56.camel@ronnote> References: <1107883223.2977.50.camel@ronnote> <1107884842.6410.51.camel@localhost.localdomain> <1107885195.2977.54.camel@ronnote> <1107885494.23264.117.camel@edbrown.lanl.gov> <1107887249.2977.56.camel@ronnote> Message-ID: <1109097495.2982.38.camel@ronnote> I have found that the scsihosts= boot line command is only for kernels that have the modules built into the kernel, but no other resolution has been found. I have tried the device parameter in the kickstart file, but anaconda seems to ignore them. Anyone have any other ideals? Here is a portion of my kickstart file: #kickstart file (partial) install cdrom lang en_US.UTF-8 langsupport --default en_US.UTF-8 en_US.UTF-8 device scsi aacraid device scsi megaraid device scsi aic7xxx device eth eepro100 device eth bcm5700 keyboard us mouse genericwheelps/2 --device psaux skipx network --device eth0 --bootproto dhcp --hostname nfs-basic Ron On Tue, 2005-02-08 at 12:27, Ronald Reed wrote: > No, I need the drive letter assignments to be different. > > Ron > > On Tue, 2005-02-08 at 11:58, Ed Brown wrote: > > The --driveorder option won't change the drive letter assignments, but > > it will change the drive that grub is installed to. Isn't that what you > > are after? In your case, you probably want: > > > > bootloader --driveorder=sdb,sda --location=mbr > > > > -Ed > > > > > > On Tue, 2005-02-08 at 10:53, Ronald Reed wrote: > > > Yes, the aacraid device get set to /dev/sdb. The accraid device is a > > > mirrored pair of 36GB drives that are inside the hardware. The megaraid > > > device is a Raid 5 group of 4 73GB drives (3 in the array, and 1 hot > > > spare). The megaraid is to be used for NFS file storage and the accraid > > > is to be used for the system drive. > > > > > > Ron > > > > > > On Tue, 2005-02-08 at 11:47, Brian Long wrote: > > > > > > > What does it detect the aacraid device as? /dev/sdb? If so, why don't > > > > you use the bootloader option mentioned previously to get grub to use > > > > sdb as the boot drive? > > > > > > > > /Brian/ > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list -- =========================== Ron Reed RedHat Certified Engineer SGP Computer Department Manager Unix Systems Administrator ARM SGP CART Site (580)388-4053 ron.reed at arm.gov From peter at boku.net Tue Feb 22 19:39:53 2005 From: peter at boku.net (Peter Eisch) Date: Tue, 22 Feb 2005 13:39:53 -0600 Subject: initrd.img module loading In-Reply-To: <1109097495.2982.38.camel@ronnote> Message-ID: Did you try rebuilding the initrd.img using something like: /sbin/mkinitrd --preload scsi_mod --preload sd_mod --with aacraid \ --with megaraid --with aic7xxx --with eepro100 --with bcm5700 \ /boot/ninitrd-%{KVERREL}.img %{KVERREL} /bin/mv /boot/initrd-%{KVERREL}.img /boot/oinitrd-%{KVERREL}.img /bin/mv /boot/ninitrd-%{KVERREL}.img /boot/initrd-%{KVERREL}.img I put this in my kernel's %post so it gets done at boot, but do the same kind of thing with the initrd.img on the install media. peter On 2/22/05 12:38 PM, "Ronald Reed" wrote: > I have found that the scsihosts= boot line command is only for kernels > that have the modules built into the kernel, but no other resolution has > been found. > > I have tried the device parameter in the kickstart file, but anaconda > seems to ignore them. Anyone have any other ideals? Here is a portion of > my kickstart file: > > #kickstart file (partial) > install > cdrom > lang en_US.UTF-8 > langsupport --default en_US.UTF-8 en_US.UTF-8 > device scsi aacraid > device scsi megaraid > device scsi aic7xxx > device eth eepro100 > device eth bcm5700 > keyboard us > mouse genericwheelps/2 --device psaux > skipx > network --device eth0 --bootproto dhcp --hostname nfs-basic > > Ron > > On Tue, 2005-02-08 at 12:27, Ronald Reed wrote: >> No, I need the drive letter assignments to be different. >> >> Ron >> >> On Tue, 2005-02-08 at 11:58, Ed Brown wrote: >>> The --driveorder option won't change the drive letter assignments, but >>> it will change the drive that grub is installed to. Isn't that what you >>> are after? In your case, you probably want: >>> >>> bootloader --driveorder=sdb,sda --location=mbr >>> >>> -Ed >>> >>> >>> On Tue, 2005-02-08 at 10:53, Ronald Reed wrote: >>>> Yes, the aacraid device get set to /dev/sdb. The accraid device is a >>>> mirrored pair of 36GB drives that are inside the hardware. The megaraid >>>> device is a Raid 5 group of 4 73GB drives (3 in the array, and 1 hot >>>> spare). The megaraid is to be used for NFS file storage and the accraid >>>> is to be used for the system drive. >>>> >>>> Ron >>>> >>>> On Tue, 2005-02-08 at 11:47, Brian Long wrote: >>>> >>>>> What does it detect the aacraid device as? /dev/sdb? If so, why don't >>>>> you use the bootloader option mentioned previously to get grub to use >>>>> sdb as the boot drive? >>>>> >>>>> /Brian/ >>> >>> _______________________________________________ >>> Kickstart-list mailing list >>> Kickstart-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/kickstart-list From James_Martin at ao.uscourts.gov Tue Feb 22 20:02:06 2005 From: James_Martin at ao.uscourts.gov (James_Martin at ao.uscourts.gov) Date: Tue, 22 Feb 2005 15:02:06 -0500 Subject: kickstart file BNF syntax In-Reply-To: <16923.29092.477981.172119@localhost.localdomain> Message-ID: Niko, The syntax is available in the RHEL manuals. James James S. Martin, RHCE Contractor Administrative Office of the United States Courts Washington, DC (202) 502-2394 kickstart-list-bounces at redhat.com wrote on 02/22/2005 12:53:40 PM: > Hi, > > Recently I migrated a machine from AS2.1 to EL3. During that exercise, I > realized that kickstart files from 2.1 and 3 are not compatible (e.gdifferent > syntax for the mouse directive). > > I would like to make that migration process easier. Does anyone know > where I can > find the complete syntax description (BNF would be nice) for KS files for each > release? > > Thanks > > Niko > > -- > Nicolas Catania > > HP Change & Configuration Software Operation > +1 408 447-4564 > nicolas.catania at hp.com > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From phr at doc.ic.ac.uk Tue Feb 22 21:31:37 2005 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Tue, 22 Feb 2005 21:31:37 +0000 (GMT) Subject: kickstart file BNF syntax In-Reply-To: <16923.29092.477981.172119@localhost.localdomain> References: <16923.29092.477981.172119@localhost.localdomain> Message-ID: On Tue, 22 Feb 2005, niko wrote: >I would like to make that migration process easier. Does anyone know >where I can find the complete syntax description (BNF would be nice) >for KS files for each release? See /usr/share/doc/anaconda-*/kickstart-docs.txt. Cheers, Phil From nicolas.catania at hp.com Wed Feb 23 00:53:38 2005 From: nicolas.catania at hp.com (niko) Date: Tue, 22 Feb 2005 16:53:38 -0800 Subject: (no subject) Message-ID: <16923.54290.251363.332815@localhost.localdomain> Hi, I am getting an exception when I try to do a kickstart install using http of AS2.1. A quick search on google seems to indicate that the problem is still unresolved[1][2]. The set up I am using worked fine for EL3 though. Does anyone know host to get rid of this usrintall.py bad magic in header exception? Cheers Niko Footnotes: [1] http://www.google.com/search?q=urlinstall.py+bad+magic+in+header [2] https://bugzilla.redhat.com/beta/show_bug.cgi?id=109821 -- Nicolas Catania HP Change & Configuration Software Operation +1 408 447-4564 nicolas.catania at hp.com From daniel.spratlen at cox.net Wed Feb 23 19:51:36 2005 From: daniel.spratlen at cox.net (Daniel Spratlen) Date: Wed, 23 Feb 2005 14:51:36 -0500 Subject: passing a variable from boot to %pre or %post scripts Message-ID: <1109188297.4509.3.camel@boo> Is it possible to pass a variable from kernel boot time to a %pre or %post install script? thanks, Daniel From David_French at intuit.com Wed Feb 23 19:55:07 2005 From: David_French at intuit.com (French, David) Date: Wed, 23 Feb 2005 11:55:07 -0800 Subject: passing a variable from boot to %pre or %post scripts Message-ID: <9839AD0F1396F845A28E594EF28B2BA80B5EE709@sdgex01.sd.intuit.com> Sure. A trick I use is to set values on the boot command line in the grub loader config. I modified my boot CD to have an option called quick at the loader prompt. I then pass the param anaconda_quick as a command line argument to the kernel, which will ignore unknown options, and so will the drivers. Now in %pre and %post you can get the info from the /proc/cmdline file. -_Dave -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Daniel Spratlen Sent: Wednesday, February 23, 2005 11:52 AM To: Discussion list about Kickstart Subject: passing a variable from boot to %pre or %post scripts Is it possible to pass a variable from kernel boot time to a %pre or %post install script? thanks, Daniel _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list