Since Tumbleweed 20210622 I have the problem that Tumbleweed ignores when I insert an USB stick. Previously I received the message that a new drive was added and I selected “Mount and open”. Now nothing happens. If I select in the system Tray Disks & Devices I just get “No removable devices attached”. When selectiong “Configure Removable Devices” there is a tick at “Enable automatic mounting of removable media” and below are the tw0 ticks at “Automatically mount all removable media at login” and “Automatically mount all removable media when attached” and that is how it should be. However when I go into dolphin to /run/media/uli/<whatever name of device> it shows the device in dolphin. But even then it says at "Disks & Devices that no removable device is attached. What is there going on and how can that be fixed? I have just upgraded to version 20210623 but it is still the same.
JFI
I have the same problem. 3 usb memory sticks have become unusable. That’s on laptop and pc.
Backups were made to 64GB ScanDisk Ultra SIM memory cards, from USB HDD, and they appear to work reliably.
Suspect its a timing problem on the I/F.
Sorry cannot help further
I have no issues
Using KDE
I am using KDE too.
Not sure if it will help but after a USB stick is attached I get the following line in /etc/mtab"
uli@linux-4skc:~> cat /etc/mtab
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
......
/dev/sdb1 /run/media/uli/USB\040DISK vfat rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0022,codepage=437,iocharset=iso885
9-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0
uli@linux-4skc:~>
Disk & Devices still says "no removable devices attached. Nothing shows in dolphin and in /etc/fstab is only sda listed.
Further the command dmesg | grep sdb for the last two times I tried today
[FONT=monospace]uli@linux-4skc:~> dmesg | grep sdb
**sdb**: **sdb**1
[16945.159354] sd 2:0:0:0: **sdb**] Attached SCSI removable disk
[16945.352779] FAT-fs (**sdb**1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[17082.708756] **sdb**: detected capacity change from 122880000 to 0
[17549.501483] sd 2:0:0:0: **sdb**] 61440000 512-byte logical blocks: (31.5 GB/29.3 GiB)
[17549.501949] sd 2:0:0:0: **sdb**] Write Protect is off
[17549.501960] sd 2:0:0:0: **sdb**] Mode Sense: 23 00 00 00
[17549.502406] sd 2:0:0:0: **sdb**] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[17549.535309] **sdb**: **sdb**1
[17549.537573] sd 2:0:0:0: **sdb**] Attached SCSI removable disk
[17549.726085] FAT-fs (**sdb**1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[17640.277978] **sdb**: detected capacity change from 61440000 to 0
[18788.745575] sd 2:0:0:0: **sdb**] 61440000 512-byte logical blocks: (31.5 GB/29.3 GiB)
[18788.746054] sd 2:0:0:0: **sdb**] Write Protect is off
[18788.746060] sd 2:0:0:0: **sdb**] Mode Sense: 23 00 00 00
[18788.746465] sd 2:0:0:0: **sdb**] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[18788.770485] **sdb**: **sdb**1
[18788.771944] sd 2:0:0:0: **sdb**] Attached SCSI removable disk
[18788.932123] FAT-fs (**sdb**1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[19400.019359] **sdb**: detected capacity change from 61440000 to 0
[34343.997362] sd 2:0:0:0: **sdb**] 122880000 512-byte logical blocks: (62.9 GB/58.6 GiB)
[34343.997524] sd 2:0:0:0: **sdb**] Write Protect is off
[34343.997534] sd 2:0:0:0: **sdb**] Mode Sense: 43 00 00 00
[34343.997688] sd 2:0:0:0: **sdb**] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[34344.026031] **sdb**: **sdb**1
[34344.027687] sd 2:0:0:0: **sdb**] Attached SCSI removable disk
[34344.194017] FAT-fs (**sdb**1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[34713.419463] **sdb**: detected capacity change from 122880000 to 0
uli@linux-4skc:~>
[/FONT]
You may try journal:
**3400G:~ #** journalctl -b 0 _KERNEL_SUBSYSTEM=usb _KERNEL_SUBSYSTEM=scsi --since 09:00
-- Logs begin at Thu 2021-06-24 13:51:04 CEST, end at Fri 2021-06-25 09:16:52 CEST. --
Jun 25 09:14:47 3400G kernel: usb 2-3: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Jun 25 09:14:47 3400G kernel: usb 2-3: New USB device found, idVendor=090c, idProduct=2000, bcdDevice=11.00
Jun 25 09:14:47 3400G kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 25 09:14:47 3400G kernel: usb 2-3: Product: Intenso Ultra Line
Jun 25 09:14:47 3400G kernel: usb 2-3: Manufacturer: SMI
Jun 25 09:14:47 3400G kernel: usb 2-3: SerialNumber: CCYYMMDDHHmmSSUP
Jun 25 09:14:47 3400G kernel: usb-storage 2-3:1.0: USB Mass Storage device detected
Jun 25 09:14:47 3400G kernel: scsi host8: usb-storage 2-3:1.0
Jun 25 09:14:48 3400G kernel: **scsi 8:0:0:0: Direct-Access Intenso Ultra Line 1100 PQ: 0 ANSI: 6**
Jun 25 09:14:48 3400G kernel: **sd 8:0:0:0: Attached scsi generic sg3 type 0**
Jun 25 09:14:48 3400G kernel: **sd 8:0:0:0: [sdd] 62545920 512-byte logical blocks: (32.0 GB/29.8 GiB)**
Jun 25 09:14:48 3400G kernel: **sd 8:0:0:0: [sdd] Write Protect is off**
Jun 25 09:14:48 3400G kernel: sd 8:0:0:0: [sdd] Mode Sense: 43 00 00 00
Jun 25 09:14:48 3400G kernel: **sd 8:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA**
Jun 25 09:14:48 3400G kernel: **sd 8:0:0:0: [sdd] Attached SCSI removable disk**
Jun 25 09:14:53 3400G kernel: usb 2-3: USB disconnect, device number 2
**3400G:~ #**
Consider deleting the system tray and trying a new one.
[34344.194017] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Maybe run an check.
I have no solution, but a few remarks.
Please use CODE tags, not HTML tags. The CODE tags is one left of the HTML tags (the # left of the <>).
Better use
mount
instead of
cat /etc.mtab
It provides the same, but is a more general accepted means of showing what is mounted.
Of course there is not change to /etc/fstab. That is only a configuration file, to be managed by the system manager (probably using tools like YaST > partitioner, or by editing). It does not show a prsent situation.
BTW, your mtab show that the file system (vfat) is mounted on a mount point as they are normally created for spontanious added mass-storage when done by a user (in this case uli) sitting “in the seat” of a desktop session. The ownership to be faked is for UID 1000 and group 100. That is all as to be expected after that desktop user would have clicked on one of the options in the pop-up menu.
That all looks very normal and, as you say, it is usable.
The only thing that is problematic is that the mounting is done without you seeing the pop-up and giving an opportunity to use it by file manager, Gwenview, …, or not at all.
I wonder if that isn’t the result from all those “automatic mount at …” features that are switched on. I, in my KDE on Leap 15.2, have that “Enable automatic mounting of removable media” not checked on. And when I connect mass-storage to an USB port, I get the pop-up.
BTW, I admit that the word “automatic” is problematic. Specially in relation with the mounting of file systems. I know of at least three interpretations of “automatic” or “auto…” in relation to mounting.
(For some people “automatic” is another word for “magically”, in other words for everything they do not understand).
fwiw
with some usb memory sticks, when plugged in, mtab shows 24 lines of data,
with others, although identified as present in KDE, the file system cannot be accessed,
mtab shows a file size of 0 bytes.
the problematic usb memory sticks are 64GB and 32GB, these can be reformated in Yast,
both ext4 and xfs have been used, but within a few days become unusable again.
using fsck and xfs_repair, again only help for a few days.
after these progs used, directory lost+found soon begin to fill up
the contents of usb memory sticks is,
~ 25k files in
~ 1,5k directories
The above is not behavior as expected with working hardware. Installed btrfs on this large stick and copied system snapshots until full (more than 1,000,000 files):
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 114.61 GiB block-size:
physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
**
No problems encountered. No problem with btrfs balance, scrub or trim. No file system errors, no messages from usb or scsi kernel subsystems.**
I have this problem too…whenever I plug in any USB drive the applet doesn’t pop up as before. However it is available in Dolphin which I can open and access the files without any problem. But I still would like to have the popup.
When I go to the “Disks & Devices” icon, it does not show any removable disks despite the options for it is enabled.
And did you check my suggestion to uncheck “automatic mount” in KDE?
I guess that when you have “automatic mount” on, you can not complain that it is done without asking you.
You may try log out from Plasma and log in to tty1. Move file .config/plasma-org.kde.plasma.desktop-appletsrc to a safe place, say home directory and log in to plasma again. It will create a new .config/plasma-org.kde.plasma.desktop-appletsrc. Does device manager now work correctly?
Thank you to all of you who contributed overnight. Thanks Karlmistelberger for the journal options here they nare:
linux-4skc:~ # journalctl -b 0 _KERNEL_SUBSYSTEM=usb _KERNEL_SUBSYSTEM=scsi --since 09:00
......
Jun 26 09:20:34 linux-4skc kernel: usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Jun 26 09:20:34 linux-4skc kernel: usb 2-2: New USB device found, idVendor=090c, idProduct=2000, bcdDevice=11.00
Jun 26 09:20:34 linux-4skc kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 26 09:20:34 linux-4skc kernel: usb 2-2: Product: USB DISK
Jun 26 09:20:34 linux-4skc kernel: usb 2-2: Manufacturer: SMI Corporation
Jun 26 09:20:35 linux-4skc kernel: usb-storage 2-2:1.0: USB Mass Storage device detected
Jun 26 09:20:35 linux-4skc kernel: scsi host2: usb-storage 2-2:1.0
Jun 26 09:20:37 linux-4skc kernel: **scsi 2:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 6**
Jun 26 09:20:37 linux-4skc kernel: **sd 2:0:0:0: Attached scsi generic sg1 type 0**
Jun 26 09:20:37 linux-4skc kernel: **sd 2:0:0:0: [sdb] 122880000 512-byte logical blocks: (62.9 GB/58.6 GiB)**
Jun 26 09:20:37 linux-4skc kernel: **sd 2:0:0:0: [sdb] Write Protect is off**
Jun 26 09:20:37 linux-4skc kernel: sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
Jun 26 09:20:37 linux-4skc kernel: **sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA**
Jun 26 09:20:37 linux-4skc kernel: **sd 2:0:0:0: [sdb] Attached SCSI removable disk**
Jun 26 09:21:13 linux-4skc kernel: usb 2-2: USB disconnect, device number 2
Jun 26 09:22:01 linux-4skc kernel: usb 2-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Jun 26 09:22:01 linux-4skc kernel: usb 2-2: New USB device found, idVendor=1f75, idProduct=0918, bcdDevice= 3.10
Jun 26 09:22:01 linux-4skc kernel: usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jun 26 09:22:01 linux-4skc kernel: usb 2-2: Product: STORAGE DEVICE
Jun 26 09:22:01 linux-4skc kernel: usb 2-2: Manufacturer: Device Storage
Jun 26 09:22:01 linux-4skc kernel: usb 2-2: SerialNumber: 46980919
Jun 26 09:22:01 linux-4skc kernel: usb-storage 2-2:1.0: USB Mass Storage device detected
Jun 26 09:22:01 linux-4skc kernel: scsi host2: usb-storage 2-2:1.0
Jun 26 09:22:02 linux-4skc kernel: **scsi 2:0:0:0: Direct-Access Specific STORAGE DEVICE 0009 PQ: 0 ANSI: 6**
Jun 26 09:22:02 linux-4skc kernel: **sd 2:0:0:0: Attached scsi generic sg1 type 0**
Jun 26 09:22:02 linux-4skc kernel: **sd 2:0:0:0: [sdb] 61440000 512-byte logical blocks: (31.5 GB/29.3 GiB)**
Jun 26 09:22:02 linux-4skc kernel: **sd 2:0:0:0: [sdb] Write Protect is off**
Jun 26 09:22:02 linux-4skc kernel: sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
Jun 26 09:22:02 linux-4skc kernel: **sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA**
Jun 26 09:22:02 linux-4skc kernel: **sd 2:0:0:0: [sdb] Attached SCSI removable disk**
**linux-4skc:~ #**
Though I can’t see what the problem is. May be someone else can.
Sauerland, when you cannot see anywhere that the USB stick is mounted and have no option to unmount and just pull it out then you get this command line telling you not properly unmounted. I tried with two different USB sticks and I don’t think both have the same corruption. But how should you remove the USB stick then when nothing shows?
hcvv sorry about the HTML tags I just hit the wrong symbosl. You can see that these are the code tags which I added when I noticed it but I didn’t delete the HTML tags completely.
BTW, your mtab show that the file system (vfat) is mounted on a mount point as they are normally created for spontanious added mass-storage when done by a user (in this case uli) sitting “in the seat” of a desktop session. The ownership to be faked is for UID 1000 and group 100. That is all as to be expected after that desktop user would have clicked on one of the options in the pop-up menu.
That all looks very normal and, as you say, it is usable.
THat is what happened before the update. Now nothingn shows, and nothing can be clicked, Disks & Devices in the system tray says no removable file attached. THe only thing I can do is to go to /run/media/uli/<devicename> to see the device. That is the problem this thread is about. By the way I have tried to have the automatic mounting unchecked and it makes no difference.
I will try to delete ~/.config/plasma-org.kde.plasma.desktop-appletsrc lateron to see if that makes any difference and report about it later.
OK, thank you karlmistelberger, the deleting of ~/.config/plasma-org.kde.plasma.desktop-appletsrc did the trick, It seems the mounting/unmounting is now back to normal. I didn’t know that this file is the configuration file so I learned something new. And,keellambert, in the config panel the automatic mounting needs to be unchecked. Thank you to everyone who got involved.
See this bug report: https://bugs.kde.org/show_bug.cgi?id=438874
Thanks for the feedback. When the clipboard was gone from the system tray this morning, deleting it and adding a new tray would restore the clipboard. Users may first try to remove and create again the affected element on the panel before removing the whole panel.
Removing the system tray and adding it again did the trick! Thanks karlmistelberger.
I was dreading removing the plasma configuration as I have a lot of settings / configurations that I made for my workflow. Thanks once again.
You are welcome. Thanks for the feedback.
thanks go to karlmistelberger
removing .config/plasma-org.kde.plasma.desktop-appletsrc seems to have
cleared most of the problems
next I’ll try replacing the system tray