In This Article
What is GUID Partition Table (GPT)?
The Globally Unique Identifier Partition Table or GPT refers to the standard for the design of partition tables in the physical storage device in a computer such as the Hard Disk Drive and uses the UEFI startup firmware to define the partitions.
Also usable in the older BIOS systems, a GPT or GUID Partition Table is that which manages the startup process of the newer hard drives, operating systems, and motherboards.
- The GPT can support large partitions of about 18 Exabyte and comes with an extra Protective MBR and Legacy MBR to use third-party MBR utilities and the first partition to boot as an MBR drive respectively.
- The use of the Unified Extensible Firmware Interface initiative the GUID Partition Table offers more flexibility in partitioning the disks.
- A traditional GPT comes with three parts in it such as the primary partition table, the backup partition table, and the normal data partitions. It supports different operating systems differently.
- The features of this partition table include a unique number identification, UEFI combination, larger storage capacity, multiple copies of data stored in different locations of the disk, Cyclic Redundancy Check values, a dynamic or basic nature and NTFS and FAT file systems.
- The GPT header defines the location of the address on the disk, range of LBA used by the partition entries, GUID and the CRC 32 checksum.
Understanding GUID Partition Table (GPT)
GPT actually refers to the typical layout of the partition tables of a physical storage device of a computer such as a HDD or Hard Disk Drive or an SSD or Solid State Drive.
GPT usually forms a part of the UEFI or the Unified Extensible Firmware Interface standard.
However, you will also find it being used for some specific BIOS systems.
This is mainly due to the limitations present in the Master Boot Record or MBR partition tables.
The GPT plays a significant role in the proper functioning of the larger and newer hard drives in particular that typically comes with a storage space of more than 2 TB.
This partition scheme normally helps in recording the actual capacity of the hard drives properly that is necessary for the operating system to use for boot up.
The computing world today is moving forward to the GPT partitioning scheme so that it can sustain and survive the changes that are about to come in the future in this sector.
Typically, GPT has already started to show signs that it will become the standard in the future computers, though the change as of now is gradual.
Still, almost all operating systems of the modern personal computers support the GUID Partition Table standard, albeit with a little difference.
For example, the Microsoft Windows operating systems that are based on an x86 architecture and macOS support booting from the GPT partition scheme only on systems that come with an EFI or Extensible Firmware Interface.
On the other hand, most of the Linux distributions and FreeBSD can boot from the GPT partitions on systems that come with either an EFI or BIOS.
The GUID Partition Table can support partitions as large as 18 exabytes in comparison to the lowly support of the MBR method which is restricted to 2 TB or 2.2 TB to be precise.
The GPT standard comes with an additional Protective MBR which makes the best use of the third-party MBR utilities to identify the disk properly.
In addition to that, it also comes with a Legacy MBR which helps the first partition to boot as an MBR drive as and when required.
The GUID Partition Table offers a more flexible way to partition the disks compared to the MBR standard that was so common to personal computers due to the Unified Extensible Firmware Interface initiative.
The contiguous storage space created on a logical or a physical disk functions just like a separate physical disk.
These partitions are clearly visible to the operating system installed in the computer as well as its firmware.
The access to it is however controlled by the firmware of the system before it boots the operating system.
The control is then transferred to the operating system after it starts.
A conventional GUID Partition Table scheme will typically come in three parts in order as follows:
- A primary partition table
- The normal data partitions and
- A secondary or backup partition table.
If you look at the layout of a GUID Partition Table you will see that each of these portions consist of different components.
For example, the primary partition table contains:
- The protective MBR in the beginning of the GPT disk
- The GPT header or Logical Block Address in LBA 1 in the middle and
- The partition table in LBA 2 that loads information and access the partition data.
Normal data partitions, on the other hand, refer to the four physical locations at the middle section of the GPT disk where all data and personal files are stored.
And finally, the backup or secondary partition table refers to the end of the GPT disk where all the backup or duplicate information is stored. This consists of two specific parts namely:
- Backup GPT header or last LBA n and
- Backup Partition table following it or the last LBA n-32.
The GPT header and the partition tables can access the backup partition table to recover data in case of damage to or data loss from the primary partition table.
The GPT disks typically come with a few advanced features that make them stand apart and offer more flexibility and much better management. Here are some of these features:
- The GUID that gives every GPT partition its unique number for identification
- The UEFI combination that eliminates the old and cumbersome BIOS of the MBR partitioning system
- Its support to much larger storage capacity in comparison to the MBR partition system that offers the users a chance to create unlimited number of partitions
- Its ability to create and store multiple copies of data in different partitions of the disk instead of all in one place that helps in easier and data recovery in worst case scenarios when a partition is corrupted
- Its ability to store Cyclic Redundancy Check values to check whether or not the data stored in the partitions is intact and know the issues beforehand if there is any and try to recover the damaged data from another part on the disk for use and
- The GPT disk can be either dynamic or basic and the file system of the partition can be NTFS or New Technology File System and FAT or File Allocation Table file system.
The GPT partition is bootable not only as long as the primary partition table of it is intact but also when it is damaged because it can reload the necessary data and information from the secondary partition table.
The Protective MBR of the GPT partitioning scheme needs a specific mention here.
It is found in the beginning in sector 0 and comes at the start of the GPT on the disk. It typically contains one type 0xEE partition and spans across the disk.
The need of a Protective MBR by a GPT is to protect it from the particular MBR disk tools released previously such as:
- The Microsoft MS-DOS FDISK and
- The Microsoft Windows NT Disk Administrator.
These tools do not know about GPT and how to access a GPT disk properly.
Therefore, these tools need a Protective MBR that it will access first and which will allow them to see the GPT disk as a solitary partition encompassing and not consider it to be an unpartitioned disk erroneously.
With all these features of the GPT there is hardly any doubt that it is a much better disk partitioning system than the MBR partitioning scheme.
It allows much better disk partition management and higher data protection.
The format of the GPT partitioning system may be different for different types of disks.
For example, for the basic disks, which are the most widely used storage type with Windows and have primary partitions and logical drives, the formatting is usually done with a file system that happens to be the volume for storing the files.
Here, on the GUID Partition Table there is a Protective MBR area that ensures backward compatibility with all of the disk management utilities that typically operate on Master Boot Record.
There is also a GPT header that defines the range of LBA or Logical Block Address that is used by the partition entries. Apart from that, this also defines other useful things such as:
- The location of the address on the disk
- The GUID and
- The CRC 32 or the 32-bit Cyclic Redundancy Check checksum.
The entries made in the GUID partition table starts typically with the GUID of the partition type which is pretty much similar to the system ID of the MBR partition scheme.
This partition type GUID is of 16 bytes and identifies how exactly the particular partition is being used and what is the type of data that the partition holds.
On the other hand, the format for the dynamic disks with GPT partition style includes up to 128 primary partitions.
This means that in this format you will not need to create any logical drives or any extended partitions.
Here is the GPT header format with offset, length, and contents in order:
- 0 (0x00), 8 bytes – signature
- 8 (0x08), 4 bytes – revision 1.0 for UEFI 2.8
- 12 (0x0C), 4 bytes – header size
- 16 (0x10), 4 bytes – CRC 32 of header
- 20 (0x14), 4 bytes – reserved and must be zero
- 24 (0x18), 8 bytes – current LBA or location of current header copy
- 32 (0x20), 8 bytes – backup LBA or location of other header copy
- 40 (0x28), 8 bytes – first usable LBA
- 48 (0x30), 8 bytes – last usable LBA
- 56 (0x38), 16 bytes – disk GUID
- 72 (0x48), 8 bytes – starting LBA
- 80 (0x50), 4 bytes – number of entries of partition in an array and
- 84 (0x54), 4 bytes – size of one partition entry.
Now, take a look at the GUID partition entry format, which is in the same order of offset, length and contents and are as follows:
- 0 (0x00), 16 bytes – partition type GUID
- 16 (0x10), 16 bytes – unique partition GUID
- 32 (0x20), 8 bytes – first LBA
- 40 (0x28), 8 bytes –last LBA
- 48 (0x30), 8 bytes – attribute flags and
- 56 (0x38), 72 bytes – partition name.
Since the GPT standard is self-defining and self-identifying and it uses the UEFI, there are some specific requirements for it to function.
One of the most significant requirements is that all of the information is contained in particular structures.
These structures are stored in specific locations on the physical media so that it can be interpreted easily and quickly by the GPT partitioning mechanism.
Now, how do you know whether or not the hard drive of your system uses GPT? Well, for that you will need to use the diskpart command.
The steps to follow for this include:
- Typing diskpart in the windows command line
- Hitting Enter
- Clicking OK when the UAC or User Account Control prompt is displayed
- Typing list disk in the DISKPART> prompt and
- Hitting enter.
The listing of disk partitions will be displayed. If the disk is GPT enabled, there will be an indication under the GPT column as well as for every drive that is GPT enabled.
Now, take a look at the various technical aspects of GPT.
However, this section may seem to be a bit difficult to understand for any average user but for a tech-savvy person, this is very important.
Intel developed a new partition table format in the late 1990s which eventually became UEFI and called it GPT.
It uses 64 bits for LBA which allows a maximum disk size of up to 264 sectors.
This means that for any disk with 512 byte sectors, the maximum size will be 264 × 512 bytes = 8 ZB or 9.44 × 10²¹ bytes = 9.44 ZB.
And, for disks with 4,096 byte sectors, the maximum size will be 264 × 4,096 bytes = 64 ZB or 75.6 × 10²¹ bytes = 75.6 ZB.
Later on, with the development of technology, the manufacturers of hard disks created drives with 4,096 byte sectors with advanced format included in them such as a 512e emulation technology.
This allowed compatibility with legacy software and hardware.
And, this also allowed 512 byte sectors access to the hard drive in spite of the fact that they had 4,096 byte physical sectors underlying.
As said earlier, there is a GPT header in LBA 1 which has a pointer to the Partition Entry Array or partition table, which is usually at LBA 2.
Every entry that is made in the partition table is of 128 bytes size.
However, according to the UEFI specification it is stipulated that at least 16,384 bytes will be allocated for the Partition Entry Array, irrespective of the size of the sector.
Therefore, for a disk with 512 byte sectors there will be at least 32 sectors used for the Partition Entry Array out of which the first usable block will be at LBA 34 or higher.
On the other hand, for a disk with 4,096 byte sectors, there will be 4 sectors at the least that will be used for the partition tables out of which the LBA 6 or higher will be considered as the first usable block.
At this point, it is good to know a bit about the attributes regarding the partition tables.
Typically, the partition table attributes of 64-bit are usually shared between the 16 bit type-specific attributes and the 45 bit common attributes.
Here is the breakdown of the bits and contents of these following attributes:
- 0 bit – The platform required
- 1 bit – The EFI should ignore the partition content and not read it
- 2 bit – The Legacy BIOS is bootable
- 3 to 47 – Is reserved for use in the future and
- 48 to 63 – Is defined and utilized by each partition type.
There are a few type-specific attributes for basic data partition that are defined by Microsoft such as:
- 60 bit – Read-only
- 61 bit – Shadow copy of another partition
- 62 bit – Hidden and
- 63 bit – No drive letter which is not to be auto mounted.
On the other hand, there are a few other type-specific attributes that Google defines for its Chrome OS kernel such as:
- 56 bit – Successful boot flag
- 55 to 52 – The remaining tries and
- 51 to 48 – Priority, where 15 indicate the highest, 1 the lowest, and 0 as not bootable.
Partition Type Globally Unique Identifiers:
Finally, your knowledge about the technical aspects of GPT will not be complete if you do not know the different GUIDs for different partition types.
Typically, each partition will have its own GUID. Some of the standard GUIDs used are:
- For unused entry – 00000000-0000-0000-0000-000000000000
- For MBR partition scheme – 024DEE41-33E7-11D3-9D69-0008C781F39F
- For EFI system partition – C12A7328-F81F-11D2-BA4B-00A0C93EC93B
- For BIOS boot partition – 21686148-6449-6E6F-744E-656564454649
- For Intel Fast Flash or iFFS – D3BFE2DE-3DAF-11DF-BA40-E3A556D89593
- For Sony boot partition – F4019732-066E-4E12-8273-346C5641494F and
- For the Lenovo boot partition – BFBFAFE7-A34F-448A-9A5B-6213EB736C22.
As for the Windows operating systems, the GUIDs are as follows:
- For Microsoft Reserved Partition – E3C9E316-0B5C-4DB8-817D-F92DF00215AE
- For basic data partition – EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
- For Logical Disk Manager Metadata partition – 5808C8AA-7E8F-42E0-85D2-E1E90434CFB3
- For Logical Disk Manager data partition – AF9B60A0-1431-4F62-BC68-3311714A69AD
- For Windows Recovery Environment – DE94BBA4-06D1-4D40-A16A-BFD50179D6AC
- For IBM General Parallel File System partition – 37AFFC90-EF7D-4E96-91C3-2D7AE055B174
- For storage spaces partition – E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D and
- For storage replica partition – 558D43C5-A1AC-43C0-AAC8-D1472B2923D1.
As for HP-UX operating system, the GUIDs are as follows:
- For data partition – 75894C1E-3AEB-11D3-B7C1-7B03A0000000 and
- For device partition – E2A1E728-32E3-11D6-A682-7B03A0000000.
As for Linux operating system, the GUIDs are as follows:
- For Linux file system data – 0FC63DAF-8483-4772-8E79-3D69D8477DE4
- For RAID partition – A19D880F-05FC-4D3B-A006-743F0F84911E
- For root partition (x86) – 44479540-F297-41B2-9AF7-D131D5F0458A
- For root partition (x86-64) – 4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
- For root partition (32-bit ARM) – 69DAD710-2CE4-4E3C-B16C-21A1D49ABED3
- For root partition (64-bit ARM/AArch64) – B921B045-1DF0-41C3-AF44-4C6F280D3FAE
- For /boot partition – BC13C2FF-59E6-4262-A352-B275FD6F7172
- For swap partition – 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
- For Logical Volume Manager partition – E6D6D379-F507-44C2-A23C-238F2A3DF928
- For /home partition – 933AC7E1-2EB4-4F13-B844-0E14E2AEF915
- For /srv (server data) partition – 3B8F8425-20E0-4F3B-907F-1A25A76F98E8
- For plain dm-crypt partition – 7FFEC5C9-2D00-49B7-8941-3EA10A5586B7
- For LUKS partition – CA7D7CCB-63ED-4C53-861C-1742536059CC and
- For the reserved partition – 8DA63339-0007-60C0-C436-083AC8230908.
As for FreeBSD operating system, the GUIDs are as follows:
- For boot partition – 83BD6B9D-7F41-11DC-BE0B-001560B84F0F
- For BSD disk label partition – 516E7CB4-6ECF-11D6-8FF8-00022D09712B
- For swap partition – 516E7CB5-6ECF-11D6-8FF8-00022D09712B
- For Unix File System partition – 516E7CB6-6ECF-11D6-8FF8-00022D09712B
- For Vinum volume manager partition – 516E7CB8-6ECF-11D6-8FF8-00022D09712B
- For ZFS partition – 516E7CBA-6ECF-11D6-8FF8-00022D09712B and
- For nandfs partition – 74BA7DD9-A689-11E1-BD04-00E081286ACF.
As for macOS Darwin operating system, the GUIDs are as follows:
- For Hierarchical File System Plus partition – 48465300-0000-11AA-AA11-00306543ECAC
- For Apple APFS container and for APFS FileVault volume container – 7C3457EF-0000-11AA-AA11-00306543ECAC
- For Apple UFS container – 55465300-0000-11AA-AA11-00306543ECAC
- For ZFS – 6A898CC3-1DD2-11B2-99A6-080020736631
- For Apple RAID partition – 52414944-0000-11AA-AA11-00306543ECAC
- For Apple RAID partition, offline – 52414944-5F4F-11AA-AA11-00306543ECAC
- For Apple Boot partition (Recovery HD) – 426F6F74-0000-11AA-AA11-00306543ECAC
- For Apple Label – 4C616265-6C00-11AA-AA11-00306543ECAC
- For Apple TV Recovery partition – 5265636F-7665-11AA-AA11-00306543ECAC
- For Apple Core Storage Container and for HFS+ FileVault volume container – 53746F72-6167-11AA-AA11-00306543ECAC
- For Apple APFS Preboot partition – 69646961-6700-11AA-AA11-00306543ECAC and
- For Apple APFS Recovery partition – 52637672-7900-11AA-AA11-00306543ECAC.
As for Solaris Illumos operating system, the GUIDs are as follows:
- For boot partition – 6A82CB45-1DD2-11B2-99A6-080020736631
- For root partition – 6A85CF4D-1DD2-11B2-99A6-080020736631
- For swap partition – 6A87C46F-1DD2-11B2-99A6-080020736631
- For backup partition – 6A8B642B-1DD2-11B2-99A6-080020736631
- For /usr partition – 6A898CC3-1DD2-11B2-99A6-080020736631
- For /var partition – 6A8EF2E9-1DD2-11B2-99A6-080020736631
- For /home partition – 6A90BA39-1DD2-11B2-99A6-080020736631
- For alternate sector – 6A9283A5-1DD2-11B2-99A6-080020736631
- For reserved partition – 6A945A3B-1DD2-11B2-99A6-080020736631
- For reserved partition – 6A9630D1-1DD2-11B2-99A6-080020736631
- For reserved partition – 6A980767-1DD2-11B2-99A6-080020736631
- For reserved partition – 6A96237F-1DD2-11B2-99A6-080020736631 and
- For the reserved partition – 6A8D2AC7-1DD2-11B2-99A6-080020736631.
As for NetBSD operating system, the GUIDs are as follows:
- For swap partition – 49F48D32-B10E-11DC-B99B-0019D1879648
- For FFS partition – 49F48D5A-B10E-11DC-B99B-0019D1879648
- For LFS partition – 49F48D82-B10E-11DC-B99B-0019D1879648
- For RAID partition – 49F48DAA-B10E-11DC-B99B-0019D1879648
- For concatenated partition – 2DB519C4-B10F-11DC-B99B-0019D1879648 and
- For encrypted partition – 2DB519EC-B10F-11DC-B99B-0019D1879648.
As for Chrome operating system, the GUIDs are as follows:
- For Chrome OS kernel – FE3A2A5D-4F32-41A7-B725-ACCC3285A309
- For Chrome OS rootfs – 3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC
- For Chrome OS firmware – CAB6E88E-ABF3-4102-A07A-D4BB9BE3C1D3
- For Chrome OS future use – 2E0A753D-9E48-43B0-8337-B15192CB1B5E
- For Chrome OS miniOS – 09845860-705F-4BB5-B16C-8A8A099CAF52 and
- For Chrome OS hibernate – 3F0F8318-F146-4E6B-8222-C28C8F02E0D5.
As for Container Linux by CoreOS, the GUIDs are as follows:
- For Resizable rootfs (coreos-resize) – 3884DD41-8582-4404-B9A8-E9B84F2DF50E
- For OEM customizations (coreos-reserved) – C95DC21A-DF0E-4340-8D7B-26CBFA9A03E0
- For /usr partition (coreos-usr) – 5DFBF5F4-2848-4BAC-AA5E-0D9A20B745A6 and
- For Root filesystem on RAID (coreos-root-raid) – BE9067B9-EA49-4F15-B4F6-F36F8C9E1818.
As for MidnightBSD operating system, the GUIDs are as follows:
- For boot partition – 85D5E45E-237C-11E1-B4B3-E89A8F7FC3A7
- For data partition – 85D5E45A-237C-11E1-B4B3-E89A8F7FC3A7
- For swap partition – 85D5E45B-237C-11E1-B4B3-E89A8F7FC3A7
- For Unix File System partition – 0394EF8B-237E-11E1-B4B3-E89A8F7FC3A7
- For Vinum volume manager partition – 85D5E45C-237C-11E1-B4B3-E89A8F7FC3A7 and
- For ZFS partition – 85D5E45D-237C-11E1-B4B3-E89A8F7FC3A7.
As for Ceph operating system, the GUIDs are as follows:
- For journal – 45B0969E-9B03-4F30-B4C6-B4B80CEFF106
- For dm-crypt journal – 45B0969E-9B03-4F30-B4C6-5EC00CEFF106
- For OSD – 4FBD7E29-9D25-41B8-AFD0-062C0CEFF05D
- For dm-crypt OSD – 4FBD7E29-9D25-41B8-AFD0-5EC00CEFF05D
- For disk in creation – 89C57F98-2FE5-4DC0-89C1-F3AD0CEFF2BE
- For dm-crypt disk in creation – 89C57F98-2FE5-4DC0-89C1-5EC00CEFF2BE
- For block – CAFECAFE-9B03-4F30-B4C6-B4B80CEFF106
- For block DB – 30CD0809-C2B2-499C-8879-2D6B78529876
- For block write-ahead log – 5CE17FCE-4087-4169-B7FF-056CC58473F9
- For Lockbox for dm-crypt keys – FB3AABF9-D25F-47CC-BF5E-721D1816496B
- For multipath OSD – 4FBD7E29-8AE0-4982-BF9D-5A8D867AF560
- For multipath journal – 45B0969E-8AE0-4982-BF9D-5A8D867AF560
- For multipath block – CAFECAFE-8AE0-4982-BF9D-5A8D867AF560
- For multipath block – 7F4A666A-16F3-47A2-8445-152EF4D03F6C
- For multipath block DB – EC6D6385-E346-45DC-BE91-DA2A7C8B3261
- For multipath block write-ahead log – 01B41E1B-002A-453C-9F17-88793989FF8F
- For dm-crypt block – CAFECAFE-9B03-4F30-B4C6-5EC00CEFF106
- For dm-crypt block DB – 93B0052D-02D9-4D8A-A43B-33A3EE4DFBC3
- For dm-crypt block write-ahead log – 306E8683-4FE2-4330-B7C0-00A917C16966
- For dm-crypt LUKS journal – 45B0969E-9B03-4F30-B4C6-35865CEFF106
- For dm-crypt LUKS block – CAFECAFE-9B03-4F30-B4C6-35865CEFF106
- For dm-crypt LUKS block DB – 166418DA-C469-4022-ADF4-B30AFD37F176
- For dm-crypt LUKS block write-ahead log – 86A32090-3647-40B9-BBBD-38D8C573AA86 and
- For dm-crypt LUKS OSD – 4FBD7E29-9D25-41B8-AFD0-35865CEFF05D.
As for VMware ESX operating system, the GUIDs are as follows:
- For vmkcore (coredump partition) – 9D275380-40AD-11DB-BF97-000C2911D1B8
- For VMFS file system partition – AA31E02A-400F-11DB-9590-000C2911D1B8 and
- For VMware Reserved – 9198EFFC-31C0-11DB-8F78-000C2911D1B8.
As for Android-IA operating system, the GUIDs are as follows:
- For boot loader – 2568845D-2332-4675-BC39-8FA5A4748D15
- For boot loader 2 – 114EAFFE-1552-4022-B26E-9B053604CF84
- For boot – 49A4D17F-93A3-45C1-A0DE-F50B2EBE2599
- For recovery – 4177C722-9E92-4AAB-8644-43502BFD5506
- For misc – EF32A33B-A409-486C-9141-9FFB711F6266
- For Metadata – 20AC26BE-20B7-11E3-84C5-6CFDB94711E9
- For system – 38F428E6-D326-425D-9140-6E0EA133647C
- For cache – A893EF21-E428-470A-9E55-0668FD91A2D9
- For data – DC76DDA9-5AC1-491C-AF42-A82591580C0D
- For persistent – EBC597D0-2053-4B15-8B64-E0AAC75F4DB1
- For vendor – C5A0AEEC-13EA-11E5-A1B1-001E67CA0C3C
- For config – BD59408B-4514-490D-BF12-9878D963F378
- For factory – 8F68CC74-C5E5-48DA-BE91-A0C8C15E9C80
- For factory (alt) – 9FDAA6EF-4B3F-40D2-BA8D-BFF16BFB887B
- For fastboot / tertiary – 767941D0-2085-11E3-AD3B-6CFDB94711E9 and
- For OEM – AC6D7924-EB71-4DF8-B48D-E267B27148FF.
As for Android 6.0+ ARM operating system, the GUIDs are as follows:
- For Android Meta – 19A710A2-B3CA-11E4-B026-10604B889DCF and
- For Android EXT – 193D1EA4-B3CA-11E4-B075-10604B889DCF.
As for Open Network Install Environment or ONIE operating system, the GUIDs are as follows:
- For boot – 7412F7D5-A156-4B13-81DC-867174929325 and
- For config – D4E6E2CD-4469-46F3-B5CB-1BFF57AFC149.
As for SoftRAID utility software, the GUIDs are as follows:
- For SoftRAID_Status – B6FA30DA-92D2-4A9A-96F1-871EC6486200
- For SoftRAID_Scratch – 2E313465-19B9-463F-8126-8A7993773801
- For SoftRAID_Volume – FA709C7E-65B1-4593-BFD5-E71D61DE9B02 and
- For SoftRAID_Cache – BBBA6DF5-F46F-4A89-8F59-8765B2727503.
As for Fuchsia standard partitions, the GUIDs are as follows:
- For boot loader (slot A/B/R) – FE8A2634-5E2E-46BA-99E3-3A192091A350
- For durable mutable encrypted system data – D9FD4535-106C-4CEC-8D37-DFC020CA87CB
- For durable mutable bootloader data (including A/B/R metadata) – A409E16B-78AA-4ACC-995C-302352621A41
- For factory-provisioned read-only system data – F95D940E-CABA-4578-9B93-BB6C90F29D3E
- For factory-provisioned read-only boot loader data – 10B8DBAA-D2BF-42A9-98C6-A7C5DB3701E7
- For Fuchsia Volume Manager – 49FD7CB8-DF15-4E73-B9D9-992070127F0F
- For verified boot metadata (slot A/B/R) – 421A8BFC-85D9-4D85-ACDA-B64EEC0133E9 and
- For Zircon boot image (slot A/B/R) – 9B37FFF6-2E58-466A-983A-F7926D0B04E0.
As for Fuchsia legacy partitions, the GUIDs are as follows:
- For fuchsia-esp – C12A7328-F81F-11D2-BA4B-00A0C93EC93B
- For fuchsia-system – 606B000B-B7C7-4653-A7D5-B737332C899D
- For fuchsia-data – 08185F0C-892D-428A-A789-DBEEC8F55E6A
- For fuchsia-install – 48435546-4953-2041-494E-5354414C4C52
- For fuchsia-blob – 2967380E-134C-4CBB-B6DA-17E7CE1CA45D
- For fuchsia-fvm – 41D0E340-57E3-954E-8C1E-17ECAC44CFF5
- For Zircon boot image (slot A) – DE30CC86-1F4A-4A31-93C4-66F147D33E05
- For Zircon boot image (slot B) – 23CC04DF-C278-4CE7-8471-897D1A4BCDF7
- For Zircon boot image (slot R) – A0E5CF57-2DEF-46BE-A80C-A2067C37CD49
- For sys-config – 4E5E989E-4C86-11E8-A15B-480FCF35F8E6
- For factory-config – 5A3A90BE-4C86-11E8-A15B-480FCF35F8E6
- For boot loader – 5ECE94FE-4C86-11E8-A15B-480FCF35F8E6
- For guid-test – 8B94D043-30BE-4871-9DFA-D69556E8C1F3
- For verified boot metadata (slot A) – A13B4D9A-EC5F-11E8-97D8-6C3BE52705BF
- For verified boot metadata (slot B) – A288ABF2-EC5F-11E8-97D8-6C3BE52705BF
- For verified boot metadata (slot R) – 6A2460C3-CD11-4E8B-80A8-12CCE268ED0A
- For misc – 1D75395D-F2C6-476B-A8B7-45CC1C97B476
- For emmc-boot1 – 900B0FC5-90CD-4D4F-84F9-9F8ED579DB88 and
- For emmc-boot2 – B2B2E8D1-7C10-4EBC-A2D0-4614568260AD.
And, the single GUIDs for some other operating systems and utility software are as follows:
- As for the Haiku operating system, the GUID is 42465331-3BA3-10F1-802A-4861696B7521 for Haiku BFS.
- As for the OpenBSD operating system, the GUID for the data partition is 824CC7A0-36A8-11E3-890A-952519AD3F61.
- For the QNX operating system, the GUID is CEF5A9AD-73BC-4601-89F3-CDEEEEE321A1 for the Power-safe (QNX6) file system.
- The GUID for the partition of the Plan 9 operating system is C91818F9-8025-47AF-89D2-F030D7000C2C.
- For the PowerPC operating system, the GUID for PReP boot is 9E1A2D38-C612-4316-AA26-8B49521E5A8B.
- For freedesktop.org operating system, the GUID for shared boot loader configuration BC13C2FF-59E6-4262-A352-B275FD6F7172.
- As for Atari TOS operating system, the GUID for Basic data partition is 734E5AFE-F61A-11E6-BC64-92361F002671.
- For VeraCrypt open-source utility, the GUID for encrypted data partition is 8C8F8EFF-AC95-4770-814A-21994F2DBC8F.
- For OS/2, the GUID for the ArcaOS Type 1 partition is 90B6FF38-B98F-4358-A21F-48F35B4A8AD3.
- For the Storage Performance Development Kit or SPDK, the GUID for its block device is 7C5222BD-8F5D-4087-9C00-BF9843C7B58C.
- For barebox boot loaders, the GUID for barebox-state is 4778ED65-BF42-45FA-9C5B-287A1DC4AAB1.
- And, for the U-Boot boot loader, the GUID for the U-Boot environment is 3DE21764-95BD-54BD-A5C3-4ABE786F38A8.
Operating System Support
GPT supports different operating systems differently. For example, in the case of UNIX and UNIX-like operating systems, it supports both read and write operations as well as offers boot support.
On the other hand, for different versions of Windows operating systems, for some it supports both read and write operations and booting while in others it offers only read and write support.
Also, in some cases, to offer boot support, it has a few specific requirements. All of these are enlisted below.
As for the UNIX and UNIX-like operating systems, GPT offers read, write and boot support to these particular operating systems:
- Most x86 Linux distributions including Fedora 8+ and Ubuntu 8.04+
- Solaris and
However, for the MidnightBSD operating system family, it needs BIOS to offer boot support.
As for the Microsoft Windows 32-bit versions, GPT offers only read and write support to these specific operating systems:
- Windows Server 2003 SP1
- Windows Vista
- Windows Server 2008 and
- Windows 7.
However, for Windows 8, Windows 8.1, and Windows 10, it needs UEFI to offer boot support in addition to read and write support.
And as for the Microsoft Windows: 64-bit versions, GPT offers both read and write support as well as boot support to these following operating systems:
- Windows XP 64-Bit Edition Version 2002 for Itanium systems
- Windows XP 64-Bit Edition Version 2003
- Windows Server 2003
- Windows Server 2008 and
- Windows Server 2008 R2.
On the other hand, it offers read and write support but requires UEFI to offer boot support to the following operating systems depending on the platform:
- Windows Vista
- Windows 7
- Windows 8
- Windows Server 2012
- Windows 8.1
- Windows 10
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022 and
- Windows 11.
And, depending on the platform used, it offers only read and write support to Windows XP Professional x64 Edition Windows Server 2003.
Now, with all the technicalities, features and requirements explained, you must have understood what a GPT partitioning scheme actually is.
However, to make a decisive choice, you will also need to know the uses, advantages and disadvantages of this particular partitioning style, which brings to the next sections of the article.
Most of the users now are more inclined toward using the GPT based disks because it allows growth.
This is due to the fact that the larger number of partitions on a GPT disks eliminates the constraints of temporary partition schemes which is so common in MBR or Master Boot Record based disks.
Another significant use of the GPT disk partition scheme is seen by the data critical platforms.
This is primarily due to the self-identifying and well defined nature of the new GPT partition scheme.
This allows storing platform operations in partitions instead of in any hidden or un-partitioned sectors.
The GPT partition scheme is also useful for CRC 32 fields for redundancy due to the use of both primary as well as backup partition tables.
This helps in improving the integrity of the partition data structures.
The GPT partition format is also used by sectors that are looking for future expansion.
The different version numbers and size fields make this possible for them.
The global unique identification of the GPT partition and its content type prevents partition identifier collisions with proper coordination and management.
The GPT partition scheme is used in the 64-bit UEFI-based computers since Windows works best on a GPT partition.
This means that GPT can be read by almost all versions of Windows including and not limited to:
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Vista as well as their server versions.
It can boot easily from a UEFI-based computer.
Also, other operating systems use GPT partition schemes.
For example, the Intel Mac computers of Apple have shifted to this scheme from their proprietary Apple Partition Table or APT format.
The latest GPT structures are also used by Linux operating systems, on the other hand, which typically comes with built-in support for the GPT partition schemes.
This new GUID PT scheme offers quite a lot of advantages to the users. Here are a few of them listed for your knowledge.
One of the most significant advantages of the GPT scheme is that it is more resilient to corruption in comparison to the MBR partition scheme.
This is primarily because the GPT stores several versions of the data. This means that when data in one partition is corrupted, it can be recovered from a different location.
It is also more secure and offers a much higher data protection.
This is mainly because the GPT scheme stores CRC or Cyclic Redundancy Check values.
It allows the GPT to know about any issues or chances of data corruption beforehand and act accordingly.
This protects the data and the partition table which is a feature that is found lacking in the MBR partition scheme.
Another significant advantage of the GPT scheme is related to the Globally Unique Identifier or GUID itself.
This is actually a 36 character plain text Unicode name for the partition. This helps the software to identify the partition easily and directly.
For this, the software does not need to rely on the special translation to be made between the operating system and the BIOS.
It will present a name for the partition that a human can read without requiring any extra knowledge of the partition.
In terms of the number of partitions, the advantage of using GPT in Windows is that you will get as many as 128 primary partitions instead of just 4 as you would get in the Master Boot Record partition scheme.
However, theoretically, it is unlimited.
In Windows it is not impossible to access as much as 32,768 TB of information on one single drive mechanism.
This is slightly more than the 128 kilobytes that you usually got on those single density and single-sided floppy drives that were used extensively in the 1980s.
Moreover, a GPT formatted disk typically does not need UEFI or the Unified Extensible Firmware Interface because all of the information that is necessary for the disk is enclosed in the format itself.
Perhaps the best advantage offered by the GPT partition scheme is that it supports not only the Windows standard versions as mentioned above but also the other ones as well such as:
- The Windows XP x64
- The 64 bit Windows Server 2003
- The Windows Server 2003 SP1 and
- The Windows Server 2008 R2 and 2008.
In short, the features and functionalities of the new GPT partition scheme offer a much better management of the partitions in the disks.
The disadvantage of the new GPT scheme is not many. However, the most significant one is related predominantly to its compatibility with the older operating systems.
For example, if you have computer running on a Windows XP 32-bit, forget about booting because GPT will not work on it.
This drawback of the GPT scheme is mainly due to its support to the latest Unified Extensible Firmware Interface.
Apart from that, you will also find it quite difficult to set up a Windows dual-boot system by using a Linux operating system and UEFI so that it starts in the BIOS mode.
However, the disadvantages of the GPT are felt more while using it.
This, however, does not mean that the issues lie with the GPT itself. For example:
- It is found that GPT is not compatible with the older utility software as well such as partition managers, boot managers, and others and
- It still does not have any specialized recovery software that is exclusive for GUID Partition Tables structure recovery.
Perhaps the only significant disadvantage that is related directly to the GPT itself is its relatively larger overhead in comparison to the Master Boot Record partition scheme. This is mainly because the GPT standard uses 64-bit values.
And, when the GPT partition type actually matters, the probable disadvantage is that the GUIDs may not include all of the known MBR partition types.
For example, the Novell Netware, especially when the GPT comes with a Protective MBR to boot into that particular operating system.
So, now you have gained some knowledge about the GUID Partition Table and will probably want to use it while setting up a drive.
This will help you to stay with the crowd and the computers that is slowly but surely moving towards a more robust and modern standard.