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 <moacyrs@xxxxxxxxxxxxxx> 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" <jskohli@xxxxxxxxx> > To: "Discussion list about Kickstart" <kickstart-list@xxxxxxxxxx> > 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 > > <jskohli@xxxxxxxxx> 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 <peter@xxxxxxxx> 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" <jskohli@xxxxxxxxx> 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 <peter@xxxxxxxx> > 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" <jskohli@xxxxxxxxx> > 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@xxxxxxxxxx > > > > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > > > >> > > > > > > > > > > > > > _______________________________________________ > > > > Kickstart-list mailing list > > > > Kickstart-list@xxxxxxxxxx > > > > 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@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > -- Regards JSK jskohli (AT) gmail (DOT) com
