Bug 56218 - mkinitrd fails during anaconda install of kernel
Summary: mkinitrd fails during anaconda install of kernel
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-13 23:44 UTC by gofish
Modified: 2007-04-18 16:38 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-11-13 23:44:49 UTC


Attachments (Terms of Use)

Description gofish 2001-11-13 23:44:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (Windows NT 5.0; U)

Description of problem:
Inspection of /tmp/install.log after ftp network build with latest Errata applied to the RPMS directory reveals
Installing kernel.
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)

I traced the awk commands back to lines 271 and 293 of /sbin/mkinitrd from mkinitrd-3.2.6-1.rpm.  "/etc/fstab" does not appear to exist at 
the time the kernel is installed during the Anaconda build.

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


How reproducible:
Always

Steps to Reproduce:
1.Setup RH7.1 network install server with latest kernel errata (kernel-2.4.6-12) included
2.run a network ftp build
3.view /tmp/install.log after build and initial reboot
	

Actual Results:  <Snipped> output of /tmp/install.log

Installing ipchains.
Installing kernel.
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
Installing devfsd


Expected Results:  
Installing ipchains.
Installing kernel.
Installing devfsd.

Additional info:

Based on my limited knowledge of awk it appears that this would only affect those whose root device is a on a loopback or they have the 
root filesystem type as a loadable module

Comment 1 Erik Troan 2002-05-21 23:19:05 UTC
this was fixed for 7.2


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