I have an issue where `gparted` seems to display incorrect information on my system drive (and `parted` seems to report correct information.) I filed a bug on Launchpad (since this manifests on Ubuntu 18.10) https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1808421 and was directed to https://gitlab.gnome.org/GNOME/gparted/issues/14 which does appear to be the same issue. Near the end of the first link is information I collected when running Ubuntu 18.04 (from `blkid` and `wipefs`) I have found that when this system is running Debian Stretch from USB that `gparted` appears to produce the correct output. Below is the same information collected when running Debian Stretch. root@debian:/home/user# apt policy util-linux util-linux: Installed: 2.29.2-1+deb9u1 Candidate: 2.29.2-1+deb9u1 Version table: *** 2.29.2-1+deb9u1 500 500 http://deb.debian.org/debian stretch/main amd64 Packages 100 /var/lib/dpkg/status root@debian:/home/user# blkid /dev/sda /dev/sda: LABEL="rpool" UUID="4510611204828545482" UUID_SUB="9816084798696086204" TYPE="zfs_member" PTUUID="eba09d2e-0f70-4d11-8e37-c1c170cfd9dd" PTTYPE="gpt" root@debian:/home/user# wipefs --no-act /dev/sda offset type ---------------------------------------------------------------- 0x200 gpt [partition table] 0xe8e0d3f000 zfs_member [filesystem] LABEL: rpool UUID: 4510611204828545482 root@debian:/home/user# I would like to know if this identifies a problem in the partition table or an issue with `blkid`. (Or something else?) I don't think I installed a ZFS pool on the entire disk but I could be wrong about that. It is also possible that one of my operations did cause a problem with the partition table. This is a test system and relatively new install so it would not be a huge problem to 'nuke and repave' if that is necessary to fix this or to try anything that can further identify the problem. Suggestions on what I should do next are most welcome! Thanks! -- Beautiful Sunny Winfield, Illinois
