Can't mount USB drive

Can’t mount USB drive in Tumbleweed KDE while it is successfully mounts on my Kubuntu Laptop. Dolphin prints error:

Error mounting /dev/sdd1 at /run/media/user/TRANSCEND: The function 'bd_fs_mount' called, but not implemented!

What is the problem and how to solve?

dmesg:

   72.496579] usb 3-2: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
   72.496589] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
   72.496595] usb 3-2: Product: DataTraveler 3.0
   72.496599] usb 3-2: Manufacturer: Kingston
   72.547077] usb-storage 3-2:1.0: USB Mass Storage device detected
   72.547399] scsi host6: usb-storage 3-2:1.0
   72.547558] usbcore: registered new interface driver usb-storage
   72.558363] usbcore: registered new interface driver uas
   73.567883] scsi 6:0:0:0: Direct-Access     Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
   73.568311] sd 6:0:0:0: Attached scsi generic sg4 type 0
   73.568669] sd 6:0:0:0: [sdd] 60604416 512-byte logical blocks: (31.0 GB/28.9 GiB)
   73.568937] sd 6:0:0:0: [sdd] Write Protect is off
   73.568942] sd 6:0:0:0: [sdd] Mode Sense: 45 00 00 00
   73.569203] sd 6:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
   73.724508]  sdd: sdd1
   73.725951] sd 6:0:0:0: [sdd] Attached SCSI removable disk
   89.015184] usb 5-3: reset high-speed USB device number 2 using ehci-pci
  117.251473] usb 5-3: reset high-speed USB device number 2 using ehci-pci

Can’t mount any flash drive which was not a problem few days ago.

Try logging in as a different user. I plugged in 2 sticks at once on TW20211213. Three of four partitions showed in Plasma’s popup, and as selected, each of the three mounted:

# dmesg tail
  136.663747] ext4 filesystem being remounted at /run/systemd/unit-ouser/var/tmp supports timestamps until 2038 (0x7fffffff)
  401.948901] usb 7-3: new high-speed USB device number 3 using ehci-pci
  402.234865] usb 7-3: New USB device found, idVendor=13fe, idProduct=4300, bcdDevice= 1.00
  402.234874] usb 7-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  402.234878] usb 7-3: Product: USB DISK 2.0
  402.234880] usb 7-3: Manufacturer:
  402.234883] usb 7-3: SerialNumber: 90000983E198BB33
  402.275491] usb-storage 7-3:1.0: USB Mass Storage device detected
  402.275728] scsi host8: usb-storage 7-3:1.0
  402.275861] usbcore: registered new interface driver usb-storage
  402.280931] usbcore: registered new interface driver uas
  405.267540] scsi 8:0:0:0: Direct-Access              USB DISK 2.0     PMAP PQ: 0 ANSI: 4
  405.268028] sd 8:0:0:0: Attached scsi generic sg2 type 0
  405.271377] sd 8:0:0:0: [sdb] 15132672 512-byte logical blocks: (7.75 GB/7.22 GiB)
  405.274211] sd 8:0:0:0: [sdb] Write Protect is off
  405.274217] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  405.276002] sd 8:0:0:0: [sdb] No Caching mode page found
  405.276006] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  405.295021]  sdb: sdb1 sdb2 sdb3
  405.300026] sd 8:0:0:0: [sdb] Attached SCSI removable disk
  410.024953] usb 7-4: new high-speed USB device number 4 using ehci-pci
  410.182121] usb 7-4: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
  410.182130] usb 7-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  410.182133] usb 7-4: Product: Ultra
  410.182136] usb 7-4: Manufacturer: SanDisk
  410.182138] usb 7-4: SerialNumber: 4C530000210529123153
  410.183191] usb-storage 7-4:1.0: USB Mass Storage device detected
  410.184234] scsi host9: usb-storage 7-4:1.0
  411.209903] scsi 9:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
  411.210261] scsi 9:0:0:0: Attached scsi generic sg3 type 0
  411.211509] sd 9:0:0:0: [sdc] 120127488 512-byte logical blocks: (61.5 GB/57.3 GiB)
  411.212761] sd 9:0:0:0: [sdc] Write Protect is off
  411.212766] sd 9:0:0:0: [sdc] Mode Sense: 43 00 00 00
  411.216274] sd 9:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
  411.253169]  sdc: sdc1
  411.257142] sd 9:0:0:0: [sdc] Attached SCSI removable disk
  487.864495] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
  490.458721] EXT4-fs (sdb3): mounting ext2 file system using the ext4 subsystem
  491.538937] EXT4-fs (sdb3): mounted filesystem without journal. Opts: errors=remount-ro. Quota mode: none.
  494.897308] ISO 9660 Extensions: Microsoft Joliet Level 3
  494.905065] ISO 9660 Extensions: Microsoft Joliet Level 3
  494.909850] ISO 9660 Extensions: RRIP_1991A
# df -h | egrep -v 'sda|srv'
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdc1        58G  1.2G   57G   2% /run/media/ouser/DFSPUP64BIO
/dev/sdb3       3.4G   32M  3.3G   1% /run/media/ouser/usrlclusb
/dev/sdb2       3.9G  3.9G     0 100% /run/media/ouser/openSUSE-Leap-15.4-DVD-x86_64119

I don’t know why the openSUSE 15.4 ESP on sdb1 didn’t show in Plasma’s popup.

Same with other user.

Are you able to mount sticks manually, as superuser if necessary?

Yes, I can.

I don’t know much else to suggest, except to wait for the next complete KDE rebuild (last happened around 3 days ago IIRC), and if it still is a problem after that, report a bug.

If you have BTRFS and snapshots, roll back 3-4 days or more to see if it still happens there.

Another thing: any time Plasma does strange things that you can’t stop, log out of it and delete ~/.cache/* before logging back into it.

Will wait for KDE update, cleaning the cache does not help.

Have the Tumbleweed UDisks libraries changed recently?

  • libudisks2-0 or similar …

How to check this? Updates history in yast does not allow to search in. Current version is 2.9.4-1.1.

Take a look in ‘/var/log/zypp/history’ – grep for ‘udisk’ …

> sudo cat /var/log/zypp/history | grep udisk 
2021-06-08 03:36:53|install|lib**udisk**s2-0|2.9.2-1.5|x86_64||openSUSE-20210605-0|0bcc1023d0361808b05ec41026e62f73596959ea2b4d07581610748379b2e713| 
2021-06-08 03:37:37|install|lib**udisk**s2-0_btrfs|2.9.2-1.5|x86_64||openSUSE-20210605-0|d8bff95a31899fb5847efaa7825233d1c560cf0da759e2630e7f160425c91871| 
# 2021-06-08 03:41:23 **udisk**s2-2.9.2-1.5.x86_64.rpm installed ok 
2021-06-08 03:41:23|install|**udisk**s2|2.9.2-1.5|x86_64||openSUSE-20210605-0|7f1084f4aec50400e4f3b960097f0bd540ed79e53a0ad023a66b39b35149a8b2| 
2021-06-08 03:41:31|install|**udisk**s2-lang|2.9.2-1.5|noarch||openSUSE-20210605-0|ad2c70257cfcd4cacb03b24b3aa4772d7a801d32d8d24cc57792546c70c35102| 
2021-09-23 01:29:57|install|lib**udisk**s2-0|2.9.2-1.6|x86_64||download.opensuse.org-oss|5c900d19be18947905f0cb23ceb159b8b672db8064a14cb36e8031d8d6a0d2ce| 
2021-09-23 01:39:20|install|lib**udisk**s2-0_btrfs|2.9.2-1.6|x86_64||download.opensuse.org-oss|9922c0c8e653c1185fab933327383afeebb3f2f25456846c0262ce8d95419243| 
2021-09-23 01:52:03|install|**udisk**s2|2.9.2-1.6|x86_64||download.opensuse.org-oss|4175667f26accbd70ac36869a280accf89771879f4d7cf2c97b56d990343c0d7| 
2021-09-23 01:52:05|install|**udisk**s2-lang|2.9.2-1.6|noarch||download.opensuse.org-oss|8cd300906feeb2e77f83faed9a77c103996f254a11674ba321aff5eae718f1ac| 
2021-12-13 11:00:52|install|lib**udisk**s2-0|2.9.4-1.1|x86_64||download.opensuse.org-oss|623e3637ff1c1f9630d26036f52eda9a5ce3a32fe8f5b9483ff496486e0e3baa| 
2021-12-13 11:01:20|install|lib**udisk**s2-0_btrfs|2.9.4-1.1|x86_64||download.opensuse.org-oss|323bffb7d838d95db762a7e991e932c3e50fd9b3a190476b98d48c6e9d12959c| 
2021-12-13 11:01:56|install|**udisk**s2|2.9.4-1.1|x86_64||download.opensuse.org-oss|4dd86a175e7d4e420d592b1682f34236bbe1f6217ca925e08c912f0b4a84fdd9| 
2021-12-13 11:01:59|install|**udisk**s2-lang|2.9.4-1.1|noarch||download.opensuse.org-oss|bf085519c147f6bd5eb5bb22119a181c91afd7686da3da35fe955ec24a28e50d| 

So it stopped to work after 2021-12-13.

With version 2.9.4 –

  • It was probably OK with version 2.9.2 …

Try to install version 2.9.2 and then lock that version to retain it until the next “zypper dup”.

Where to take it? Older tumbleweed spin? url?

You may well be forced to back off to an older Tumbleweed version …

No, exists there: http://download.opensuse.org/history/20211213/tumbleweed/repo/oss/x86_64/

However it does not work as well - same error. I’ve restarted after install.

Seems fixed after recent upgrades. How to mark this solved?

Hi
Your comment :wink: We don’t mark them as solved.

I marked it as solved - tag added. :wink: