Bug 374941 - Wrong label for FAT32 partition in fstab (don't know to which component this belows)
Summary: Wrong label for FAT32 partition in fstab (don't know to which component this ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 8
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-10 18:29 UTC by Sergio Cordeiro
Modified: 2008-04-22 14:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-04-22 14:40:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sergio Cordeiro 2007-11-10 18:29:26 UTC
Hi

Sorry for posting this under the bootparamd, I don't know which component I
should have used.

The problem:
In F8 installation, if I tell the Anaconda installer to mount an existing FAT32
partition, it will use a label (label=/mnt/fat) instead of using /dev/sdX. 

After installing F8, this causes an error upon booting the PC which I solved by
replacing "label=/mnt/fat" with "/dev/sdX".

Thanks!

Comment 1 Andrew Farris 2008-01-10 11:40:49 UTC
The correct fix here would be to label your FAT32 partition and mount by label
since the ordering of the devices will not necessarily be determinant anymore
(as I understand), which is why it is supposed to be choosing mount by label. 
The /dev/sdX is not guaranteed to be the same X for that partition at all
reboots starting with F8 where all harddrive devices are moved from /dev/hdX to
/dev/sdX irregardless of scsi/ide.

I'm guessing the bug here is probably that Anaconda needs to label the partition
for you as well as setup fstab to mount by label, when an existing partition is
in place and is not yet labeled and is not being reformatted during install.


Comment 2 Chris Lumens 2008-04-22 14:40:46 UTC
This should be fixed in F9.  We're using UUIDs instead of labels throughout now.


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