GUID Partition Table - Revision history

GreenC bot: Move 1 url. Wayback Medic 2.5 per WP:URLREQ#citeftp

2025-05-27T09:28:45Z

Move 1 url. Wayback Medic 2.5 per WP:URLREQ#citeftp

← Previous revision		Revision as of 09:28, 27 May 2025
Line 479:		Line 479:
	\| style="background:#f0f0f0;"\|{{mono\|21686148-6449-6E6F-744E-656564454649}}		\| style="background:#f0f0f0;"\|{{mono\|21686148-6449-6E6F-744E-656564454649}}
	\|- style="background:#f0f0f0;"		\|- 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 ~~\|title=Archived copy~~ \|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}}</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}}</ref>		\| 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=Archived copy }}</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}}</ref>
	\| {{mono\|D3BFE2DE-3DAF-11DF-BA40-E3A556D89593}}		\| {{mono\|D3BFE2DE-3DAF-11DF-BA40-E3A556D89593}}
	\|-		\|-

Guy Harris: Use {{cite IETF}} for an RFC.

2025-05-14T09:26:43Z

Use {{cite IETF}} for an RFC.

← Previous revision		Revision as of 09:26, 14 May 2025
Line 91:		Line 91:
	\|align="right"\| 48 (0x30) \|\|align="right"\| 8 bytes \|\| Last usable LBA (secondary partition table first LBA − 1)		\|align="right"\| 48 (0x30) \|\|align="right"\| 8 bytes \|\| Last usable LBA (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 ~~web~~ \|date= July 2005\|title= A ~~universally~~ ~~unique~~ ~~identifier~~ (UUID) URN Namespace \|~~url~~= ~~https://datatracker.ietf.org/doc/html/rfc4122#~~section-4.1.2 ~~\|page= 6~~\|access-date=13 February 2025 \|last1= Leach \|first1= Paul J. \|last2= Salz \|first2= Rich \|last3= Mealling \|first3= Michael H. }}</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"\| 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"\| 72 (0x48) \|\|align="right"\| 8 bytes \|\| Starting LBA of array of partition entries (usually 2 for compatibility)

Dondervogel 2: /* History */ it's not obvious

2025-05-13T19:54:10Z

History: it's not obvious

← Previous revision		Revision as of 19:54, 13 May 2025
Line 15:		Line 15:
	{{Main\|INT 13H\|Enhanced BIOS}}		{{Main\|INT 13H\|Enhanced BIOS}}

	The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, ~~obviously~~ had limitations when it came to modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|www.uefi.org]] \|date=2010 \|access-date=12 December 2020}}</ref>		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 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).		In the late 1990s, [[Intel]] developed a new partition table format as part of what eventually became the [[Unified Extensible Firmware Interface]] (UEFI). The GUID Partition Table is specified in chapter 5 of the UEFI 2.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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).

Artem S. Tashkinov: /* History */

2025-05-13T11:58:07Z

History

← Previous revision		Revision as of 11:58, 13 May 2025
Line 15:		Line 15:
	{{Main\|INT 13H\|Enhanced BIOS}}		{{Main\|INT 13H\|Enhanced BIOS}}

	The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s~~, had~~, obviously limitations ~~for~~ ~~use~~ of modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|www.uefi.org]] \|date=2010 \|access-date=12 December 2020}}</ref>		The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, obviously had limitations when it came to modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).		In the late 1990s, [[Intel]] developed a new partition table format as part of what eventually became the [[Unified Extensible Firmware Interface]] (UEFI). The GUID Partition Table is specified in chapter 5 of the UEFI 2.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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).

Acastiello: "imposed" sounds like a design flaw or glitch. MBR was developed according to existing hardware, so it could not "impose" limitations to future disks, the same way plate disks didn't impose limitations to SSD disks

2025-05-13T06:04:12Z

"imposed" sounds like a design flaw or glitch. MBR was developed according to existing hardware, so it could not "impose" limitations to future disks, the same way plate disks didn't impose limitations to SSD disks

← Previous revision		Revision as of 06:04, 13 May 2025
Line 15:		Line 15:
	{{Main\|INT 13H\|Enhanced BIOS}}		{{Main\|INT 13H\|Enhanced BIOS}}

	The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, ~~imposed~~ limitations for use of modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|www.uefi.org]] \|date=2010 \|access-date=12 December 2020}}</ref>		The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, had, obviously limitations for use of modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).		In the late 1990s, [[Intel]] developed a new partition table format as part of what eventually became the [[Unified Extensible Firmware Interface]] (UEFI). The GUID Partition Table is specified in chapter 5 of the UEFI 2.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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).

Citation bot: Add: authors 1-3. | Use this bot. Report bugs. | Suggested by Dominic3203 | Category:Booting | #UCB_Category 15/42

2025-04-15T02:12:34Z

Add: authors 1-3. | Use this bot. Report bugs. | Suggested by Dominic3203 | Category:Booting | #UCB_Category 15/42

← Previous revision		Revision as of 02:12, 15 April 2025
Line 91:		Line 91:
	\|align="right"\| 48 (0x30) \|\|align="right"\| 8 bytes \|\| Last usable LBA (secondary partition table first LBA − 1)		\|align="right"\| 48 (0x30) \|\|align="right"\| 8 bytes \|\| Last usable LBA (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 web \|date= July 2005\|title= A universally unique identifier (UUID) URN Namespace \|url= https://datatracker.ietf.org/doc/html/rfc4122#section-4.1.2 \|page= 6\|access-date=13 February 2025 }}</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"\| 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 web \|date= July 2005\|title= A universally unique identifier (UUID) URN Namespace \|url= https://datatracker.ietf.org/doc/html/rfc4122#section-4.1.2 \|page= 6\|access-date=13 February 2025 \|last1= Leach \|first1= Paul J. \|last2= Salz \|first2= Rich \|last3= Mealling \|first3= Michael H. }}</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"\| 72 (0x48) \|\|align="right"\| 8 bytes \|\| Starting LBA of array of partition entries (usually 2 for compatibility)

Citation bot: Altered title. Removed parameters. | Use this bot. Report bugs. | Suggested by Dominic3203 | Category:Booting | #UCB_Category 13/42

2025-03-31T17:27:21Z

Altered title. Removed parameters. | Use this bot. Report bugs. | Suggested by Dominic3203 | Category:Booting | #UCB_Category 13/42

← Previous revision		Revision as of 17:27, 31 March 2025
Line 91:		Line 91:
	\|align="right"\| 48 (0x30) \|\|align="right"\| 8 bytes \|\| Last usable LBA (secondary partition table first LBA − 1)		\|align="right"\| 48 (0x30) \|\|align="right"\| 8 bytes \|\| Last usable LBA (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 web \|date= July 2005\|title= A universally unique identifier (UUID) URN Namespace \|url= https://datatracker.ietf.org/doc/html/rfc4122#section-4.1.2 \|page= 6\|access-date=13 February 2025 ~~\|url-status= live~~}}</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 ~~\|url-status= live~~}}</ref>}}		\|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 web \|date= July 2005\|title= A universally unique identifier (UUID) URN Namespace \|url= https://datatracker.ietf.org/doc/html/rfc4122#section-4.1.2 \|page= 6\|access-date=13 February 2025 }}</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"\| 72 (0x48) \|\|align="right"\| 8 bytes \|\| Starting LBA of array of partition entries (usually 2 for compatibility)

Laffer1: Updated MidnightBSD support. It will boot without CSM

2025-03-16T18:58:37Z

Updated MidnightBSD support. It will boot without CSM

← Previous revision		Revision as of 18:58, 16 March 2025
Line 212:		Line 212:
	\| IA-32, x86-64		\| IA-32, x86-64
	\| {{Yes}}		\| {{Yes}}
	\| {{~~Partial\|Requires CSM~~}}		\| {{Yes}}
	\| In a hybrid configuration, both GPT and MBR partition identifiers may be used.		\| In a hybrid configuration, both GPT and MBR partition identifiers may be used.
	\|-		\|-

Dmoews: discuss backup partition entry array; conform to the spec re partition table entry size

2025-03-12T16:50:48Z

discuss backup partition entry array; conform to the spec re partition table entry size

← Previous revision		Revision as of 16:50, 12 March 2025
Line 52:		Line 52:

	== Features ==		== Features ==

	Like MBR, GPT uses [[logical block addressing]] (LBA) in place of the historical [[cylinder-head-sector]] (CHS) addressing. The protective MBR is stored at LBA 0, and the GPT header is in LBA 1, with a backup GPT header stored at the final LBA. The GPT header has a [[Pointer (computer programming)\|pointer]] to the partition table (''Partition Entry Array''), which is typically at LBA 2. Each entry on the partition table has a size of 128 bytes.
	The UEFI specification stipulates that a minimum of 16,384 bytes, regardless of sector size, are allocated for the Partition Entry Array.~~{{r\|UEFI2.11\|p=116}}~~ Thus, on a disk with 512-byte sectors, at least 32 sectors are used for the Partition Entry Array, and the first usable block is at LBA 34 or higher, while on a 4,096-byte ~~sectors~~ disk, at least 4 sectors are used for the Partition Entry Array, and the first usable block is at LBA 6 or higher.		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 (computer programming)\|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==		==MBR variants==

Davexvi: /* Partition table header (LBA 1) */ Changed last offset of CRC32 calculation from 5C to 5

2025-03-04T01:40:40Z

Partition table header (LBA 1): Changed last offset of CRC32 calculation from 5C to 5

← Previous revision		Revision as of 01:40, 4 March 2025
Line 79:		Line 79:
	\|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"\| 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 \|\| [[CRC32]] of header (offset +0 to +~~0x5c~~) in little endian, with this field zeroed during calculation		\|align="right"\| 16 (0x10) \|\|align="right"\| 4 bytes \|\| [[CRC32]] 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"\| 20 (0x14) \|\|align="right"\| 4 bytes \|\| Reserved; must be zero

← Previous revision		Revision as of 19:54, 13 May 2025
Line 15:		Line 15:
	{{Main\|INT 13H\|Enhanced BIOS}}		{{Main\|INT 13H\|Enhanced BIOS}}

	The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, ~~obviously~~ had limitations when it came to modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|www.uefi.org]] \|date=2010 \|access-date=12 December 2020}}</ref>		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 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).		In the late 1990s, [[Intel]] developed a new partition table format as part of what eventually became the [[Unified Extensible Firmware Interface]] (UEFI). The GUID Partition Table is specified in chapter 5 of the UEFI 2.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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).

← Previous revision		Revision as of 11:58, 13 May 2025
Line 15:		Line 15:
	{{Main\|INT 13H\|Enhanced BIOS}}		{{Main\|INT 13H\|Enhanced BIOS}}

	The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s~~, had~~, obviously limitations ~~for~~ ~~use~~ of modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|www.uefi.org]] \|date=2010 \|access-date=12 December 2020}}</ref>		The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, obviously had limitations when it came to modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).		In the late 1990s, [[Intel]] developed a new partition table format as part of what eventually became the [[Unified Extensible Firmware Interface]] (UEFI). The GUID Partition Table is specified in chapter 5 of the UEFI 2.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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).

← Previous revision		Revision as of 06:04, 13 May 2025
Line 15:		Line 15:
	{{Main\|INT 13H\|Enhanced BIOS}}		{{Main\|INT 13H\|Enhanced BIOS}}

	The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, ~~imposed~~ limitations for use of modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|www.uefi.org]] \|date=2010 \|access-date=12 December 2020}}</ref>		The Master Boot Record (MBR) partitioning scheme, widely used since the early 1980s, had, obviously limitations for use of modern hardware. The available size for block addresses and related information is limited to 32 bits. For hard disks with 512{{nbh}}byte sectors, the MBR partition table entries allow a maximum size of 2 [[Tebibyte\|TiB]] (2³² × 512{{nbh}}bytes) or 2.20 [[Terabyte\|TB]] (2.20 × 10¹² 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=[[UEFI\|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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).		In the late 1990s, [[Intel]] developed a new partition table format as part of what eventually became the [[Unified Extensible Firmware Interface]] (UEFI). The GUID Partition Table is specified in chapter 5 of the UEFI 2.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=[[UEFI\|www.uefi.org]]}}</ref>{{rp\|page=111}} GPT uses 64 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 [[ZiB]] (2<sup>64</sup> × 512{{nbh}}bytes) or 9.44 [[Zettabyte\|ZB]] (9.44 × 10²¹ bytes).<ref name="UEFIFAQ" /> For disks with 4,096{{nbh}}byte sectors the maximum size is 64 [[ZiB]] (2<sup>64</sup> × 4,096{{nbh}}bytes) or 75.6 [[Zettabyte\|ZB]] (75.6 × 10²¹ bytes).