does not detect file systems -- old vol_id rule in /etc/udev/rules.d

[piratemurray]

Binary package hint: gvfs

As requested by bug #463347 I'm creating this bug for my Casio digital camera. This is could be well related to the other USB auto mounting problems that are around Karmic. I can also report that none of my external USB devices automount.

I've tried stopping and starting udev. No luck.

I've tried installing the latest udeve release. No luck.

I can however manually mount these devices but I don't want to.

I'd appreciate some help with getting this and my other USB devices to work since everything used to work with Jaunty. Let me know what further information you need. Thanks again!

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 2b0cf00db3f4873927e0d1860c991de1
CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
Date: Tue Nov 10 16:57:15 2009
DistroRelease: Ubuntu 9.10
HotplugNewDevices: /dev/sdf1 /dev/sdf
HotplugNewMounts:

Package: gvfs 1.4.1-0ubuntu1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.49-generic
SourcePackage: gvfs
Symptom: storage
Uname: Linux 2.6.31-15-generic x86_64

[Nico Isenbeck (nico-isenbeck)]

Maybe a duplicate of bug #450546, Martin?

[piratemurray (mez-pahlan)]

I'm checking the suggestions of bug #450546 now to see if they help.

On an unrelated note I tried putting in a USB stick and restarting to see if upon restart the drive is recognised (as suggested by some posts). No luck I'm afraid.

[Martin Pitt (pitti)]

Does your USB stick automount? I. e. does this affect only your camera, or other USB hard disks/sticks as well?

The problem here is that udev does not detect the file system on this device. Can you please plug it in, and copy&paste the output of

  sudo blkid -p /dev/sdf1

? (Assuming that it is still /dev/sdf; the enumeration might change, please check "dmesg" after plugging it in).

> I can however manually mount these devices but I don't want to.

You mean with "sudo mount"?

[piratemurray (mez-pahlan)]

Hello again.

Yes this also affects other USB hard disks/ sticks however I have run your commands with respect to the digital camera first. Do let me know if you want them run against a USB stick as well?

You were right the enumeration did change to sdb1 (I got this from Palimpsest Disk Utility, which recognises the USB devices but as unrecognised, since I'm not too comfortable using dmesg just yet)

The out put is:

/dev/sdb1: UUID="0000-0DF1" VERSION="FAT32" TYPE="vfat" USAGE="filesystem"

I hope that helps?

[piratemurray (mez-pahlan)]

Sorry I forgot to reply to your last point. I manually mount my camera (and other USB sticks) for the time being following the instructions on this page https://help.ubuntu.com/community/Mount/USB#Manually%20Mounting

[Martin Pitt (pitti)]

Are you sure that /dev/sdb is your camera now? (since in your original report you had a lot of other devices, and your camera was only /dev/sdf). Can you please plug it in, and do

  udevadm info --export-db > /tmp/udev.txt
  sudo blkid > /tmp/blkid.txt

and attach /tmp/udev.txt and /tmp/blkid.txt here?

[Martin Pitt (pitti)]

Oh, please do that with your camera being plugged in, of course.

[piratemurray (mez-pahlan)]

I'm fairly certain /dev/sdb was my camera at the time I ran those tests. I will go home tonight and redo them along with your other suggestion.

[piratemurray (mez-pahlan)]

Ok here are the files you requested. Looks like the
camera is now sdf again. But I'm pretty sure it wasn't the last time.
Anyways I hope that doesn't cause much of an issue.

Thanks
again

[Martin Pitt (pitti)]

Thanks for making sure. So it seems to be confirmed that blkid works, but that information doesn't make it into blkid for some reason. Can you please plug in your camera, determine its device file (such as /dev/sdf1), and copy&paste the output of

  sudo udevadm test `udevadm info --query=path --name=/dev/sdf1`

? (Replace "sdf1" with the current device file). Thanks!

[piratemurray (mez-pahlan)]

Here you go. The output should be in the attachment. By the way what does this command do?

[Martin Pitt (pitti)]

It shows which rules udev runs for this device, and also calls the prober programs, so that you can see their output.

And voila:

udev_rules_apply_to_event: IMPORT 'vol_id --export /dev/sdf1' /etc/udev/rules.d/60-persistent-storage.rules:58
util_run_program: 'vol_id --export /dev/sdf1' started
util_run_program: '/lib/udev/vol_id' (stderr) 'util_run_program: program '/lib/udev/vol_id' not found'

There we go -- you still have a /etc/udev/rules.d/60-persistent-storage.rules which "shadows" the /lib/udev/rules.d/60-persistent-storage.rules that we ship by default now.

How did you install this? Was this an upgrade from a previous Ubuntu version? Do you use backup software which includes /etc and restore this file somehow? Did you ever modify this file manually here?

Can you please attach /etc/udev/rules.d/60-persistent-storage.rules here? We might be able to tell why it wasn't cleaned up on upgrade automatically.

Please make a backup copy of /etc/udev/rules.d/60-persistent-storage.rules (e. g. into your home directory) in case we need to examine it further, and then delete it with

  sudo rm /etc/udev/rules.d/60-persistent-storage.rules

This should fix things for you.

[piratemurray (mez-pahlan)]

Ahh ok so the /etc version was blocking the now default /lib version of the persistent storage rule?

I upgraded from Jaunty to the Karmic beta around October 12th ish and then around the 1st November I did the usual sudo apt-get upgrade -d with the intention of going from beta to full release. I didn't use any backup file to restore anything after the installation and I wouldn't mess about with anything in /etc unless it was recommended to.

Here's my /etc version of the file. So far deleting hasn't caused the camera device to auto mount but I will restart the computer just in case.

[piratemurray (mez-pahlan)]

This is fantastic! USB storage devices now mount correctly!!

The only problem I have now is that the icon that used to be created on the desktop for the mounted camera is no longer a camera icon but a generic USB stick icon. in Jaunty, for example, if I mounted a USB stick or a camera or my external HDD there would be three distinct icons that were used to show which was which. This is a minor issue though. I'm happy that the camera now auto mounts!

One other point to note that the desktop icon only appears after I click on the '8GB media' selection from the Places menu. Otherwise no icon appears. This is different to the behaviour of the USB stick which appeared on my desktop and the Places menu at the same time.

But thanks again for your help! This is why Ubuntu is so good!

[Martin Pitt (pitti)]

> Ahh ok so the /etc version was blocking the now default /lib version of the persistent storage rule?

Yes, an identically named file in /etc/udev/rules.d replaces /lib/udev/rules.d/.

> I upgraded from Jaunty to the Karmic beta around October 12th ish

Jaunty did not ship the file in /etc/ any more either. What Ubuntu version did you install originally?

I compared your file to the original versions in both hardy (8.04 LTS) and intrepid (8.10), and it's different from both of them. It's closer to the intrepid version, but even there there is still a diff:

 # forward scsi device event to corresponding block device
-ACTION=="change", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST=="block", ATTR{block/*/uevent}="change"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST=="block", ATTR{block/*/uevent}="change"

 ACTION!="add|change", GOTO="persistent_storage_end"
 SUBSYSTEM!="block", GOTO="persistent_storage_end"
@@ -51,12 +51,16 @@
 ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}-part%n"

 # skip unpartitioned removable media devices from drivers which do not send "change" events
-ENV{DEVTYPE}=="disk", KERNEL!="sd*|sr*", ATTR{removable}=="1", GOTO="persistent_storage_end"
+# ENV{DEVTYPE}=="disk", KERNEL!="sd*|sr*", ATTR{removable}=="1", GOTO="persistent_storage_end"
 # skip optical drives without media
+
+#XXX
+ENV{DEVTYPE}=="partition", IMPORT{program}="vol_id --export $tempnode"
+
 ENV{DEVTYPE}=="disk", KERNEL=="sr*", ENV{ID_CDROM_MEDIA_TRACK_COUNT}!="?*", GOTO="persistent_storage_end"

 # import filesystem metadata
-IMPORT{program}="vol_id --export $tempnode"
+#IMPORT{program}="vol_id --export $tempnode"

 # by-label/by-uuid links (filesystem metadata)
 ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

> The only problem I have now is that the icon that used to be created on the desktop for the mounted camera is no longer a camera icon

That sounds like a gvfs problem. Is there a "DCIM" folder on the camera? That's used as an indication of whether it is a digital camera. Please open a new report against gvfs, with the output of "gvfs-mount -li" and "ls -l /media/YOUR_CAMERA_NAME" when the camera is automounted.

[piratemurray (mez-pahlan)]

The first Ubuntu I installed was 8.04 Hardy via a CD downloaded from Canonical. I was on 8.10 Intrepid for only a brief period (a few hours) in order to upgrade to 9.04 Jaunty and then to Karmic in the steps outlined above. All upgrades have been done via the upgrade manager and the internet. I don't recall changing this file manually or even as part of a script.

The camera folder does have a DCIM folder so I will raise a new report on gvfs once I get home. Cheers.

[Scott James Remnant (Canonical) (canonical-scott)]

On Wed, 2009-11-11 at 21:15 +0000, piratemurray wrote:

> Ok here are the files you requested. Looks like the
> camera is now sdf again. But I'm pretty sure it wasn't the last time.
> Anyways I hope that doesn't cause much of an issue.
>
Can you run

udevadm test /class/block/sdf/sdf1

and supply the output?

Scott
--
Scott James Remnant
<email address hidden>

[Scott James Remnant (Canonical) (canonical-scott)]

On Wed, 2009-11-11 at 22:02 +0000, piratemurray wrote:

> Here you go. The output should be in the attachment. By the way what
> does this command do?
>
What is your /etc/udev/rules.d/60-persistent-storage.rules file doing;
did you follow some documentation that told you to create this?

Scott
--
Scott James Remnant
<email address hidden>

[piratemurray (mez-pahlan)]

Hi Scott

> What is your /etc/udev/rules.d/60-persistent-storage.rules file doing did you follow some documentation that told you to create this?
>
I don't know and no I didn't follow anything to create this. I assume from what Martin was saying that it was left over from a previous Ubuntu installation but not Jaunty (perhaps Intrepid?).

The file is now removed and the camera mounting automatically now. I'll run the command you requested when I get home. Thanks again.

[piratemurray (mez-pahlan)]

Here you go Scott. The output of udevadm test /class/block/sdf/sdf1 is attached.

[piratemurray (mez-pahlan)]

Oh actually Martin come to think about it I installed Xubuntu Jaunty for a brief period before I installed the Karmic beta. Not a clean install but one of those 'apt-get install xubuntu-desktop' things.

Could that be the cause of my automounting problems?

[Luke-Jr (luke-jr)]

Why is this bug marked Invalid?? My friend has the same problem with a fresh install of Kubuntu 9.10

[Luke-Jr (luke-jr)]

Sorry, posted on the wrong bug :(