GUID Partition Table

GUID Partition Table ( GPT ), in German GUID partition table (from English Globally Unique Identifier ), is a standard for the format of partition tables on data carriers such as hard drives . The specification is part of the UEFI standard, which, based on mainframes, has replaced the BIOS in PCs since around the year 2000 . GPT is the successor to the partition table of the master boot record . GUID partition tables can also be used as firmware on computers with a BIOS, subject to restrictions .

construction

Schematic representation of a GPT. Each LBA block corresponds to a sector of the hard disk and is 512 bytes in size.

According to the GPT scheme , a data carrier consists of the following areas:

• Master Boot Record (MBR) in sector 0 (the first, 512-byte data block ), the special configuration of which allows the disk to be used under MBR operating systems and protects it against changes by MBR partitioning tools (Schutz-MBR; from English protective MBR )
• primary GUID partition table (GPT), consisting of headers and partition entries
• Partitions
• secondary GPT, consisting of header and partition entries

The secondary GUID partition table at the end of the data carrier is partly a copy of the primary GPT at the beginning of the data carrier: The contents of the fields for the positions of the own and the alternative GPT headers are reversed and the address of the partition table refers to the copy of the partition table at the end the disk before the alternative header. Thus, both GPT header also have a different CRC32 - checksum . Thanks to the redundancy it contains, the partition table can be restored in the event of an error. Since a checksum is entered in the GPT, it can be determined whether both or which of the two GPTs are faulty.

MBR partition table

In the first sector / block of the data carrier ( LBA  0) is the MBR with a classic MBR partition table and an entry that marks the rest of the data carrier as occupied. For a partitioning tool that can only read MBR but not GPT partition tables, the entire space on the disk appears to be occupied. The MBR of a GPT disk, thus constitutes a protection for the contents of the disc if you want to to that with partitioning tools that do not yet know the GPT accessed (hence English protective MBR ). The partition identifier is EE ₁₆ for a protection MBR (with a GUID partition table below) or EF ₁₆ for an EFI system partition.

GUID partition table header

The header of the primary GPT is in the second sector / block ( LBA 1) and the secondary backup GPT is in the last sector / block (LBA −1). The header itself describes u. a. the usable blocks of the data carrier, the position of the own header and the secondary backup header as well as the number and size of the partition entries. The EFI specifications dictate a minimum of 16,384 bytes for the partition table, so there is room for 128 entries. The header itself and the partition entries are also protected with CRC32 checksums, which must be checked by the firmware , the boot loader or the operating system . Therefore, if the header z. B. changed with a hex editor , this makes the checksum invalid and the system becomes unstable or even unusable.

The following information is stored in the header of the GPT:

Offset	length	content
0	8 bytes	Signature ("EFI PART", 45h 46h 49h 20h 50h 41h 52h 54h)
8th	4 bytes	Revision ( 00h 00h 01h 00h)
12	4 bytes	Header size - Little Endian ( 5Ch 00h 00h 00hcorresponds to 92 bytes)
16	4 bytes	Header CRC32 checksum (from offset 0 to header size, this field itself is set to 0 during the calculation)
20th	4 bytes	Reserved Area - Must be zero (0)
24	8 bytes	Position of your own LBA (this header)
32	8 bytes	Location of the backup LBA (the other header)
40	8 bytes	First usable LBA for partitions (last LBA of the primary partition table + 1, usually 34)
48	8 bytes	Last usable LBA (first LBA of the secondary partition table - 1, usually disk size - 34)
56	16 bytes	Data carrier GUID (for reference see also UUID for UNIXe)
72	8 bytes	Start LBA of the partition table
80	4 bytes	Number of partition entries (partitions)
84	4 bytes	Size of a partition entry (usually 128)
88	4 bytes	Partition table CRC32 checksum
92	*	Reserved area; must be filled with zeros for the rest of the block (420 bytes for a 512-byte LBA)

Partition entry

The partition entries are stored in LBA 2 to LBA 33 (secondary header: LBA -33 to LBA -1). Each partition entry is 128 bytes. This means that four partition entries can be stored per logical block. This minimum number of 32 sectors for partition entries prescribed in the specification can be increased as required, so that the maximum possible number of partitions is in principle only limited by the available disk space.

The following data is stored in the partition entry itself:

Offset	length	content
0	16 bytes	Partition type GUID
16	16 bytes	Unique partition GUID
32	8 bytes	Beginning of the partition (first LBA - little-endian)
40	8 bytes	End of partition (last LBA - inclusive)
48	8 bytes	Attributes (see following table)
56	72 bytes	Partition name (36 UTF-16 LE characters)
	128 bytes in total

The individual entries have a relatively simple structure. The first 16 bytes describe the partition type. The partition type GUID for an EFI system partition is e.g. B. {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}. This is followed by 16 bytes with the partition GUID. This is followed by the number of the first and the last LBA sector of the partition, 8 bytes with attributes and the name of the partition (36 Unicode characters long).

Microsoft defines the following attribute entries:

bit	content
0	System partition
1	hide from EFI
2	Legacy BIOS bootable (analogous to MBR 80hActive flag)
60	Read only
62	Hidden
63	Do not mount automatically (= do not assign a drive letter)

Partition type GUIDs

Partition type		original system	English name	Name and description
GPT ( GUID , hexadecimal )	MBR ( hex )
00000000-0000-0000-0000-000000000000	0x00	GPT	Unused entry	Entry for an unused partition.
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7	0x01	IBM PC	Microsoft basic data	FAT12
	0x04			FAT16 <32 MB
	0x06			FAT16
	0x07			NTFS (or HPFS )
	0x0b			FAT32
	0x0c			FAT32 LBA
	0x0e			FAT16 LBA
	0x11			FAT12 (hidden)
	0x14			FAT16 <32 MB (hidden)
	0x16			FAT16 (hidden)
	0x17			NTFS (or HPFS ) (hidden)
	0x1b			FAT32 (hidden)
	0x1c			FAT32 LBA (hidden)
	0x1e			FAT16 LBA (hidden)
E3C9E316-0B5C-4DB8-817D-F92DF00215AE	0x0c	Windows ( EFI )	Microsoft reserved	Hybrid MBR type 0x0cis the same as that of FAT32 LBA
DE94BBA4-06D1-4D40-A16A-BFD50179D6AC	0x27	Windows	Windows RE	Recovery partition with Windows Recovery Environment (from Vista based on Windows PE )
7412F7D5-A156-4B13-81DC-867174929325	0x30, 0xe1	ONIE	ONIE boot	Open Network Install Environment (ONIE)
D4E6E2CD-4469-46F3-B5CB-1BFF57AFC149			ONIE config
C91818F9-8025-47AF-89D2-F030D7000C2C	0x39	Plan 9	Plan 9	Partition used by the Plan 9 operating system.
9E1A2D38-C612-4316-AA26-8B49521E5A8B	0x41	PReP	PowerPC PReP boot	PReP was the forerunner of CHRP or the PowerPC Platform .
AF9B60A0-1431-4F62-BC68-3311714A69AD	0x42	Windows	Windows LDM data	The Logical Disk Manager (LDM) is the implementation of a Logical Volume Manager under Windows NT , which is available in Windows 2000 to Windows 7. As of Windows 8, its successor Storage Spaces is included.
5808C8AA-7E8F-42E0-85D2-E1E90434CFB3			Windows LDM metadata
E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D			Windows Storage Spaces
37AFFC90-EF7D-4E96-91C3-2D7AE055B174	0x75		IBM GPFS	General Parallel File System (GPFS)
FE3A2A5D-4F32-41A7-B725-ACCC3285A309	0x7f	Chromebook	ChromeOS kernel	Google Chrome OS
3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC			ChromeOS root
2E0A753D-9E48-43B0-8337-B15192CB1B5E			ChromeOS reserved
0657FD6D-A4AB-43C4-84E5-0933C84B4F4F	0x82	Linux	Linux swap	Linux swap partition. Solaris also uses the type 0x82as swap on MBR partitions .
0FC63DAF-8483-4772-8E79-3D69D8477DE4	0x83		Linux filesystem	This type of partition is also known as “Linux native”.
8DA63339-0007-60C0-C436-083AC8230908			Linux reserved	The hybrid MBR type corresponds to the "Linux native" of, 0x83.
933AC7E1-2EB4-4F13-B844-0E14E2AEF915	0x83	freedesktop.org (Linux)	Linux / home	auto-mount for systemd from freedesktop.org
3B8F8425-20E0-4F3B-907F-1A25A76F98E8			Linux / srv
7FFEC5C9-2D00-49B7-8941-3EA10A5586B7			Linux dm-crypt
CA7D7CCB-63ED-4C53-861C-1742536059CC			Linux LUKS
44479540-F297-41B2-9AF7-D131D5F0458A			Linux x86	root partition on 32-bit - x86 systems ( IA-32 ).
4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709			Linux x86-64	root partition on 64-bit - x86 systems ( IA-32 in x64 mode).
69DAD710-2CE4-4E3C-B16C-21A1D49ABED3			Linux ARM32	root partition to 32-bit - ARM systems.
B921B045-1DF0-41C3-AF44-4C6F280D3FAE			Linux ARM64	root partition on 64-bit - ARM systems (ARMv8).
993d8d3d-f80e-4225-855a-9daf8ed7ea97	-		Linux IA-64	root partition on Itanium systems (IA-64).
D3BFE2DE-3DAF-11DF-BA40-E3A556D89593	0x84	Intel PC	Intel Rapid Start	What is referred to as Intel Rapid Start Technology is actually a hybrid of standby mode ( S3, “suspend to RAM” ) and hibernation (S4, “suspend to disk” ).
E6D6D379-F507-44C2-A23C-238F2A3DF928	0x8e	Linux	Linux LVM	Logical Volume Manager
734E5AFE-F61A-11E6-BC64-92361F002671	0xa2	Atari TOS	TOS basic data	FAT16 <32 MB,'GEM'
				FAT16 ,'BGM'
				FAT32 ,'F32'
516E7CB4-6ECF-11D6-8FF8-00022D09712B	0xa5	FreeBSD	FreeBSD disklabel
83BD6B9D-7F41-11DC-BE0B-001560B84F0F			FreeBSD boot
516E7CB5-6ECF-11D6-8FF8-00022D09712B			FreeBSD swap
516E7CB6-6ECF-11D6-8FF8-00022D09712B			FreeBSD UFS
516E7CBA-6ECF-11D6-8FF8-00022D09712B			FreeBSD ZFS
516E7CB8-6ECF-11D6-8FF8-00022D09712B			FreeBSD Vinum / RAID
85D5E45A-237C-11E1-B4B3-E89A8F7FC3A7	0xa5	MidnightBSD	MidnightBSD data
85D5E45E-237C-11E1-B4B3-E89A8F7FC3A7			MidnightBSD boot
85D5E45B-237C-11E1-B4B3-E89A8F7FC3A7			MidnightBSD swap
0394EF8B-237E-11E1-B4B3-E89A8F7FC3A7			MidnightBSD UFS
85D5E45D-237C-11E1-B4B3-E89A8F7FC3A7			MidnightBSD ZFS
85D5E45C-237C-11E1-B4B3-E89A8F7FC3A7			MidnightBSD Vinum
824CC7A0-36A8-11E3-890A-952519AD3F61	0xa6	OpenBSD	OpenBSD data
55465300-0000-11AA-AA11-00306543ECAC	0xa8	Mac OS X	Apple UFS	Partition that contains a Unix file system . Corresponds to the APM partition type Apple_UFS.
516E7CB4-6ECF-11D6-8FF8-00022D09712B	0xa9	FreeBSD	FreeBSD disklabel	FreeBSD, NetBSD, OpenBSD (OpenBSD uses MBR type 0xa6)
49F48D32-B10E-11DC-B99B-0019D1879648		NetBSD	NetBSD swap
49F48D5A-B10E-11DC-B99B-0019D1879648			NetBSD FFS
49F48D82-B10E-11DC-B99B-0019D1879648			NetBSD LFS
2DB519C4-B10F-11DC-B99B-0019D1879648			NetBSD concatenated
2DB519EC-B10F-11DC-B99B-0019D1879648			NetBSD encrypted
49F48DAA-B10E-11DC-B99B-0019D1879648			NetBSD RAID
426F6F74-0000-11AA-AA11-00306543ECAC	0xab	macOS	Apple boot	Recovery partition since Mac OS X Lion (10.7, 2011). Contains an HFS + or APFS file system and is normally called Recovery HDbut is hidden.
48465300-0000-11AA-AA11-00306543ECAC	0xaf		Apple HFS / HFS +	Partition for the HFS + file system , corresponds to APM partition type Apple_HFSX. The older hierarchical file system (HFS) , APM partition type Apple_HFS, is normally no longer used on GPT partitions.
52414944-0000-11AA-AA11-00306543ECAC			Apple RAID	Houses a partition from a RAID group. Corresponds to the APM partition type Apple_RAID.
52414944-5F4F-11AA-AA11-00306543ECAC			Apple RAID offline	Houses a partition removed from a RAID system.
4C616265-6C00-11AA-AA11-00306543ECAC			Apple label	"Apple Label" is a disk label variant for Mac OS X .
5265636F-7665-11AA-AA11-00306543ECAC			AppleTV recovery	The Apple TV uses an operating system based on Mac OS X with an optimized user interface for television.
53746F72-6167-11AA-AA11-00306543ECAC			Apple Core Storage	A core storage partition for FileVault  2 (encrypted). Apple Fusion Drive also uses a partition of this type.
B6FA30DA-92D2-4A9A-96F1-871EC6486200			Apple SoftRAID status	Apple SoftRAID partition.
2E313465-19B9-463F-8126-8A7993773801			Apple SoftRAID Scratch
FA709C7E-65B1-4593-BFD5-E71D61DE9B02			Apple SoftRAID Volume
BBBA6DF5-F46F-4A89-8F59-8765B2727503			Apple SoftRAID Cache
7C3457EF-0000-11AA-AA11-00306543ECAC			Apple APFS	Partition for the APFS file system , the successor to HFS + on macOS .
CEF5A9AD-73BC-4601-89F3-CDEEEEE321A1	0xb3	QNX	QNX6 Power-Safe
0311FC50-01CA-4725-AD77-9ADBB20ACE98	0xbc	Acronis	Acronis Secure Zone
6A82CB45-1DD2-11B2-99A6-080020736631	0xbe	Solaris	Solaris boot
6A85CF4D-1DD2-11B2-99A6-080020736631	0xbf		Solaris root
6A898CC3-1DD2-11B2-99A6-080020736631			Solaris / usr	Usually accommodates the UFS file system up to Solaris 9 and ZFS from Solaris 10 onwards . MacZFS uses the same GUID.
6A87C46F-1DD2-11B2-99A6-080020736631			Solaris swap
6A8B642B-1DD2-11B2-99A6-080020736631			Solaris backup
6A8EF2E9-1DD2-11B2-99A6-080020736631			Solaris / var
6A90BA39-1DD2-11B2-99A6-080020736631			Solaris / home
6A9283A5-1DD2-11B2-99A6-080020736631			Solaris alternate sector
6A945A3B-1DD2-11B2-99A6-080020736631	0xbf		Solaris Reserved
6A9630D1-1DD2-11B2-99A6-080020736631
6A980767-1DD2-11B2-99A6-080020736631
6A96237F-1DD2-11B2-99A6-080020736631
6A8D2AC7-1DD2-11B2-99A6-080020736631
75894C1E-3AEB-11D3-B7C1-7B03A0000000	0xc0	HP-UX	HP-UX data
E2A1E728-32E3-11D6-A682-7B03A0000000			HP-UX service
BC13C2FF-59E6-4262-A352-B275FD6F7172	0xea	freedesktop.org	Freedesktop $ BOOT
42465331-3BA3-10F1-802A-4861696B7521	0xeb	Haiku	Haiku FSO	Although BeOS itself did not support a GUID partition table, this partition is used by its further development, Haiku, for a Be file system .
BFBFAFE7-A34F-448A-9A5B-6213EB736C22	0xed	ESP, manufacturer-specific	Lenovo system partition	Manufacturer- specific EFI system partition (ESP), which is identified as ESP by the specific firmware (UEFI).
F4019732-066E-4E12-8273-346C5641494F			Sony system partition
C12A7328-F81F-11D2-BA4B-00A0C93EC93B	0xef	EFI	EFI system (ESP)	This partition is known as the EFI System Partition (ESP). It contains a FAT file system from which the firmware is an executable file ( PE / COFF ), e.g. B. /EFI/BOOT/BOOTX64.EFI, loads and executes. Under partedthis partition is displayed with “boot flag” , ie as the start partition .
024DEE41-33E7-11D3-9D69-0008C781F39F			MBR partition scheme	This partition contains an embedded full MBR partition table including partitions. However, since the partitions contained are not hybrid partitions, they cannot be accessed from the GUID partition table. But it is possible to pass a partition through to a virtual machine for virtualization purposes, which sets up and uses a complete MBR partition table on it.
21686148-6449-6E6F-744E-656564454649			BIOS boot partition	A partition that GRUB uses to boot up BIOS-based PCs. The GUID is read !haHdInotNeedEFIin hexadecimal notation (which in the required little-endian form in the GPT then results in "Hah! IdontNeedEFI").
4FBD7E29-9D25-41B8-AFD0-062C0CEFF05D	0xf8	Ceph	Ceph OSD	Ceph Object Storage Daemon
4FBD7E29-9D25-41B8-AFD0-5EC00CEFF05D			Ceph dm-crypt OSD	Ceph Object Storage Daemon (encrypted)
45B0969E-9B03-4F30-B4C6-B4B80CEFF106			Ceph journal
45B0969E-9B03-4F30-B4C6-5EC00CEFF106			Ceph dm-crypt journal
89C57F98-2FE5-4DC0-89C1-F3AD0CEFF2BE			Ceph disk in creation
89C57F98-2FE5-4DC0-89C1-5EC00CEFF2BE			Ceph dm-crypt disk in creation
AA31E02A-400F-11DB-9590-000C2911D1B8	0xfb	VMware ESX	VMware VMFS
9198EFFC-31C0-11DB-8F78-000C2911D1B8			VMware reserved
9D275380-40AD-11DB-BF97-000C2911D1B8	0xfc		VMware kcore crash protection
A19D880F-05FC-4D3B-A006-743F0F84911E	0xfd	Linux	Linux RAID

Since MBR partitions can be converted into GUID partitions in many systems, there is a corresponding MBR partition type for many GUID partition types. Even when using hybrid MBRs, the corresponding partitions are created once with a GUID and once with the corresponding MBR partition type.

Conversion

Basically, it is possible to convert from the master boot record partition table to the GUID partition table, but sufficient free space is required between the MBR and the first partition as well as after the last partition to accommodate the necessary data structure for the GUID partition table to be able to. The gptfdisk program, among others, offers this possibility. It is also possible to transfer some BSD disklabel partitions to GPT.

Limitations

The GPT uses Logical Block Addressing (LBA) with 64-bit entries, so that - with a sector size of 512 bytes - hard disks with a total capacity of 8  zebibytes can be addressed. The maximum number of possible partitions depends on the size of the partition table, which according to the specification offers space for at least 128 partitions. Not all systems offer this option . For example, the partitioning gdisktool can generate a larger partition table.

Hybrid MBR

A hybrid MBR describes the definition of individual partitions both in the GUID partition table (GPT) and in the partition table of the master boot record (MBR) . Access to the partitions is possible via both GPT and MBR, which enables dual booting between operating systems that only use or support one of the two partition tables .

The MBR is usually only the entire data area comprehensive protection partition contain what is considered protective MBR ( English "protective MBR" ) is called. With hybrid partitioning, one and the same partition is defined in both the GUID and the MBR partition table: since the master boot record is a hybrid of the actual GUID partition table, the term "hybrid MBR" is used in this case .

The danger with hybrid partitioning is that changing only one of the two partition tables can lead to gross partitioning errors. Hybrid partitioning must therefore be carried out using programs provided for this purpose and must never be changed using the partitioning tools of an operating system that only uses one of the two partition tables.

The number of hybrid partitions is limited to four shared partitions. Defining an extended MBR partition is not possible because GPT does not support extended partitions. Conversely, there is only space for a total of four primary partitions in the partition table of the master boot record. Since a primary partition is required for EFI - the EFI System Partition (ESP) - three hybrid partitions are available for operating systems or shared data partitions. It is the only safe solution to partition the entire usable storage space with a maximum of four hybrid partitions (including the ESP).

With manual partitioning it is still possible not to map all partitions as hybrid partitions: then the operating system, which only evaluates the MBR, cannot access all partitions, but it allows a sufficient number of shared partitions for dual boot operation. However, in such a configuration there is no protection for GUID partitions that do not also exist as MBR partitions. The operating system, which only evaluates the MBR, sees further supposedly unpartitioned and thus empty space that is not used by any of the MBR partitions. It is up to the user not to allow the operating system to make use of this storage space, as it is actually used by other GUID partitions, thus containing data and erroneous overwriting leads to data loss within the GUID partitions.

Apple uses a hybrid MBR with Boot Camp under macOS ("OS X" until 2016 and "Mac OS X" until 2012) . When Windows starts, this is done via a Compatibility Support Module (CSM) of the Apple EFI firmware, so that Windows uses the MBR partition table, like a PC with BIOS, but not the GUID partition table. However, if macOS is started, the GUID partition table is used. The macOS Disk Utility automatically creates a hybrid MBR as soon as one of the partitions is formatted with a FAT32 file system and there are no more than four partitions on the disk.

Support in operating systems

For operating systems based on the Itanium architecture (also IA-64 for English Intel Architecture 64-Bit ), the support of GPT is absolutely necessary, since these computers use the Extensible Firmware Interface . From around 2005, the successor to the BIOS, now called UEFI , also became increasingly popular in PCs , so that operating systems for the IA-32 architecture of the x86 processor also support GPT. In addition to the corresponding Itanium versions of FreeBSD , HP-UX , Linux , NetBSD , OpenVMS , Solaris and Windows , which support GPT due to the firmware, GPT has also been supported by all x86-64 versions since the BIOS was replaced by UEFI .

Since the conversion of Apple Macintosh computers to Intel processors at the beginning of 2006, Mac OS X (since 2016 “macOS”) has also been using GPT, since Intel-based Macs use Apple's own EFI variant. Mac OS X Tiger (10.4, 2005) and newer can, however, also use GPT media on the PowerPC platform, but cannot start from it due to the firmware .

The versions of Windows XP that were still developed for the 32-bit Intel i386 architecture, on the other hand, can only be installed and operated on a GPT hard drive with restrictions. Among other things, they only read the MBR but not the GPT to get partitioning data. By using hybrid partition tables, the respective partitions can be set up as both MBR and GPT partitions, however, a maximum of three primary partitions are available in the MBR, as this does not allow more than four entries and the first partition is already for the EFI -Firmware is reserved. Conversely, extended partitions of the MBR, which can contain multiple logical partitions as containers, are no longer supported by GPT.

Up until the appearance of Windows Vista in early 2007, the 64-bit Windows versions were primarily aimed at server operators and professional users (e.g. CAD or graphics / design). This also includes Windows XP Professional x64 Edition , which was released in 2005 . When they were released, comprehensive GPT support was only available with selected hardware through the corresponding 64-bit drivers. With the release of Vista, the availability of 64-bit drivers generally improved, so that they usually also support the x64 version of XP.

In the initial phase of the introduction during the test of a 4 TB hard drive partitioned with GPT, the specialist magazine c't found that numerous hard drive drivers from well-known manufacturers stored the data instead of at the desired location at the beginning of the hard drive when writing to areas beyond 2 TB, so that there was massive data loss or even loss of formatting of the hard drive. The problem apparently occurred specifically with the 32-bit versions of Windows XP, some of which already had support for GPT, but due to their 32-bit driver design with the previously common physical sector size of 512 bytes, the 2- Could not exceed the TB limit. Since the use of such partitions was mainly found in servers at that time, these problems most likely arose when the hard disks of such a system were exchanged with other computers.

A 64-bit Linux can - without any UEFI or separate BIOS support - boot from a GPT partition with GRUB2 . No UEFI is necessary for this - the coupling of GPT to (U) EFI is therefore not mandatory.

OpenBSD supports the installation on a GPT partition of an x86_64 - UEFI system since version 5.9.

swell

1. ↑ ^{a b} Thorsten Leemhuis: Growth problems - special features in the interaction of Linux with large hard drives . In: c't . tape 2011 , no. 4 . Heise-Verlag , January 31, 2011, p. 170–172 ( article archive [accessed on May 2, 2020]): “[…] the UEFI, which is often declared as the“ BIOS successor ”[is] usually mentioned in the same breath as GPT, although the latter can also be used independently - GPT-compatible boot loaders such as the still young Grub2 start Linux without any problems without UEFI. "
2. ↑ List of partition identifiers for PCs . Technical University of Eindhoven. Retrieved April 18, 2012.
3. ↑ Archive link ( Memento of the original from April 15, 2012 in the Internet Archive ) Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice. (U) EFI Specification (English) 
4. ↑ e09127r3 EDD-4 Hybrid MBR boot code annex (PDF; 119 kB) Retrieved on May 18, 2012.
5. ↑ Microsoft TechNet: Recommended configurations for UEFI-based disk partitions on Windows 7 and Windows Server 2008 R2, accessed July 7, 2015
6. ↑ Microsoft TechNet: What is Windows RE? , accessed July 4, 2015
7. ↑ https://github.com/onie/onie/blob/master/rootconf/x86_64/sysroot-lib-onie/onie-blkdev-common  ( page no longer available , search in web archives )  Info: The link was automatically defective marked. Please check the link according to the instructions and then remove this notice.  
8. ↑ onie.org
9. ↑ man.cat-v.org
10. ↑ vboot_reference / firmware / lib / cgptlib / include / gpt.h, ChromeOS source code from December 23, 2010
11. ↑ chromium.org
12. ↑ freedesktop.org
13. ↑ ^{a b} freedesktop.org
14. ↑ c't Hotline: What is "Rapid Start Technology"? from issue 7/2014, accessed on July 9, 2015
15. ↑ gptfdisk on sourceforge.com (English), accessed July 4, 2015
16. ↑ Apple Developer: disklabel man page , accessed July 12, 2015
17. ↑ MacZFS.org: Official Site for the Free ZFS for Mac OS , accessed July 9, 2015
18. ↑ Managing EFI Boot Loaders for Linux: Basic Principles , Rod Smith, accessed July 9, 2015
19. ↑ github.com
20. ^ Converting to or from GPT , Rod Smith, accessed July 12, 2015
21. ↑ GUID Partition Table. ( Blog ) UEFI Support, January 26, 2015, accessed December 23, 2018 : “Advantages of GPT; 3. Arbitrary number of partitions - depends on space allocated for the partition table ... By default the GPT table contains space for defining 128 partitions. However if the user wants to define more partitions, he / she can allocate more space to the partition table (currently only gdisk is known to support this feature). " 
22. ↑ RAID system: 4 TB in one housing , In: c't No. 2/2009, p. 54
23. ↑ Microsoft TechNet: GUID Partition Table
24. ↑ OpenBSD 5.9 ( en )