MMC cards no longer auto mount

[Andy Whitcroft]

Binary package hint: gnome-volume-manager

When inserting an SDHC card into an MMC card reader in my Dell 1537 the card is no longer mounted. The card is detected by the kernel and the partitions detected, udev then creates the appropriate device files. The device is not mounted automatically. If I manually mount it, then gnome detects it and notes the photos offering to start fspot on them for import.

  $ udevadm monitor
  KERNEL[1252921022.493903] add /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/mmc_host/mmc0/mmc0:8fe4 (mmc)
  UDEV [1252921022.493929] add /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/mmc_host/mmc0/mmc0:8fe4 (mmc)
  KERNEL[1252921022.508157] add /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/mmc_host/mmc0/mmc0:8fe4/block/mmcblk0 (block)
  KERNEL[1252921022.508180] add /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/mmc_host/mmc0/mmc0:8fe4/block/mmcblk0/mmcblk0p1 (block)
  KERNEL[1252921022.508207] add /devices/virtual/bdi/179:0 (bdi)
  UDEV [1252921022.509283] add /devices/virtual/bdi/179:0 (bdi)
  UDEV [1252921022.572229] add /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/mmc_host/mmc0/mmc0:8fe4/block/mmcblk0 (block)
  UDEV [1252921023.021407] add /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/mmc_host/mmc0/mmc0:8fe4/block/mmcblk0/mmcblk0p1 (block)

ProblemType: Bug
Architecture: amd64
Date: Mon Sep 14 10:40:16 2009
DistroRelease: Ubuntu 9.10
Package: gnome-volume-manager 2.24.1-3ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SourcePackage: gnome-volume-manager
Uname: Linux 2.6.31-10-generic x86_64

[Andy Whitcroft (apw)]

erm, dunno what i did there but it wasn't meant for this bug thats for sure.

[Rick Spencer (rick-rickspencer3)]

please comment, change assignment, un-assign, as appropriate.

[Oleksiy Lukin (alukin)]

On my ASUS A6VM Ubuntu 9.10 does not see SD cards in build-in card reader at all, but it worked perfect in 9.04 and 8.10
 lspci output:
02:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 17)

dmesg does not says any messages on inserting/removing SD card.
Kerlnel is latest as for 2009-10-17
uname -a output:

Linux lukin 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

[Kai Jauch (kaijauch)]

Confirmed on a Dell Latitude E6400. The kernel detects the card and udev creates /dev/mmcblk0 and /dev/mmcblk0p1. Gnome doesn't list it anywhere, but I can mount it manually as root. It was working a few weeks ago.

KERNEL[1256317077.981652] add /devices/pci0000:00/0000:00:1e.0/0000:03:01.1/mmc_host/mmc0/mmc0:b368 (mmc)
UDEV [1256317077.981719] add /devices/pci0000:00/0000:00:1e.0/0000:03:01.1/mmc_host/mmc0/mmc0:b368 (mmc)
KERNEL[1256317077.985831] add /devices/pci0000:00/0000:00:1e.0/0000:03:01.1/mmc_host/mmc0/mmc0:b368/block/mmcblk0 (block)
UDEV [1256317077.985879] add /devices/virtual/bdi/179:0 (bdi)
KERNEL[1256317077.985923] add /devices/pci0000:00/0000:00:1e.0/0000:03:01.1/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p1 (block)
KERNEL[1256317077.985958] add /devices/virtual/bdi/179:0 (bdi)
UDEV [1256317078.032295] add /devices/pci0000:00/0000:00:1e.0/0000:03:01.1/mmc_host/mmc0/mmc0:b368/block/mmcblk0 (block)
UDEV [1256317078.170757] add /devices/pci0000:00/0000:00:1e.0/0000:03:01.1/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p1 (block)

gnome-volume-manager 2.24.1-3ubuntu1
udev 147~-6
kernel 2.6.31-14.48

[Kai Jauch (kaijauch)]

03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
03:01.2 SD Host controller: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11)

[Rick Spencer (rick-rickspencer3)]

somehow assigned to myself :/

[Martin Pitt (pitti)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

In Ubuntu 9.10 (Karmic) we have a new tool to debug storage related problems. Please run "ubuntu-bug", select "storage problem", and walk through the steps. This will create a new bug report, please send the new bug number here, so that I get to know it quickly.

Thank you!

[Colin Marquardt (ubuntu-marquardt-home)]

Though I'm not the original reporter, I added the requested info to bug 478770.

[Martin Pitt (pitti)]

Thanks Colin Marquardt, I'll reply in the new bug. However, this bug is about SDHC cards, so I won't mark it as a duplicate. I need "ubuntu-bug storage" from someone who is affected by this SHDC card problem.

[dkapell (david-rigitech)]

Martin: I have opened bug 479193 for a ubuntu-bug report for this issue.

[Kris (kriscampbell4)]

To Martin Pitt.

I have run into the problem you are asking about using a Patriot Memory SDHC 16GB card and internal card reader. The card does not mount automatically as it did in 9.04. IT does register under "places" and can be mounted manually. Here are the results of the ubuntu-bug test, I have submitted the results as well.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kris 2001 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfbbf4000 irq 16'
   Mixer name : 'Realtek ALC1200'
   Components : 'HDA:10ec0888,104382fe,00100101'
   Controls : 40
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbcec000 irq 19'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
CheckboxSubmission: a569623c13a3fb868a1442205a70c6ec
CheckboxSystem: edda5d4f616ca792bf437989cb597002
DKDisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
Date: Wed Nov 11 18:05:47 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=31955956-6762-4227-b751-86f013a08d3b
HotplugNewDevices:

HotplugNewMounts:

InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: fglrx
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=c32657d9-6556-47f5-bb50-ae9d32b548da ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 11/26/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1206
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A78-EM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Martin Pitt (pitti)]

Kris, looks like your problem is similar to bug 479193 (since you don't get any events in udevadm monitor), not to this one.

Andy, I still need this from you:

  udevadm monitor -e --udev 2>&1 | tee /tmp/udev.log
  devkit-disks --monitor-detail 2>&1 | tee /tmp/dkd.log
  gvfs-mount -oi 2>&1 | tee /tmp/gvfs.log

then insert the card, wait 10 seconds, and attach the three log files here. Thanks!

[lnx (nwegener)]

That is what I get:

udevadm monitor -e --udev 2>&1 | tee /tmp/udev.log
^C
root@norbert-laptop:~# ls -l /tmp/udev.log
-rw-r--r-- 1 root root 0 2009-11-18 19:58 /tmp/udev.log

udevadm monitor without further parameters:
udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1258570894.067959] add /devices/pci0000:00/0000:00:1e.0/0000:1c:03.2/mmc_host/mmc0/mmc0:0002 (mmc)
UDEV [1258570894.068710] add /devices/pci0000:00/0000:00:1e.0/0000:1c:03.2/mmc_host/mmc0/mmc0:0002 (mmc)
KERNEL[1258570894.075584] add /devices/pci0000:00/0000:00:1e.0/0000:1c:03.2/mmc_host/mmc0/mmc0:0002/block/mmcblk0 (block)
UDEV [1258570894.075633] add /devices/virtual/bdi/179:0 (bdi)
KERNEL[1258570894.075670] add /devices/virtual/bdi/179:0 (bdi)
UDEV [1258570894.743494] add /devices/pci0000:00/0000:00:1e.0/0000:1c:03.2/mmc_host/mmc0/mmc0:0002/block/mmcblk0 (block)

root@norbert-laptop:~# devkit-disks --monitor-detail 2>&1 | tee /tmp/dkd.log
Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
added: /org/freedesktop/DeviceKit/Disks/devices/mmcblk0
Showing information for /org/freedesktop/DeviceKit/Disks/devices/mmcblk0
  native-path: /sys/devices/pci0000:00/0000:00:1e.0/0000:1c:03.2/mmc_host/mmc0/mmc0:0002/block/mmcblk0
  device: 179:0
  device-file: /dev/mmcblk0
    by-id: /dev/disk/by-id/mmc-SD016_0x09000281
    by-path: /dev/disk/by-path/pci-0000:1c:03.2
  detected at: Mi 18 Nov 2009 19:58:33 CET
  system internal: 0
  removable: 0
  has media: 1 (detected at Mi 18 Nov 2009 19:58:33 CET)
    detects change: 0
    detection by polling: 0
    detection inhibitable: 0
    detection inhibited: 0
  is read only: 0
  is mounted: 0
  mount paths:
  mounted by uid: 0
  presentation hide: 0
  presentation nopolicy: 0
  presentation name:
  presentation icon:
  size: 13107200
  block size: 512
  job underway: no
  usage:
  type:
  version:
  uuid:
  label:
  drive:
    vendor:
    model: SD016
    revision: 01/2048
    serial: 09000281
    detachable: 0
    can spindown: 0
    rotational media: 0
    ejectable: 0
    media: flash_sd
      compat: flash_sd
    interface: sdio
    if speed: (unknown)
    ATA SMART: not available

^C

gvfs-mount -oi 2>&1 | tee /tmp/gvfs.log
more /tmp/gvfs.log
Monitoring events. Press Ctrl+C to quit.
norbert@norbert-laptop:~$

[Martin Pitt (pitti)]

Norbert, with the card being plugged in, can you please give me the output of

  sudo blkid -p /dev/mmcblk0

? Also, please do

  sudo udevadm test /class/block/mmcblk0

and copy&paste the output here.

Thanks!

[gataman (peteringata)]

I have the same problem. Does this help?
peter@peterb-netbook:~$ sudo blkid -p /dev/mmcblk0
peter@peterb-netbook:~$ sudo udevadm test /class/block/mmcblk0
run_command: calling: test
udevadm_test: version 147
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

parse_file: reading '/lib/udev/rules.d/40-gnupg.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-hplip.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ia64.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-infiniband.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-isdn.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libgphoto2-2.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libpisock9.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libsane.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-pilot-links.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ppc.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-xserver-xorg-input-wacom.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-zaptel.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-libmtp8.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-firmware.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
parse_file: reading '/lib/udev/rules.d/56-hpmud_support.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-cdrom_id.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-alsa.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-mobile-action.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-option-modem-modeswitch.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-persistent-storage-edd.rules' as rules file
parse_file: reading '/lib/udev/rules.d/64-device-mapper.rules' as rules file
parse_file: reading '/lib/udev/rules.d/65-dmsetup.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-acl.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-hid2hci.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-printers.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-net-description.rules' as ru...

[Martin Pitt (pitti)]

gataman [2010-01-04 16:51 -0000]:
> peter@peterb-netbook:~$ sudo blkid -p /dev/mmcblk0

That means that there's no recognized file system on that device at
all. Therefore this looks like quite a different symptom to the
original report here. Can you mount this with

  sudo mount /dev/mmcblk0 /mnt

?

> peter@peterb-netbook:~$ sudo udevadm test /class/block/mmcblk0
> [...]
> unable to open device '/sys/class/block/mmcblk0'

Does this path even exist for you then?

Martin

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[Jamin (jaminbw-sonic)]

I am having same Problem in Karmic 9.10 on acer aspire one. card did auto mount at start up until a few days ago.
First time I have ever bothered to post a bug so please bear with me if I haven't given enough information to help you.

[Jamin (jaminbw-sonic)]

jamin@Blacklabel:~$ sudo udevadm test /class/block/mmcblk0
[sudo] password for jamin:
run_command: calling: test
udevadm_test: version 147
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

parse_file: reading '/etc/udev/rules.d/10-vboxdrv.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-gnupg.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-hplip.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ia64.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-infiniband.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-isdn.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libgphoto2-2.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libpisock9.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libsane.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-pilot-links.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ppc.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-xserver-xorg-input-wacom.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-zaptel.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-libmtp8.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-firmware.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
parse_file: reading '/lib/udev/rules.d/56-hpmud_support.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-cdrom_id.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-alsa.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-mobile-action.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-option-modem-modeswitch.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-persistent-storage-edd.rules' as rules file
parse_file: reading '/lib/udev/rules.d/64-device-mapper.rules' as rules file
parse_file: reading '/lib/udev/rules.d/65-dmsetup.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-acl.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-hid2hci.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-printers.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-net-description.rules' a...

[Martin Pitt (pitti)]

Thanks Jamin. For you this seems to work alright. Can you please also give me the output of

  sudo udevadm test /class/block/mmcblk0p1

?

[gataman (peteringata)]

gataman [2010-01-04 16:51 -0000]:
> peter@peterb-netbook:~$ sudo blkid -p /dev/mmcblk0

That means that there's no recognized file system on that device at
all. Therefore this looks like quite a different symptom to the
original report here. Can you mount this with

  sudo mount /dev/mmcblk0 /mnt

?

> peter@peterb-netbook:~$ sudo udevadm test /class/block/mmcblk0
> [...]
> unable to open device '/sys/class/block/mmcblk0'

Does this path even exist for you then?

Martin

Hi Martin. Thanks for your reply

No I dont think the path above exists for me.
Under block I have sda,sda1,sda2,sda5,sdb,sdb1

[naputro (naputro)]

user@user-laptop:~$ sudo udevadm test /class /block /mmcblk0
run_command: calling: test
udevadm_test: version 147
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

parse_file: reading '/lib/udev/rules.d/40-gnupg.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-hplip.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ia64.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-infiniband.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-isdn.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libgphoto2-2.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libpisock9.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libsane.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-pilot-links.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ppc.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-xserver-xorg-input-wacom.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-zaptel.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-libmtp8.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-firmware.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
parse_file: reading '/lib/udev/rules.d/56-hpmud_support.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-cdrom_id.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-alsa.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-mobile-action.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-option-modem-modeswitch.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-persistent-storage-edd.rules' as rules file
parse_file: reading '/lib/udev/rules.d/64-device-mapper.rules' as rules file
parse_file: reading '/lib/udev/rules.d/65-dmsetup.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-acl.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-hid2hci.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-printers.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-net-description.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-persistent-net-generator.rules' as rules fi...

[Martin Pitt (pitti)]

> sudo udevadm test /class /block /mmcblk0

That doesn't work, please no spaces in between. Please just copy&paste the command that I gave:

  sudo udevadm test /class/block/mmcblk0p1

[Martin Pitt (pitti)]

ddcc, you haven't previously commented on this bug, and your udevadm test output looks correct. Thus it's a different root cause than the original report here. Can you please open a new bug with "ubuntu-bug storage"? (This will collect all necessary information)

[Martin Pitt (pitti)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!