Bug 91004 - wrong root fs mount point
Summary: wrong root fs mount point
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: All Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2003-05-16 11:36 UTC by Jean-Jacques Sarton
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-16 18:22:59 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 Jean-Jacques Sarton 2003-05-16 11:36:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

Description of problem:
The file /etc/fstab contain the line:


This implies that the apparently mounted partition is not the real
mounted partition. The root file system will also not be checked
while the system is booting.

On my system RH 7.3 was installed on hda2, the complete system
was copied to a partition on a new drive (hdd, hdc is a cdrom).
df / show "/dev/hdda2 ..."  instead of "/dev/hdd7 ..." The size
reported correspond to the correct partition.

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

How reproducible:

Steps to Reproduce:
1. install RH
2. create a partition on an other drive and copy the content of the
   actual system to the new partition, edit the file /boot/grub/menu.lst
   in order to be able to boot the new "installation"
3. reboot the system with / at the new partition.

Actual Results:  see description,

Expected Results:  correct information about the real mounted file system

Additional info:

The idea of using LABEL=/ within /etc/fstab is good but the boot
process work not correctly.

Modifying the lile "LABEL=/ ..." with e.g. /dev/hdd7 / ..." solve the
problem but is not as pretty as the original line.

Comment 1 Jeremy Katz 2003-05-16 18:22:59 UTC
If you copy and are using a new root fs, then you need to update the label on
the destination partition as well.  The label is set in the filesystem
superblock, it's not really very deep magic.

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