Hi Karel, Thanks for the suggestion. I tried that fix and it didn't seem to help. I went ahead and wiped the disk partitioning information (using `wipefs`) and conforming that it was wiped. I reinstalled Windows and followed with Debian Linux and find the same situation. I'm not sure where this went wrong. On Mon, Dec 17, 2018 at 3:14 AM Karel Zak <kzak@xxxxxxxxxx> wrote: > > On Fri, Dec 14, 2018 at 11:53:52AM -0600, Hank Barta wrote: > > 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. > > It seems like disk originally formatted as ZFS has been later > partitioned by GPT. > > In this case it does not seem like false positive ZFS detection. You > need ZFS magic string and guid= (aka UUID_SUB), pool_guid= (aka UUID) > and name= (aka LABEL) variable names and data on the right offsets. > > > 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! > > The ideal is to use partitioning tools that wipe the disk before it > writes partition table. Or use "wipefs -a" to cleanup all from the > disk before you use it (this is recommended step during system > installation). > > For now you can use "wipefs -o 0xe8e0d3f000" to remove only the > unwanted ZFS stuff. > > Karel > > -- > Karel Zak <kzak@xxxxxxxxxx> > http://karelzak.blogspot.com -- '03 BMW F650CS - hers '98 Dakar K12RS - "BABY K" grew up. '93 R100R w/ Velorex 700 (MBD starts...) '95 Miata - "OUR LC" polish visor: apply squashed bugs, rinse, repeat Beautiful Sunny Winfield, Illinois
