Misplaced Pages

The GUID Partition Table (GPT) is a standard for the layout of partition tables of a physical computer storage device, such as a hard disk drive or solid-state drive, using universally unique identifiers (UUIDs), which are also known as globally unique identifiers (GUIDs). Forming a part of the Unified Extensible Firmware Interface (UEFI) standard (Unified EFI Forum-proposed replacement for the PC BIOS), it is nevertheless also used for some BIOSs, because of the limitations of master boot record (MBR) partition tables, which use 32 bits for logical block addressing (LBA) of traditional 512-byte disk sectors.

All modern personal computer operating systems support GPT. Some, including macOS and Microsoft Windows on the x86 architecture, support booting from GPT partitions only on systems with EFI firmware, but FreeBSD and most Linux distributions can boot from GPT partitions on systems with either the BIOS or the EFI firmware interface.

History

The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, imposed limitations for use of modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512‑byte sectors, the MBR partition table entries allow a maximum size of 2 TiB (2³² × 512‑bytes) or 2.20 TB (2.20 × 10¹² bytes).

In the late 1990s, Intel developed a new partition table format as part of what eventually became the Unified Extensible Firmware Interface (UEFI). The GUID Partition Table is specified in chapter 5 of the UEFI 2.8 specification. GPT uses 64 bits for logical block addresses, allowing a maximum disk size of 2 sectors. For disks with 512‑byte sectors, the maximum size is 8 ZiB (2 × 512‑bytes) or 9.44 ZB (9.44 × 10²¹ bytes). For disks with 4,096‑byte sectors the maximum size is 64 ZiB (2 × 4,096‑bytes) or 75.6 ZB (75.6 × 10²¹ bytes).

In 2010, hard-disk manufacturers introduced drives with 4,096‑byte sectors (Advanced Format). For compatibility with legacy hardware and software, those drives include an emulation technology (512e) that presents 512‑byte sectors to the entity accessing the hard drive, despite their underlying 4,096‑byte physical sectors. Performance could be degraded on write operations, when the drive is forced to perform two read-modify-write operations to satisfy a single misaligned 4,096‑byte write operation. Since April 2014, enterprise-class drives without emulation technology (4K native) have been available on the market.

Readiness of the support for 4 KB logical sectors within operating systems differs among their types, vendors and versions. For example, Microsoft Windows supports 4K native drives since Windows 8 and Windows Server 2012 (both released in 2012) in UEFI.

Features

Like MBR, GPT uses logical block addressing (LBA) in place of the historical cylinder-head-sector (CHS) addressing. The protective MBR is stored at LBA 0, and the GPT header is in LBA 1, with a backup GPT header stored at the final LBA. The GPT header has a pointer to the partition table (Partition Entry Array), which is typically at LBA 2. Each entry on the partition table has a size of 128 bytes. The UEFI specification stipulates that a minimum of 16,384 bytes, regardless of sector size, are allocated for the Partition Entry Array. Thus, on a disk with 512-byte sectors, at least 32 sectors are used for the Partition Entry Array, and the first usable block is at LBA 34 or higher, while on a 4,096-byte sectors disk, at least 4 sectors are used for the Partition Entry Array, and the first usable block is at LBA 6 or higher.

MBR variants

Protective MBR (LBA 0)

For limited backward compatibility, the space of the legacy Master Boot Record (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 of type 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.

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 the disk. This amounts to a maximum reported size of 2 TiB, assuming a disk with 512 bytes per sector (see 512e). It would result in 16 TiB with 4 KiB sectors (4Kn), but since many older operating systems and tools are hard coded for a sector size of 512 bytes or are limited to 32-bit calculations, exceeding the 2 TiB limit could cause compatibility problems.

Hybrid MBR (LBA 0 + GPT)

In operating systems that support GPT-based boot through BIOS services rather than EFI, the first sector may also still be 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 sector size of 512 bytes.

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 (offsets 80 and 84 in the table).

Partition entries (LBA 2–33)

After the primary header and before the backup header, the Partition Entry Array describes partitions, using a minimum size of 128 bytes for each entry block. The starting location of the array on disk, and the size of each entry, are given in the GPT header. The first 16 bytes of each entry designate the partition type's globally unique identifier (GUID). For example, the GUID for an EFI system partition is C12A7328-F81F-11D2-BA4B-00A0C93EC93B. The second 16 bytes are a GUID unique to the partition. Then follow the starting and ending 64 bit LBAs, partition attributes, and the 36 character (max.) Unicode partition name. As is the nature and purpose of GUIDs and as per RFC 4122, no central registry is needed to ensure the uniqueness of the GUID partition type designators.

The 64-bit partition table attributes are shared between 48-bit common attributes for all partition types, and 16-bit type-specific attributes:

Microsoft defines the type-specific attributes for basic data partition as:

Google defines the type-specific attributes for ChromeOS kernel as:

Operating-system support

UNIX and Unix-like systems

Windows: 32-bit versions

Windows 7 and earlier do not support UEFI on 32-bit platforms, and therefore do not allow booting from GPT partitions.

Windows: 64-bit versions

Limited to 128 partitions per disk.

Partition type GUIDs

The accessibility of this table is in question. The specific issue is: screen readers can not read content that is collapsed and hidden. Relevant discussion may be found on the talk page. (September 2024)

"Partition type GUID" means that each partition type is strictly identified by a GUID number unique to that type, and therefore partitions of the same type will all have the same "partition type GUID". Each partition also has a "partition unique GUID" as a separate entry, which as the name implies is a unique id for each partition.

See also

• Advanced Active Partition (AAP)
• Apple Partition Map (APM)
• Boot Engineering Extension Record (BEER)
• BSD disklabel
• Device Configuration Overlay (DCO)
• Extended Boot Record (EBR)
• Host Protected Area (HPA)
• Partition alignment
• Rigid Disk Block (RDB)
• Volume Table of Contents (VTOC)

Notes

1. Adding ULL suffix to an integer constant makes it of type unsigned long long int.
2. Third party implementation exists (GPTTSD)
3. Windows XP 64-bit does not normally support booting from GPT disks, but unofficial methods exist to boot XP from it.
4. Only if using its service pack 1 or 2
5. In a multi-disk setup, non-UEFI bootloader (boot drive) requires MBR-based partitioning, while a system drive can use GUID partitioning.
6. The GUIDs in this table are written as per RFC 4122, i.e. big-endian byte order, recognizable by the position of the version bits. For example, the GUID for an EFI System partition (C12A7328-F81F-11D2-BA4B-00A0C93EC93B), when serialized in GPT data structures (little-endian), corresponds to the hex sequence 28 73 2A C1 1F F8 D2 11 BA 4B 00 A0 C9 3E C9 3B. The first three blocks are byte-swapped to little-endian, the last is a byte array. See details in TN2166
7. 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.
8. ^ 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.
9. ^ 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.
10. ^ The GUID for /usr on Solaris is used as a generic GUID for ZFS by macOS.
11. ^ NetBSD and MidnightBSD had used the FreeBSD GUIDs before their unique GUIDs were created.
12. The Ceph filesystem uses GUIDs to mark the state of preparation a disk is in.
13. The legacy Fuchsia GUIDs had two oddities: UUIDs were not generated randomly (several runs of bits were common between partitions), and partitions were uniquely identified by type GUID. The standardized scheme uses randomly-generated GUIDs, and slotted partitions (e.g. zircon_{a,b,r}) share the same type and are distinguished by name and unique GUID.

References

1. ^ "FAQ: Drive Partition Limits" (PDF). www.uefi.org. 2010. Retrieved 12 December 2020.
2. ^ "Unified Extensible Firmware Interface (UEFI) Specification" (PDF). www.uefi.org. 29 August 2022. p. 110. Retrieved 23 June 2023.
3. Swinburne, Richard (1 April 2010). "The Facts: 4K Advanced Format Hard Disks". www.bit-tech.net. Retrieved 12 December 2020.
4. ^ Smith, Ryan (18 December 2009). "Western Digital's Advanced Format: The 4K Sector Transition Begins". www.anandtech.com. Archived from the original on 28 December 2020. Retrieved 12 December 2020.
5. "Enterprise Capacity 3.5 HDD Data Sheet" (PDF). Seagate Technology. April 23, 2014. p. 2. Archived (PDF) from the original on 2014-08-12. Retrieved August 10, 2014.
6. "WD Re Datacenter Distribution Specification Sheet" (PDF). Western Digital. January 21, 2016. p. 2. Archived (PDF) from the original on 2015-09-06. Retrieved February 14, 2016.
7. "Advanced format (4K) disk compatibility update (Windows)". November 28, 2012. Archived from the original on 2013-01-11. Retrieved January 3, 2013.
8. "Microsoft support policy for 4K sector hard drives in Windows". Microsoft. Archived from the original on 2011-08-19. Retrieved October 24, 2013.
9. "UEFI specification". UEFI.org.
10. ^ Smith, Roderick (3 July 2012). "Make the most of large drives with GPT and Linux". IBM. Retrieved 14 December 2020.
11. ^ "Technical Note TN2166: Secrets of the GPT". Apple Developer. Apple. 2006-11-06. Retrieved 2014-04-16.
12. 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. Apple. Retrieved 2014-07-13.
13. Leach, P.; Mealling, M.; Salz, R. (July 2005). A Universally Unique IDentifier (UUID) URN Namespace. Internet Engineering Task Force. doi:10.17487/RFC4122. RFC 4122. Retrieved 18 December 2020.{{citation}}: CS1 maint: year (link)
14. Elliott, Rob (4 January 2010). "e09127r3 EDD-4 Hybrid MBR Boot Code Annex" (PDF). www.t13.org. Archived from the original (PDF) on 20 August 2020. Retrieved 16 December 2020.
15. "GPT | Microsoft Docs". 31 August 2016.
16. "CREATE_PARTITION_PARAMETERS (vds.h) - Win32 apps | Microsoft Docs". 9 February 2023.
17. "Disk Format". Chromium.org. Retrieved 2022-02-09.
18. "Ubuntu on MacBook". Community Documentation. Ubuntu.
19. "GNU Parted FAQ".
20. "mklabel". Parted Manual. GNU.
21. "fdisk: add GPT support". kernel.org. 2013-09-27. Retrieved 2013-10-18.
22. Bueso, Davidlohr (2013-09-28). "fdisk updates and GPT support". Retrieved 2013-10-18.
23. "DISK_MAX_PARTS define". Archived from the original on 2020-03-26. Retrieved 2020-03-26.
24. "Myths and Facts About Intel Macs". rEFIt. Source forge.
25. "Partition schemes available in Disk Utility on Mac". Apple Support. Retrieved 2024-11-08.
26. "Significant changes from NetBSD 5.0 to 6.0"..
27. "Significant changes from NetBSD 5.0 to 6.0 (NetBSD/i386)"..
28. "Significant changes from NetBSD 5.0 to 6.0 (NetBSD/amd64)"..
29. "OpenBSD 5.9"..
30. "Booting from a ZFS Root File System". Oracle. Archived from the original on 2011-12-10.
31. "idisk(1M)". Hewlett-Packard.
32. ^ "Windows and GPT FAQ". msdn.microsoft.com. 1 June 2017. Retrieved 14 December 2020.
33. Windows 8 32-bit supports booting from UEFI-based PC (x86-32 only) using GPT-based disks.
34. Windows 8.1 32-bit supports booting from UEFI-based PC (x86-32 only) using GPT-based disks.
35. Windows 10 32-bit supports booting from UEFI-based PC (x86-32 only) using GPT-based disks.
36. Microsoft raises the speed limit with the availability of 64-bit editions of Windows Server 2003 and Windows XP Professional Archived 2010-11-10 at the Wayback Machine
37. http://windowsenthusiasts1.epizy.com/WindowsXPUEFI.html?i=1
38. Windows 8 64-bit supports booting from UEFI-based PC (x86-64 only) using GPT-based disks.
39. Windows 8.1 64-bit supports booting from UEFI-based PC (x86-64 only) using GPT-based disks.
40. Windows 10 64-bit supports booting from UEFI-based PC (x86-64 only) using GPT-based disks.
41. Microsoft's 'Weirdest Release': Windows Server 2022 Quietly Becomes Generally Available
42. "Archived copy" (PDF). Archived from the original (PDF) on 2013-07-28.{{cite web}}: CS1 maint: archived copy as title (link)
43. "F6F: Funtoo Linux and Intel Rapid Start Technology". Blog.adios.tw. 2012-10-30. Retrieved 2014-01-29.
44. GPT fdisk: parttypes.cc, line 198
45. ^ "PARTITION_INFORMATION_GPT - Win32 apps". Microsoft Docs. Retrieved 2021-08-21.
46. Smith, Rod (23 June 2011). "Need for a unique Linux GPT GUID type code (PATCH included)". bug-parted (Mailing list). Retrieved 12 April 2016.
47. Sergei Antonov (2014-07-31). "libfdisk: (gpt) add Microsoft Storage Spaces GUID". util-linux/util-linux.git - The util-linux code repository. Retrieved 2021-08-21.
48. Known issues with Storage Replica
49. ^ The Discoverable Partitions Specification (DPS)
50. ^ systemd-gpt-auto-generator(8)
51. Home Directories
52. The Boot Loader Specification
53. ^ "[dm-crypt] LUKS GPT GUID". Saout.de. Archived from the original on 2014-02-03. Retrieved 2014-01-29.
54. ^ "[dm-crypt] LUKS GPT GUID". Saout.de. Archived from the original on 2014-02-03. Retrieved 2014-01-29.
55. ^ "pyuefi source code".
56. "udisks-2.7.4 source code". GitHub. 10 July 2022.
57. The GNU/Hurd User's Guide: Installing, Internet Install
58. Hurd and GRUB use the same Linux ext2 file system to run and it no longer supports "UFS". file system
59. Hurd uses the same Linux swap file system
60. ^ "FreeBSD System Manager's Manual gpart(8)". Retrieved 2021-08-21.
61. "Add a partition type for nandfs to the apm, bsd, gpt and vtoc8 schemes. · freebsd/freebsd-src@f24a822 · GitHub". GitHub. Retrieved 2021-08-21.
62. "CVS log for src/sys/sys/disklabel_gpt.h". Cvsweb.netbsd.org. Retrieved 2014-01-29.
63. "Disk Format - The Chromium Projects". Chromium.org. Retrieved 2014-01-29.
64. "Disk Format - The Chromium Projects". Chromium.org. Retrieved 2024-01-18.
65. "Constants and IDs". CoreOS. Retrieved 2018-07-26.
66. src/add-ons/kernel/partitioning_systems/gpt/gpt_known_guids.h
67. 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
68. Script to set up a ceph disk: ceph-disk, lines 76-81
69. ceph-disk labels
70. QNX Power-safe filesystem
71. "gpt.ini (github.com/android-ia/device-androidia-mixins)". GitHub.
72. "gpt.ini (github.com/android-ia/device-androidia)". GitHub.
73. "gpt.ini (github.com/android-ia/vendor_intel_baytrail)". GitHub.
74. "gpt-sample.ini (github.com/android-ia/platform_bootable_userfastboot)". GitHub.
75. "gpt_ini2bin.py (android.googlesource.com/platform/hardware/bsp/intel)".
76. "gpt.c (github.com/android-ia/platform_bootable_userfastboot)". GitHub.
77. "gpt_ini2bin.py (github.com/android-ia/vendor_intel_common)". GitHub.
78. "The Boot Loader Specification". freedesktop.org. Retrieved 2017-01-05.
79. "SPDK Block Device User Guide". Retrieved 2021-01-20.
80. "Barebox State Framework". Retrieved 2021-05-21.
81. Villemoes, Rasmus (2020-11-17). "RFC: Partition type GUID for U-Boot environment". U-Boot mailing list (Mailing list). Retrieved 2021-09-28.
82. "U-boot 2021.07 source code: include/part_efi.h". 20 November 2020. Retrieved 2021-09-28.
83. ^ zircon/system/public/zircon/hw/gpt.h
84. "[paver] add support for new partition scheme". Retrieved 2021-10-22.

External links

• Microsoft TechNet: Disk Sectors on GPT Disks (archived page)
• Microsoft Windows Deployment: Converting MBR to GPT without dats loss
• Microsoft TechNet: Troubleshooting Disks and File Systems
• Microsoft TechNet: Using GPT Drives
• Microsoft: FAQs on Using GPT disks in Windows
• Microsoft Technet: How Basic Disks and Volumes Work A bit MS-specific but good figures relate GPT to older MBR format and protective-MBR, shows layouts of complete disks, and how to interpret partition-table hexdumps.
• Apple Developer Connection: Secrets of the GPT
• Make the most of large drives with GPT and Linux
• Convert Windows Vista SP1+ or 7 x86_64 boot from BIOS-MBR mode to UEFI-GPT mode without Reinstall
• 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

v t e Firmware and booting
Processes	Windows 9x NT Linux Android
Booting firmware	Types Proprietary firmware Open-source firmware Custom firmware Interfaces UEFI BIOS Video BIOS Open Firmware ACPI MultiProcessor Specification APM Legacy Plug and Play AlphaBIOS SRM SFI Implementations SeaBIOS Award BIOS American Megatrends AMIBIOS AMI Aptio InsydeH2O Phoenix SecureCore UEFI TianoCore EDK II OpenBIOS Coreboot Libreboot LinuxBoot Kickstart Run-Time Abstraction Services
Hybrid firmware bootloader	Common Firmware Environment Das U-Boot ARCS
Bootloaders	Bootloader unlocking Comparison of bootloaders Implementations Acronis OS Selector Barebox BootManager BootX (Apple) BootX (Linux) GNU GRUB iBoot systemd-boot loadlin NTLDR OpeniBoot RedBoot rEFInd rEFIt SYSLINUX Windows Boot Manager xOSL Yaboot Plop Boot Manager MILO
Partition layouts	GUID Partition Table Master boot record Apple Partition Map
Partitions	EFI system partition BIOS boot partition /boot/
Utilities	Software flashrom fwupd UEFITool Odin Heimdall Hardware Bus Pirate Raspberry Pi ft2232
Network boot	Preboot Execution Environment gPXE iPXE NetBoot Remote Initial Program Load Wake-on-LAN Wake-on-ring
ROM variants	ROM PROM EPROM EEPROM
Related	Boot ROM ROM hacking ROM image Execute in place Devicetree Fastboot Instant-on Power-on self-test EDL mode

• BIOS
• Unified Extensible Firmware Interface
• Booting
• Disk partitions