Red Hat Bugzilla – Bug 154487
Boot after install hangs; fstab given improper label
Last modified: 2007-11-30 17:11:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050324 Firefox/1.0.2
Description of problem:
After an install of FC4test2-ppc, when the computer is rebooted it hangs because when anaconda wrote the fstab file, the root partition was given a disk label to reference, and the startup process couldn't find it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install FC4test2-ppc
Actual Results: The computer hanged and presented a screen requesting root maintence.
Expected Results: A normal bootup.
I'm not sure if it's a poorly written fstab file, or if it's that the disk label did'nt get set by the format process.
Can you provide the fstab?
I'm extremely sorry but I've already modified it and didn't save a backup of the
Hindsight is 20/20.
Hmmm. Can you provide /sbin/e2label for each of the partitions you were mounting?
I'm really sorry, I already re-installed Yellow Dog Linux, but I'm pretty sure
it was /1.
I just saw that I didn't mention this before: the first line in the fstab was
LABEL=/1 ext3 ........
(and there may have been something like /dev/hda/ before it.)
Sorry, I hope I'm not wasting your time; I kinda feel like an a$$. I guess I
could backup and install test2 again.....
I did an install from a rawhide snapshot, and /etc/fstab seemed to have been
written quite niely. Things just worked
Andrew, do you mind reinstalling test2, and seeing if you can reproduce it?
Also, give us more details about /dev/hda
Well, I reinstalled FC4 Test2, allowing it to install over all existing
partitions. This time everything "just worked." Once it was booted into Gnome,
I looked at the fstab and the only partition referenced via a LABEL tag was
boot, correctly as "LABEL=/boot".
/dev/hda is just the standard Ultra ATA 12GB hard disk that shipped on the Blue
& White G3 Macintoshes. Also, I think I have a revision 2 motherboard. I'm
sure it's the master drive. Past that, I don't know much about it.
Think this should be fixed now