{{Short description|Computer data storage partitioning standard}} thumb|upright=1.1|The layout of a disk with the GUID Partition Table. In this example, each logical block is 512 bytes in size and each entry has 128 bytes. The corresponding partition entries are assumed to be located in LBA{{nbsp}}2–33. Negative LBA addresses indicate a position from the end of the volume, with −1 being the last addressable block.

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. It is part of the Unified Extensible Firmware Interface (UEFI) standard.

It has several advantages over master boot record (MBR) partition tables, such as support for more than four primary partitions and 64-bit rather than 32-bit logical block addresses (LBA) for blocks on a storage device. The larger LBA size supports larger disks.

Some BIOSes support GPT partition tables as well as MBR partition tables, in order to support larger disks than MBR partition tables can support.

GPT uses universally unique identifiers (UUIDs), which are also known as globally unique identifiers (GUIDs), to identify partitions and partition types.

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 == {{Main|INT 13H|Enhanced BIOS}}

The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, had limitations when it came to modern hardware. The available size for block addresses and related information is limited to 32&nbsp;bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2&nbsp;TiB (2<sup>32</sup>&nbsp;× 512{{nbh}}bytes) or 2.20&nbsp;TB (2.20&nbsp;× 10<sup>12</sup>&nbsp;bytes).<ref name="UEFIFAQ">{{cite web |url=https://www.uefi.org/sites/default/files/resources/UEFI_Drive_Partition_Limits_Fact_Sheet.pdf |title=FAQ: Drive Partition Limits |website=www.uefi.org |date=2010 |access-date=12 December 2020}}</ref>

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.11 specification.<ref name="UEFI2.11">{{cite web |date=21 November 2024 |title=Unified Extensible Firmware Interface (UEFI) Specification Release 2.11 |url=https://uefi.org/sites/default/files/resources/UEFI_Spec_Final_2.11.pdf |access-date=9 January 2025 |website=www.uefi.org}}</ref>{{rp|page=111}} GPT uses 64&nbsp;bits for logical block addresses, allowing a maximum disk size of 2<sup>64</sup> sectors. For disks with 512{{nbh}}byte sectors, the maximum size is 8&nbsp;ZiB (2<sup>64</sup>&nbsp;× 512{{nbh}}bytes) or 9.44&nbsp;ZB (9.44&nbsp;× 10<sup>21</sup>&nbsp;bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64&nbsp;ZiB (2<sup>64</sup>&nbsp;× 4,096{{nbh}}bytes) or 75.6&nbsp;ZB (75.6&nbsp;× 10<sup>21</sup>&nbsp;bytes).

In 2010, hard-disk manufacturers introduced drives with 4,096{{nbh}}byte sectors (Advanced Format).<ref name="bittech">{{cite web |url=https://bit-tech.net/reviews/tech/storage/the-facts-4k-advanced-format-hard-disks/ |title=The Facts: 4K Advanced Format Hard Disks |last=Swinburne |first=Richard |website=www.bit-tech.net |date=1 April 2010 |access-date=12 December 2020}}</ref> For compatibility with legacy hardware and software, those drives include an emulation technology (512e) that presents 512{{nbh}}byte sectors to the entity accessing the hard drive, despite their underlying 4,096{{nbh}}byte physical sectors.<ref name="anandAF">{{cite web |last=Smith |first=Ryan |website=www.anandtech.com |url=https://www.anandtech.com/show/2888 |title=Western Digital's Advanced Format: The 4K Sector Transition Begins |date=18 December 2009 |access-date=12 December 2020 |archive-url=https://web.archive.org/web/20201228122738/https://www.anandtech.com/show/2888 |archive-date=28 December 2020 |url-status=dead }}</ref> 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{{nbh}}byte write operation.<ref name="anandAF"/> Since April 2014, enterprise-class drives without emulation technology (4K native) have been available on the market.<ref>{{cite web |url = http://www.seagate.com/www-content/product-content/enterprise-hdd-fam/enterprise-capacity-3-5-hdd/constellation-es-4/en-us/docs/enterprise-capacity-3-5-hdd-ds1791-4-1404us.pdf#page=2 |title = Enterprise Capacity 3.5 HDD Data Sheet |date = April 23, 2014 |accessdate = August 10, 2014 |publisher = Seagate Technology |format = PDF |page = 2 |archive-url = https://web.archive.org/web/20140812220618/http://www.seagate.com/www-content/product-content/enterprise-hdd-fam/enterprise-capacity-3-5-hdd/constellation-es-4/en-us/docs/enterprise-capacity-3-5-hdd-ds1791-4-1404us.pdf#page=2 |archive-date = 2014-08-12 |url-status = live }}</ref><ref>{{cite web |url = http://www.wdc.com/wdproducts/library/SpecSheet/ENG/2879-800066.pdf#page=2 |title = WD Re Datacenter Distribution Specification Sheet |date = January 21, 2016 |accessdate = February 14, 2016 |publisher = Western Digital |format = PDF |page = 2 |archive-url = https://web.archive.org/web/20150906040839/http://www.wdc.com/wdproducts/library/SpecSheet/ENG/2879-800066.pdf#page=2 |archive-date = 2015-09-06 |url-status = live }}</ref>

Readiness of the support for 4&nbsp;KB logical sectors within operating systems differs among their types, vendors and versions.<ref name="hh848035">{{cite web|title=Advanced format (4K) disk compatibility update (Windows)|url=http://msdn.microsoft.com/en-us/library/windows/desktop/hh848035(v=vs.85).aspx|date=November 28, 2012|accessdate=January 3, 2013|archive-url=https://web.archive.org/web/20130111233631/http://msdn.microsoft.com/en-us/library/windows/desktop/hh848035(v=vs.85).aspx|archive-date=2013-01-11|url-status=live}}</ref> For example, Microsoft Windows supports 4K&nbsp;native drives since Windows&nbsp;8 and Windows Server 2012 (both released in 2012) in UEFI.<ref>{{cite web |url = https://learn.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/support-policy-4k-sector-hard-drives |title = Microsoft support policy for 4K sector hard drives in Windows |date = 26 December 2023 |accessdate = January 10, 2025 |publisher = Microsoft }}</ref>

== Features == [[File:GNU GRUB components.svg|thumb|upright=1.5|MBR vs. GPT partitioning and boot sequence visualized (systems using BIOS firmware). See GRUB2.]] 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. The GPT header has a pointer to the partition table (''Partition Entry Array''), which is typically at LBA 2. Each entry in the partition table has the same size, which is 128 or 256 or 512, etc., bytes; typically this size is 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 sector disk, at least 4 sectors are used for the Partition Entry Array, and the first usable block is at LBA 6 or higher. In addition to the primary GPT header and Partition Entry Array, stored at the beginning of the disk, there is a backup GPT header and Partition Entry Array, stored at the end of the disk. The backup GPT header must be at the last block on the disk (LBA -1) and the backup Partition Entry Array is placed between the end of the last partition and the last block.{{r|UEFI2.11|at=pp. 115-120, §5.3}}

==MBR variants==

=== {{Anchor|PROTECTIVE-MBR}}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''.<ref name="IBMLargeDrivesGPT">{{cite web |title=Make the most of large drives with GPT and Linux |first=Roderick |last=Smith |publisher=IBM |url=http://www.ibm.com/developerworks/library/l-gpt/ |date=3 July 2012 |access-date=14 December 2020}}</ref>

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.<ref name="IBMLargeDrivesGPT" /> Furthermore, GPT-aware OSes may check the protective MBR and if the enclosed partition type is not of type {{mono|EEh}} or if there are multiple partitions defined on the target device, the OS may refuse to manipulate the partition table.<ref name="tn2166">{{cite web|url=https://developer.apple.com/library/mac/technotes/tn2166/_index.html#//apple_ref/doc/uid/DTS10003927-CH1-SUBSECTION11 |title=Technical Note TN2166: Secrets of the GPT |website=Apple Developer |publisher=Apple |date=2006-11-06 |access-date=2014-04-16}}</ref>

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&nbsp;TiB, assuming a disk with 512 bytes per sector (see 512e). It would result in 16&nbsp;TiB with 4&nbsp;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&nbsp;TiB limit could cause compatibility problems.<ref name="IBMLargeDrivesGPT" /><!-- Still, what remains unclear here is, if tools should use 2 TiB as a hard cut-off value even on disks with larger sectors, or if the actual maximum grows in relation with the sector size. Assume a protective MBR on a disk with 4Kn sectors and a storage size of more than 2 TiB, but less then 16 TiB, should the entries in the PT default to "all entries set to maximum" or "all entries set according to a fixed size of 2 TiB)? "All entries maximum" is definitely the saver approach, as it leaves no bits free, which could be interpreted as "there's still some free space" by tools working in quantities of sectors rather than bytes. However, it may also cause disk tools, which are not limited to 32-bit arithmetics, to display a volume size eight times as large as real. Is this defined in the spec? -->

=== {{anchor|HYBRIDMBR}}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.<ref name="IBMLargeDrivesGPT" />

== Partition table header (LBA 1) ==

{| class="wikitable" |+ GPT header format ! Offset !! Length !! Contents |- |align="right"| 0 (0x00) ||align="right"| 8 bytes || Signature ("EFI PART", {{mono|45h 46h 49h 20h 50h 41h 52h 54h}} or {{mono|0x5452415020494645ULL}}{{Efn|Adding <code>ULL</code> suffix to an integer constant makes it of type <code>unsigned long long int</code>.}} on little-endian machines) |- |align="right"| 8 (0x08) ||align="right"| 4 bytes || Revision number of header - 1.0 ({{mono|00h 00h 01h 00h}}) for UEFI 2.10 |- |align="right"| 12 (0x0C) ||align="right"| 4 bytes || Header size in little endian (in bytes, usually {{mono|5Ch 00h 00h 00h}} or 92 bytes) |- |align="right"| 16 (0x10) ||align="right"| 4 bytes || CRC-32 of header (offset +0 to +0x5B) in little endian, with this field zeroed during calculation |- |align="right"| 20 (0x14) ||align="right"| 4 bytes || Reserved; must be zero |- |align="right"| 24 (0x18) ||align="right"| 8 bytes || Current LBA (location of this header copy) |- |align="right"| 32 (0x20) ||align="right"| 8 bytes || Backup LBA (location of the other header copy) |- |align="right"| 40 (0x28) ||align="right"| 8 bytes || First usable LBA for partitions (primary partition table last LBA + 1) |- |align="right"| 48 (0x30) ||align="right"| 8 bytes || Last usable LBA for partitions (secondary partition table first LBA − 1) |- |align="right"| 56 (0x38) ||align="right"| 16 bytes || Disk GUID in little endian{{Efn|name="GUID-Endian"|GUIDs are structured in little endian format,<ref name="RFC4122">{{cite IETF |date= July 2005|title= A Universally Unique IDentifier (UUID) URN Namespace |rfc= 4122 |section= 4.1.2 |access-date=13 February 2025 |last1= Leach |first1= Paul J. |last2= Salz |first2= Rich |last3= Mealling |first3= Michael H. |publisher=Internet Engineering Task Force}}</ref> but appear as mixed endian, due to a byte array being used to store the last eight bytes.<ref>{{cite web |date= 28 September 2022|title= Why does COM express GUIDs in a mix of big-endian and little-endian? Why can't it just pick a side and stick with it? |url=https://devblogs.microsoft.com/oldnewthing/20220928-00/?p=107221 |access-date=13 February 2025 }}</ref>}} |- |align="right"| 72 (0x48) ||align="right"| 8 bytes || Starting LBA of array of partition entries (usually 2 for compatibility) |- |align="right"| 80 (0x50) ||align="right"| 4 bytes || Number of partition entries in array |- |align="right"| 84 (0x54) ||align="right"| 4 bytes || Size of a single partition entry (usually {{mono|80h}} or 128) |- |align="right"| 88 (0x58) ||align="right"| 4 bytes || CRC-32 of partition entries array in little endian |- |align="right"| 92 (0x5C) ||align="center"| * || 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 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).{{r|UEFI2.11|p=117-118}}

{{Clear}}

== Partition entries (LBA 2–33) ==

{| class="wikitable" |+ GUID partition entry format ! Offset !! Length !! Contents |- |align=right| 0 (0x00) ||align=right| 16 bytes || Partition type GUID (little endian{{Efn|name="GUID-Endian"}}) |- |align=right| 16 (0x10) ||align=right| 16 bytes || Unique partition GUID (little endian{{Efn|name="GUID-Endian"}}) |- |align=right| 32 (0x20) ||align=right| 8 bytes || First LBA (little endian) |- |align=right| 40 (0x28) ||align=right| 8 bytes || Last LBA (inclusive, usually odd) |- |align=right| 48 (0x30) ||align=right| 8 bytes || Attribute flags (e.g. bit 60 denotes read-only) |- |align=right| 56 (0x38) ||align=right| 72 bytes || Partition name (36 UTF-16LE code units) |}

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.<ref>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 {{cite web|url=https://developer.apple.com/library/archive/technotes/tn2166/_index.html#//apple_ref/doc/uid/DTS10003927-CH1-SECTION2 |title=Technical Note TN2166 Secrets of the GPT |publisher=Apple |website=Developer.Apple.com |access-date=2025-01-10}}</ref> The starting location of the array on disk, and the size of each entry, are given in the GPT header. The first 16&nbsp;bytes of each entry designate the partition type's globally unique identifier (GUID). For example, the GUID for an EFI system partition is {{mono|C12A7328-F81F-11D2-BA4B-00A0C93EC93B}}. The second 16&nbsp;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 <nowiki>RFC 4122</nowiki>, no central registry is needed to ensure the uniqueness of the GUID partition type designators.<ref name="RFC 4122">{{cite IETF |title=A Universally Unique IDentifier (UUID) URN Namespace |rfc=4122 |first1=P. |last1=Leach |first2=M. |last2=Mealling |first3=R. |last3=Salz |publisher=Internet Engineering Task Force |date=July 2005 |access-date=18 December 2020}}</ref><ref name="UEFI2.11" />{{rp|1970|q=All EFI GUIDs (Globally Unique Identifiers) have the format described in RFC 4122 and comply with the referenced algorithms for generating GUIDs.}}

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

{| class="wikitable" |+ Partition attributes ! Bit !! Content |- |align=right| 0 || Platform required (required by the computer to function properly, OEM partition for example, disk partitioning utilities must preserve the partition as is) |- |align=right| 1 || EFI firmware should ignore the content of the partition and not try to read from it |- |align=right| 2 || Legacy BIOS bootable (equivalent to ''active flag'' (typically bit 7 set) at offset {{mono|+0h}} in partition entries of the MBR partition table)<ref>{{cite web |last=Elliott |first=Rob |title=e09127r3 EDD-4 Hybrid MBR Boot Code Annex |url=http://t13.org/documents/UploadedDocuments/docs2010/e09127r3-EDD-4_Hybrid_MBR_boot_code_annex.pdf |website=www.t13.org |date=4 January 2010 |access-date=16 December 2020 |archive-url=https://web.archive.org/web/20200820000316/https://t13.org/documents/UploadedDocuments/docs2010/e09127r3-EDD-4_Hybrid_MBR_boot_code_annex.pdf |archive-date=20 August 2020 |url-status=dead}}</ref> |- |align=right| 3–47 || Reserved for future use |- |align=right| 48–63 || Defined and used by the individual partition type |}

Microsoft defines the type-specific attributes for basic data partition as:<ref>{{cite web |url=https://technet.microsoft.com/en-us/library/cc753455.aspx#Anchor_1 |title = GPT {{!}} Microsoft Docs| date=31 August 2016 }}</ref><ref>{{cite web |url=https://msdn.microsoft.com/en-us/library/aa381635.aspx |title = CREATE_PARTITION_PARAMETERS (vds.h) - Win32 apps {{!}} Microsoft Docs| date=9 February 2023 }}</ref>

{| class="wikitable" |+ Basic data partition attributes ! Bit !! Content |- |align=right| 60 || Read-only |- |align=right| 61 || Shadow copy (of another partition) |- |align=right| 62 || Hidden |- |align=right| 63 || No drive letter (i.e. do not automount) |}

Google defines the type-specific attributes for ChromeOS kernel as:<ref>{{cite web |title=Disk Format |url=https://www.chromium.org/chromium-os/developer-library/reference/device/disk-format/#selecting-the-kernel |access-date=2022-02-09 |website=Chromium.org}}</ref>

{| class="wikitable" |+ ChromeOS kernel partition attributes ! Bit !! Content |- |align=right| 56 || Successful boot flag |- |align=right| 55–52 || Tries remaining |- |align=right| 51–48 || Priority (15: highest, 1: lowest, 0: not bootable) |}

=={{anchor|OSSUPPORT}}Operating-system support== {{See also|Unified Extensible Firmware Interface#DISKDEVCOMPAT|l1=UEFI: Disk device compatibility}}

===UNIX and Unix-like systems=== {| class="wikitable" |+ Details of GPT support on 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<br />Fedora 8+ and Ubuntu 8.04+<ref>{{cite web |publisher=Ubuntu | work = Community Documentation |url= https://help.ubuntu.com/community/MacBook |title=Ubuntu on MacBook}}</ref> | IA-32, x86-64, ARM | {{Yes}} | {{Yes}} | Tools such as gdisk, GNU Parted,<ref>{{cite web | url = https://www.gnu.org/software/parted/faq.shtml#features | title = GNU Parted FAQ}}</ref><ref>{{cite web | url = https://www.gnu.org/software/parted/manual/html_node/mklabel.html | title = mklabel |publisher = GNU | work = Parted Manual}}</ref> util-linux v2.23+ fdisk,<ref>{{cite web | url = https://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=766d5156c43b784700d28d1c1141008b2bf35ed7 | title = fdisk: add GPT support | date = 2013-09-27 | access-date = 2013-10-18 | publisher = kernel.org}}</ref><ref>{{cite web | url = http://blog.stgolabs.net/2012/09/fdisk-updates-and-gpt-support.html | title = fdisk updates and GPT support | date = 2013-09-28 | access-date = 2013-10-18 | first = Davidlohr | last = Bueso}}</ref> SYSLINUX, GRUB 0.96 + patches and GRUB 2 have been GPT-enabled. Limited to 256 partitions per disk.<ref>{{cite web | url = https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/include/linux/genhd.h | title = DISK_MAX_PARTS define | access-date = 2020-03-26 | archive-date = 2020-03-26 | archive-url = https://web.archive.org/web/20200326214544/https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/include/linux/genhd.h | url-status = dead }}</ref> |- | macOS | Since 10.4.0 (some features since 10.4.6)<ref>{{cite web|url= https://refit.sourceforge.net/myths/ |publisher= Source forge | work = rEFIt |title= Myths and Facts About Intel Macs}}</ref> | IA-32, x86-64, PowerPC, Apple silicon | {{Yes}} | {{Yes}} | Only Intel and Apple silicon Macs can boot from GPT.<ref>{{Cite web |title=Partition schemes available in Disk Utility on Mac |url=https://support.apple.com/en-gb/guide/disk-utility/dsku1c614201/mac |access-date=2024-11-08 |website=Apple Support |language=en}}</ref> |- | MidnightBSD | Since 0.4-CURRENT | IA-32, x86-64 | {{Yes}} | {{Yes}} | In a hybrid configuration, both GPT and MBR partition identifiers may be used. |- | NetBSD | Since 6.0<ref>{{cite web|title= Significant changes from NetBSD 5.0 to 6.0|url= http://www.netbsd.org/changes/changes-6.0.html}}.</ref> | IA-32,<ref>{{cite web|title= Significant changes from NetBSD 5.0 to 6.0 (NetBSD/i386) |url= http://www.netbsd.org/changes/changes-6.0.html#port-i386}}.</ref> x86-64,<ref>{{cite web |title=Significant changes from NetBSD 5.0 to 6.0 (NetBSD/amd64) |url=http://www.netbsd.org/changes/changes-6.0.html#port-amd64}}.</ref> ARM | {{Yes}} | {{Yes}} | |- | OpenBSD | Since 5.9 | IA-32, x86-64, ARM | {{Yes}} | {{Yes}} | <ref>{{cite web|title=OpenBSD 5.9|url=https://www.openbsd.org/59.html}}.</ref> |- | Solaris | Since Solaris 10 | IA-32, x86-64, SPARC | {{Yes}} | {{Yes}} | <ref>{{cite web | publisher=Oracle | url=http://docs.oracle.com/cd/E19963-01/html/821-1448/ggpco.html | archive-date=2011-12-10 | archive-url=https://web.archive.org/web/20111210093231/http://docs.oracle.com/cd/E19963-01/html/821-1448/ggpco.html | title=Booting from a ZFS Root File System}}</ref> |- | HP-UX | Since HP-UX 11.20 | IA-64 | {{Yes}} | {{Yes}} | <ref>{{cite web |url= https://nixdoc.net/man-pages/HP-UX/man1/idisk.1m.html |publisher= Hewlett-Packard |title= idisk(1M) }}</ref> |}

===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.<ref name="GPTFAQ" />

{| class="wikitable" |+ Details of GPT support on 32-bit editions of Microsoft Windows<ref name="GPTFAQ" /> ! OS version ! Release date ! Platform ! Read or write support ! Boot support ! Note |- | Windows 9x | 1995-08-24 | IA-32 | {{No}}{{Efn|Third party implementation exists (GPTTSD)}} | {{No}} | |- | Windows XP | 2001-10-25 | IA-32 | {{No}} | {{No}} | |- | 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}} | {{Partial|Requires UEFI}}<ref>[https://technet.microsoft.com/en-us/library/hh824898.aspx Windows 8 32-bit supports booting from UEFI-based PC (x86-32 only) using GPT-based disks.]</ref> | MBR takes precedence in hybrid configuration. |- | Windows 8.1 | 2013-08-27 | IA-32 | {{Yes}} | {{Partial|Requires UEFI}}<ref>[https://technet.microsoft.com/en-us/library/hh824898.aspx Windows 8.1 32-bit supports booting from UEFI-based PC (x86-32 only) using GPT-based disks.]</ref> | MBR takes precedence in hybrid configuration. |- | Windows 10 | 2015-07-29 | IA-32, ARM32 | {{Yes}} | {{Partial|Requires UEFI}}<ref>[https://technet.microsoft.com/en-us/library/hh824898.aspx Windows 10 32-bit supports booting from UEFI-based PC (x86-32 only) using GPT-based disks.]</ref> | MBR takes precedence in hybrid configuration. |}

===Windows: 64-bit versions=== Limited to 128 partitions per disk.<ref name="GPTFAQ">{{Cite web|url=https://msdn.microsoft.com/en-us/library/windows/hardware/dn640535(v=vs.85).aspx |title=Windows and GPT FAQ |website=msdn.microsoft.com |date=1 June 2017 |access-date=14 December 2020}}</ref> {| class="wikitable" |+ Details of GPT support on 64-bit editions of Microsoft Windows<ref name="GPTFAQ" /> ! OS version ! Release date ! Platform ! Read and write support ! style="width: 8em;" | Boot support ! style="width: 21em;" | Note |- | Windows XP 64-Bit Edition for Itanium systems, Version 2002 | 2001-10-25 | IA-64 | {{Yes}} | {{Yes}} | MBR takes precedence in hybrid configuration. |- | Windows XP 64-Bit Edition, Version 2003 | 2003-03-28 | IA-64 | {{Yes}} | {{Yes}} | MBR takes precedence in hybrid configuration. |- | Windows XP Professional x64 Edition<br />Windows Server 2003 | 2005-04-25<ref>[http://www.microsoft.com/presspass/press/2005/apr05/04-25Winx64LaunchPR.mspx Microsoft raises the speed limit with the availability of 64-bit editions of Windows Server 2003 and Windows XP Professional] {{webarchive|url=https://web.archive.org/web/20101110033856/http://www.microsoft.com/presspass/press/2005/apr05/04-25Winx64LaunchPR.mspx |date=2010-11-10 }}</ref> | x64 | {{Yes}} | {{No}}{{efn|Windows XP 64-bit does not normally support booting from GPT disks, but unofficial methods exist to boot XP from it.<ref>{{cite web |url=http://windowsenthusiasts1.epizy.com/WindowsXPUEFI.html |title=Windows XP on UEFI mode via the command prompt. |website=Windows Enthusiasts}}</ref>}} | MBR takes precedence in hybrid configuration. |- | Windows Server 2003 | 2005-04-25 | IA-64 | {{Yes}} | {{Yes}} | MBR takes precedence in hybrid configuration. |- | Windows Vista | 2006-07-22 | x64 | {{Yes}} | {{Partial|Requires UEFI}}{{Efn|Only if using its service pack 1 or 2}} | MBR takes precedence in hybrid configuration. |- | Windows Server 2008 | 2008-02-27 | x64 | {{Yes}} | {{Partial|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}} | {{Partial|Requires UEFI}}{{Efn|In a multi-disk setup, non-UEFI bootloader (boot drive) requires MBR-based partitioning, while a system drive can use GUID partitioning.}} | MBR takes precedence in hybrid configuration. |- | Windows Server 2008 R2 | 2009-10-22 | IA-64 | {{Yes}} | {{Yes}} | MBR takes precedence in hybrid configuration. |- | Windows 8<br />Windows Server 2012 | 2012-08-01 | x64 | {{Yes}} | {{Partial|Requires UEFI}}<ref>[https://technet.microsoft.com/en-us/library/hh824898.aspx Windows 8 64-bit supports booting from UEFI-based PC (x86-64 only) using GPT-based disks.]</ref> | MBR takes precedence in hybrid configuration. |- | Windows 8.1 | 2013-08-27 | x64 | {{Yes}} | {{Partial|Requires UEFI}}<ref>[https://technet.microsoft.com/en-us/library/hh824898.aspx Windows 8.1 64-bit supports booting from UEFI-based PC (x86-64 only) using GPT-based disks.]</ref> | MBR takes precedence in hybrid configuration. |- | Windows 10 | 2015-07-29 | x64, ARM64 | {{Yes}} | {{Partial|Requires UEFI}}<ref>[https://technet.microsoft.com/en-us/library/hh824898.aspx Windows 10 64-bit supports booting from UEFI-based PC (x86-64 only) using GPT-based disks.]</ref> | MBR takes precedence in hybrid configuration. |- | Windows Server 2016 | 2016-10-12 | x64 | {{Yes}} | {{Partial|Requires UEFI}} | MBR takes precedence in hybrid configuration. |- | Windows Server 2019 | 2018-10-02 | x64 | {{Yes}} | {{Partial|Requires UEFI}} | MBR takes precedence in hybrid configuration. |- | Windows Server 2022 | 2021-08-18<ref>{{cite web |url=https://rcpmag.com/articles/2021/08/20/windows-server-2022-ga.aspx |title=Microsoft's 'Weirdest Release': Windows Server 2022 Quietly Becomes Generally Available |first=Kurt |last=Mackie |date=21 August 2021 |website=Redmond Channel Partner}}</ref> | x64 | {{Yes}} | {{Partial|Requires UEFI}} | MBR takes precedence in hybrid configuration. |- | Windows 11 | 2021-10-05 | x64, ARM64 | {{Yes}} | {{Yes}} | UEFI is a system requirement for Windows 11. |- | Windows Server 2025 | 2024-11-01 | x64 | {{Yes}} | {{Yes}} | UEFI is a system requirement for Windows Server 2025. |}

== Partition type GUIDs == "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. {| class="wikitable sortable mw-collapsible mw-collapsed" |- ! Operating system ! colspan="2" | Partition type ! style="width: 23em;" | Globally unique identifier (GUID){{Efn|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 (<code>C12A7328-F81F-11D2-BA4B-00A0C93EC93B</code>), when serialized in GPT data structures (little-endian), corresponds to the hex sequence <code>28 73 2A C1 1F F8 D2 11 BA 4B 00 A0 C9 3E C9 3B</code>. The first three blocks are byte-swapped to little-endian, the last is a byte array. See details in TN2166<ref name="tn2166" />}} |- style="background:#f0f0f0;" | rowspan="7" | OS-independent | colspan="2" | Unused entry | {{mono|00000000-0000-0000-0000-000000000000}} |- | colspan="2" style="background:#f0f0f0;"|MBR partition scheme | style="background:#f0f0f0;"|{{mono|024DEE41-33E7-11D3-9D69-0008C781F39F}} |- style="background:#f0f0f0;" | colspan="2" | EFI System partition | {{mono|C12A7328-F81F-11D2-BA4B-00A0C93EC93B}} |- | colspan="2" style="background:#f0f0f0;"|BIOS boot partition{{Efn|The formation of this GUID does not follow the GUID definition; it is formed by using the ASCII codes for the string "{{mono|Hah!IdontNeedEFI}}". Such formation of "GUID" value breaks down the guaranteed uniqueness of GUID.}} | style="background:#f0f0f0;"|{{mono|21686148-6449-6E6F-744E-656564454649}} |- style="background:#f0f0f0;" | colspan="2" | Intel Fast Flash (iFFS) partition (for Intel Rapid Start technology)<!-- a BIOS option provided by various PC manufacturers such as Asus, Gigabyte, NEC etc. - corresponds with 0x84 as MBR partition --><ref name="Gigabyte_2012_RS">{{cite web |url=ftp://download.gigabyte.ru/manual/mb_manual_intel-ui_e.pdf |archive-url=https://web.archive.org/web/20130728154909/http://download.gigabyte.ru/manual/mb_manual_intel-ui_e.pdf |archive-date=2013-07-28 |url-status=dead |title=Intel Rapid Start Technology}}</ref><ref>{{cite web|url=http://blog.adios.tw/2012/10/funtoo-linux-and-intel-rapid-start.html |title=F6F: Funtoo Linux and Intel Rapid Start Technology |publisher=Blog.adios.tw |date=2012-10-30 |access-date=2014-01-29 |url-status=dead |archive-url=https://web.archive.org/web/20240803092928/https://blog.adios.tw/2012/10/funtoo-linux-and-intel-rapid-start.html |archive-date=2024-08-03}}</ref> | {{mono|D3BFE2DE-3DAF-11DF-BA40-E3A556D89593}} |- | colspan="2" style="background:#f0f0f0;"|Sony boot partition{{Efn|name="manufacturerbootpartition"|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.<ref>{{cite web |url=https://sourceforge.net/p/gptfdisk/code/ci/master/tree/parttypes.cc |title=GPT fdisk: parttypes.cc}}</ref>}} | style="background:#f0f0f0;"|{{mono|F4019732-066E-4E12-8273-346C5641494F}} |- | colspan="2" style="background:#f0f0f0;"|Lenovo boot partition{{Efn|name="manufacturerbootpartition"}} | style="background:#f0f0f0;"|{{mono|BFBFAFE7-A34F-448A-9A5B-6213EB736C22}} |- <!-- Windows --> |rowspan="10"| Windows | colspan="2" | Microsoft Reserved Partition (MSR)<ref name="microsoft-partition-information-gpt">{{cite web |url=https://learn.microsoft.com/en-us/windows/win32/api/winioctl/ns-winioctl-partition_information_gpt |title=PARTITION_INFORMATION_GPT (winioctl.h) |website=Microsoft Learn |date=September 2022 |access-date=2025-01-10}}</ref> | {{mono|E3C9E316-0B5C-4DB8-817D-F92DF00215AE}} |- | colspan="2" | Basic data partition<ref name="microsoft-partition-information-gpt"/>{{Efn|name="linwin"|Previously, Linux used the same GUID for the data partitions as Windows (Basic data partition: {{mono|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: {{mono|0FC63DAF-8483-4772-8E79-3D69D8477DE4}}) was defined jointly by GPT fdisk and GNU Parted developers.<ref name="RodSmithMLpost">{{cite mailing list|last=Smith|first=Rod|title=Need for a unique Linux GPT GUID type code (PATCH included)|mailing-list=bug-parted|date=23 June 2011|url=http://lists.gnu.org/archive/html/bug-parted/2011-06/msg00026.html |access-date=12 April 2016}}</ref> It is identified as type code {{mono|0x8300}} in GPT fdisk.}} | {{mono|EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}} |- | colspan="2" | Logical Disk Manager (LDM) metadata partition<ref name="microsoft-partition-information-gpt"/> | {{mono|5808C8AA-7E8F-42E0-85D2-E1E90434CFB3}} |- | colspan="2" | Logical Disk Manager data partition<ref name="microsoft-partition-information-gpt"/> | {{mono|AF9B60A0-1431-4F62-BC68-3311714A69AD}} |- | colspan="2" | Windows Recovery Environment<ref name="microsoft-partition-information-gpt"/> | {{mono|DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}} |- | colspan="2" | IBM General Parallel File System (GPFS) partition | {{mono|37AFFC90-EF7D-4E96-91C3-2D7AE055B174}} |- | colspan="2" | Storage Spaces partition<ref>{{cite web |url=https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=210d4595dea9ff998a04ba07b3d07694abd32d24 |title=libfdisk: (gpt) add Microsoft Storage Spaces GUID |author=Sergei Antonov |date=2014-07-31 |website=util-linux/util-linux.git - The util-linux code repository. |access-date=2021-08-21}}</ref> | {{mono|E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D}} |- | colspan="2" | Storage Replica partition<ref name="microsoft-storage-replica-partition">{{cite web |url=https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/storage-replica-known-issues#small-unknown-volume-listed-in-diskmgmt-for-each-replicated-volume |title=Known issues with Storage Replica |date=31 May 2023 |at=Small unknown volume listed in DISKMGMT for each replicated volume}}</ref> | {{mono|558D43C5-A1AC-43C0-AAC8-D1472B2923D1}} |- | colspan="2" | S2D Cache<ref name="microsoft-s2d-cache">As appears in %SystemRoot%\System32\WindowsPowerShell\v1.0\Modules\Storage\Storage.types.ps1xml</ref> | {{mono|EEFF8352-DD2A-44DB-AE83-BEE1CF7481DC}} |- | colspan="2" | S2D Cache Metadata<ref name="microsoft-s2d-cache"></ref> | {{mono|03AAA829-EBFC-4E7E-AAC9-C4D76C63B24B}} |- style="background:#f0f0f0;" | rowspan="2"| HP-UX | colspan="2" | Data partition<!-- (UFS ?)--> | {{mono|75894C1E-3AEB-11D3-B7C1-7B03A0000000}} |- style="background:#f0f0f0;" | colspan="2" | Service partition | {{mono|E2A1E728-32E3-11D6-A682-7B03A0000000}} |- <!-- Linux --> | rowspan="137" | Linux<ref name="DiscoverablePartitionsSpec">{{cite web |url=https://uapi-group.org/specifications/specs/discoverable_partitions_specification/ |title=The Discoverable Partitions Specification (DPS)}}</ref><ref name="man-systemd-gpt-auto-generator">[{{cite web |url=https://www.freedesktop.org/software/systemd/man/latest/systemd-gpt-auto-generator.html |title=systemd-gpt-auto-generator(8)}}</ref><ref name="HomeDirectories">{{cite web |url=https://systemd.io/HOME_DIRECTORY/ |title=Home Directories}}</ref><ref name="TheBootLoaderSpecification">{{cite web |url=https://uapi-group.org/specifications/specs/boot_loader_specification/ |title=The Boot Loader Specification}}</ref> | colspan="2" | Linux filesystem data{{Efn|name="linwin"}} | {{mono|0FC63DAF-8483-4772-8E79-3D69D8477DE4}} |- | colspan="2" | RAID partition<ref name="freebsdgpt">{{cite web |title=FreeBSD source code |url=https://cgit.freebsd.org/src/commit/sys/sys/gpt.h?h=stable/7&id=fb584e48411205c7f3ac442145d4db96c3128dad |access-date=28 August 2025}}</ref> | {{mono|A19D880F-05FC-4D3B-A006-743F0F84911E}} |- | rowspan="21" | Root partition | Alpha<ref name="DiscoverablePartitionsSpec" /> |{{Mono|6523F8AE-3EB1-4E2A-A05A-18B695AE656F}} |- | ARC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|D27F46ED-2919-4CB8-BD25-9531F3C16534}} |- | ARM 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|69DAD710-2CE4-4E3C-B16C-21A1D49ABED3}} |- | AArch64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|B921B045-1DF0-41C3-AF44-4C6F280D3FAE}} |- | IA-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|993D8D3D-F80E-4225-855A-9DAF8ED7EA97}} |- | LoongArch 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|77055800-792C-4F94-B39A-98C91B762BB6}} |- | mips: 32‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|E9434544-6E2C-47CC-BAE2-12D6DEAFB44C}} |- | mips64: 64‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|D113AF76-80EF-41B4-BDB6-0CFF4D3D4A25}} |- | mipsel: 32‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|37C58C8A-D913-4156-A25F-48B1B64E07F0}} |- | mips64el: 64‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|700BDA43-7A34-4507-B179-EEB93D7A7CA3}} |- | PA-RISC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|1AACDB3B-5444-4138-BD9E-E5C2239B2346}} |- | 32‐bit PowerPC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|1DE3F1EF-FA98-47B5-8DCD-4A860A654D78}} |- | 64‐bit PowerPC big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|912ADE1D-A839-4913-8964-A10EEE08FBD2}} |- | 64‐bit PowerPC little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C31C45E6-3F39-412E-80FB-4809C4980599}} |- | RISC-V 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|60D5A7FE-8E7D-435C-B714-3DD8162144E1}} |- | RISC-V 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|72EC70A6-CF74-40E6-BD49-4BDA08E8F224}} |- | s390<ref name="DiscoverablePartitionsSpec" /> |{{Mono|08A7ACEA-624C-4A20-91E8-6E0FA67D23F9}} |- | s390x<ref name="DiscoverablePartitionsSpec" /> |{{Mono|5EEAD9A9-FE09-4A1E-A1D7-520D00531306}} |- | TILE-Gx<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C50CDD70-3862-4CC3-90E1-809A8C93EE2C}} |- | x86<ref name="DiscoverablePartitionsSpec" /> |{{Mono|44479540-F297-41B2-9AF7-D131D5F0458A}} |- | x86-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709}} |- | rowspan="21" | {{mono|/usr}} partition | Alpha<ref name="DiscoverablePartitionsSpec" /> |{{Mono|E18CF08C-33EC-4C0D-8246-C6C6FB3DA024}} |- | ARC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|7978A683-6316-4922-BBEE-38BFF5A2FECC}} |- | ARM 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|7D0359A3-02B3-4F0A-865C-654403E70625}} |- | AArch64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|B0E01050-EE5F-4390-949A-9101B17104E9}} |- | IA-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|4301D2A6-4E3B-4B2A-BB94-9E0B2C4225EA}} |- | LoongArch 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|E611C702-575C-4CBE-9A46-434FA0BF7E3F}} |- | mips: 32‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|773B2ABC-2A99-4398-8BF5-03BAAC40D02B}} |- | mips64: 64‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|57E13958-7331-4365-8E6E-35EEEE17C61B}} |- | mipsel: 32‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|0F4868E9-9952-4706-979F-3ED3A473E947}} |- | mips64el: 64‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C97C1F32-BA06-40B4-9F22-236061B08AA8}} |- | PA-RISC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|DC4A4480-6917-4262-A4EC-DB9384949F25}} |- | 32‐bit PowerPC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|7D14FEC5-CC71-415D-9D6C-06BF0B3C3EAF}} |- | 64‐bit PowerPC big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|2C9739E2-F068-46B3-9FD0-01C5A9AFBCCA}} |- | 64‐bit PowerPC little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|15BB03AF-77E7-4D4A-B12B-C0D084F7491C}} |- | RISC-V 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|B933FB22-5C3F-4F91-AF90-E2BB0FA50702}} |- | RISC-V 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|BEAEC34B-8442-439B-A40B-984381ED097D}} |- | s390<ref name="DiscoverablePartitionsSpec" /> |{{Mono|CD0F869B-D0FB-4CA0-B141-9EA87CC78D66}} |- | s390x<ref name="DiscoverablePartitionsSpec" /> |{{Mono|8A4F5770-50AA-4ED3-874A-99B710DB6FEA}} |- | TILE-Gx<ref name="DiscoverablePartitionsSpec" /> |{{Mono|55497029-C7C1-44CC-AA39-815ED1558630}} |- | x86<ref name="DiscoverablePartitionsSpec" /> |{{Mono|75250D76-8CC6-458E-BD66-BD47CC81A812}} |- | x86-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|8484680C-9521-48C6-9C11-B0720656F69E}} |- | rowspan="21" | Root verity partition for dm-verity | Alpha<ref name="DiscoverablePartitionsSpec" /> |{{Mono|FC56D9E9-E6E5-4C06-BE32-E74407CE09A5}} |- | ARC <ref name="DiscoverablePartitionsSpec" /> |{{Mono|24B2D975-0F97-4521-AFA1-CD531E421B8D}} |- | ARM 32‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|7386CDF2-203C-47A9-A498-F2ECCE45A2D6}} |- | AArch64 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|DF3300CE-D69F-4C92-978C-9BFB0F38D820}} |- | IA-64 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|86ED10D5-B607-45BB-8957-D350F23D0571}} |- | LoongArch 64‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|F3393B22-E9AF-4613-A948-9D3BFBD0C535}} |- | mips: 32‐bit MIPS big‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|7A430799-F711-4C7E-8E5B-1D685BD48607}} |- | mips64: 64‐bit MIPS big‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|579536F8-6A33-4055-A95A-DF2D5E2C42A8}} |- | mipsel: 32‐bit MIPS little‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|D7D150D2-2A04-4A33-8F12-16651205FF7B}} |- | mips64el: 64‐bit MIPS little‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|16B417F8-3E06-4F57-8DD2-9B5232F41AA6}} |- | PA-RISC <ref name="DiscoverablePartitionsSpec" /> |{{Mono|D212A430-FBC5-49F9-A983-A7FEEF2B8D0E}} |- | 64‐bit PowerPC little‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|906BD944-4589-4AAE-A4E4-DD983917446A}} |- | 64‐bit PowerPC big‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|9225A9A3-3C19-4D89-B4F6-EEFF88F17631}} |- | 32‐bit PowerPC <ref name="DiscoverablePartitionsSpec" /> |{{Mono|98CFE649-1588-46DC-B2F0-ADD147424925}} |- | RISC-V 32‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|AE0253BE-1167-4007-AC68-43926C14C5DE}} |- | RISC-V 64‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|B6ED5582-440B-4209-B8DA-5FF7C419EA3D}} |- | s390 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|7AC63B47-B25C-463B-8DF8-B4A94E6C90E1}} |- | s390x <ref name="DiscoverablePartitionsSpec" /> |{{Mono|B325BFBE-C7BE-4AB8-8357-139E652D2F6B}} |- | TILE-Gx <ref name="DiscoverablePartitionsSpec" /> |{{Mono|966061EC-28E4-4B2E-B4A5-1F0A825A1D84}} |- | x86-64 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|2C7357ED-EBD2-46D9-AEC1-23D437EC2BF5}} |- | x86 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|D13C5D3B-B5D1-422A-B29F-9454FDC89D76}} |- | rowspan="21" | {{mono|/usr}} verity partition for dm-verity | Alpha <ref name="DiscoverablePartitionsSpec" /> |{{Mono|8CCE0D25-C0D0-4A44-BD87-46331BF1DF67}} |- | ARC <ref name="DiscoverablePartitionsSpec" /> |{{Mono|FCA0598C-D880-4591-8C16-4EDA05C7347C}} |- | ARM 32‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|C215D751-7BCD-4649-BE90-6627490A4C05}} |- | AArch64 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|6E11A4E7-FBCA-4DED-B9E9-E1A512BB664E}} |- | IA-64 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|6A491E03-3BE7-4545-8E38-83320E0EA880}} |- | LoongArch 64‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|F46B2C26-59AE-48F0-9106-C50ED47F673D}} |- | mips: 32‐bit MIPS big‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|6E5A1BC8-D223-49B7-BCA8-37A5FCCEB996}} |- | mips64: 64‐bit MIPS big‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|81CF9D90-7458-4DF4-8DCF-C8A3A404F09B}} |- | mipsel: 32‐bit MIPS little‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|46B98D8D-B55C-4E8F-AAB3-37FCA7F80752}} |- | mips64el: 64‐bit MIPS little‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|3C3D61FE-B5F3-414D-BB71-8739A694A4EF}} |- | PA-RISC <ref name="DiscoverablePartitionsSpec" /> |{{Mono|5843D618-EC37-48D7-9F12-CEA8E08768B2}} |- | 64‐bit PowerPC little‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|EE2B9983-21E8-4153-86D9-B6901A54D1CE}} |- | 64‐bit PowerPC big‐endian <ref name="DiscoverablePartitionsSpec" /> |{{Mono|BDB528A5-A259-475F-A87D-DA53FA736A07}} |- | 32‐bit PowerPC <ref name="DiscoverablePartitionsSpec" /> |{{Mono|DF765D00-270E-49E5-BC75-F47BB2118B09}} |- | RISC-V 32‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|CB1EE4E3-8CD0-4136-A0A4-AA61A32E8730}} |- | RISC-V 64‐bit <ref name="DiscoverablePartitionsSpec" /> |{{Mono|8F1056BE-9B05-47C4-81D6-BE53128E5B54}} |- | s390 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|B663C618-E7BC-4D6D-90AA-11B756BB1797}} |- | s390x <ref name="DiscoverablePartitionsSpec" /> |{{Mono|31741CC4-1A2A-4111-A581-E00B447D2D06}} |- | TILE-Gx <ref name="DiscoverablePartitionsSpec" /> |{{Mono|2FB4BF56-07FA-42DA-8132-6B139F2026AE}} |- | x86-64 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|77FF5F63-E7B6-4633-ACF4-1565B864C0E6}} |- | x86 <ref name="DiscoverablePartitionsSpec" /> |{{Mono|8F461B0D-14EE-4E81-9AA9-049B6FB97ABD}} |- | rowspan="21" | Root verity signature partition for dm-verity | Alpha<ref name="DiscoverablePartitionsSpec" /> |{{Mono|D46495B7-A053-414F-80F7-700C99921EF8}} |- | ARC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|143A70BA-CBD3-4F06-919F-6C05683A78BC}} |- | ARM 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|42B0455F-EB11-491D-98D3-56145BA9D037}} |- | AArch64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|6DB69DE6-29F4-4758-A7A5-962190F00CE3}} |- | IA-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|E98B36EE-32BA-4882-9B12-0CE14655F46A}} |- | LoongArch 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|5AFB67EB-ECC8-4F85-AE8E-AC1E7C50E7D0}} |- | mips: 32‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|BBA210A2-9C5D-45EE-9E87-FF2CCBD002D0}} |- | mips64: 64‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|43CE94D4-0F3D-4999-8250-B9DEAFD98E6E}} |- | mipsel: 32‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C919CC1F-4456-4EFF-918C-F75E94525CA5}} |- | mips64el: 64‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|904E58EF-5C65-4A31-9C57-6AF5FC7C5DE7}} |- | PA-RISC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|15DE6170-65D3-431C-916E-B0DCD8393F25}} |- | 64‐bit PowerPC little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|D4A236E7-E873-4C07-BF1D-BF6CF7F1C3C6}} |- | 64‐bit PowerPC big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|F5E2C20C-45B2-4FFA-BCE9-2A60737E1AAF}} |- | 32‐bit PowerPC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|1B31B5AA-ADD9-463A-B2ED-BD467FC857E7}} |- | RISC-V 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|3A112A75-8729-4380-B4CF-764D79934448}} |- | RISC-V 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|EFE0F087-EA8D-4469-821A-4C2A96A8386A}} |- | s390<ref name="DiscoverablePartitionsSpec" /> |{{Mono|3482388E-4254-435A-A241-766A065F9960}} |- | s390x<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C80187A5-73A3-491A-901A-017C3FA953E9}} |- | TILE-Gx<ref name="DiscoverablePartitionsSpec" /> |{{Mono|B3671439-97B0-4A53-90F7-2D5A8F3AD47B}} |- | x86-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|41092B05-9FC8-4523-994F-2DEF0408B176}} |- | x86<ref name="DiscoverablePartitionsSpec" /> |{{Mono|5996FC05-109C-48DE-808B-23FA0830B676}} |- | rowspan="21" | {{mono|/usr}} verity signature partition for dm-verity | Alpha<ref name="DiscoverablePartitionsSpec" /> |{{Mono|5C6E1C76-076A-457A-A0FE-F3B4CD21CE6E}} |- | ARC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|94F9A9A1-9971-427A-A400-50CB297F0F35}} |- | ARM 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|D7FF812F-37D1-4902-A810-D76BA57B975A}} |- | AArch64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C23CE4FF-44BD-4B00-B2D4-B41B3419E02A}} |- | IA-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|8DE58BC2-2A43-460D-B14E-A76E4A17B47F}} |- | LoongArch 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|B024F315-D330-444C-8461-44BBDE524E99}} |- | mips: 32‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|97AE158D-F216-497B-8057-F7F905770F54}} |- | mips64: 64‐bit MIPS big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|05816CE2-DD40-4AC6-A61D-37D32DC1BA7D}} |- | mipsel: 32‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|3E23CA0B-A4BC-4B4E-8087-5AB6A26AA8A9}} |- | mips64el: 64‐bit MIPS little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|F2C2C7EE-ADCC-4351-B5C6-EE9816B66E16}} |- | PA-RISC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|450DD7D1-3224-45EC-9CF2-A43A346D71EE}} |- | 64‐bit PowerPC little‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C8BFBD1E-268E-4521-8BBA-BF314C399557}} |- | 64‐bit PowerPC big‐endian<ref name="DiscoverablePartitionsSpec" /> |{{Mono|0B888863-D7F8-4D9E-9766-239FCE4D58AF}} |- | 32‐bit PowerPC<ref name="DiscoverablePartitionsSpec" /> |{{Mono|7007891D-D371-4A80-86A4-5CB875B9302E}} |- | RISC-V 32‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|C3836A13-3137-45BA-B583-B16C50FE5EB4}} |- | RISC-V 64‐bit<ref name="DiscoverablePartitionsSpec" /> |{{Mono|D2F9000A-7A18-453F-B5CD-4D32F77A7B32}} |- | s390<ref name="DiscoverablePartitionsSpec" /> |{{Mono|17440E4F-A8D0-467F-A46E-3912AE6EF2C5}} |- | s390x<ref name="DiscoverablePartitionsSpec" /> |{{Mono|3F324816-667B-46AE-86EE-9B0C0C6C11B4}} |- | TILE-Gx<ref name="DiscoverablePartitionsSpec" /> |{{Mono|4EDE75E2-6CCC-4CC8-B9C7-70334B087510}} |- | x86-64<ref name="DiscoverablePartitionsSpec" /> |{{Mono|E7BB33FB-06CF-4E81-8273-E543B413E2E2}} |- | x86<ref name="DiscoverablePartitionsSpec" /> |{{Mono|974A71C0-DE41-43C3-BE5D-5C5CCD1AD2C0}} |- | colspan="2" | {{mono|/boot}}, as an Extended Boot Loader (XBOOTLDR) partition<ref name="DiscoverablePartitionsSpec" /><ref name="man-systemd-gpt-auto-generator" /> | {{mono|BC13C2FF-59E6-4262-A352-B275FD6F7172}} |- | colspan="2" | Swap partition<ref name="DiscoverablePartitionsSpec" /><ref name="man-systemd-gpt-auto-generator" /> | {{mono|0657FD6D-A4AB-43C4-84E5-0933C84B4F4F}} |- | colspan="2" | Logical Volume Manager (LVM) partition<ref name="freebsdgpt" /> | {{mono|E6D6D379-F507-44C2-A23C-238F2A3DF928}} |- | colspan="2" | {{mono|/home}} partition<ref name="DiscoverablePartitionsSpec" /><ref name="man-systemd-gpt-auto-generator" /> | {{mono|933AC7E1-2EB4-4F13-B844-0E14E2AEF915}} |- | colspan="2" | {{mono|/srv}} (server data) partition<ref name="DiscoverablePartitionsSpec" /><ref name="man-systemd-gpt-auto-generator" /> | {{mono|3B8F8425-20E0-4F3B-907F-1A25A76F98E8}} |- | colspan="2" | Per‐user home partition<ref name="DiscoverablePartitionsSpec" /> | {{mono|773F91EF-66D4-49B5-BD83-D683BF40AD16}} |- | colspan="2" | Plain dm-crypt partition<ref name="saout1">{{cite web |url=http://www.saout.de/pipermail/dm-crypt/2014-January/003855.html |title=[dm-crypt&#93; LUKS GPT GUID |publisher=Saout.de |access-date=2014-01-29 |archive-date=2014-02-03 |archive-url=https://web.archive.org/web/20140203045532/http://www.saout.de/pipermail/dm-crypt/2014-January/003855.html |url-status=dead }}</ref><ref name="saout2">{{cite web |url=http://www.saout.de/pipermail/dm-crypt/2014-January/003859.html |title=[dm-crypt&#93; LUKS GPT GUID |publisher=Saout.de |access-date=2014-01-29 |archive-date=2014-02-03 |archive-url=https://web.archive.org/web/20140203045703/http://www.saout.de/pipermail/dm-crypt/2014-January/003859.html |url-status=dead }}</ref><ref name="pyuefi">{{cite web|url=https://bitbucket.org/mmabey/pyuefi/src/master/pyuefi/partition_types/uefi.py |title=pyuefi source code}}</ref> | {{mono|7FFEC5C9-2D00-49B7-8941-3EA10A5586B7}} |- | colspan="2" | LUKS partition<ref name="saout1" /><ref name="saout2" /><ref name="pyuefi" /><ref name="usdisks">{{cite web|url=https://github.com/storaged-project/udisks/blob/udisks-2.7.4/src/udiskslinuxblock.c#L2363 |title=udisks-2.7.4 source code|website=GitHub|date=10 July 2022 }}</ref> | {{mono|CA7D7CCB-63ED-4C53-861C-1742536059CC}} |- | colspan="2" | Reserved | {{mono|8DA63339-0007-60C0-C436-083AC8230908}} |- <!-- GNU --> | rowspan="2" | GNU/Hurd<ref>{{cite web |url=https://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html#Internet-Install |title=The GNU/Hurd User's Guide |at=Installing, Internet Install}}</ref> | colspan="2" | Linux filesystem data{{efn|Hurd and GRUB use the same Linux ext2 file system to run and Hurd no longer supports the UFS file system<ref>{{Cite web|url=https://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=84cf9c0f312637b670cc87224ff7e7c4da659e36|title=Remove UFS support|work=hurd/hurd.git - Hurd}}</ref>}} | {{mono|0FC63DAF-8483-4772-8E79-3D69D8477DE4}} |- | colspan="2" | Linux Swap partition{{efn|Hurd uses the same Linux swap file system}} | {{mono|0657FD6D-A4AB-43C4-84E5-0933C84B4F4F}} |- <!-- FreeBSD --> style="background:#f0f0f0;" | rowspan="7"| FreeBSD | colspan="2" | Boot partition<ref name="freebsd">{{Cite web |url=https://www.freebsd.org/cgi/man.cgi?query=gpart&apropos=0&sektion=8&manpath=FreeBSD+13.0-RELEASE&arch=default&format=html |title=FreeBSD System Manager's Manual gpart(8) |accessdate=2021-08-21}}</ref> | {{mono|83BD6B9D-7F41-11DC-BE0B-001560B84F0F}} |- style="background:#f0f0f0;" | colspan="2" | BSD disklabel partition<ref name="freebsd"/> | {{mono|516E7CB4-6ECF-11D6-8FF8-00022D09712B}} |- style="background:#f0f0f0;" | colspan="2" | Swap partition<ref name="freebsd"/> | {{mono|516E7CB5-6ECF-11D6-8FF8-00022D09712B}} |- style="background:#f0f0f0;" | colspan="2" | Unix File System (UFS) partition<ref name="freebsd"/> | {{mono|516E7CB6-6ECF-11D6-8FF8-00022D09712B}} |- style="background:#f0f0f0;" | colspan="2" | Vinum volume manager partition<ref name="freebsd"/> | {{mono|516E7CB8-6ECF-11D6-8FF8-00022D09712B}} |- style="background:#f0f0f0;" | colspan="2" | ZFS partition<ref name="freebsd"/> | {{mono|516E7CBA-6ECF-11D6-8FF8-00022D09712B}} |- style="background:#f0f0f0;" | colspan="2" | nandfs partition<ref>{{Cite web |url=https://github.com/freebsd/freebsd-src/commit/f24a8224b2046c7b7e4525ccb94b8e1f39a600d4#diff-d173c53f561bf0a9536ac882e798fca502622ded0a8e4ac7a8beb15205896327 |title=Add a partition type for nandfs to the apm, bsd, gpt and vtoc8 schemes. · freebsd/freebsd-src@f24a822 · GitHub |website=GitHub |accessdate=2021-08-21}}</ref> | {{mono|74BA7DD9-A689-11E1-BD04-00E081286ACF}} |- <!-- Macintosh --> | rowspan="12" | macOS<br />Darwin | colspan="2" | Hierarchical File System Plus (HFS+) partition | {{mono|48465300-0000-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple APFS container<br />APFS FileVault volume container | {{mono|7C3457EF-0000-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple UFS container | {{mono|55465300-0000-11AA-AA11-00306543ECAC}} |- | colspan="2" | ZFS{{Efn|name="solmac"|The GUID for <code>/usr</code> on Solaris is used as a generic GUID for ZFS by macOS.}} | {{mono|6A898CC3-1DD2-11B2-99A6-080020736631}} |- | colspan="2" | Apple RAID partition | {{mono|52414944-0000-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple RAID partition, offline | {{mono|52414944-5F4F-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple Boot partition (Recovery HD) | {{mono|426F6F74-0000-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple Label | {{mono|4C616265-6C00-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple TV Recovery partition | {{mono|5265636F-7665-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple Core Storage Container<br />HFS+ FileVault volume container | {{mono|53746F72-6167-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple APFS Preboot partition | {{mono|69646961-6700-11AA-AA11-00306543ECAC}} |- | colspan="2" | Apple APFS Recovery partition | {{mono|52637672-7900-11AA-AA11-00306543ECAC}} |- <!-- Solaris / OpenSolaris --> | style="background:#f0f0f0;" rowspan="13"| Solaris<br />illumos | colspan="2" style="background:#f0f0f0;"| Boot partition | style="background:#f0f0f0;"| {{mono|6A82CB45-1DD2-11B2-99A6-080020736631}} |- style="background:#f0f0f0;" | colspan="2" | Root partition | {{mono|6A85CF4D-1DD2-11B2-99A6-080020736631}} |- style="background:#f0f0f0;" | colspan="2" | Swap partition | {{mono|6A87C46F-1DD2-11B2-99A6-080020736631}} |- style="background:#f0f0f0;" | colspan="2" | Backup partition | {{mono|6A8B642B-1DD2-11B2-99A6-080020736631}} |- | colspan="2" style="background:#f0f0f0;"|{{mono|/usr}} partition{{Efn|name="solmac"}} | style="background:#f0f0f0;"|{{mono|6A898CC3-1DD2-11B2-99A6-080020736631}} |- style="background:#f0f0f0;" | colspan="2" | {{mono|/var}} partition | {{mono|6A8EF2E9-1DD2-11B2-99A6-080020736631}} |- style="background:#f0f0f0;" | colspan="2" | {{mono|/home}} partition | {{mono|6A90BA39-1DD2-11B2-99A6-080020736631}} |- style="background:#f0f0f0;" | colspan="2" | Alternate sector | {{mono|6A9283A5-1DD2-11B2-99A6-080020736631}} |- style="background:#f0f0f0;" | colspan="2" rowspan="5"| Reserved partition | {{mono|6A945A3B-1DD2-11B2-99A6-080020736631}} |- | style="background:#f0f0f0;"|{{mono|6A9630D1-1DD2-11B2-99A6-080020736631}} |- | style="background:#f0f0f0;"|{{mono|6A980767-1DD2-11B2-99A6-080020736631}} |- | style="background:#f0f0f0;"|{{mono|6A96237F-1DD2-11B2-99A6-080020736631}} |- | style="background:#f0f0f0;"|{{mono|6A8D2AC7-1DD2-11B2-99A6-080020736631}} |- <!-- NetBSD --> |rowspan="6"| NetBSD<ref>{{cite web|url=http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/sys/disklabel_gpt.h?only_with_tag=MAIN |title=CVS log for src/sys/sys/disklabel_gpt.h |publisher=Cvsweb.netbsd.org |access-date=2014-01-29}}</ref>{{Efn|name="netbsd"|NetBSD and MidnightBSD had used the FreeBSD GUIDs before their unique GUIDs were created.}} | colspan="2" | Swap partition | {{mono|49F48D32-B10E-11DC-B99B-0019D1879648}} |- | colspan="2" | FFS partition | {{mono|49F48D5A-B10E-11DC-B99B-0019D1879648}} |- | colspan="2" | LFS partition | {{mono|49F48D82-B10E-11DC-B99B-0019D1879648}} |- | colspan="2" | RAID partition | {{mono|49F48DAA-B10E-11DC-B99B-0019D1879648}} |- | colspan="2" | Concatenated partition | {{mono|2DB519C4-B10F-11DC-B99B-0019D1879648}} |- | colspan="2" | Encrypted partition | {{mono|2DB519EC-B10F-11DC-B99B-0019D1879648}} |- <!-- Chrome OS --> style="background:#f0f0f0;" | rowspan="6"|ChromeOS<ref name="disk-format">{{cite web|url=https://www.chromium.org/chromium-os/developer-library/reference/device/disk-format/#partition-types |title=Disk Format - The Chromium Projects |publisher=Chromium.org |access-date=2025-01-10}}</ref> | colspan="2" | ChromeOS kernel | {{mono|FE3A2A5D-4F32-41A7-B725-ACCC3285A309}} |- style="background:#f0f0f0;" | colspan="2" | ChromeOS rootfs | {{mono|3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC}} |- style="background:#f0f0f0;" | colspan="2" | ChromeOS firmware | {{mono|CAB6E88E-ABF3-4102-A07A-D4BB9BE3C1D3}} |- style="background:#f0f0f0;" | colspan="2" | ChromeOS future use | {{mono|2E0A753D-9E48-43B0-8337-B15192CB1B5E}} |- style="background:#f0f0f0;" | colspan="2" | ChromeOS miniOS | {{mono|09845860-705F-4BB5-B16C-8A8A099CAF52}} |- style="background:#f0f0f0;" | colspan="2" | ChromeOS hibernate | {{mono|3F0F8318-F146-4E6B-8222-C28C8F02E0D5}}<ref>{{cite web |url=https://android.googlesource.com/platform/external/gptfdisk/+/refs/heads/main/parttypes.cc |title=parttypes.cc - platform/external/gptfdisk - Git at Google |access-date=2025-01-10}}</ref> |- <!-- Container Linux by CoreOS --> style="background:#f0f0f0;" | rowspan="4"|Container Linux by CoreOS<ref>{{cite web|url=https://coreos.com/os/docs/latest/constants-and-ids.html#gpt-partition-types |title=Constants and IDs |publisher=CoreOS |access-date=2018-07-26}}</ref> | colspan="2" | /usr partition (coreos-usr) | {{mono|5DFBF5F4-2848-4BAC-AA5E-0D9A20B745A6}} |- style="background:#f0f0f0;" | colspan="2" | Resizable rootfs (coreos-resize) | {{mono|3884DD41-8582-4404-B9A8-E9B84F2DF50E}} |- style="background:#f0f0f0;" | colspan="2" | OEM customizations (coreos-reserved) | {{mono|C95DC21A-DF0E-4340-8D7B-26CBFA9A03E0}} |- style="background:#f0f0f0;" | colspan="2" | Root filesystem on RAID (coreos-root-raid) | {{mono|BE9067B9-EA49-4F15-B4F6-F36F8C9E1818}} |- <!-- Haiku --> | Haiku<ref>{{cite web |url=https://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/partitioning_systems/gpt/gpt_known_guids.h |title=src/add-ons/kernel/partitioning_systems/gpt/gpt_known_guids.h}}</ref> | colspan="2" | Haiku BFS | {{mono|42465331-3BA3-10F1-802A-4861696B7521}} |- <!-- MidnightBSD --> | style="background:#f0f0f0;" rowspan="6"|MidnightBSD<ref>{{cite web |url=https://github.com/MidnightBSD/src/commit/42f68de006872da142849aa2c54069c0453e9ef2 |title=define MIDNIGHTBSD GPT types for future use! - MidnightBSD/src@42f68de|website=GitHub }}</ref>{{Efn|name="netbsd"}} | colspan="2" style="background:#f0f0f0;"|Boot partition | style="background:#f0f0f0;"|{{mono|85D5E45E-237C-11E1-B4B3-E89A8F7FC3A7}} |- style="background:#f0f0f0;" | colspan="2" | Data partition | {{mono|85D5E45A-237C-11E1-B4B3-E89A8F7FC3A7}} |- style="background:#f0f0f0;" | colspan="2" | Swap partition | {{mono|85D5E45B-237C-11E1-B4B3-E89A8F7FC3A7}} |- style="background:#f0f0f0;" | colspan="2" | Unix File System (UFS) partition | {{mono|0394EF8B-237E-11E1-B4B3-E89A8F7FC3A7}} |- style="background:#f0f0f0;" | colspan="2" | Vinum volume manager partition | {{mono|85D5E45C-237C-11E1-B4B3-E89A8F7FC3A7}} |- style="background:#f0f0f0;" | colspan="2" | ZFS partition | {{mono|85D5E45D-237C-11E1-B4B3-E89A8F7FC3A7}} |- <!-- Ceph --> |rowspan="24"| Ceph{{Efn|name="cephuuidlist"|The Ceph filesystem uses GUIDs to mark the state of preparation a disk is in.<ref>{{cite web |url=https://github.com/ceph/ceph/blob/9bcc42a3e6b08521694b5c0228b2c6ed7b3d312e/src/ceph-disk#L76-L81 |title=Script to set up a ceph disk: ceph-disk, lines 76-81|website=GitHub }}</ref><ref>{{cite web |url=https://github.com/ceph/ceph/blob/c19250ce3cb30a5a0409e3ebd4142dad6191642e/src/ceph-volume/ceph_volume/util/constants.py#L18 |title=ceph-disk labels|website=GitHub }}</ref>}} | colspan="2" | Journal | {{mono|45B0969E-9B03-4F30-B4C6-B4B80CEFF106}} |- | colspan="2" | dm-crypt journal | {{mono|45B0969E-9B03-4F30-B4C6-5EC00CEFF106}} |- | colspan="2" | OSD | {{mono|4FBD7E29-9D25-41B8-AFD0-062C0CEFF05D}} |- | colspan="2" | dm-crypt OSD | {{mono|4FBD7E29-9D25-41B8-AFD0-5EC00CEFF05D}} |- | colspan="2" | Disk in creation | {{mono|89C57F98-2FE5-4DC0-89C1-F3AD0CEFF2BE}} |- | colspan="2" | dm-crypt disk in creation | {{mono|89C57F98-2FE5-4DC0-89C1-5EC00CEFF2BE}} |- | colspan="2" | Block | {{mono|CAFECAFE-9B03-4F30-B4C6-B4B80CEFF106}} |- | colspan="2" | Block DB | {{mono|30CD0809-C2B2-499C-8879-2D6B78529876}} |- | colspan="2" | Block write-ahead log | {{mono|5CE17FCE-4087-4169-B7FF-056CC58473F9}} |- | colspan="2" | Lockbox for dm-crypt keys | {{mono|FB3AABF9-D25F-47CC-BF5E-721D1816496B}} |- | colspan="2" | Multipath OSD | {{mono|4FBD7E29-8AE0-4982-BF9D-5A8D867AF560}} |- | colspan="2" | Multipath journal | {{mono|45B0969E-8AE0-4982-BF9D-5A8D867AF560}} |- | colspan="2" | Multipath block | {{mono|CAFECAFE-8AE0-4982-BF9D-5A8D867AF560}} |- | colspan="2" | Multipath block | {{mono|7F4A666A-16F3-47A2-8445-152EF4D03F6C}} |- | colspan="2" | Multipath block DB | {{mono|EC6D6385-E346-45DC-BE91-DA2A7C8B3261}} |- | colspan="2" | Multipath block write-ahead log | {{mono|01B41E1B-002A-453C-9F17-88793989FF8F}} |- | colspan="2" | dm-crypt block | {{mono|CAFECAFE-9B03-4F30-B4C6-5EC00CEFF106}} |- | colspan="2" | dm-crypt block DB | {{mono|93B0052D-02D9-4D8A-A43B-33A3EE4DFBC3}} |- | colspan="2" | dm-crypt block write-ahead log | {{mono|306E8683-4FE2-4330-B7C0-00A917C16966}} |- | colspan="2" | dm-crypt LUKS journal | {{mono|45B0969E-9B03-4F30-B4C6-35865CEFF106}} |- | colspan="2" | dm-crypt LUKS block | {{mono|CAFECAFE-9B03-4F30-B4C6-35865CEFF106}} |- | colspan="2" | dm-crypt LUKS block DB | {{mono|166418DA-C469-4022-ADF4-B30AFD37F176}} |- | colspan="2" | dm-crypt LUKS block write-ahead log | {{mono|86A32090-3647-40B9-BBBD-38D8C573AA86}} |- | colspan="2" | dm-crypt LUKS OSD | {{mono|4FBD7E29-9D25-41B8-AFD0-35865CEFF05D}} |- | style="background:#f0f0f0;"| OpenBSD | style="background:#f0f0f0;" colspan="2" | Data partition | style="background:#f0f0f0;"| {{mono|824CC7A0-36A8-11E3-890A-952519AD3F61}} |- | QNX | colspan="2" | Power-safe (QNX6) file system<ref>{{cite web |url=https://www.qnx.com/developers/docs/8.0/com.qnx.doc.neutrino.utilities/topic/d/diskimage_config_file.html#diskimage_config_file__GUID_partition_names |title=diskimage configuration file |at=Supported short type names for GUID partitions}}</ref> | {{mono|CEF5A9AD-73BC-4601-89F3-CDEEEEE321A1}} |- | style="background:#f0f0f0;" | Plan 9 | style="background:#f0f0f0;" colspan="2" | Plan 9 partition | style="background:#f0f0f0;" | {{mono|C91818F9-8025-47AF-89D2-F030D7000C2C}} |- | rowspan="3"| VMware ESX | colspan="2" | vmkcore (coredump partition) | {{mono|9D275380-40AD-11DB-BF97-000C2911D1B8}} |- | colspan="2" | VMFS filesystem partition | {{mono|AA31E02A-400F-11DB-9590-000C2911D1B8}} |- | colspan="2" | VMware Reserved | {{mono|9198EFFC-31C0-11DB-8F78-000C2911D1B8}} |- <!-- Android-IA --> | style="background:#f0f0f0;" rowspan="16" | Android-IA<ref>{{Cite web|url=https://github.com/android-ia/device-androidia-mixins/blob/master/groups/boot-arch/android_ia/gpt.ini|title=gpt.ini (github.com/android-ia/device-androidia-mixins)|website=GitHub}}</ref><ref>{{Cite web|url=https://github.com/android-ia/device-androidia/blob/master/androidia_64/gpt.ini|title=gpt.ini (github.com/android-ia/device-androidia)|website=GitHub}}</ref><ref>{{Cite web|url=https://github.com/android-ia/vendor_intel_baytrail/blob/master/minnow_max/gpt.ini|title=gpt.ini (github.com/android-ia/vendor_intel_baytrail)|website=GitHub}}</ref><ref>{{Cite web|url=https://github.com/android-ia/platform_bootable_userfastboot/blob/master/gpt-sample.ini|title=gpt-sample.ini (github.com/android-ia/platform_bootable_userfastboot)|website=GitHub}}</ref> | colspan="2" style="background:#f0f0f0;" | Bootloader | style="background:#f0f0f0;" | {{mono|2568845D-2332-4675-BC39-8FA5A4748D15}} |- style="background:#f0f0f0;" | colspan="2" | Bootloader2 | {{mono|114EAFFE-1552-4022-B26E-9B053604CF84}} |- style="background:#f0f0f0;" | colspan="2" | Boot | {{mono|49A4D17F-93A3-45C1-A0DE-F50B2EBE2599}} |- style="background:#f0f0f0;" | colspan="2" | Recovery | {{mono|4177C722-9E92-4AAB-8644-43502BFD5506}} |- style="background:#f0f0f0;" | colspan="2" | Misc | {{mono|EF32A33B-A409-486C-9141-9FFB711F6266}} |- style="background:#f0f0f0;" | colspan="2" | Metadata | {{mono|20AC26BE-20B7-11E3-84C5-6CFDB94711E9}} |- style="background:#f0f0f0;" | colspan="2" | System | {{mono|38F428E6-D326-425D-9140-6E0EA133647C}} |- style="background:#f0f0f0;" | colspan="2" | Cache | {{mono|A893EF21-E428-470A-9E55-0668FD91A2D9}} |- style="background:#f0f0f0;" | colspan="2" | Data | {{mono|DC76DDA9-5AC1-491C-AF42-A82591580C0D}} |- style="background:#f0f0f0;" | colspan="2" | Persistent | {{mono|EBC597D0-2053-4B15-8B64-E0AAC75F4DB1}} |- style="background:#f0f0f0;" | colspan="2" | Vendor | {{mono|C5A0AEEC-13EA-11E5-A1B1-001E67CA0C3C}} |- style="background:#f0f0f0;" | colspan="2" | Config | {{mono|BD59408B-4514-490D-BF12-9878D963F378}} |- style="background:#f0f0f0;" | colspan="2" | Factory | {{mono|8F68CC74-C5E5-48DA-BE91-A0C8C15E9C80}} |- style="background:#f0f0f0;" | colspan="2" | Factory (alt)<ref>{{Cite web|url=https://android.googlesource.com/platform/hardware/bsp/intel/+/e2ef91a5723be4c50e0bd93f82c329d262c2f366/soc/common/tools/gpt_ini2bin.py|title=gpt_ini2bin.py (android.googlesource.com/platform/hardware/bsp/intel)}}</ref> | {{mono|9FDAA6EF-4B3F-40D2-BA8D-BFF16BFB887B}} |- style="background:#f0f0f0;" | colspan="2" | Fastboot / Tertiary<ref>{{Cite web|url=https://github.com/android-ia/platform_bootable_userfastboot/blob/master/libgpt/gpt.c|title=gpt.c (github.com/android-ia/platform_bootable_userfastboot)|website=GitHub}}</ref><ref>{{Cite web|url=https://github.com/android-ia/vendor_intel_common/blob/master/gpt_bin/gpt_ini2bin.py|title=gpt_ini2bin.py (github.com/android-ia/vendor_intel_common)|website=GitHub}}</ref> | {{mono|767941D0-2085-11E3-AD3B-6CFDB94711E9}} |- style="background:#f0f0f0;" | colspan="2" | OEM | {{mono|AC6D7924-EB71-4DF8-B48D-E267B27148FF}} |- <!-- Android-ARM --> | rowspan="2" | Android 6.0+ ARM | colspan="2" | Android Meta | {{mono|19A710A2-B3CA-11E4-B026-10604B889DCF}} |- | colspan="2" | Android EXT | {{mono|193D1EA4-B3CA-11E4-B075-10604B889DCF}} |- <!-- Onie --> | rowspan="2" | Open Network Install Environment (ONIE) | colspan="2" | Boot | {{mono|7412F7D5-A156-4B13-81DC-867174929325}} |- | colspan="2" | Config | {{mono|D4E6E2CD-4469-46F3-B5CB-1BFF57AFC149}} |- <!-- PowerPC --> | style="background:#f0f0f0;" | PowerPC | style="background:#f0f0f0;" colspan="2" | PReP boot | style="background:#f0f0f0;" | {{mono|9E1A2D38-C612-4316-AA26-8B49521E5A8B}} |- <!-- Freedesktop--> | freedesktop.org OSes (Linux, etc.) | colspan="2" | Shared boot loader configuration<ref>{{cite web |url=https://freedesktop.org/wiki/Specifications/BootLoaderSpec/ |title=The Boot Loader Specification |website=freedesktop.org |access-date=2017-01-05 }}</ref> | {{mono|BC13C2FF-59E6-4262-A352-B275FD6F7172}} |- | style="background:#f0f0f0;" rowspan="2" | Atari TOS | style="background:#f0f0f0;" colspan="2" | Basic data partition (GEM, BGM, F32) | style="background:#f0f0f0;" | {{mono|734E5AFE-F61A-11E6-BC64-92361F002671}} |- | style="background:#f0f0f0;" colspan="2" | Raw data partition (RAW), XHDI | style="background:#f0f0f0;" | {{mono|35540011-B055-499F-842D-C69AECA357B7}} |- | VeraCrypt | colspan="2" | Encrypted data partition | {{mono|8C8F8EFF-AC95-4770-814A-21994F2DBC8F}} |- | style="background:#f0f0f0;" | OS/2 | style="background:#f0f0f0;" colspan="2" | ArcaOS Type 1 | style="background:#f0f0f0;" | {{mono|90B6FF38-B98F-4358-A21F-48F35B4A8AD3}} |- | Storage Performance Development Kit (SPDK) | colspan="2" | SPDK block device<ref>{{cite web |url=https://spdk.io/doc/bdev.html#bdev_ug_gpt |title=SPDK Block Device User Guide |access-date=2021-01-20 }}</ref> | {{mono|7C5222BD-8F5D-4087-9C00-BF9843C7B58C}} |- | style="background:#f0f0f0;" | barebox bootloader | style="background:#f0f0f0;" colspan="2" | barebox-state<ref>{{cite web |url=https://barebox.org/doc/latest/user/state.html?highlight=guid#sd-emmc-and-ata |title=Barebox State Framework |access-date=2021-05-21 }}</ref> | style="background:#f0f0f0;" | {{mono|4778ED65-BF42-45FA-9C5B-287A1DC4AAB1}} |- | U-Boot bootloader | colspan="2" | U-Boot environment<ref>{{cite mailing list |url=https://lists.denx.de/pipermail/u-boot/2020-November/432928.html |title=RFC: Partition type GUID for U-Boot environment |date=2020-11-17 |access-date=2021-09-28 |mailing-list=U-Boot mailing list |last=Villemoes |first=Rasmus}}</ref><ref>{{cite web |url=https://source.denx.de/u-boot/u-boot/-/blob/v2021.07/include/part_efi.h#L59-61 |title=U-boot 2021.07 source code: include/part_efi.h |date=20 November 2020 |access-date=2021-09-28 }}</ref> | {{mono|3DE21764-95BD-54BD-A5C3-4ABE786F38A8}} |- style="background:#f0f0f0;" | rowspan="4" | SoftRAID{{Citation needed|date=August 2021}} | colspan="2" | SoftRAID_Status | {{mono|B6FA30DA-92D2-4A9A-96F1-871EC6486200}} |- style="background:#f0f0f0;" | colspan="2" | SoftRAID_Scratch | {{mono|2E313465-19B9-463F-8126-8A7993773801}} |- style="background:#f0f0f0;" | colspan="2" | SoftRAID_Volume | {{mono|FA709C7E-65B1-4593-BFD5-E71D61DE9B02}} |- style="background:#f0f0f0;" | colspan="2" | SoftRAID_Cache | {{mono|BBBA6DF5-F46F-4A89-8F59-8765B2727503}} |- <!-- Fuchsia --> |rowspan="8"| Fuchsia standard partitions<ref name="FuchsiaGUIDs">{{cite web |url=https://cs.opensource.google/fuchsia/fuchsia/+/main:zircon/system/public/zircon/hw/gpt.h |title=zircon/system/public/zircon/hw/gpt.h}}</ref> | colspan="2" | Bootloader (slot A/B/R) | {{mono|FE8A2634-5E2E-46BA-99E3-3A192091A350}} |- | colspan="2" | Durable mutable encrypted system data | {{mono|D9FD4535-106C-4CEC-8D37-DFC020CA87CB}} |- | colspan="2" | Durable mutable bootloader data (including A/B/R metadata) | {{mono|A409E16B-78AA-4ACC-995C-302352621A41}} |- | colspan="2" | Factory-provisioned read-only system data | {{mono|F95D940E-CABA-4578-9B93-BB6C90F29D3E}} |- | colspan="2" | Factory-provisioned read-only bootloader data | {{mono|10B8DBAA-D2BF-42A9-98C6-A7C5DB3701E7}} |- | colspan="2" | Fuchsia Volume Manager | {{mono|49FD7CB8-DF15-4E73-B9D9-992070127F0F}} |- | colspan="2" | Verified boot metadata (slot A/B/R) | {{mono|421A8BFC-85D9-4D85-ACDA-B64EEC0133E9}} |- | colspan="2" | Zircon boot image (slot A/B/R) | {{mono|9B37FFF6-2E58-466A-983A-F7926D0B04E0}} |- <!-- Fuchsia legacy --> |rowspan="20"| Fuchsia legacy partitions<ref name="FuchsiaGUIDs" />{{Efn|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. <code>zircon_{a,b,r}</code>) share the same type and are distinguished by name and unique GUID.<ref>{{Cite web |url=https://cs.opensource.google/fuchsia/fuchsia/+/0010ded76edc81fcde8d4582461dc628447e3810 |title=[paver] add support for new partition scheme |accessdate=2021-10-22}}</ref>}} |- | colspan="2" | fuchsia-esp | {{mono|C12A7328-F81F-11D2-BA4B-00A0C93EC93B}} |- | colspan="2" | fuchsia-system | {{mono|606B000B-B7C7-4653-A7D5-B737332C899D}} |- | colspan="2" | fuchsia-data | {{mono|08185F0C-892D-428A-A789-DBEEC8F55E6A}} |- | colspan="2" | fuchsia-install | {{mono|48435546-4953-2041-494E-5354414C4C52}} |- | colspan="2" | fuchsia-blob | {{mono|2967380E-134C-4CBB-B6DA-17E7CE1CA45D}} |- | colspan="2" | fuchsia-fvm | {{mono|41D0E340-57E3-954E-8C1E-17ECAC44CFF5}} |- | colspan="2" | Zircon boot image (slot A) | {{mono|DE30CC86-1F4A-4A31-93C4-66F147D33E05}} |- | colspan="2" | Zircon boot image (slot B) | {{mono|23CC04DF-C278-4CE7-8471-897D1A4BCDF7}} |- | colspan="2" | Zircon boot image (slot R) | {{mono|A0E5CF57-2DEF-46BE-A80C-A2067C37CD49}} |- | colspan="2" | sys-config | {{mono|4E5E989E-4C86-11E8-A15B-480FCF35F8E6}} |- | colspan="2" | factory-config | {{mono|5A3A90BE-4C86-11E8-A15B-480FCF35F8E6}} |- | colspan="2" | bootloader | {{mono|5ECE94FE-4C86-11E8-A15B-480FCF35F8E6}} |- | colspan="2" | guid-test | {{mono|8B94D043-30BE-4871-9DFA-D69556E8C1F3}} |- | colspan="2" | Verified boot metadata (slot A) | {{mono|A13B4D9A-EC5F-11E8-97D8-6C3BE52705BF}} |- | colspan="2" | Verified boot metadata (slot B) | {{mono|A288ABF2-EC5F-11E8-97D8-6C3BE52705BF}} |- | colspan="2" | Verified boot metadata (slot R) | {{mono|6A2460C3-CD11-4E8B-80A8-12CCE268ED0A}} |- | colspan="2" | misc | {{mono|1D75395D-F2C6-476B-A8B7-45CC1C97B476}} |- | colspan="2" | emmc-boot1 | {{mono|900B0FC5-90CD-4D4F-84F9-9F8ED579DB88}} |- | colspan="2" | emmc-boot2 | {{mono|B2B2E8D1-7C10-4EBC-A2D0-4614568260AD}} |- | style="background:#f0f0f0;" | Minix | style="background:#f0f0f0;" colspan="2" | Minix filesystem | style="background:#f0f0f0;" | {{mono|481B2A38-0561-420B-B72A-F1C4988EFC16}} |- | Emu68/AmigaOS | colspan="2" | A partition that includes Rigid Disk Block{{Efn|Due to the limitations of the Rigid Disk Block (RDB), the size of this partition cannot exceed 2 TiB.}} | {{mono|3F82EEBC-87C9-4097-8165-89D6540557C0}} |- | Weka NeuralMesh (Storage System) | colspan="2" | Weka Data Partition | {{mono|993EC906-B4E2-11E7-A205-A0A8CD3EA1DE}} |}

== Example == Here is an example of GUID Partition Table for a 512{{nbsp}}GB NVM Express solid state drive as used with multi-booting configuration, containing an EFI system partition, a Microsoft Reserved Partition, three Microsoft Basic Data Partitions (one is Windows standard partition and two are hidden Windows Recovery Environment partitions), and three Linux partitions (including a swap partition):

<syntaxhighlight lang="sh"> label: gpt label-id: 96BB56B7-AE3C-4E94-986E-10E7F3CCA80B device: /dev/nvme0n1 unit: sectors first-lba: 34 last-lba: 1000215182 sector-size: 512

/dev/nvme0n1p1 : start= 2048, size= 532480, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=7885D52E-0F50-4E28-B058-8DCE7B7FF921, name="EFI system partition" /dev/nvme0n1p2 : start= 534528, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=5C34D099-E77A-4B46-9662-430D33E55AFF, name="Microsoft reserved partition" /dev/nvme0n1p3 : start= 567296, size= 419196928, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=109218B1-3097-4635-BE5F-044E28C2BCB0, name="Basic data partition" /dev/nvme0n1p4 : start= 419764224, size= 1669120, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=527B26E5-2768-444E-AB1F-ECB28201F3C8, attrs="RequiredPartition GUID:63" /dev/nvme0n1p5 : start= 421435392, size= 329410560, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=5C52E480-AEE7-437B-A136-53F8C946D5ED, name="Linux Stuff" /dev/nvme0n1p6 : start= 750845952, size= 243933184, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=023F3B88-D3D9-4E39-9F50-77F242410789, name="Linux Root" /dev/nvme0n1p7 : start= 994779136, size= 4194304, type=0657FD6D-A4AB-43C4-84E5-0933C84B4F4F, uuid=18F44D65-B28D-4871-AF02-DDBD96771460, name="Swap" /dev/nvme0n1p8 : start= 998973440, size= 1228800, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=D4A41B1A-2F28-4AE5-AC67-A2D98FB91E22, name="Basic data partition", attrs="RequiredPartition GUID:63" </syntaxhighlight>

== See also == {{Div col|colwidth=22em}} * Advanced Active Partition (AAP) * Apple Partition Map (APM) * Boot Engineering Extension Record (BEER) * BSD disklabel * Das U-Boot * Device Configuration Overlay (DCO) * Extended Boot Record (EBR) * GNU GRUB * Host Protected Area (HPA) * Master Boot Record (MBR) * Partition alignment * Rigid Disk Block (RDB) * Volume Table of Contents (VTOC) {{Div col end}}

== Notes == {{Notelist|30em}}

== References == {{Reflist|35em}}

== External links == * Microsoft TechNet: [https://web.archive.org/web/20080321063028/http://technet2.microsoft.com/windowsserver/en/library/bdeda920-1f08-4683-9ffb-7b4b50df0b5a1033.mspx?mfr=true Disk Sectors on GPT Disks (archived page)] * Microsoft Windows Deployment: [https://docs.microsoft.com/en-us/windows/deployment/mbr-to-gpt Converting MBR to GPT without dats loss] * Microsoft TechNet: [https://technet.microsoft.com/en-us/library/bb457122.aspx Troubleshooting Disks and File Systems ] * Microsoft TechNet: [https://docs.microsoft.com/en-us/previous-versions/windows/hardware/design/dn653580(v=vs.85) Using GPT Drives] * Microsoft: [http://www.microsoft.com/whdc/device/storage/GPT_FAQ.mspx FAQs on Using GPT disks in Windows] * Microsoft Technet: [https://technet.microsoft.com/en-us/library/cc739412.aspx 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: [https://developer.apple.com/technotes/tn2006/tn2166.html Secrets of the GPT] * [http://www.ibm.com/developerworks/linux/library/l-gpt/ Make the most of large drives with GPT and Linux] * [https://web.archive.org/web/20120426234357/https://gitorious.org/tianocore_uefi_duet_builds/pages/Windows_x64_BIOS_to_UEFI Convert Windows Vista SP1+ or 7 x86_64 boot from BIOS-MBR mode to UEFI-GPT mode without Reinstall] * [http://www.ghacks.net/2010/11/04/how-to-use-3tb-hard-drives-on-windows-xp/ Support for GPT (Partition scheme) and HDD greater than 2.19 TB in Microsoft Windows XP] * [https://web.archive.org/web/20111119090413/http://www.technotes.se/?p=1732 Setting up a RAID volume in Linux with >2TB disks]

{{Firmware and booting}}

Category:BIOS Category:Unified Extensible Firmware Interface Category:Booting Category:Disk partitions