Partition msftres not detected (Microsoft reserved partition). lsblk does not detect anything either. -------------------------------------------------------------------------- root@kubuntu:~# fdisk -l /dev/nvme0 nvme0 nvme0n1 nvme0n1p1 nvme0n1p2 nvme0n1p3 nvme0n1p4 root@kubuntu:~# fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: Device Start End Sectors Size Type /dev/nvme0n1p1 2048 616447 614400 300M EFI System /dev/nvme0n1p2 616448 878591 262144 128M Microsoft reserved /dev/nvme0n1p3 878592 496540241 495661650 236.4G Microsoft basic data /dev/nvme0n1p4 496541696 500117503 3575808 1.7G Windows recovery environment --------------------------------------------------------------------------
root@kubuntu:~# lsblk -fm NAME FSTYPE LABEL UUID MOUNTPOINT SIZE OWNER GROUP MODE loop0 iso9660 Kubuntu 18.04 LTS amd64 2018-04-04-05-21-38-00 /cdrom 1.8G root disk brw-rw---- loop1 squashfs /rofs 1.7G root disk brw-rw---- nvme0n1 238.5G root disk brw-rw---- ├─nvme0n1p1 vfat SYSTEM xxxx-xxxx 300M root disk brw-rw---- ├─nvme0n1p2 128M root disk brw-rw---- ├─nvme0n1p3 236.4G root disk brw-rw---- └─nvme0n1p4 ntfs xxxxxxxxxxxxxxxx 1.7G root disk brw-rw----
Created attachment 112198 [details] nvme-gparted
Created attachment 112199 [details] nvme-kde-partition-manager
root@kubuntu:~# parted /dev/nvme0n1 GNU Parted 3.2 Using /dev/nvme0n1 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: NVMe Device (nvme) Disk /dev/nvme0n1: 256GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 316MB 315MB fat32 EFI system partition boot, esp 2 316MB 450MB 134MB Microsoft reserved partition msftres 3 450MB 254GB 254GB Basic data partition msftdata 4 254GB 256GB 1831MB ntfs hidden, diag
Isnt' mstfres just unused space, so basically like unformatted file system?
(In reply to Andrius Štikonas from comment #5) > Isnt' mstfres just unused space, so basically like unformatted file system? No idea, but should be displayed I think...
Reported to util-linux https://bugzilla.redhat.com/show_bug.cgi?id=1570876
(In reply to Teddy from comment #7) > Reported to util-linux > > https://bugzilla.redhat.com/show_bug.cgi?id=1570876 util-linux issue tracker is here https://github.com/karelzak/util-linux/issues But I guess it will reach util-linux maintainer anyway. KPM does all fs detection via udevadm which eventually gets info from util-linux. Let's see what they say, but from what I see online it's just fancily named unformatted partition.
(In reply to Andrius Štikonas from comment #8) > (In reply to Teddy from comment #7) > > Reported to util-linux > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1570876 > > util-linux issue tracker is here > https://github.com/karelzak/util-linux/issues > But I guess it will reach util-linux maintainer anyway. > > KPM does all fs detection via udevadm which eventually gets info from > util-linux. > > Let's see what they say, but from what I see online it's just fancily named > unformatted partition. From now on it's better that you report the bugs, because you depend on so many command line tools that I get lost.
blkid does detect PARTLABEL for nvme0n1p2 and nvme0n1p3, why don't you use it? You use so many utilities, that you need to get it sorted. -------------------------------------------------- root@kubuntu:~# blkid /dev/nvme0n1p1: LABEL="SYSTEM" UUID="xxxxxxx" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="xxxxxxxx" /dev/nvme0n1p4: UUID="xxxx" TYPE="ntfs" PARTUUID="xxxxxxxx" /dev/loop0: UUID="2018-04-04-05-21-38-00" LABEL="Kubuntu 18.04 LTS amd64" TYPE="iso9660" PTUUID="xxxxx" PTTYPE="dos" /dev/loop1: TYPE="squashfs" /dev/nvme0n1: PTUUID="xxxxxxx" PTTYPE="gpt" /dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="xxxxxx" /dev/nvme0n1p3: PARTLABEL="Basic data partition" PARTUUID="xxxxx"
(In reply to Teddy from comment #10) > blkid does detect PARTLABEL for nvme0n1p2 and nvme0n1p3, why don't you use > it? > > You use so many utilities, that you need to get it sorted. > > -------------------------------------------------- > root@kubuntu:~# blkid > /dev/nvme0n1p1: LABEL="SYSTEM" UUID="xxxxxxx" TYPE="vfat" PARTLABEL="EFI > system partition" PARTUUID="xxxxxxxx" > > /dev/nvme0n1p4: UUID="xxxx" TYPE="ntfs" PARTUUID="xxxxxxxx" > > /dev/loop0: UUID="2018-04-04-05-21-38-00" LABEL="Kubuntu 18.04 LTS amd64" > TYPE="iso9660" PTUUID="xxxxx" PTTYPE="dos" > > /dev/loop1: TYPE="squashfs" > > /dev/nvme0n1: PTUUID="xxxxxxx" PTTYPE="gpt" > > /dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="xxxxxx" > > /dev/nvme0n1p3: PARTLABEL="Basic data partition" PARTUUID="xxxxx" KPM also detects it. Older versions do not display it (it reads but there is no GUI). In git it also shows PARTLABEL and PARTUUID (but can't change them yet)
How can I test git?
Reported: https://github.com/karelzak/util-linux/issues/623
(In reply to Teddy from comment #12) > How can I test git? For latest code you need to compile it yourself (both kpmcore and partitionmanager). Latest code is in kauth branch. You can also try KDE Neon Developer Edition, that probably already has Partition LABEL and UUID. A bit later I'll merge kauth branch into master branch, then Neon will have it too. But that will happen at some point after Ubuntu 18.04 LTS is released and Neon is rebased on top of that (now it follows 16.04 LTS).