KDE Partition Manager scan takes forever to finish

Hi, hope everyone is well.

I’m having this problem with KDE Partition Manager taking forever to complete its scan.

A few months back, I moved to btrfs and I’d say that’s when I started having issues, although I can’t say for sure. Things seem to be working fine otherwise. I have a Win10 dual boot setup with windows on its own drive (/dev/sdb) and Manjaro on the Samsung nvme. The rest are spare storage drives.

Any thoughts on why the scan would take so long? Are the two not properly aligned partitions causing this issue? If yes, can I realign them without starting over fresh?

❯ partitionmanager 
Loaded backend plugin:  "pmsfdiskbackendplugin"
"Using backend plugin: pmsfdiskbackendplugin (1)"
"Scanning devices..."
"Device found: Samsung SSD 970 EVO Plus 1TB"
getting temp failed for  "/dev/nvme0n1" :  Success
getting powered on time failed for  "/dev/nvme0n1" :  Success
getting power cycles failed for  "/dev/nvme0n1" :  Success
"Partition ‘/dev/nvme0n1p2’ is not properly aligned (last sector: 1,917,577,739, modulo: 524)."
"Device found: WDC WD5000BEKT-00KA9T0"
"Device found: KINGSTON SA400S37240G"
unknown file system type  ""  on  "/dev/sdb2"
"Partition ‘/dev/sdb3’ is not properly aligned (last sector: 467,835,607, modulo: 728)."
"Device found: My Passport 0820"
"Scan finished."
❯ lsblk
sda           8:0    0 465.8G  0 disk 
└─sda1        8:1    0 465.8G  0 part /wd
sdb           8:16   0 223.6G  0 disk 
├─sdb1        8:17   0   100M  0 part 
├─sdb2        8:18   0    16M  0 part 
├─sdb3        8:19   0   223G  0 part /win10
└─sdb4        8:20   0   500M  0 part 
sdc           8:32   0 931.5G  0 disk 
└─sdc1        8:33   0 931.5G  0 part 
sdd           8:48   1     0B  0 disk 
sde           8:64   1     0B  0 disk 
sr0          11:0    1  1024M  0 rom  
sr1          11:1    1  1024M  0 rom  
nvme0n1     259:0    0 931.5G  0 disk 
├─nvme0n1p1 259:1    0   301M  0 part /boot/efi
├─nvme0n1p2 259:2    0 914.1G  0 part /run/timeshift/backup
│                                     /var/lib/docker/btrfs
│                                     /var/cache
│                                     /var/log
│                                     /home
│                                     /
└─nvme0n1p3 259:3    0  17.1G  0 part [SWAP]

UUID=XXXX-XXXX                              /boot/efi      vfat    umask=0077 0 2
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   /              btrfs   subvol=/@,defaults,noatime,autodefrag,compress=zstd 0 0
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   /home          btrfs   subvol=/@home,defaults,noatime,autodefrag,compress=zstd 0 0
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   /var/cache     btrfs   subvol=/@cache,defaults,noatime,autodefrag,compress=zstd 0 0
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   /var/log       btrfs   subvol=/@log,defaults,noatime,autodefrag,compress=zstd 0 0
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   swap           swap    defaults,noatime 0 0
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   /wd            ext4    noatime,discard 0 0
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   /wdusb         ext4    noauto,x-systemd.automount,x-systemd.idle-timeout=10min,nofail,>
UUID=xxxxxxxxxxxxxxxxxxxxxxxx   /toshiba       ext4    noauto,x-systemd.automount,x-systemd.idle-timeout=10min,nofail,>
#UUID=XXXXXXXXXXXXXXXXXXXX                  /win10         ntfs    uid=1000,gid=1000,rw,user,exec,umask=000 0 0
UUID=XXXXXXXXXXXXXXXXXXXX                   /win10         ntfs-3g uid=1000,gid=1000,dmask=022,fmask=133,windows_names 0 0

Did the Partition manager prompt you to grand system management rights?
If not please check if the PolicyKit Authentication window is hidden behind the KDE Partition management window(it should also appear in your taskbar).
At least that was the issue I had, needed some time to notice it.

Yes. It prompts me.

Aside: I wish the scan window didn’t get in the way of the auth window every time lol. (so yes, I’m annoyed by that window and very familiar with it.)

This seem to have fixed itself in one of the updates (or something) but, I honestly can’t say when or how.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.