Bug 52976 - kernel panic at boot: unable to mount root fs
Summary: kernel panic at boot: unable to mount root fs
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mkinitrd   
(Show other bugs)
Version: 7.3
Hardware: ia64 Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-31 20:20 UTC by Ben Levenson
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-31 21:13:09 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ben Levenson 2001-08-31 20:20:58 UTC
(I was given the impression that this is a known issue, but I couldn't find
anything in bugzilla....)

Description of Problem:
system won't reboot after install.
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
request_module[block-major-8]: Root fs not mounted
VFS: Cannot open root device "sda2" or 08:02
Please append a correct "root=" boot option
Kernel Panic: unable to mount root fs on 08:02

FWIW, this happened during a kickstart install - base + X Windows + KDE

Version-Release number of selected component (if applicable):
build re0831.0

Comment 1 Arjan van de Ven 2001-08-31 20:23:47 UTC
What sort of device did you install on ?
Could this be a missing initrd ?

Comment 2 Ben Levenson 2001-08-31 21:02:25 UTC
sorry about the vague bug report....
I installed to /dev/sda2 - 9gig SCSI on a qla1280
initrd is present in /boot. Is it supposed to be there? It is located in
/boot/efi on our 7.1 system.  Also, the 7.1 system includes vmlinux in addition
to vmlinuz. The failing system only has vmlinuz.

There are no failures listed in the install log.

Comment 3 Arjan van de Ven 2001-08-31 21:13:05 UTC
mkinitrd bug; should be fixed already

Comment 4 Jeremy Katz 2001-08-31 21:37:03 UTC
Yep, fixed in mkinitrd-3.2.5-1

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