Red Hat Bugzilla – Bug 171102
uuid of vfat partition not recognized by hal
Last modified: 2013-03-05 22:44:17 EST
Description of problem:
I have an portable music player (Jens Of Sweden MP-400) that appears to my
system as an USB Mass Storage device with a VFAT partition. To be able to
store files with non-ascii filenames on the partition I would like to be able to
pass the iocharset=cp850 mount option when mounting the device. The simplest way
to do this that I've found ATM is to attach the device, let hal mount it and add
a line to the /etc/fstab, edit the line adding the desired mount option and
remount the device with 'umount /media/usbdisk; mount /media/usbdisk'.
However I would like to be able to have hal do this for me, and was looking into
using the method described in http://tinyurl.com/a53hu
/sbin/blkid identifies the partition as /dev/sdd1: UUID="4354-B26C" TYPE="vfat"
but when I browse the hal tree the volume.uuid field is empty like this (output
volume.uuid = '' (string)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attach my device
2. Check the hal tree with hal-device-manager
3. To compare get the output of "/sbin/blkid /dev/sdd1"
empty volume.uuid field
volume.uuid field matching the output of /sbin/blkid
uuids for my other volumes, such as RAID and NTFS volumes gets inserted
correctly in the hal tree.
A workaround that I use now for the people lurking the bugzilla is to add
iocharset to all vfat partitions. Also I found that iocharset=utf8 works better
than cp850 (actually, iocharset=utf8 for all vfat partitions would be a
reasonable global default for fedora IMHO)
Created attachment 121735 [details]
my .fdi file that gives correct non-latin filenames on vfat partitions
To save non-latin characters in vfat filenames correctly, save the attached
file in /usr/share/hal/fdi/policy/20thirdparty (I call mine 10-vfat.fdi),
hald with '/sbin/service haldaemon restart', unmount, detach and re-attach your
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
The UUID field still turns up blank, however the workaround (always use UTF8
iocharset) seems implemeted as default on FC6. There are other perfectly good
reasons for wanting to have access to the UUID field in hal, so I'm leaving this
one as active
Fedora Core 4 is now completely unmaintained. These bugs can't be fixed in that
version. If the issue still persists in current Fedora Core, please reopen.
Thank you, and sorry about this.