In the blkid output, some lines contain UUID and PARTUUID pairs and others only PTUUID. What do they mean?
In particular, why are two IDs required for a partition and why are some partitions identified by UUID/PARTUUID and some by PTUUID?
In the blkid output, some lines contain UUID and PARTUUID pairs and others only PTUUID. What do they mean?
In particular, why are two IDs required for a partition and why are some partitions identified by UUID/PARTUUID and some by PTUUID?
UUID is a filesystem-level UUID, which is retrieved from the filesystem metadata inside the partition. It can only be read if the filesystem type is known and readable.
PARTUUID is a partition-table-level UUID for the partition, a standard feature for all partitions on GPT-partitioned disks. Since it is retrieved from the partition table, it is accessible without making any assumptions at all about the actual contents of the partition. If the partition is encrypted using some unknown encryption method, this might be the only accessible unique identifier for that particular partition.
PTUUID is the UUID of the partition table itself, a unique identifier for the entire disk assigned at the time the disk was partitioned. It is the equivalent of the disk signature on MBR-partitioned disks but with more bits and a standardized procedure for its generation.
On MBR-partitioned disks, there are no UUIDs in the partition table. The 32-bit disk signature is used in place of a PTUUID, and PARTUUIDs are created by adding a dash and a two-digit partition number to the end of the disk signature.
man fstab on my Debian 10 system, yes. If you use a different distribution, check the man page on your system to verify.
– telcoM
May 23 '20 at 10:41
dd?
– Yousha Aleayoub
Oct 08 '20 at 06:11
fdisk that is of a recent enough version to support GPT partitioning: x then i to change PTUUID, or x then u to change PARTUUID of a specific partition.
– telcoM
Oct 08 '20 at 06:24
PTUUIDandPART_ENTRY_UUID(akaPARTUUID) ? – don_crissti Jul 05 '17 at 18:45