Removable media are not mounted automatically

Bug #1946525 reported by Akbarkhon Variskhanov
68
This bug affects 12 people
Affects Status Importance Assigned to Milestone
udisks2 (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

1) Ubuntu Desktop amd 64 20211008.1 daily build
2) udisks 2.9.4-1
3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically
4) the automount feature seems to be gone or non-functional in the last couple of days

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: udisks2 2.9.4-1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules
Date: Sat Oct 9 01:37:13 2021
InstallationDate: Installed on 2021-10-08 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
     |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Akbarkhon Variskhanov (kbar) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1946525

tags: added: iso-testing
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Is that a virtualbox issue? Could you try connecting for example an usb stick and see if that's also not working? Could you give some extra details on the setup used to test the bug?

Changed in udisks2 (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Akbarkhon Variskhanov (kbar) wrote :

Yes. This behavior is observed in a VirtualBox virtual machine. It doesn't occur every time.

I'll try reproducing it on a hardware in a live session environment and see if I can get relevant journal entries and outputs.

Thank you.

Revision history for this message
Nicolás Abel Carbone (nicocarbone) wrote :
Download full text (3.4 KiB)

I am seeing the same behavior on real hardware after upgrading to Ubuntu 21.10.

This is what I see on the logs after connecting a TOSHIBA SSD in a SATAtoUSB enclosure (I plugged it two times, at 12:08 and 12:09):

12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1.
12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1.
12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_arm64 /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1.
12:09:16 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_arm /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3 189:133' failed with exit code 1.
12:09:16 mtp-probe: bus: 2, device: 6 was not an MTP device
12:09:16 mtp-probe: bus: 2, device: 6 was not an MTP device
12:09:16 mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3"
12:09:16 systemd-udevd: 2-2.3:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3/2-2.3:1.0 0:0' failed with exit code 1.
12:09:16 mtp-probe: bus: 2, device: 6 was not an MTP device
12:09:16 kernel: scsi host9: uas
12:09:16 kernel: usb 2-2.3: SerialNumber: 000000123AE3
12:09:12 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper remove snap_qemu-virgil_qemu-virgil /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3 189:132' failed with exit code 1.
12:09:12 kernel: sd 9:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
12:09:12 kernel: usb 2-2.3: USB disconnect, device number 5
12:08:47 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3 189:132' failed with exit code 1.
12:08:47 kernel: sd 9:0:0:0: [sda] Attached SCSI disk
12:08:47 kernel: sda: sda1
12:08:47 mtp-probe: bus: 2, device: 5 was not an MTP device
12:08:47 systemd-udevd: 2-2.3:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_qemu-virgil_qemu-virgil /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3/2-2.3:1.0 0:0' failed with exit code 1.
12:08:47 mtp-probe: bus: 2, device: 5 was not an MTP device
12:08:47 kernel: sd 9:0:0:0: [sda] Optimal transfer size 33553920 bytes
12:08:47 mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3"
12:08:47 kernel: scsi 9:0:0:0: Direct-Access TOSHIBA THNSNH128GBS HTRA PQ: 0 ANSI: 6
12:08:47 kernel: usb 2-2.3: SerialNumber: 000000123AE3
12:08:43 systemd-udevd: 2-2.3: Process '/usr/lib/snapd/snap-device-helper remove snap_qemu-virgil_qemu-virgil /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb2/2-2/2-2.3 189:130' failed with exit code 1.
12:08:43 kernel: sd 9:0:0:0: [sda] Synchronize Cache(10) f...

Read more...

Changed in udisks2 (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Akbarkhon Variskhanov (kbar) wrote :

I have tried to reproduce this bug numerous times, but to no avail. Further testing is required.

Revision history for this message
Björn Hutmacher (bjorn-hutmacher) wrote :

I have two machines, both upgraded to Ubuntu 21.10. Since the upgrade, automounting removable media has stopped working completely on both of these two. For regular USB disks, etc. I can mount them manually either from the console or by using the Gnome Disks utility. However, I have no idea about how I'm supposed to mount an MTP storage like my phone.

The USB devices are obviously being detected, but there seems to be no mechanism active to mount it to the usual /media/<username>/<UUID> path.

My results are consistent with no exceptions.

summary: - Disks are not being mounted automatically
+ Removable media are not mounted automatically
Revision history for this message
Akbarkhon Variskhanov (kbar) wrote :

@bjorn-hutmacher, thank you for the thorough description!

Do removable media show up in the Files at least? In my case, I could see them being recognized and I could click on them, which would then mount them successfully.

Revision history for this message
Björn Hutmacher (bjorn-hutmacher) wrote :

No, the only indication of me inserting a removable storage is in dmesg where the device is acknowledged. I have to either mount the device manually from shell or go through the Gnome Disks utility. Today I discovered that connecting my phone, which uses MTP for file transfers, doesn't mount automatically anymore either. Could be related.

Revision history for this message
Sebastien Bacher (seb128) wrote :

@Björn, do you use the standard kernel?

Could you start
$ udevadm monitor

connect a device which isn't working properly and then copy the log to the bug?

Revision history for this message
Björn Hutmacher (bjorn-hutmacher) wrote :
Download full text (8.2 KiB)

I'm using kernel 5.15.0-051500rc5-lowlatency from https://kernel.ubuntu.com/~kernel-ppa/mainline. I guess I could try the official standard kernel as well.

udevadm monitor reports this on insertion of a USB pen drive:

KERNEL[34211.745784] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3 (usb)
KERNEL[34211.766347] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0 (usb)
KERNEL[34211.766487] add /devices/virtual/workqueue/scsi_tmf_15 (workqueue)
KERNEL[34211.766582] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15 (scsi)
KERNEL[34211.766596] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/scsi_host/host15 (scsi_host)
KERNEL[34211.766623] bind /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0 (usb)
KERNEL[34211.766651] bind /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3 (usb)
UDEV [34211.768695] add /devices/virtual/workqueue/scsi_tmf_15 (workqueue)
UDEV [34211.782340] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3 (usb)
UDEV [34211.786977] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0 (usb)
UDEV [34211.787738] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15 (scsi)
UDEV [34211.788758] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/scsi_host/host15 (scsi_host)
UDEV [34211.789765] bind /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0 (usb)
UDEV [34211.792650] bind /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3 (usb)
KERNEL[34212.770824] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0 (scsi)
KERNEL[34212.770866] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0 (scsi)
KERNEL[34212.770889] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_device/15:0:0:0 (scsi_device)
KERNEL[34212.770943] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_generic/sg11 (scsi_generic)
KERNEL[34212.770964] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_disk/15:0:0:0 (scsi_disk)
KERNEL[34212.771058] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/bsg/15:0:0:0 (bsg)
UDEV [34212.772488] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0 (scsi)
UDEV [34212.773741] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0 (scsi)
UDEV [34212.774701] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_device/15:0:0:0 (scsi_device)
UDEV [34212.775890] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_generic/sg11 (scsi_generic)
UDEV [34212.776260] add /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb2/2-3/2-3:1.0/host15/target15:0:0/15:0:0:0/scsi_disk/15:0:0:0 (scsi_disk)
UDEV [34212.7766...

Read more...

Revision history for this message
Björn Hutmacher (bjorn-hutmacher) wrote :

Okay, so now I've also tried this with 5.13.0-20-generic from the official repository with the exact same result.

Johan Tol (jto-joto)
description: updated
Revision history for this message
Henrik Dahle (hodahle) wrote :

It's a strange one. I appear to have had this as well. The output from dmesg shows it detects the drive just fine. It also appears in Nautilus, which will mount it for you when you click on it, but that's obviously a complete no-go.

What fixed it for me was simply reinstalling the fuse package:

sudo apt install --reinstall fuse

and rebooting, as per the advice here https://askubuntu.com/questions/1361627/ubuntu-mate-21-04-usb-stick-will-not-automount which I know isn't 21.10, but worked for me regardless. No clue why it went wrong in the first place, but at least I've got it sorted for now.

Revision history for this message
Eric Buell (erbuell) wrote (last edit ):

Noob to Ubuntu... I have a similar problem with a U.S. Robotics USR5637 modem. lsusb and usb-devices both show the device, and dmesg shows it being recognized, however it does not show up in /dev as ttyACM*. Running 21.10 on a Raspberry Pi 4. The device works as expected with 20.04.3 LTS also on a Pi 4. I tried Henrik Dahle's work around of reinstalling fuse simply because he had luck with it, but no joy. The device is also not created with it left installed during a reboot.

lsusb:
Bus 001 Device 008: ID 0baf:0303 U.S. Robotics USR5637 56K Faxmodem

usb-devices:
T: Bus=01 Lev=04 Prnt=06 Port=01 Cnt=01 Dev#= 8 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0baf ProdID=0303 Rev=02.00
S: Manufacturer=U.S.Robotics
S: Product=USB Modem
S: SerialNumber=0000002
C: #Ifs= 2 Cfg#= 2 Atr=80 MxPwr=360mA
I: If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=(none)
I: If#=0x1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none)

dmesg:
[ 127.376952] usb 1-1.2.4.1: new high-speed USB device number 7 using xhci_hcd
[ 127.585699] usb 1-1.2.4.1: New USB device found, idVendor=0baf, idProduct=0303, bcdDevice= 2.00
[ 127.585739] usb 1-1.2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=10
[ 127.585757] usb 1-1.2.4.1: Product: USB Modem
[ 127.585771] usb 1-1.2.4.1: Manufacturer: U.S.Robotics
[ 127.585784] usb 1-1.2.4.1: SerialNumber: 0000002
[ 127.747138] kauditd_printk_skb: 518 callbacks suppressed
[ 127.747159] audit: type=1400 audit(1646439492.316:597): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.1/busnum" pid=2810 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 127.747191] audit: type=1400 audit(1646439492.316:598): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.1/devnum" pid=2810 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Revision history for this message
giacof (giacof) wrote :

I'm having the same issue on Ubuntu 21.10. It's NOT a VirtualBox virtual machine, but an Ubuntu desktop installation on a physical volume.

When I insert any usb device, it doesn't get mounted, despite org.gnome.desktop.media-handling configuration:

$ gsettings get org.gnome.desktop.media-handling automount
true
$ gsettings get org.gnome.desktop.media-handling automount-open
true

Here is dmesg log after connecting my smartphone via usb:

[13254.311575] usb 3-6: USB disconnect, device number 5
[13265.122249] usb 3-6: new high-speed USB device number 7 using xhci_hcd
[13265.250291] usb 3-6: device descriptor read/64, error -32
[13265.506983] usb 3-6: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 4.04
[13265.506991] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[13265.506994] usb 3-6: Product: Redmi 9
[13265.506996] usb 3-6: Manufacturer: Xiaomi
[13265.506998] usb 3-6: SerialNumber: cXXXXXXXXX
[13272.500089] usb 3-6: USB disconnect, device number 7
[13272.946154] usb 3-6: new high-speed USB device number 8 using xhci_hcd
[13273.094848] usb 3-6: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 4.04
[13273.094862] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[13273.094867] usb 3-6: Product: Redmi 9
[13273.094872] usb 3-6: Manufacturer: Xiaomi
[13273.094875] usb 3-6: SerialNumber: cXXXXXXXXX

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.