Dolphin doesn't show one of my partitions under 'Devices'

janr · September 25, 2024, 11:15am

Hello,

I have some partitions on my system with test installations of distros.
There is one of them, that weirdly doesnt show up in Dolphin’s ‘Devices’ section. Since I have run out of ideas what could cause this, I’m asking if anybody else may have a clue?

Additional information:

OS: Kubuntu 24.10 with Dolphin 24.08.1, Plasma 6.1.5 , Frameworks 6.6, Qt 6.6.2
SSD is partitioned with gpt.
Missing partition contains a Neon Unstable installation, formatted with Btrfs (without containing any subvolumes so far).
Missing partition is not displayed when I enable showing hidden sidebar entries in Dolphin.
Missing partition has not an fstab entry (same as my other test partitions).
Other test partitions on that SSD do show up just fine.
The missing partition did show up once shortly after creating it – I can’t remember whether I had mounted it via Dolphin back then or not, but I do remember I had mounted it manually in a custom directory with sudo mount /dev/....
Mounting it manually shows no sign of problems.

Is there maybe a place where Dolphin stores a list of partition that it will never display?

Kind regards, Jan

meven · October 9, 2024, 9:43am

You can use solid-hardware6 query 'Is StorageAccess' to query the drives dolphin potentially can show.

If your btrfs mount is there. You can solid-hardware6 details <UDI> and post it here.

If it is not present it is a bug in solid.
I have a MR that may fix that case.

janr · October 9, 2024, 11:47am

@meven Thanks, solid-hardware6 query includes that particular partition.

Output for the invisible partition:

$ solid-hardware6 details '/org/freedesktop/UDisks2/block_devices/sda3'
udi = '/org/freedesktop/UDisks2/block_devices/sda3'
  parent = '/org/freedesktop/UDisks2/drives/CT1000BX500SSD1_2050E4DBD355' (string)
  vendor = '' (string)
  product = 'CT1000BX500SSD1' (string)
  description = 'neon-test' (string)
  icon = 'drive-harddisk' (string)
  Block.major = 8  (0x8)  (int)
  Block.minor = 3  (0x3)  (int)
  Block.device = '/dev/sda3' (string)
  StorageAccess.accessible = false (bool)
  StorageAccess.filePath = '' (string)
  StorageAccess.ignored = true (bool)
  StorageAccess.encrypted = false (bool)
  StorageVolume.ignored = true (bool)
  StorageVolume.usage = 'FileSystem'  (0x2)  (enum)
  StorageVolume.fsType = 'btrfs' (string)
  StorageVolume.label = 'neon-test' (string)
  StorageVolume.uuid = '3cb37636-c4d2-4835-a1d0-e21b1ee1ce64' (string)
  StorageVolume.size = 21474836480  (0x500000000)  (qulonglong)

For comparision, this is the output for one of the visible partitions:

$ solid-hardware6 details '/org/freedesktop/UDisks2/block_devices/sda2'
udi = '/org/freedesktop/UDisks2/block_devices/sda2'
  parent = '/org/freedesktop/UDisks2/drives/CT1000BX500SSD1_2050E4DBD355' (string)
  vendor = '' (string)
  product = 'CT1000BX500SSD1' (string)
  description = 'kubuntu-test' (string)
  icon = 'drive-harddisk' (string)
  Block.major = 8  (0x8)  (int)
  Block.minor = 2  (0x2)  (int)
  Block.device = '/dev/sda2' (string)
  StorageAccess.accessible = false (bool)
  StorageAccess.filePath = '' (string)
  StorageAccess.ignored = true (bool)
  StorageAccess.encrypted = false (bool)
  StorageVolume.ignored = false (bool)
  StorageVolume.usage = 'FileSystem'  (0x2)  (enum)
  StorageVolume.fsType = 'ext4' (string)
  StorageVolume.label = 'kubuntu-test' (string)
  StorageVolume.uuid = '40f51d0f-ebc1-4797-8616-263836bd3dc6' (string)
  StorageVolume.size = 21474836480  (0x500000000)  (qulonglong)

meven · October 9, 2024, 12:18pm

That’s the reason, dolphin does not show it.

It is udisks that classified as ignored.

Might want to try:
https://wiki.archlinux.org/title/Udisks#Hidden_devices

eeeeeeeeee · October 9, 2024, 1:15pm

Not entirely sure the arch wiki is giving the best advice here. That file contains the heuristics based on which udisks determines which devices to ignore and it might be worth it to use ‘udisksctl info’ to find out what about OP’s device triggers it to be set to ignored and then fixing that or deleting only that part in the config file instead of removing the entire section, no?

janr · October 9, 2024, 2:33pm

This is the output from udiskctl:

$ sudo udisksctl info -b /dev/disk/by-partlabel/neon-test
/org/freedesktop/UDisks2/block_devices/sda3:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/sda3
    DeviceNumber:               2051
    Drive:                      '/org/freedesktop/UDisks2/drives/CT1000BX500SSD1_2050E4DBD355'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 true
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-ata-CT1000BX500SSD1_2050E4DBD355-part3
    IdLabel:                    neon-test
    IdType:                     btrfs
    IdUUID:                     3cb37636-c4d2-4835-a1d0-e21b1ee1ce64
    IdUsage:                    filesystem
    IdVersion:                  
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/sda3
    ReadOnly:                   false
    Size:                       21474836480
    Symlinks:                   /dev/disk/by-diskseq/9-part3
                                /dev/disk/by-id/ata-CT1000BX500SSD1_2050E4DBD355-part3
                                /dev/disk/by-id/wwn-0x500a0751e4dbd355-part3
                                /dev/disk/by-label/neon-test
                                /dev/disk/by-partlabel/neon-test
                                /dev/disk/by-partuuid/331cae58-9a25-42a9-aa39-862f9a1a1433
                                /dev/disk/by-path/pci-0000:01:00.1-ata-1-part3
                                /dev/disk/by-path/pci-0000:01:00.1-ata-1.0-part/by-label/neon-test
                                /dev/disk/by-path/pci-0000:01:00.1-ata-1.0-part/by-partlabel/neon-test
                                /dev/disk/by-path/pci-0000:01:00.1-ata-1.0-part/by-partnum/3
                                /dev/disk/by-path/pci-0000:01:00.1-ata-1.0-part/by-partuuid/331cae58-9a25-42a9-aa39-862f9a1a1433
                                /dev/disk/by-path/pci-0000:01:00.1-ata-1.0-part/by-uuid/3cb37636-c4d2-4835-a1d0-e21b1ee1ce64
                                /dev/disk/by-path/pci-0000:01:00.1-ata-1.0-part3
                                /dev/disk/by-uuid/3cb37636-c4d2-4835-a1d0-e21b1ee1ce64
    UserspaceMountOptions:      
  org.freedesktop.UDisks2.Filesystem:
    MountPoints:        
    Size:               21474836480
  org.freedesktop.UDisks2.Partition:
    Flags:              0
    IsContained:        false
    IsContainer:        false
    Name:               neon-test
    Number:             3
    Offset:             910007730176
    Size:               21474836480
    Table:              '/org/freedesktop/UDisks2/block_devices/sda'
    Type:               c12a7328-f81f-11d2-ba4b-00a0c93ec93b
    UUID:               331cae58-9a25-42a9-aa39-862f9a1a1433

eeeeeeeeee · October 9, 2024, 2:45pm

There’s your problem

From udisks/data/80-udisks2.rules at adc3d3f1c32f200eae71dd0b7532c83f5acc1a70 · storaged-project/udisks · GitHub

# special GUID-identified partition types (EFI System Partition, BIOS Boot partition, RAID/LVM)
# see http://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs
ENV{ID_PART_ENTRY_SCHEME}=="gpt", \
  ENV{ID_PART_ENTRY_TYPE}=="c12a7328-f81f-11d2-ba4b-00a0c93ec93b|21686148-6449-6e6f-744e-656564454649|a19d880f-05fc-4d3b-a006-743f0f84911e|e6d6d379-f507-44c2-a23c-238f2a3df928|e3c9e316-0b5c-4db8-817d-f92df00215ae|de94bba4-06d1-4d40-a16a-bfd50179d6ac", \
  ENV{UDISKS_IGNORE}="1"

janr · October 9, 2024, 8:48pm

Uh, that’s quite interesting. If I understand this correctly, the partition type of that partition is set to a value indicating this is an EFI System Partition, while of course it actually isn’t - I’m not sure why/ how this happened. But now I know how I can fix it.

Anyway, thanks alot for the help!

meven · October 10, 2024, 7:27am

I would recommend you to report the bug to udisk.
This shouldn’t happen in the first place and others are probably affected.

skyfishgoo · March 31, 2025, 1:49pm

having the same issue i think.

solution is unclear to me.

the main partitions of my linux disk are not showing up in dolphin because they are of a org.freedesktop.UDisks2.Partition: Type: that is listed in

/usr/lib/udev/rules.d/80-udisks2.rules as

# ------------------------------------------------------------------------
# ------------------------------------------------------------------------
# ------------------------------------------------------------------------
# Devices which should not be display in the user interface

in the section

# special GUID-identified partition types (EFI System Partition, BIOS Boot partition, RAID/LVM)
# see http://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs

these are the offending references in that file

so what is the best path forward to clear them from this list?

skyfishgoo · March 31, 2025, 1:51pm

would filing a bug report with bugs.kde.org accomplish that?

eeeeeeeeee · March 31, 2025, 3:14pm

I think you can just change the partition type to an appropriate type like this:

No, here’s how/where to report a udisks issue

skyfishgoo · March 31, 2025, 4:37pm

noted, thanks.

will back up every thing and give this a try if another solution doesn’t present itself.

and if i were to do this, any advice on what type to change it to? The example given seems very specific to the one who posted the question.

so are you against the idea of brute force deleting the two problematic types highlighted above from this file?

/usr/lib/udev/rules.d/80-udisks2.rules

skyfishgoo · March 31, 2025, 5:17pm

fresh bit of info…

all 3 linux partitions are coded as

DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

which according to fdisk, is a Windows recovery environment

for some reason.

so i would likely need to change each one to something else

/ (root file system)

/home

/games

there are lots of linux choices in fdisk and i’m unclear on which ones would be the best choice for each of these

the EFI partition is also listed as one to hide but i think that’s probably appropriate as i don’t have any need to access that from dolphin.

skyfishgoo · April 1, 2025, 1:08am

thanks again,

here is how it ended up Dolphin can't find nvme device after moving to a new m/b - #18 by skyfishgoo