[SOLVED] KDE does not detect USB drive after update

[AECFXI]

EDIT: I've discovered the issue is specifically a bizarre behavior with my base Gentoo system recognizing the exFAT filesystem on my USB drive. When a exFAT filesystem is initially formatted on the USB stick in KDE Partition Manager, the partition is recognized by the system and KDE automounts it and I have full read/write capabilities. However when the USB drive is safely removed, unplugged, and plugged back in, the drive itself is detected and has a target (/dev/sda) however the fielsystem on the USB device is not detected and there is no target present in /dev for the filesystem. The missing filesystem target can also be seen in my lsblk output below. The KDE partition manager says the partition type is "unknown", but can still reformat the drive. When the USB stick is then plugged into other hardware in my home, it works just fine. The behavior is common across multiple USB devices. I have exfatprogs installed and kernel-enabled exfat support.

I had a working functionality where KDE would detect and automount USB drives, with the drive visible in Dolphin and appearing in the Removable Devices system tray feature.

I recently discovered this feature is no longer working and have not had success in identifying a solution in search results.

The device appears in lsblk perfectly fine with the following output:

[AECFXI]

I followed the instructions on this page and section ( https://wiki.gentoo.org/wiki/Removable_media#Mounting_removable_media ) to edit /usr/share/polkit-1/actions/org.freedesktop.UDisks2.policy to allow for drive mounting by any rather than requiring root auth. No change was observed.

I followed these steps for kernel configuration and pulling in the exfatprogs tool: https://wiki.gentoo.org/wiki/ExFAT page. Also no change in behavior.

I have been observing some particularly bizarre behavior since I first had issues with USB sticks: If I open up the KDE partition manager, it says the flash drive partition is unknown. If I wipe it and write in an exfat partition, kde instantly automounts the usb drive and it appears in dolphin. But then if I 'safely remove' the USB stick, pull it out of my computer and then plug it back in, it does not automount and is not observed to exist in KDE's removable media system settings like before. What's more, looking carefully at the USB drive in the KDE partition manager with root access, it reports that the partition type (which moments ago had been showing exfat when I freshly formatted the drive and before I safely removed it) is now listed as "unknown" rather than exfat. It should be noted the USB stick works perfectly fine on a windows laptop and other equipment with the exfat partition I gave it in the KDE partition manager, it is only Gentoo that is refusing to recognize it when it is plugged in again.

[rab0171610]

[AECFXI]

In KDE System Settings -> Removable Storage -> Removable Devices, there is an entry for the USB stick in question however it is listed under "Disconnected Devices." I can select it and I've had "On Login" and "On Attach" both ticked, but the USB drive has stayed under Disconnected Devices even when I plug it in. I can also press "Forget Device" on this USB stick entry. When I do that, it disappears from the device list and nothing re-appears or changes when unplugging and replugging the USB drive.

Curiously, the bottom tick box for "Automatically mount removable media that have never been mounted before" is grayed out.

I can't "Forget" all devices because the attached NVME drive has the Forget Device optioned grayed out.

I am actually now thinking it is some kind of partition recognition issue that's developed on my system and not a KDE issue. The lsblk and dmesg output both made me think all is well on the low system level, however under /dev (and even lsblk if you look carefully) there is only /dev/sda and no /dev/sda1. Which says even the base system is not detecting any filessytem on the USB drive. I cannot even manually perform a mount with root because there is no filesystem target.

Should I make a new thread in the Kernel and Hardware forum, request this thread be moved, or continue to request support for this partition discovery issue in the Desktop Environments forum?

Also, to clarify: This same issue was initially observed across a variety of removable media and this particular USB device is confirmed to work on other hardware, to allay any concerns that we are dealing with a bad USB stick rather than a bad system.

[jburns]

Do you have CONFIG_MSDOS_PARTITION=y in .config

[AECFXI]

[rab0171610]

The problem was only with fat fs - sorry I didn't realize that. I'm happy you got things working correctly.