Bug 499802 - New mkinitrd make system unbootable, when root partition is RAID1 device
New mkinitrd make system unbootable, when root partition is RAID1 device
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd (Show other bugs)
All Linux
low Severity urgent
: rc
: ---
Assigned To: Brian Lane
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2009-05-08 06:03 EDT by Boris B. Zhmurov
Modified: 2013-03-20 09:42 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-03-20 09:42:48 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 Boris B. Zhmurov 2009-05-08 06:03:37 EDT
Description of problem:
mkinitrd version make system unbootable, if we have root partition (/) on software RAID1 and if there is LABEL=... in /etc/fstab for root partition.

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

How reproducible:

Steps to Reproduce:
1. Install RHEL5.3 on server, where root partition is software raid1

root@server ~ # mount
/dev/md1 on / type ext3 (rw)

and there is labeled root partition in fstab:
root@server ~ # cat /etc/fstab 
LABEL=PS09011241452342                /                       ext3    defaults        1 1

2. Install new updated kernel _any version_

3. reboot

Actual results:
mount: error mounting /dev/root on /sysroot as ext3: Device or resource busy
switchroot: mount failed: No such file or directory
kernel panic - not syncing: Attempt to kill init!

Expected results:
normal boot

Additional info:
Comment 1 David Cantrell 2013-03-20 09:42:48 EDT
While Red Hat welcomes bug reports on Red Hat products here in our public
bugzilla database, please keep in mind that bugzilla is not a support tool or
means of accessing support.  If you would like technical support please visit
our support portal at access.redhat.com or call us for information on
subscription offerings to suit your needs.

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