~/.config/dolphinrc doesn’t seem to show anything related to where it finds devices.
/etc/fstab shows everything by UUID so the file structure is still accessible in dolphin, but the device section does not show my linux partitions nor does disks & devices in the system tray.
any way to resolve this?
nvme was installed to slot M.2_2 and now installed in M.2_1 on a different m/b
tempted to move it to the M.2_2 position just to see everything comes back
Hi - what’s shown for that device in KDE Partition Manager?
pretty much how you would expect, including the labels… only it this nvme used to be nvme0n2, on the previous m/b slot.
this is what the disks & devices shows, in spite of me checking them here they show up as disconnected
and do not show up in dolphin under “devices” panel.
any more thoughts on this?
should i move the nvme to my 2nd slot on this motherboard to see if this starts working normally or is there some other way to reset dolphin’s ability find devices on the system?
also of note is looking into sensors in the system monitor, under the disks category
it only shows the same list of devices as shown in dolphin, so maybe its a more kde wide issue than just an application issue.
the underlying OS itself seems fine tho
how do i resolve?
This is a weird one
Have you tried it with a new user account? (ie, fresh out-of-the-box default KDE config) (I mean, for testing - I am not suggesting solutions yet)
with my current user setting Disk&Devices in the system tray to automount ALL:ALL
i get this result in dolphin
and this result from
udevadm settle && lsblk -e7 -o NAME,MAJ:MIN,LABEL,MOUNTPOINTS
sda 8:0
├─sda1 8:1 GatewayBare /media/goo/GatewayBare
├─sda2 8:2 timeshift /media/goo/timeshift
├─sda3 8:3
├─sda4 8:4 linuxbackup /media/goo/linuxbackup
├─sda5 8:5 System Backup /media/goo/System Backup
└─sda6 8:6 sysrestore
nvme0n1 259:0
├─nvme0n1p1 259:1
├─nvme0n1p2 259:2
├─nvme0n1p3 259:3 WinSys /media/goo/WinSys
├─nvme0n1p4 259:4
├─nvme0n1p5 259:5 WinData /media/goo/WinData
├─nvme0n1p6 259:6 WinGames /media/goo/WinGames
└─nvme0n1p7 259:7 Win Setup Files /media/goo/Win Setup Files
nvme1n1 259:8
├─nvme1n1p1 259:9 EFI /boot/efi
├─nvme1n1p2 259:10 LinSys /
├─nvme1n1p3 259:11 LinData /home
├─nvme1n1p4 259:12 LinGames /media
└─nvme1n1p6 259:13 swap [SWAP]
as you can see all the sda and nvme0n1 devices show up but none of the nvme1n1 devices do.
irrc, on the previous m/b my nvme devices were:
nvme0n1 (windows)
nvme0n2 (linux)
rather than:
nvme0n1 (linux)
nvme1n1 (windows)
not only have i reversed the order by moving the linux disk to the first slot, but the m/b has chosen to name them differently for some reason.
one (or both) of these changes has something to do with it, but i have no idea how to resolve it.
i will try a new user and report back.
My guess would be, according to this simplified explanation of namespaces from the NVME specifications, your old m/b used one NVME controller for both drives and your new one uses separate controllers (probably for better transfer speeds).
But I’m not sure why it is not visible either, on my setup with two NVME drives I have /home at nvme1n1p1 and all the rest at nvme0n1p… so just having nvme0n1… and nvme1n1… should not be a problem by itself.
Just to be sure, have you right-clicked and selected “show all entries” at the Dolphins Devices panel, maybe it is set to hidden for some reason?
yes, the screen shots are with show all entries checked.
and i’ve now tested a new user and the same issue persists in dolphin for the new user… it is not liking the nvme0n2 drive now being on the nvme01 slot.
windows has it worse being moved to different controller and everything but it still works as expected… perhaps because the drive number is the same where with the linux disk the drive number changed.
totally guessing at this point.
i’m going to try moving the linux disk to the 2nd slot next to the windows disk which cause it to be read as nvme1n2 so that the drive number will be the same as before and see what that does.
unless someone has a better idea.
well that didn’t work work either.
dolphin looks the same and still no linux disks in the performance monitor…
all moving the linux drive did was make it nvme0n1 instead.
and now the windows disk is nvme1n1
seems the m/b automagically moves any 2nd nvme to a different controller regardless its connection to the CPU being direct or via the Chipset.
perhaps i’ll RTFM for my BIOS and see if anything sticks out.
for ref.
udevadm settle && lsblk -e7 -o NAME,MAJ:MIN,LABEL,MOUNTPOINTS
NAME MAJ:MIN LABEL MOUNTPOINTS
sda 8:0
├─sda1 8:1 GatewayBare /media/goo/GatewayBare
├─sda2 8:2 timeshift /media/goo/timeshift
├─sda3 8:3
├─sda4 8:4 linuxbackup /media/goo/linuxbackup
├─sda5 8:5 System Backup /media/goo/System Backup
└─sda6 8:6 sysrestore
nvme1n1 259:0
├─nvme1n1p1 259:1
├─nvme1n1p2 259:2
├─nvme1n1p3 259:3 WinSys /media/goo/WinSys
├─nvme1n1p4 259:4
├─nvme1n1p5 259:5 WinData /media/goo/WinData
├─nvme1n1p6 259:6 WinGames /media/goo/WinGames
└─nvme1n1p7 259:7 Win Setup Files /media/goo/Win Setup Files
nvme0n1 259:8
├─nvme0n1p1 259:9 EFI /boot/efi
├─nvme0n1p2 259:10 LinSys /
├─nvme0n1p3 259:11 LinData /home
├─nvme0n1p4 259:12 LinGames /media
└─nvme0n1p6 259:13 swap [SWAP]
OK so new user didn’t help, now you know it isn’t the config. Maybe its the installation. Try a Live USB stick.
a live USB shows me the / directory along with the same list of other devices (unmounted of course) from the two disks that are working… the windows nvme disk and the HDD.
but nothing from the linux nvme disk
weird right?
Sorry I’m clueless here mate.
Does it fix itself after a reboot ?
Otherwise that’s an issue with Solid framework.
You can use solid-hardware6 list and solid-hardware6 details <UDI> to find out what kde-apps recognizes about your drive.
There is probably something not working properly, that might be a case that hasn’t been reported yet.
udisksctl dump would be interesting also.
thanks for the info, i found this other thread on what appears to be the same topic and posted there
and no, a reboot does not fix it.
where should this be reported?
and how best to correct it?
udisks
Don’t forget to include what is asked:
There is a workaround in udisks - ArchWiki
You didn’t share any data about your case, I can’t say more.
thanks, i saw the work around but its seems rather a blunt instrument and according to one poster on the other thread, not entirely necessary.
i would be more inclined to simply delete the two types that are causing the issue, rather than deleting the whole section.
the udisks bug filing requires a lot a lot of info (which i will happily do) but what info would you need to see from your perspective?
here’s what i’ve done so far:
used solid-hardware5 details to see that each of the 4 partitions are coded as StorageAccess.ignored = true (bool)
the running each one thru udisksctl info -p i can see from the output that the EFI partition and three linux partitions (/, /home/ and /games) are showing as one of these two types
org.freedesktop.UDisks2.Partition:
...
Type: de94bba4-06d1-4d40-a16a-bfd50179d6ac
and
Type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
both of these types are listed as specific types in the file
/usr/lib/udev/rules.d/80-udisks2.rules
indicating they should not be displayed in the user interface.
where to go from here:
a) delete the types from the .rules file (or a copy of it).
b) change the types using fdisk.
c) ???
any advice would be appreciated, and i can post outputs if you need them.
edit: looking at the fdisk option, the type shown for the linux partitions is Windows recovery environment for some reason… and the other one is for an EFI partition (which seems correct).
so i think it would best to use option b) and change the type using fdisk
but change it to which type? there are dozens of “linux” types
these are the three partitions
/ (root file system)
/home (where all my stuff is)
/games (where some linux steam games are installed)
any advice on which type to assign to each of these in fdisk would be appreciated.
The one Arch recommends as “should be fine for most use cases” Linux filesystem GUID 0FC63DAF-8483-4772-8E79-3D69D8477DE4 works for me here on arch with all my ext4 partitions including / (root) and /home
But if you want to follow the Discoverable Partitions Specification on a amd64/x86_64 System / (root) should probably be 4f68bce3-e8cd-4db1-96e7-fbcaf984b709 and /home 933ac7e1-2eb4-4f13-b844-0e14e2aef915
perfect, thank you
here is the final result of sudo fdisk /dev/nvme1n1
per Dolphin doesn't show one of my partitions under 'Devices' - #12 by eeeeeeeeee
thanks to @eeeeeeeeee
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 1026047 1024000 500M EFI System
/dev/nvme1n1p2 1026048 630169599 629143552 300G Linux root (x86-64)
/dev/nvme1n1p3 630169600 1469030399 838860800 400G Linux home
/dev/nvme1n1p4 1469030400 2098175999 629145600 300G Linux filesystem
/dev/nvme1n1p6 3756034048 3907028991 150994944 72G Linux swap
dolphin now shows the devices as it should
thank you everyone for all the help and pointers… learned a lot (more than i needed to 
