Announcement

**jlittle** · Jun 08, 2024, 04:14 PM

If you edit the page, click on the disk chart, click in sensors box, click Disks, do your mounted drives show up?

**rhnpl** · Jun 08, 2024, 05:25 PM

No, there is only option "All Disks" as shown on the first screenshot, if I click that it goes straight to "Free Space", "Percentage Free" options, etc..

**oshunluvr** · Jun 09, 2024, 03:00 PM

OK, this seems really unlikely as a cause, but your partitions are out of order. If it's an actual bug in the system monitor, it's worth trying.

sudo gdisk /dev/nvme0n1

Then enter "s" to sort them correctly and then "w" to save the changes.

Note this may cause issues if you're mounting in fstab with device names instead of UUIDs or labels. If you are using device names, edit fstab before rebooting.

**rhnpl** · Jun 09, 2024, 04:48 PM

Everytime I tried to run sudo gdisk /dev/nvme0n1 and use s command, it only outputs the following warning

Code:

Command (? for help): s
You may need to edit /etc/fstab and/or your boot loader configuration!

It seems all of the listed partitions in the /etc/fstab are labelled with their UUID based on the following fstab info, except for the /swapfile and tmpfs, which might be the case?

Code:

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=4877-4FE2                            /boot/efi      vfat    defaults   0 2
UUID=a6465370-f413-4e87-bea3-a1ef7614b6e5 /              ext4    defaults   0 1
/swapfile                                 swap           swap    defaults   0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

Though if I run p on the gdisk, I get the following information

Code:

Command (? for help): p
Disk /dev/nvme0n1: 1000215216 sectors, 476.9 GiB
Model: KINGSTON OM8PCP3512F-AI1
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 7FF9BD8D-1C97-4C05-B4D8-314A0D0DB850
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1000215182
Partitions will be aligned on 2048-sector boundaries
Total free space is 4717 sectors (2.3 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 616447 300.0 MiB EF00 EFI system partition
2 616448 878591 128.0 MiB 0C01 Microsoft reserved ...
3 878592 205678591 97.7 GiB 0700 Basic data partition
4 968062976 970532863 1.2 GiB 2700
5 970534912 1000214527 14.2 GiB 2700 Basic data partition
6 205678592 968062975 363.5 GiB EF00 kubuntu_2404

The kubuntu partition is on the 6th number, but the start sector is right after the 3rd, is this an indication that the disk order isn't correct?

Edit: my Linux partition was created by partitioning the Windows partition which is the nvme0n1p3, which perhaps why the sector starts from its end. I'll tinker more in my free time

**oshunluvr** · Jun 10, 2024, 07:59 AM

That gdisk printout shows what I am talking about. Partition "6" is actually between 3 and 4, which means it actually should be "4". If you ran gdisk and entered "s" but didn't enter "w" to write the changes to disk, you didn't do anything to fix it.

Again, still not likely this causes any problems but trying to identify a possible bug requires eliminating as many factors as possible to drill down to the actual cause.

Your fstab shows making the above change will not harm your boot up.

**rhnpl** · Jun 11, 2024, 04:53 PM

I have sorted the partition using gdisk method succesfully by looking at the following lsblk -f output

Code:

...
nvme0n1
├─nvme0n1p1 vfat FAT32 SYSTEM 4877-4FE2 252M 15% /boot/efi
├─nvme0n1p2
├─nvme0n1p3 ntfs Windows 4A2A77D52A77BC8F
├─nvme0n1p4 ext4 1.0 kubuntu_2404 a6465370-f413-4e87-bea3-a1ef7614b6e5 241.1G 27% /var/snap/firefox/common/host-hunspell
│ /
├─nvme0n1p5 ntfs E058123F581214BE
└─nvme0n1p6 ntfs BIOS_RVY BA9C7A929C7A4941

Yet the sensor of my system monitor still couldn't detect the rearranged disk partitions and still only shows 'All Disks' option upon clicking disk option on the edit menu.

Announcement

System Monitor Overview Dosen't Detect the Disk

System Monitor Overview Dosen't Detect the Disk

Comment

Comment

Comment

Comment

Comment

Comment

Users Viewing This Topic