Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 50695 - ks fails to install lilo on system with scsi disc
ks fails to install lilo on system with scsi disc
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
: 50696 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2001-08-02 06:38 EDT by Gerald Teschl
Modified: 2007-04-18 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-02 11:32:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gerald Teschl 2001-08-02 06:38:54 EDT
I just did a ks/nfs installation on a scsi only system (one hd and one
cdrom). I used

lilo --location mbr 

in the ks.cfg file. The installation went fine but upon reboot of the
system the kernel will not be able to load the initial ram disk
(no initrd found at block) and then naturally fail to mount the
root device because of the missing scsi drive. I tried to install
again and this is 100% reproducible. Then I used the same ks.cfg
file on my laptop (ide only) and there were no problems.

Morover, booting the scsi box from cdrom, mounting the hardrive
and executing lilo, the box will be fine.
Comment 1 Gerald Teschl 2001-08-02 06:41:09 EDT
Just noticed I forgot a 0: "no initrd found at block 0"
Comment 2 Gerald Teschl 2001-08-02 06:42:12 EDT
*** Bug 50696 has been marked as a duplicate of this bug. ***
Comment 3 Gerald Teschl 2001-08-02 11:32:29 EDT
Maybe this is a problem with lilo and not with anaconda. See also #50718.
Comment 4 Jeremy Katz 2001-08-02 11:47:28 EDT
No, there was a problem with initrd creation and lilo, since fixed in cvs

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