Bug 88608 - boot loader/kernel mounts / as read-write, fails during boot.
Summary: boot loader/kernel mounts / as read-write, fails during boot.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-11 12:54 UTC by Need Real Name
Modified: 2007-04-18 16:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:47 UTC

Attachments (Terms of Use)

Description Need Real Name 2003-04-11 12:54:08 UTC
Description of problem:

After upgrading from RH 7.2 to RH 8.0 the system will no longer boot. This is
because the root file sytem is being mounted rw by the kernel. When rc.sysinit
attempts to fsck the root filesystem it aborts to a single user shell.

The status of the mount was confirmed by modifying rc.sysinit to display mount
state at top of file. This indicated that the filesystem is mounted rw 

The configs in the boot loader specify that root should be mounted read-only and
the fault occurrs with both grub and lilo.

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

How reproducible:

Occurred on two (out of two) different systems when they were upgraded.

Steps to Reproduce:
1. System has RH 7.2 installed with up2date errata applied and boots with grub
2. Upgrade to RH 8.0 and request change to LILO boot loader
Actual results:

System fails during boot as described above

Expected results:

System boots normally

Additional info:

I don't know if the change from grub to lilo is significant, but it was the only
unusual option in the upgrade. 

Both systems are dual boot, one with win 2K, the other with win XP.
One system was subsequently overwritten with a clean install and works normally.

Comment 1 Bugzilla owner 2004-09-30 15:40:47 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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