GUIDs for ALL partitions?

[Qqmike]

Curious as to why you need GUIDs vs. UUIDs - for what purpose?

It is only incidental. In messing with UEFI booting, you find yourself having to identify where things are coming from, like where GRUB files are pointing at, where they are stored. For example,GRUB configuration files show UUIDs, but efibootmgr shows GUIDs. Tracking this stuff doing complex boot experiments can get confusing.That's why I would find it convenient to simply have a table of GUIDs to compare to UUIDs in the output of, for example, efibootmgr.

[mr_raider]

I seem to get both with blkid

mr_raider@lxde:~$ sudo blkid
/dev/sda2: UUID="5deab206-9f00-484e-841f-85916c69a1f4" TYPE="swap" PARTUUID="e5ac1315-0ee6-4750-a062-77a744cfd82d"
/dev/sda3: LABEL="boot" UUID="dc35491a-059b-4096-a01d-c977de615078" TYPE="ext2" PARTUUID="3134bfde-fbac-44bf-b706-dc591a3c06fc"
/dev/sda4: LABEL="system" UUID="1c236f0f-9c67-4629-a083-d4f80be41bd7" UUID_SUB="7d6c8658-6ab0-4e87-b0f2-d1ec4dad0be6" TYPE="btrfs" PARTUUID="7e1103d7-a83c-42da-a54b-c0521d47f881"
/dev/sda1: PARTUUID="3bb46f23-cd7f-496c-a3aa-3a29ddb2ce22"

[oshunluvr]

Ah. I didn't think about efi. Still using legacy BIOS here...

[oshunluvr]

I seem to get both with blkid

mr_raider@lxde:~$ sudo blkid
/dev/sda2: UUID="5deab206-9f00-484e-841f-85916c69a1f4" TYPE="swap" PARTUUID="e5ac1315-0ee6-4750-a062-77a744cfd82d"
/dev/sda3: LABEL="boot" UUID="dc35491a-059b-4096-a01d-c977de615078" TYPE="ext2" PARTUUID="3134bfde-fbac-44bf-b706-dc591a3c06fc"
/dev/sda4: LABEL="system" UUID="1c236f0f-9c67-4629-a083-d4f80be41bd7" UUID_SUB="7d6c8658-6ab0-4e87-b0f2-d1ec4dad0be6" TYPE="btrfs" PARTUUID="7e1103d7-a83c-42da-a54b-c0521d47f881"
/dev/sda1: PARTUUID="3bb46f23-cd7f-496c-a3aa-3a29ddb2ce22"

My results from blkid are different depending on partition type. For example, I get only GUID (aka PARTUUID) from blkid on a BIOS boot partition (type EF02). To see the UUID I have to use gdisk. Just to make things more obfuscated, I also get UUID_SUB for btrfs partitions

[mr_raider]

My results from blkid are different depending on partition type. For example, I get only GUID (aka PARTUUID) from blkid on a BIOS boot partition (type EF02). To see the UUID I have to use gdisk. Just to make things more obfuscated, I also get UUID_SUB for btrfs partitions

Seems to be a distro issue. 14.04 and 3.13 kernel gives me UUID only. 15.04 and 3.19 kernel gives me both. Looks they changed the blkid command somewhat in the interim.

[Qqmike]

Seems to be a distro issue. 14.04 and 3.13 kernel gives me UUID only. 15.04 and 3.19 kernel gives me both. Looks they changed the blkid command somewhat in the interim.

Seems to be right. I'm using 14.04.

[Qqmike]

mr_raider

Seems to be a distro issue. 14.04 and 3.13 kernel gives me UUID only. 15.04 and 3.19 kernel gives me both. Looks they changed the blkid command somewhat in the interim.

Yep, I just booted into 15.04 and I get the same output you are getting.

[SteveRiley]

For all practical purposes, the terms UUID and GUID are synonyms and interchangeable.

http://en.wikipedia.org/wiki/Univers...que_identifier
http://en.wikipedia.org/wiki/Globally_unique_identifier

/dev/disk/by-partuuid shows the UUID assigned to the partition when it was created by a partitioning tool.
/dev/disk/by-uuid shows the UUID assigned to the file system when it was formatted.

GPT uses UUIDs to indicate the type of partition; there is a one-to-one mapping between GPT UUIDs and type codes. See http://en.wikipedia.org/wiki/GUID_Pa...ion_type_GUIDs for the list. (See, here I'm intentionally interchanging UUID for GUID just, well, because. Hah.)