Bug 47496 - Kickstart'd installation doesn't create initrd image even though needed
Summary: Kickstart'd installation doesn't create initrd image even though needed
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-05 19:02 UTC by Need Real Name
Modified: 2007-04-18 16:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-07-10 17:28:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Need Real Name 2001-07-05 19:02:31 UTC 
Description of Problem:

My kickstart installation fails to create an initrd image despite I have a Compaq array controller (scsi device).
Lilo seems to be installed, but without any reference to initrd whatsoever. And once the image is missing,
the kernel cannot mount root filesystem.

I have tried adding

device scsi cpqarray 

into kickstart file, but it didn't help. The installation otherwise works all right and finishes without any errors.
I have all the newest versions of RPMs. This very same configuration worked in 6.2, so it seems like a bug.
Comment 1 Need Real Name 2001-07-10 11:00:11 UTC 
Could it be that because the kernel on installation initrd is different version (2.4.2) than
the one that is on the RPMs to be installed (2.4.3) it cannot make the initrd as
the needed modules are not found?
Comment 2 Brent Fox 2001-07-10 16:22:33 UTC 
I have not seen this problem before.  Kickstart installs on ProLiants with the
Compaq Smart Array controller have created initrd's for me with 7.1.  What kind
of install are you doing?  (CDROM, NFS, etc.)?
Comment 3 Need Real Name 2001-07-10 17:28:13 UTC 
It's a cd-rom installation off a custom made single installation cd of updated
RPMs. The cd is my current suspect, I am trying to find out if the culprit could
be one of the updated RPMs.
Comment 4 Need Real Name 2001-07-10 20:21:18 UTC 
After comparing RPM list for a second time, I noticed that losetup package had been missing.
Very sorry to bother you with this.
Note You need to log in before you can comment on or make changes to this bug.