automount of USB disk does not work anymore after suspend to disk

Bug #114919 reported by zsquareplusc
2
Affects Status Importance Assigned to Milestone
gnome-volume-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

plugging in a USB memory stick pops up a nautilus window with its contents. this works fine after a reboot but as soon as i did a "suspend to disk" and resume it does not work anymore. dmesg shows that the hardware was recognized and i can manually mount it as root.
i also have other issues after resume such as the network applet does not reflect the network state correctly (network works but icon/message say no connection). the PC also does not power down but writes just a message to power off. i have to hold the power button for 5 seconds.

System is a AMD64 Feisty on Intel Core2 Duo, Intel 82801H (ICH8 Family) chipset.

Revision history for this message
zsquareplusc (zsquareplusc) wrote :

"sudo /etc/init.d/dbus restart" fixes the network applet but it does not help to automount the USB disk. i ran it once with a memory stick plugged in and once i plugged it in afterwards. both with the same result (no automount)

Revision history for this message
zsquareplusc (zsquareplusc) wrote :

looks like udev is recognizing the disk insertion. but the receiver of the event on the other end does not mount the disk.
dmesg shows the usual messages, all looking correct.
----
sudo udevmonitor
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent

inserting an SD card:
UEVENT[1179343324.009975] add /block/sdb/sdb1 (block)
UDEV [1179343324.065325] add /block/sdb/sdb1 (block)

inserting an USB stick:
UEVENT[1179343888.298531] add /devices/pci0000:00/0000:00:1a.7/usb1/1-2 (usb)
UEVENT[1179343888.298554] add /class/usb_endpoint/usbdev1.19_ep00 (usb_endpoint)
UEVENT[1179343888.300328] add /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0 (usb)
UEVENT[1179343888.300345] add /class/scsi_host/host20 (scsi_host)
UEVENT[1179343888.300354] add /class/usb_endpoint/usbdev1.19_ep81 (usb_endpoint)
UEVENT[1179343888.300363] add /class/usb_endpoint/usbdev1.19_ep01 (usb_endpoint)
UEVENT[1179343888.300371] add /class/usb_device/usbdev1.19 (usb_device)
UDEV [1179343888.301225] add /devices/pci0000:00/0000:00:1a.7/usb1/1-2 (usb)
UDEV [1179343888.323517] add /class/usb_endpoint/usbdev1.19_ep00 (usb_endpoint)
UDEV [1179343888.326976] add /class/usb_endpoint/usbdev1.19_ep81 (usb_endpoint)
UDEV [1179343888.337949] add /class/usb_endpoint/usbdev1.19_ep01 (usb_endpoint)
UDEV [1179343888.373922] add /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0 (usb)
UDEV [1179343888.376990] add /class/scsi_host/host20 (scsi_host)
UDEV [1179343888.407046] add /class/usb_device/usbdev1.19 (usb_device)
UEVENT[1179343893.301618] add /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/host20/target20:0:0/20:0:0:0 (scsi)
UEVENT[1179343893.301640] add /class/scsi_disk/20:0:0:0 (scsi_disk)
UEVENT[1179343893.306741] add /block/sdf (block)
UEVENT[1179343893.306757] add /block/sdf/sdf1 (block)
UEVENT[1179343893.306765] add /class/scsi_device/20:0:0:0 (scsi_device)
UEVENT[1179343893.306773] add /class/scsi_generic/sg6 (scsi_generic)
UDEV [1179343893.359309] add /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/host20/target20:0:0/20:0:0:0 (scsi)
UDEV [1179343893.366155] add /class/scsi_disk/20:0:0:0 (scsi_disk)
UDEV [1179343893.371678] add /class/scsi_device/20:0:0:0 (scsi_device)
UDEV [1179343893.382690] add /block/sdf (block)
UDEV [1179343893.402885] add /class/scsi_generic/sg6 (scsi_generic)
UDEV [1179343893.458105] add /block/sdf/sdf1 (block)

Revision history for this message
zsquareplusc (zsquareplusc) wrote :

running "gnome-mount --device /dev/sdb1" does mount the device as expected and it shows up in the block partitions applet and nautilus. i can access the data as user, as expected. digging the packages that depend on gnome-mount i found the gnome-volume-manager. now i see that no process of that name is running. when i type "gnome-volume-manager" in a console it is running again. and see its popping up the import dialogs and nautilus folders again!

so my guess is that gnome-volume-manager crashes either on suspend (to disk) or resume.

Revision history for this message
zsquareplusc (zsquareplusc) wrote :

after i started gnome-volume-manager manually it survived one suspend/resume cycle. automatically mounting worked and i was able to read and write. however unmounting did not work (complained about not being root and not listed in fstab). "sudo umount" worked then as expected.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta?

Changed in gnome-volume-manager:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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!.

Changed in gnome-volume-manager:
status: Incomplete → Invalid
Revision history for this message
xenesis (wagner-sim88) wrote :

This bug still exists in Ubuntu 8.10:

sudo fdisk -l says USB disk is /dev/sdd5

gnome-mount -v -t /dev/sdd5 says that /dev/sdd5 is not a volume.
However doing a manual mount works.

If you restart GNOME after suspend with sudo /etc/init.d/gdm restart, automounting will work again.

Furthermore, it seems like the kernel doesn't wake up external HDs correctly.
Before I go to suspend the disk was known as /dev/sdc, after wakeup its /dev/sdd. It should be /dev/sdc again.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.