Red Hat Bugzilla – Bug 183183
Boot tries to find Fedora on the wrong partition
Last modified: 2007-11-30 17:11:25 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.1 (like Gecko)
Description of problem:
Installed Fedora Core 5 Test 3 onto /dev/hda7 (between two other Linux
distributions on /dev/hda6 and /dev/hda8). After rebooting I received these
VFS: Can't find ext3 filesystem on dev hda8
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
setuproot: moving /dev failed: No such file or directory
setuproot: mounting /proc: No such file or directory
setuproot: mounting /sys: No such file or directory
switchroot: mounting failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Replacing "LABEL=/" with "/dev/hda7" in /etc/fstab and /boot/grub/grub.conf
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install fc5test3 onto /dev/hda7 leaving two other Linux distributions
on /dev/hda6 and /dev/hda8 unchanged.
3. Read the error messages terminating at kernel panic.
Actual Results: Kernel panic.
Expected Results: Normal boot.
Why your system looks for root on hda8 when you have it on hda7? It seems you
have some mismatch in your grub.conf (is it shared between all dists on your
hda?) or you have same label on multiple partitions. The label has to be unique.
Please, check your partitions and labels (as root) by commands: blkid and e2label.
Yes, both /dev/hda7 and /dev/hda8 have LABEL="/". This is the output of blkid:
/dev/hda7: LABEL="/" UUID="d4bc0bbf-de9f-4d4a-80c2-4051f2497f10" SEC_TYPE="ext2"
/dev/hda8: UUID="aa7871eb-7be6-41e1-938d-8a2304ac373a" LABEL="/" TYPE="reiserfs"
/dev/hda8 had already had LABEL="/" when I installed Fedora Core 5 Test 3 onto
/dev/hda7 so it should not have added the same label to /dev/hda7. But it did.
Now I have Ubuntu on /dev/hda8 but I believe the label was left behind by an
earlier installation of Fedora Core 4.
man e2label says that e2label is to edit labels on ext2/ext3 but the filesystem
of /dev/hda8 is reiserfs.
You're probably right that installer should be check for unique labels.
We do when we can read the label. David -- didn't you fix this before test3?
I added the reiserfs label collision avoidance code before Test 3. I'll look in
to this now.
Karel, was the clock on this system invalid when you did the FC installation
(i.e., set before the epoch)? libblkid returns nil if the clock is <
(time_t)-1. I submitted a patch for e2fsprogs, but they have not rolled a new
David, I don't know. This problem is originaly reported by AriszlÃ³ (see comment #1).
Yeah, my mistake. Two bugs crossed paths in my mind. The reiserfs collision
prevention code is probably not catching his case. I'll look at this further.
Sorry for the confusion.
I can't recreate this here. The support to avoid reiserfs label collision was
added on February 2nd, so it should be in FC5 Test 3. Are you sure you're using
FC5 Test 3? I've done an install of Ubuntu 5.10 here to reiserfs, then FC5 Test
3 and it installs just fine. The root filesystem on Fedora isn't labeled and it
boots up just fine.
Yes, I installed FC5 Test 3 using the 2006-02-20 isos from
This is how I experienced the label clash. Relevant partitions before installation:
/dev/hda8 reiserfs labelled /
I don't remember if /dev/hda7 was also labelled / before installing FC5 Test 3
onto it. Let's assume the two identical labels already existed before the
During installation selected /dev/hda7 for / and reformatted it to ext3. At the
end both /dev/hda7 and /dev/hda8 were labelled / and Fedora wanted to run from
/dev/hda8 instead of /dev/hda7, which resulted in kernel panic.
To reproduce all this, first you need to identically label two reiserfs
partitions as / with reiserfstune.
This was a strange bug. I was able to recreate the scenario you described and
have fixed the problem in rawhide. Sorry it didn't make it to FC5 final.
There were several problems. First, a problem with the reiserfs label reading
code I added weeks ago. Second, we didn't have a function to write labels to
reiserfs filesystems. And we lacked a handler for the scenario you described
where two filesystems will have the same label *before* running anaconda.
Unfortunately there's no good way to handle more than two of the same fs labels,
but I say it's the user's fault in that case.
With all that, reiserfs is still 100% unsupported in Fedora. If you are
installing to a reiserfs filesystem for /, you must separate the /boot
filesystem to an ext2/ext3 partition. In addition, be sure to add "noselinux
selinux=0" to the additional boot arguments for the boot loader. Reiserfs lacks
the extended attributes needed to support selinux, so you'll just have to