GUID Partition Table
GUID Partition Table (GPT) is a standard for the layout of the partition table on a physical hard disk, using globally unique identifiers (GUID). Although it forms a part of the Unified Extensible Firmware Interface (UEFI) standard (Unified EFI Forum proposed replacement for the PC BIOS), it is also used on some BIOS systems because of the limitations of master boot record (MBR) partition tables, which use 32 bits for storing logical block addresses (LBA) and size information on a traditionally 512 byte disk sector.
As of 2010[update], most current operating systems support GPT. Some, including OS X and Microsoft Windows on x86, only support booting from GPT partitions on systems with EFI firmware, but FreeBSD and most Linux distributions can boot from GPT partitions on systems with either legacy BIOS firmware interface or EFI.
- 1 History
- 2 Features
- 3 MBR variants
- 4 Partition table header (LBA 1)
- 5 Partition entries
- 6 Operating systems support
- 7 Partition type GUIDs
- 8 See also
- 9 Notes
- 10 References
- 11 External links
The widespread MBR partitioning scheme, dating from the early 1980s, imposed limitations that affect the use of modern hardware. One of the main limitations is the usage of 32 bits for storing block addresses and quantity information. For hard disks with 512-byte sectors, the MBR partition table entries allow up to a maximum of 2 TiB (232 × 512 bytes).
Intel therefore developed a new partition table format in the late 1990s as part of what eventually became UEFI. As of 2010[update], GPT forms a subset of the UEFI specification. GPT allocates 64 bits for logical block addresses, therefore allowing a maximum disk size of 264 sectors. For disks with 512-byte sectors, maximum size is 9.4 ZB (9.4 × 1021 bytes) or 8 ZiB (9,444,732,965,739,290,427,392 bytes, coming from 18,446,744,073,709,551,616 (264) sectors × 512 (29) bytes per sector).
|This section needs additional citations for verification. (July 2013) (Learn how and when to remove this template message)|
MBR-based partition table schemes insert the partitioning information for (usually) four "primary" partitions in the master boot record (MBR) (which on a BIOS system is also the container for code that begins the process of booting the system). In a GPT, the first sector of the disk is reserved for a "protective MBR" such that booting a BIOS-based computer from a GPT disk is supported, but the bootloader and operating system must both be GPT-aware. Regardless of the sector size, the GPT header begins on the second logical block of the device.
Like modern MBRs, GPTs use logical block addressing (LBA) in place of the historical cylinder-head-sector (CHS) addressing. The protective MBR is contained in LBA 0, the GPT header is in LBA 1, and the GPT header has a pointer to the partition table, or Partition Entry Array, typically LBA 2. The UEFI specification stipulates that a minimum of 16,384 bytes, regardless of sector size, be allocated for the Partition Entry Array. On a disk having 512-byte sectors, a partition entry array size of 16,384 bytes and the minimum size of 128 bytes for each partition entry, LBA 34 is the first usable sector on the disk.
Hard disk manufacturers are transitioning to 4,096-byte sectors. As of 2010, the first such drives continue to present 512-byte physical sectors to the OS, so degraded performance can result when the drive's (hidden) internal 4 KB sector boundaries do not coincide with the 4 KB logical blocks, clusters and virtual memory pages common in many operating systems and file systems. This is a particular problem on writes when the drive is forced to perform two read-modify-write operations to satisfy a single misaligned 4 KB write operation. Such a misalignment occurs by default if the first partition is placed immediately after the GPT, as the next block is LBA 34, whereas the next 4 KB boundary begins with LBA 40.
For backward compatibility with most legacy operating systems like DOS, OS/2 and versions of Windows before Vista, MBR partitions must always start on track boundaries according to the traditional CHS addressing scheme and end on a cylinder boundary. This even holds true for partitions with emulated CHS geometries (as reflected by the BIOS and the CHS sectors entries in the MBR partition table) or partitions accessed only via LBA. Extended partitions always start on cylinder boundaries as well.
This typically causes the first primary partition to start at LBA 63 on disks accessed via LBA, leaving a gap of 62 sectors with MBR-based disks, sometimes called "MBR gap", "boot track", or "embedding area". That otherwise unused disk space is commonly used by bootloaders such as GRUB for storing their second stages. On older computers using alternative LBA/CHS translation schemes or different extended CHS mappings, with smaller LBA-accessed disks, or on disks accessed via CHS only, the gap could be smaller, although not normally less than LBA 16 on normal hard disks.
Since Windows Vista, the first partition usually starts after a gap of 2,047 sectors at LBA 2,048 as part of its new 1 MB partition alignment policy, so no large-sector misalignment occurs by default, but serious compatibility problems with older operating systems and disk tools exist.
GPT also provides redundancy, writing the GPT header and partition table both at the beginning and at the end of the disk.
If the minimum size of 16,384 bytes is allocated for the partition entry array, and the default size of 128 bytes is used for each partition entry, then the maximum number of partitions is 128.
Legacy MBR (LBA 0)
Traditionally, in IBM PC compatible systems the first sector of the disk holds the Master Boot Record (MBR), containing the drive's partitioning information and the code of the first stage boot loader for BIOS-based systems.
Protective MBR (LBA 0)
For limited backward compatibility, the space of the legacy MBR is still reserved in the GPT specification, but it is now used in a way that prevents MBR-based disk utilities from misrecognizing and possibly overwriting GPT disks. This is referred to as a protective MBR.
A single partition type of EEh, encompassing the entire GPT drive (where "entire" actually means as much of the drive as can be represented in an MBR), is indicated and identifies it as GPT. Operating systems and tools which cannot read GPT disks will generally recognize the disk as containing one partition of unknown type and no empty space, and will typically refuse to modify the disk unless the user explicitly requests and confirms the deletion of this partition. This minimizes accidental erasures. Furthermore, GPT-aware OSes may check the protective MBR and if the enclosed partition type is not of type EEh or if there are multiple partitions defined on the target device, the OS may refuse to manipulate the partition table.
While the MBR and protective MBR layouts were defined around 512 bytes per sector, the actual sector size can be larger on various media such as MO disks or hard disks with Advanced Format. Extra space in the MBR typically remains unused.
If the actual size of the disk exceeds the maximum partition size representable using the legacy 32-bit LBA entries in the MBR partition table, the recorded size of this partition is clipped at the maximum, thereby ignoring the rest of disk. This amounts to a maximum reported size of 2 TB, assuming a disk with 512 bytes per sector (see 512e). It would result in 16 TB with 4 KB sectors (4Kn), but since many older operating systems and tools are hard-wired for a sector size of 512 bytes or are limited to 32-bit calculations, exceeding the 2 TB limit would cause serious compatibility problems.
Hybrid MBR (LBA 0 + GPT)
In operating systems that support GPT-based boot through BIOS services rather than EFI, the first sector is also still used to store the first stage of the bootloader code, but modified to recognize GPT partitions. The bootloader in the MBR must not assume a fixed sector size of 512 bytes per sector.
Apple's Boot Camp software for Intel-based Apple Macs creates a hybrid partition table to allow the booting of Windows (which at the time of Boot Camp's creation did not support GPT or EFI). In this system the protective partition is reduced in size to cover from sector 1 to the sector before the first regular partition included in the hybrid MBR. Additional MBR partitions are then defined to correspond to the next three GPT partitions.
Partition table header (LBA 1)
The partition table header defines the usable blocks on the disk. It also defines the number and size of the partition entries that make up the partition table. The EFI stipulates a minimum of 16,384 bytes be reserved for the partition table array, so there are 128 partition entries reserved, each 128 bytes long.
The header contains the disk globally unique identifier (GUID). It records its own size and location (always LBA 1) and the size and location of the secondary GPT header and table (always the last sectors on the disk). Importantly, it also contains a CRC32 checksum for itself and for the partition table, which may be verified by the firmware, bootloader and/or operating system on boot. Because of this, hex editors should not be used to modify the contents of the GPT. Such modification would render the checksum invalid. In this case, the primary GPT may be overwritten with the secondary one by disk recovery software. If both GPTs contain invalid checksums, many bootloaders (those governed by an integrity model in particular) and operating systems will refuse to work with the disk until the corrupted partition tables are repaired or removed.
|0 (0x00)||8 bytes||Signature ("EFI PART", 45h 46h 49h 20h 50h 41h 52h 54h or 0x5452415020494645ULL[a] on little-endian machines)|
|8 (0x08)||4 bytes||Revision (for GPT version 1.0 (through at least UEFI version 2.3.1), the value is 00h 00h 01h 00h)|
|12 (0x0C)||4 bytes||Header size in little endian (in bytes, usually 5Ch 00h 00h 00h or 92 bytes)|
|16 (0x10)||4 bytes||CRC32 of header (offset +0 up to header size), with this field zeroed during calculation|
|20 (0x14)||4 bytes||Reserved; must be zero|
|24 (0x18)||8 bytes||Current LBA (location of this header copy)|
|32 (0x20)||8 bytes||Backup LBA (location of the other header copy)|
|40 (0x28)||8 bytes||First usable LBA for partitions (primary partition table last LBA + 1)|
|48 (0x30)||8 bytes||Last usable LBA (secondary partition table first LBA - 1)|
|56 (0x38)||16 bytes||Disk GUID (also referred as UUID on UNIXes)|
|72 (0x48)||8 bytes||Starting LBA of array of partition entries (always 2 in primary copy)|
|80 (0x50)||4 bytes||Number of partition entries in array|
|84 (0x54)||4 bytes||Size of a single partition entry (usually 80h or 128)|
|88 (0x58)||4 bytes||CRC32 of partition array|
|92 (0x5C)||*||Reserved; must be zeroes for the rest of the block (420 bytes for a sector size of 512 bytes; but can be more with larger sector sizes)|
The values for current and backup LBAs of the primary header should be the second sector of the disk (LBA 1) and the last sector of the disk, respectively. The secondary header at the end of the disk identifies its own table of partition entries, which is located directly before that header.
Since the primary header must be located at LBA 1, it will not necessarily be physically contiguous with the MBR; on an Advanced Format disk with 4 KB sectors, the header will be located at the byte 4096 from the beginning of the disk, leaving a gap of unused space between it and the MBR. On such a disk, the byte 512 that directly follows the MBR is still part of LBA 0. However, a disk with 512-byte sectors will store its GPT header at byte 512 because, as such, that position corresponds to LBA 1.
|0 (0x00)||16 bytes||Partition type GUID|
|16 (0x10)||16 bytes||Unique partition GUID|
|32 (0x20)||8 bytes||First LBA (little endian)|
|40 (0x28)||8 bytes||Last LBA (inclusive, usually odd)|
|48 (0x30)||8 bytes||Attribute flags (e.g. bit 60 denotes read-only)|
|56 (0x38)||72 bytes||Partition name (36 UTF-16LE code units)|
|128 bytes total|
After the header, the Partition Entry Array describe partitions, using 128 byte blocks per entry at a minimum. The first 16 bytes designate the partition type globally unique identifier (GUID). For example, the GUID for an EFI System partition is C12A7328-F81F-11D2-BA4B-00A0C93EC93B. The second 16 bytes contain a GUID unique to the partition. Then follow the starting and ending 64-bit LBAs, partition attributes and partition names. As is the nature and purpose of GUIDs, no central registry is needed to ensure the uniqueness of the GUID partition type designators. The location of the partition entries array on disk is defined in the GPT header.
Also, the sector size must not be assumed to be hard-wired to 512 bytes per sector in calculations (see Advanced Format), that is, there can be more than four partition entries in a single sector, and (with possible future much larger partition table entries) it is possible to have a sector hold only a fraction of a partition entry. Except for the first two sectors (LBA 0 and LBA 1), the GPT specification just describes the size and organization of a data structure, not in how many sectors it is stored on disk.
The 64-bit partition table attributes are shared between 48-bit common attributes for all partition types, and 16-bit type-specific attributes.
|0||System partition (disk partitioning utilities must preserve the partition as is)|
|1||EFI firmware should ignore the content of the partition and not try to read from it|
|2||Legacy BIOS bootable (equivalent to active flag (typically bit 7 set) at offset +0h in partition entries of the MBR partition table)|
|3–47||Reserved for future use|
|48–63||Defined and used by the individual partition type|
|63||Do not automount (i.e., do not assign drive letter)|
Operating systems support
Hybrid MBRs are non-standard and can be interpreted in different ways by different OSes. Unless otherwise noted, OSes provide precedence to the GPT data when a hybrid MBR configuration is encountered.
The term No native support on this arch and version. should be understood this way:
- Not supported as data disk, only known legacy partitions found in protective MBR are accessible via the OS. Detachable disks: only support for MBR partitioning; No access with end user applications. GPT contained raw data is accessible with third-party administrator tools for low level disk access. True file system level support in read or read-write form might be subject of software from a third-party vendor.
UNIX and Unix-like operating systems
|OS family||Version or edition||Platform||Read and write support||Boot support||Note|
|FreeBSD||Since 7.0||IA-32, x86-64, ARM||Yes||Yes||In a hybrid configuration, both GPT and MBR partition identifiers may be used.|
|Linux||Most of the x86 Linux distributions
||IA-32, x86-64||Yes||Yes||New tools such as gdisk, GNU Parted, util-linux v2.23+ fdisk, Syslinux, GRUB 0.96 + patches and GRUB 2 have been GPT-enabled.|
|OS X||Since 10.4.0 (some features since 10.4.6)||IA-32, x86-64, PowerPC||Yes||Yes||Only Intel Macintosh computers can boot from GPT.|
|MidnightBSD||Since 0.4-CURRENT||IA-32, x86-64||Yes||Requires BIOS||In a hybrid configuration, both GPT and MBR partition identifiers may be used.|
|Solaris||Since Solaris 10||IA-32, x86-64, SPARC||Yes||Yes|||
|HP-UX||Since HP-UX 11.20||IA-64||Yes||Yes|||
Windows: 32-bit versions
Windows 7 and earlier do not support (U)EFI on 32-bit platforms, and therefore do not allow booting from GPT partitions.
|OS version||Release date||Platform||Read or write support||Boot support||Note|
|Windows Server 2003||2003-04-24||IA-32||No||No|
|Windows Server 2003 SP1||2005-03-30||IA-32||Yes||No||MBR takes precedence in hybrid configuration|
|Windows Vista||2006-07-22||IA-32||Yes||No||MBR takes precedence in hybrid configuration|
|Windows Server 2008||2008-02-27||IA-32||Yes||No||MBR takes precedence in hybrid configuration|
|Windows 7||2009-10-22||IA-32||Yes||No||MBR takes precedence in hybrid configuration|
|Windows 8||2012-08-01||IA-32||Yes||Requires UEFI||MBR takes precedence in hybrid configuration|
|Windows 8.1||2013-08-27||IA-32||Yes||Requires UEFI||MBR takes precedence in hybrid configuration|
|Windows 10||2015-07-29||IA-32||Yes||Requires UEFI||MBR takes precedence in hybrid configuration|
Windows: 64-bit versions
|OS version||Release date||Platform||Read and write support||Boot support||Note|
|Windows XP Professional x64 Edition
Windows Server 2003
|2005-04-25||x64||Yes||No||MBR takes precedence in hybrid MBR configuration|
|Windows Server 2003||2005-04-25||IA-64||Yes||Yes||MBR takes precedence in hybrid MBR configuration|
|Windows Vista||2006-07-22||x64||Yes||Requires UEFI[b]||MBR takes precedence in hybrid configuration|
|Windows Server 2008||2008-02-27||x64||Yes||Requires UEFI||MBR takes precedence in hybrid configuration|
|Windows Server 2008||2008-02-27||IA-64||Yes||Yes||MBR takes precedence in hybrid configuration|
|Windows 7||2009-10-22||x64||Yes||Requires UEFI[c]||MBR takes precedence in hybrid configuration.|
|Windows Server 2008 R2||2009-10-22||IA-64||Yes||Yes||MBR takes precedence in hybrid configuration|
Windows Server 2012
|2012-08-01||x64||Yes||Requires UEFI||MBR takes precedence in hybrid configuration.|
|Windows 8.1||2013-08-27||x64||Yes||Requires UEFI||MBR takes precedence in hybrid configuration|
|Windows 10||2015-07-29||x64||Yes||Requires UEFI||MBR takes precedence in hybrid configuration|
|Windows Server 2016||2016-Q3||x64||Yes||Requires UEFI||MBR takes precedence in hybrid configuration|
Partition type GUIDs
|Operating system||Partition type||Globally unique identifier (GUID)[d]|
|MBR partition scheme||024DEE41-33E7-11D3-9D69-0008C781F39F|
|EFI System partition||C12A7328-F81F-11D2-BA4B-00A0C93EC93B|
|BIOS Boot partition[e]||21686148-6449-6E6F-744E-656564454649|
|Intel Fast Flash (iFFS) partition (for Intel Rapid Start technology)||D3BFE2DE-3DAF-11DF-BA40-E3A556D89593|
|Sony boot partition[f]||F4019732-066E-4E12-8273-346C5641494F|
|Lenovo boot partition[f]||BFBFAFE7-A34F-448A-9A5B-6213EB736C22|
|Windows||Microsoft Reserved Partition (MSR)||E3C9E316-0B5C-4DB8-817D-F92DF00215AE|
|Basic data partition[g]||EBD0A0A2-B9E5-4433-87C0-68B6B72699C7|
|Logical Disk Manager (LDM) metadata partition||5808C8AA-7E8F-42E0-85D2-E1E90434CFB3|
|Logical Disk Manager data partition||AF9B60A0-1431-4F62-BC68-3311714A69AD|
|Windows Recovery Environment||DE94BBA4-06D1-4D40-A16A-BFD50179D6AC|
|IBM General Parallel File System (GPFS) partition||37AFFC90-EF7D-4E96-91C3-2D7AE055B174|
|Storage Spaces partition||E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D|
|Linux||Linux filesystem data[g]||0FC63DAF-8483-4772-8E79-3D69D8477DE4|
|Root partition (x86)||44479540-F297-41B2-9AF7-D131D5F0458A|
|Root partition (x86-64)||4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709|
|Root partition (32-bit ARM)||69DAD710-2CE4-4E3C-B16C-21A1D49ABED3|
|Root partition (64-bit ARM/AArch64)||B921B045-1DF0-41C3-AF44-4C6F280D3FAE|
|Logical Volume Manager (LVM) partition||E6D6D379-F507-44C2-A23C-238F2A3DF928|
|/srv (server data) partition||3B8F8425-20E0-4F3B-907F-1A25A76F98E8|
|Plain dm-crypt partition||7FFEC5C9-2D00-49B7-8941-3EA10A5586B7|
|Unix File System (UFS) partition||516E7CB6-6ECF-11D6-8FF8-00022D09712B|
|Vinum volume manager partition||516E7CB8-6ECF-11D6-8FF8-00022D09712B|
|Hierarchical File System Plus (HFS+) partition||48465300-0000-11AA-AA11-00306543ECAC|
|Apple RAID partition||52414944-0000-11AA-AA11-00306543ECAC|
|Apple RAID partition, offline||52414944-5F4F-11AA-AA11-00306543ECAC|
|Apple Boot partition (Recovery HD)||426F6F74-0000-11AA-AA11-00306543ECAC|
|Apple TV Recovery partition||5265636F-7665-11AA-AA11-00306543ECAC|
|Apple Core Storage (i.e. Lion FileVault) partition||53746F72-6167-11AA-AA11-00306543ECAC|
|ChromeOS future use||2E0A753D-9E48-43B0-8337-B15192CB1B5E|
|Unix File System (UFS) partition||0394EF8B-237E-11E1-B4B3-E89A8F7FC3A7|
|Vinum volume manager partition||85D5E45C-237C-11E1-B4B3-E89A8F7FC3A7|
|Ceph dm-crypt Encrypted Journal[j]||45B0969E-9B03-4F30-B4C6-5EC00CEFF106|
|Ceph dm-crypt OSD[j]||4FBD7E29-9D25-41B8-AFD0-5EC00CEFF05D|
|Ceph disk in creation[j]||89C57F98-2FE5-4DC0-89C1-F3AD0CEFF2BE|
|Ceph dm-crypt disk in creation[j]||89C57F98-2FE5-4DC0-89C1-5EC00CEFF2BE|
|QNX||Power-safe (QNX6) file system||CEF5A9AD-73BC-4601-89F3-CDEEEEE321A1|
|Plan 9||Plan 9 partition||C91818F9-8025-47AF-89D2-F030D7000C2C|
|VMware ESX||vmkcore (coredump partition)||9D275380-40AD-11DB-BF97-000C2911D1B8|
|VMFS filesystem partition||AA31E02A-400F-11DB-9590-000C2911D1B8|
- Advanced Active Partition (AAP)
- Apple Partition Map (APM)
- BIOS Boot partition
- Boot Engineering Extension Record (BEER)
- BSD disklabel
- Device Configuration Overlay (DCO)
- Disk partitioning
- EFI System partition
- Extended Boot Record (EBR)
- Globally Unique Identifier (GUID)
- Host Protected Area (HPA)
- Master Boot Record (MBR)
- Partition alignment
- Rigid Disk Block (RDB)
- Unified Extensible Firmware Interface (UEFI)
ULLsuffix to an integer constant makes it of type
unsigned long long int.
- Only if using its service pack 1 or 2.
- In a multi-disk setup, non-UEFI bootloader (boot drive) requires MBR-based partitioning, while a system drive can use GUID partitioning.
- The GUIDs in this table are written assuming a little-endian byte order. For example, the GUID for an EFI System partition is written as C12A7328-F81F-11D2-BA4B-00A0C93EC93B here, which corresponds to the 16 byte sequence 28h 73h 2Ah C1h 1Fh F8h D2h 11h BAh 4Bh 00h A0h C9h 3Eh C9h 3Bh – only the first three blocks are byte-swapped.
- The formation of this GUID does not follow the GUID definition; it is formed by using the ASCII codes for the string "Hah!IdontNeedEFI". Such formation of "GUID" value breaks down the guaranteed uniqueness of GUID.
- Some computer manufacturers have their own GUIDs for partitions that are analogous to the EFI System Partition, but that hold boot loaders to launch manufacturer-specific recovery tools.
- Previously, Linux used the same GUID for the data partitions as Windows (Basic data partition: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7). Linux never had a separate unique partition type GUID defined for its data partitions. This created problems when dual-booting Linux and Windows in UEFI-GPT setup. The new GUID (Linux filesystem data: 0FC63DAF-8483-4772-8E79-3D69D8477DE4) was defined jointly by GPT fdisk and GNU Parted developers. It is identified as type code 0x8300 in GPT fdisk. (See definitions in gdisk's parttypes.cc)
- The GUID for
/usron Solaris is used as a generic GUID for ZFS by OS X.
- NetBSD and MidnightBSD had used the FreeBSD GUIDs before their unique GUIDs were created.
- The Ceph filesystem uses GUIDs to mark the state of preparation a disk is in.
- "FAQ: Drive Partition Limits" (PDF). UEFI Forum. Retrieved 2013-11-04.
- Nikkel, Bruce J. (September 2009). "Forensic analysis of GPT disks and GUID partition tables". Digital Investigation 6 (1-2): 39–47. doi:10.1016/j.diin.2009.07.001.
The current popular BIOS and MBR partitioning scheme was originally developed in the early 1980s for the IBM Personal Computer using IBM PC-DOS or MS-DOS. The Basic Input/Output System (BIOS) provides an interface to the hardware and initiates the boot process (IBM, 1983). The MBR, located in sector zero, contains the initial boot code and a four entry partition table (Microsoft, 1983). Intended to solve booting and partitioning limitations with newer hardware, a replacement for both the BIOS and the MBR partition table was developed by Intel in the late 1990s (Intel, 2000). This is now called the Unified EFI (UEFI, 2008 UEFI Forum. Unified extensible firmware interface specification version 2.2 2008.UEFI, 2008) specification, and managed by the UEFI Forum (UEFI, 2009). A subset of this specification includes GPT, intended to replace the DOS/MBR partition tables.
- Roderick W. Smith (2012-07-03). "Make the most of large drives with GPT and Linux". IBM. Retrieved 2013-05-29.
- UEFI specification
- "Western Digital’s Advanced Format: The 4K Sector Transition Begins". Anandtech.
- "Installation". 3.4 BIOS installation. GNU GRUB. Retrieved 2013-09-25.
- "Technical Note TN2166: Secrets of the GPT". Developer.apple.com. 2006-11-06. Retrieved 2014-04-16.
- The GPT header contains a field that specifies the size of a partition table entry. The minimum required is 128 bytes, but implementations must allow for other values. See "Mac Developer Library". Developer.apple.com. Retrieved 2014-07-13.
- "e09127r3 EDD-4 Hybrid MBR boot code annex" (PDF).
- Smith, Rod. "Hybrid MBRs: The Good, the Bad, and the So Ugly You'll Tear Your Eyes Out".
- "Windows and GPT FAQ". Microsoft.
- "Ubuntu on MacBook". Ubuntu Community Documentation.
- Smith, Rod. "GPT fdisk for Linux".
- "GNU Parted FAQ".
- "mklabel - GNU Parted Manual".
- "fdisk: add GPT support". kernel.org. 2013-09-27. Retrieved 2013-10-18.
- Davidlohr Bueso (2013-09-28). "fdisk updates and GPT support". Retrieved 2013-10-18.
- "Myths and Facts About Intel Macs". rEFIt.
- "Booting From a ZFS Root File System".
- "idisk(1M)" (PDF). Hewlett-Packard Co.
- Windows 8 32-bit supports booting from UEFI-based PC using GPT-based disks.
- Microsoft raises the speed limit with the availability of 64-bit editions of Windows Server 2003 and Windows XP Professional 
- "F6F: Funtoo Linux and Intel Rapid Start Technology". Blog.adios.tw. 2012-10-30. Retrieved 2014-01-29.
- GPT fdisk: parttypes.cc, line 198
- Smith, Rod (23 June 2011). "Need for a unique Linux GPT GUID type code (PATCH included)". bug-parted (Mailing list). lists.gnu.org. Retrieved 12 April 2016.
- The Discoverable Partitions Specification
- "[dm-crypt] LUKS GPT GUID". Saout.de. Retrieved 2014-01-29.
- "[dm-crypt] LUKS GPT GUID". Saout.de. Retrieved 2014-01-29.
- "CVS log for src/sys/sys/disklabel_gpt.h". Cvsweb.netbsd.org. Retrieved 2014-01-29.
- "Disk Format - The Chromium Projects". Chromium.org. Retrieved 2014-01-29.
- http://www.midnightbsd.org/cgi-bin/cvsweb.cgi/src/sys/sys/gpt.h.diff?r1=1.4;r2=1.5 src/sys/sys/gpt.h
- Script to set up a ceph disk: ceph-disk, lines 76-81
- QNX Power-safe filesystem
- Microsoft TechNet: Disk Sectors on GPT Disks (archived page)
- Microsoft TechNet: Troubleshooting Disks and File Systems
- Microsoft TechNet: Using GPT Drives
- Microsoft: FAQs on Using GPT disks in Windows
- Apple Developer Connection: Secrets of the GPT
- Make the most of large drives with GPT and Linux
- GPT fdisk: Information on Hybrid GPT-MBR, Converting MBR and BSD disklabels to GPT and Booting from GPT disks
- Convert Windows Vista SP1+ or 7 x86_64 boot from BIOS-MBR mode to UEFI-GPT mode without Reinstall
- Rod Smith - A BIOS to UEFI Transformation
- Support for GPT (Partition scheme) and HDD greater than 2.19 TB in Microsoft Windows XP
- Setting up a RAID volume in Linux with >2TB disks