Bugzilla – Bug 388248
hal: nothing visible happens after inserting of flash disc
Last modified: 2008-05-16 12:57:00 UTC
I connected to the computer a brand new A-DATA 4GB MyFlash PD15 FlashDrive USB2.0. It was preformatted with one partition and FAT file system in the partition 1. Partition was correctly recognized by the kernel, but GNOME volume manager did not mount it. Manual mount as vfat works. Attaching the disc image and lshal output for your furter analysis.
Created attachment 213576 [details] empty_adata_myflash_small.lshal
Created attachment 213581 [details] empty_adata_myflash_small.img.bz2 Warning: File size after decompression is 4GB.
Reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=15921
@Kay: can you take a look at this bug. You are the maintainer of libvolume_id and more familiar with fs-type detection.
Jan Kara inspected the file system a bit as part of the bug 91189. The files system is not fully conforming FAT specification. When mounted, it is corrupted by write up to 10.3. But on the other hand, exactly this image is present on some flash from factory.
While the device is connected, what does: /lib/udev/vol_id /dev/<device name> print?
/lib/udev/vol_id /dev/sdb1 /dev/sdb1: unknown volume type /lib/udev/vol_id /dev/sdb /dev/sdb: unknown volume type file -s /dev/sdb /dev/sdb: x86 boot sector, Microsoft Windows XP mbr,Serial 0x91f72d24; partition 1: ID=0xb, active, starthead 1, startsector 63, 7897024 sectors file -s /dev/sdb1 /dev/sdb1: x86 boot sector
The partition looks like a FAT32 volume, but it misses the signature to identify the volume. It is defined by the FAT filesystem: LeadSig: 0x41615252 "The signature is used to validate that this is a Info sector" We can not relax that check, because we will very likely wrongly identify volumes which are not FAT32. Sorry, you have to reformat the volume, if you want autodetection.