https://bugs.kde.org/show_bug.cgi?id=519793
Luis Alvarado <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |FIXED --- Comment #15 from Luis Alvarado <[email protected]> --- Thank you. Well they all had partitions. At 0:18 that is me clicking on the wrong panel. I clicked on the Device on the left, instead on the partition on the right, but on 0:23 you can see the partition issue. But here is the thing. Ever since you said this: In your video /dev/nvme3n1 has no partitions, it's just pure file system on the whole disk. Flags are metadata inside the partition table. That just rubbed me the wrong way because it made me investigate why the partition manager was not seeing those 2. And because of the metadata you mentioned, which makes it context aware (depends on the device being mounted / unmounted and filesystem type. Or even size in old filesystems). Then I ran the lsblk again: nvme1n1 259:0 0 1,8T 0 disk ├─nvme1n1p1 259:1 0 497,9G 0 part / ├─nvme1n1p2 259:2 0 1G 0 part /boot/efi └─nvme1n1p3 259:3 0 1,3T 0 part /home nvme3n1 259:4 0 3,6T 0 disk └─nvme3n1p1 259:6 0 3,6T 0 part /run/media/luis/ironman nvme2n1 259:5 0 7,3T 0 disk /run/media/luis/steam nvme0n1 259:7 0 7,3T 0 disk /run/media/luis/hulk Look at the TYPE column, it says DISK. So it is a raw disk partition. How that happened I think it was the DISK utility in Ubuntu 25.10 months ago. So the fix is me moving stuff around, properly partitioning them and then restoring it again. Apologies for the wasted time and the mystery here. You guys could have pretty much fixed like 10 other issues already. Consider this a "FIXED" report Andrius & Argonel. Thank you so much for the support (high quality btw) and helping debug what in the world is going on. -- You are receiving this mail because: You are watching all bug changes.
