Bug 67070 - kickstart ftp install hangs at post
Summary: kickstart ftp install hangs at post
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer   
(Show other bugs)
Version: 7.3
Hardware: i686 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-06-19 18:05 UTC by LeRoy Hogan
Modified: 2007-04-18 16:43 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-06-19 18:09:00 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
ks.cfg file from my kickstart ftp install disk when problem occurs (1.39 KB, patch)
2002-06-19 18:08 UTC, LeRoy Hogan
no flags Details | Diff

Description LeRoy Hogan 2002-06-19 18:05:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.0.0-10; Linux)

Description of problem:
The install seems to work until post starts and then hangs, I do keys Ctrl-Alt-F4 and see the following

<6>attempt to access beyond end of device
<6>01:01: rw=0, want=4846 limit=4608
<4>Error -3 while decompressing!
<4>c02a0a3c(-11791757640)->ccfda000 (4096)

Workaround that RH Support gave me. Add to my kickstart disk syslinux.cfg the following to my existing 'append' line:


This means my kickstart ftp install needs a bigger ramdisk then the normal defualt size.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.My ks.cfg and syslinux.cfg will be attached

Actual Results:  Post Install hangs with decompressing error due to ramdisk being too small.

Expected Results:  ramdisk size be big enough for decompressing during kickstart ftp install post section

Additional info:

Comment 1 LeRoy Hogan 2002-06-19 18:08:54 UTC
Created attachment 61688 [details]
ks.cfg file from my kickstart ftp install disk when problem occurs

Comment 2 Jeremy Katz 2002-06-20 03:16:50 UTC
In current releases, you *must* have the ramdisk_size for things to work.  We've
changed the default ramdisk size in the BOOT kernel for future releases.

Note You need to log in before you can comment on or make changes to this bug.