Bug 67819 - missing initrd directory causes kernel panic
Summary: missing initrd directory causes kernel panic
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: filesystem
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Aaron Brown
URL: http://groups.google.com/groups?hl=en...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-02 14:48 UTC by Need Real Name
Modified: 2014-03-17 02:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-07-02 14:48:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-07-02 14:48:31 UTC
Description of Problem:

Kernel panics after upgrade to 2.4.18-5 from 2.4.18-4.

How Reproducible:

I haven't tried rpm -e the kernel and trying it again.

Actual Results:

The kernel paniced when it tried to pivot_root(/sysroot,/sysroot/initrd)

Additional Information:
	
The solution was to recreate the missing /initrd directory. rpm -V filesystem
revealed it was missing from the original package. Somehow, the directory was
deleted. If it wasn't for the above groups.google.com link, I wouldn't have
known where to begin (though in hindsight the error message does make sense).

Comment 1 Bill Nottingham 2002-07-02 15:51:57 UTC
The /initrd directory is required; that's why it's part of the filesystem package.

Comment 2 Need Real Name 2002-07-02 16:10:06 UTC
You've seemed to miss my point! Upgrading seems to break the system badly. Does
the kernel RPM mess around with /initrd directory? All I know is I upgraded,
rebooted, and got a kernel panic (with all kernels 2.4.18-{3,4,5}).

Comment 3 Bill Nottingham 2002-07-02 16:27:41 UTC
No, the kernel upgrade does not touch the /initrd directory. Recent versions of
mkinitrd make the directory when the initrd is made, but nothing that I can see
removes it.


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