From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020311
Description of problem:
By default, anaconda uses labels instead of device names. During the install,
formatting partitions have device labels added to them. However, if you choose
to not format a partition, and the partition dosen't have a label defined, it
fails to mount on bootup.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Format a partition without defining a label
2.Install redhat, choosing a mountpoint for the partition, and choose to not
3.Attempt to boot the machine
Actual Results: The machine attempts to mount the partition with the matching
label, which dosen't exist. The machine then prompts for the root password to
repair the disk.
Expected Results: The installer should detect that the label dosen't exist and
1) add the device name into /etc/fstab instead of the label
2) Add the label to the partition (not preferred since choosing to not modify a
partition should not modify the partition)
This is actually exactly the algorithm which is used. What did your
partitioning look like before and after the install (including what was labelled
where)? If you tune2fs -l the partition which you didn't format, does it really
not have a label? Was the partition that caused problems an ext2 partition?
On first bootup, the partition had no label. I used tune2fs -l to add the
label, and it mounted fine on the next bootup.
The problematic partition was ext3, not ext2.
Hrmm... I can't reproduce this here, but will keep trying.
I'm not sure if it would matter or not, but the partition was not a standard
named partition (not /usr /home /boot, etc.)
The partition name was /scratch. I doubt it would matter, but just in case :)
What sort of device was the partition in question on?
18 gig SCSI hard drive. Fujitsu model MAJ3182MP
I still can't reproduce this :( If you can reproduce this and see any useful
messages on tty3 or tty5 during the install, feel free to reopen the bug