It comes down to vol_id not recognising a vfat partition: the device entry is created, and I can mount it by hand:
$ sudo mount -o ro -t vfat /dev/sdg1 /mnt
works fine.
But, /sbin/vol_id shows:
$ vol_id /dev/sdg1
/dev/sdg1: unknown volume type
Of course, the system *can* recognise the partition properly if you use a different command:
$ blkid /dev/sdg1
/dev/sdg1: LABEL="SEA_DISK" UUID="0000-0ED4" TYPE="vfat"
So as 118292 says, it's a udev (vol_id) bug (possibly under Ubuntu).
I am somewhat loath to do the workarounds suggested (especially rewriting vol_id as a shell script), but unless somebody decides to fix it "properly", I don't see much choice.
I've been living with this bug since Feisty broke Edgy, and Gutsy is no better (yet :-), but it's a bit of a pain...
Sadly, I've still got the problem.
I know *where* the problem is in my case, but no idea how to fix it :-( /bugs.launchpad .net/ubuntu/ +source/ udev/+bug/ 118292)
(See https:/
It comes down to vol_id not recognising a vfat partition: the device entry is created, and I can mount it by hand:
$ sudo mount -o ro -t vfat /dev/sdg1 /mnt
works fine.
But, /sbin/vol_id shows:
$ vol_id /dev/sdg1
/dev/sdg1: unknown volume type
Of course, the system *can* recognise the partition properly if you use a different command:
$ blkid /dev/sdg1
/dev/sdg1: LABEL="SEA_DISK" UUID="0000-0ED4" TYPE="vfat"
So as 118292 says, it's a udev (vol_id) bug (possibly under Ubuntu).
I am somewhat loath to do the workarounds suggested (especially rewriting vol_id as a shell script), but unless somebody decides to fix it "properly", I don't see much choice.
I've been living with this bug since Feisty broke Edgy, and Gutsy is no better (yet :-), but it's a bit of a pain...