Bug 54973

Summary: Kernel panic relating to initrd
Product: [Retired] Red Hat Linux Reporter: Nathan G. Grennan <redhat-bugzilla>
Component: mkinitrdAssignee: Arjan van de Ven <arjanv>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-12-03 20:19:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nathan G. Grennan 2001-10-23 21:15:22 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5+) Gecko/20011018

Description of problem:
If /initrd is deleted the computer will not finish booting up after a
reboot. It will kernel panic with a message about setting init=

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


How reproducible:
Always

Steps to Reproduce:
1. rm /initrd
2. Reboot
3. See error message
	

Actual Results:  I saw the error message

Expected Results:  To see the error message

Additional info:

This is using kernel-2.4.7-10
Comment 1 Bill Nottingham 2001-10-29 17:46:16 UTC 
Don't do that, then. It's required.
Comment 2 Frank Ch. Eigler 2001-12-03 20:19:44 UTC 
The problem is that, as outlined in bug 54878, this situation can arise
if RHN updates are incompletely applied.  It would be appropriate to
tolerate this situation by creating /initrd if necessary, perhaps
on each mkinitrd run, or at least during mkinitrd rpm installation.
Comment 3 Bill Nottingham 2001-12-03 20:25:30 UTC 
That's what the RPM requirement is for. I don't mean to be abrubt, but if you
break your dependencies, or remove random directories, you shouldn't be
surprised if something breaks.
Comment 4 Frank Ch. Eigler 2001-12-03 21:04:46 UTC 
I wouldn't have broken the dependencies if another way around
odd RPM packaging was eminently available.  In any case, this
particular situation is not hard to correct.  Hell, it's dead
easy to detect: make mkinitrd assert the existence of this
directory, much like it would abort if would fail to find some
modules from modules.conf.