Partition type

Last updated

The partition type (or partition ID) in a partition's entry in the partition table inside a master boot record (MBR) is a byte value intended to specify the file system the partition contains or to flag special access methods used to access these partitions (e.g. special CHS mappings, LBA access, logical mapped geometries, special driver access, hidden partitions, secured or encrypted file systems, etc.).

Contents

Overview

Lists of assigned partition types to be used in the partition table in the MBR were originally maintained by IBM and Microsoft internally. When the market of PC operating systems and disk tools grew and liberated, other vendors had a need to assign special partition types to their products as well. As Microsoft neither documented all partition types already assigned by them nor wanted to maintain foreign assignments, third parties started to simply assign partition types on their own behalf in a mostly uncoordinated trial-and-error manner. This led to various conflicting assignments sometimes causing severe compatibility problems between certain products. [1]

Several industry experts including Hale Landis, Ralf D. Brown, Matthias R. Paul, and Andries E. Brouwer in the 1990s started to research partition types and published (and later synchronized) partition type lists in order to help document the industry de facto standard and thereby reduce the risk of further conflicts. Some of them also actively helped to maintain software dealing with partitions to work with the updated lists, indicated conflicts, devised additional detection methods and work-arounds for vendors, or engaged in coordinating new non-conflictive partition type assignments as well.

It is up to an operating system's boot loader or kernel how to interpret the value. So the table specifies which operating systems or disk-related products introduced an ID and what file system or special partition type they mapped it to. Partitions with partition types unknown to the software should be treated as reserved but occupied disk storage space which should not be dealt with by the software, save for partition managers.

Local or Experimental Use

While the list is not officially maintained, [1] new assignments should be coordinated.

In particular temporary partition type assignments for local or experimental projects can utilize type 7Fh in order to avoid conflicts with already assigned types. This type was specially reserved for individual use as part of the Alternative OS Development Partition Standard (AODPS) initiative since 2002. [2]

List of partition IDs

This is a list of known master boot record partition types on IBM PC compatible computers:

Partition IDOccurrenceAccessBootableTypeOriginSupported byDescription
00h MBR, EBR NoFree IBM AllEmpty partition entry
01hMBR, EBR CHS, LBA x86, 68000, 8080/Z80File systemIBM DOS  2.0+ FAT12 as primary partition in first physical 32 MB of disk or as logical drive anywhere on disk (else use 06h instead) [3] [4] [5]
02hMBRCHSx86, 68000, Z8000, PDP-11File system Microsoft, SCO XENIX XENIX root (see 03h and FFh ) [3]
03hMBRCHSNoFile systemMicrosoft, SCOXENIXXENIX usr (see 02h and FFh ) [3]
04hMBR, EBRCHS, LBAx86, 68000, 8080/Z80File systemMicrosoftDOS 3.0+ FAT16 with less than 65,536 sectors (32 MB). As primary partition it must reside in first physical 32 MB of disk, or as logical drive anywhere on disk (else use 06h instead). [3] [4] [5]
05hMBR, EBRCHS, (LBA)No, AAP ContainerIBMSome versions of DOS 3.2, DOS 3.3+ Extended partition with CHS addressing. It must reside within the first physical 8 GB of disk, else use 0Fh instead (see 0Fh , 85h , C5h , D5h ) [3] [4] [5]
06hMBR, EBRCHS, LBAx86File system Compaq DOS 3.31+ FAT16B with 65,536 or more sectors. It must reside within the first 8 GB of disk unless used for logical drives in an 0Fh extended partition (else use 0Eh instead). Also used for FAT12 and FAT16 volumes in primary partitions if they are not residing in first physical 32 MB of disk. [nb 1] [3] [4] [5]
07hMBR, EBRCHS, LBAx86File systemMicrosoft, IBM OS/2  1.2+ IFS
MBR, EBRCHS, LBA286File systemIBMOS/2 1.2+, Windows NT HPFS [3]
MBR, EBRCHS, LBA386File systemMicrosoft Windows NT NTFS [4] [5]
MBR, EBRCHS, LBAYesFile systemMicrosoft Windows Embedded CE exFAT
File system Quantum Software Systems QNX 2QNX "qnx" (7) (pre-1988 only) [6] [nb 2]
08hMBRCHSx86File system Commodore Commodore MS-DOS 3.x Logical sectored FAT12 or FAT16 [nb 3]
CHSx86File systemIBMOS/2 1.0-1.3OS/2 (FAT?)
File systemIBM AIX AIX boot/split
File systemQuantum Software SystemsQNX 1.x/2.xQNX "qny" (8) [6] [nb 2]
Container Dell Partition spanning multiple drives
09hFile systemIBMAIXAIX data/boot
File systemQuantum Software SystemsQNX 1.x/2.xQNX "qnz" (9) [6] [nb 2]
MBRCHS286File system Mark Williams Company Coherent Coherent file system
MBRFile system Microware OS-9 OS-9 RBF
0AhService PowerQuest, IBMOS/2OS/2 Boot Manager [nb 4]
SwapMark Williams CompanyCoherentCoherent swap partition
0BhMBR, EBRCHS, LBAx86File systemMicrosoftDOS 7.1+ FAT32 with CHS addressing [4] [5]
0ChMBR, EBRLBAx86File systemMicrosoftDOS 7.1+ FAT32 with LBA [4] [5]
0EhMBR, EBRLBAx86File systemMicrosoftDOS 7.0+FAT16B with LBA [4] [5]
0FhMBR, EBRLBANo, AAPContainerMicrosoftDOS 7.0+ Extended partition with LBA (see 05h and CFh ) [4] [5]
11hMBRCHSx86File system Leading Edge Leading Edge MS-DOS 3.x Logical sectored FAT12 or FAT16 [nb 3]
Hidden FSIBMOS/2 Boot ManagerHidden FAT12 (corresponds with 01h ) [nb 4]
12hMBRCHS, LBAx86Service FSCompaqConfiguration partition (bootable FAT with MS-DOS [4] [5] [7] ); Recovery partition (bootable FAT32 with Windows setup [8] )
MBRx86Service Gang of Nine EISA machinesEISA configuration utility for the system [4] [5]
HibernationCompaq Compaq Contura Hibernation partition [7]
MBRx86Service FS NCR Diagnostics and firmware partition (bootable FAT) [7]
MBRx86Service FS Intel Service partition (bootable FAT) [7] (see 98h )
Service FSIBMRescue and Recovery partition [7]
14hFile system AST AST MS-DOS 3.x Logical sectored FAT12 or FAT16 [nb 3] (see AST MBR)
x86, 68000, 8080/Z80Hidden FSIBMOS/2 Boot ManagerHidden FAT16 (corresponds with 04h ) [nb 4]
LBAx86File systemLasse Krogh ThygesenMaverick OSOmega file system [9]
15hNo, AAPHidden containerIBMOS/2 Boot ManagerHidden extended partition with CHS addressing (corresponds with 05h ) [nb 4]
LBANoSwapLasse Krogh ThygesenMaverick OSSwap [9]
16hx86, 68000, 8080/Z80Hidden FSIBMOS/2 Boot ManagerHidden FAT16B (corresponds with 06h ) [nb 4]
17hHidden FSIBMOS/2 Boot ManagerHidden IFS (corresponds with 07h ) [nb 4]
Hidden HPFS (corresponds with 07h ) [nb 4]
Hidden NTFS (corresponds with 07h ) [nb 4]
Hidden exFAT (corresponds with 07h ) [nb 4]
18hNoHibernationASTAST WindowsAST Zero Volt Suspend or SmartSleep partition
19hWillow SchlangerWillowtech Photon coSWillowtech Photon coS (see 20h )
1BhHidden FSIBMOS/2 Boot ManagerHidden FAT32 (corresponds with 0Bh ) [nb 4]
1ChHidden FSIBMOS/2 Boot ManagerHidden FAT32 with LBA (corresponds with 0Ch ) [nb 4]
Service FSASUSASUS eRecoveryASUS recovery partition (Hidden FAT32 with LBA, see 0Ch ) [10]
1EhHidden FSIBMOS/2 Boot ManagerHidden FAT16 with LBA (corresponds with 0Eh ) [nb 4]
1FhMBR, EBRLBAHidden containerIBMOS/2 Boot ManagerHidden extended partition with LBA addressing (corresponds with 0Fh ) [nb 4]
20h ?File systemMicrosoft Windows Mobile Windows Mobile update XIP
File systemWillow SchlangerWillowsoft Overture File System (OFS1) (see 19h )
21hMBR ? Hewlett-Packard HP Volume Expansion [nb 5]
File systemDave PoirierOxygenFSo2 (Oxygen File System) (see 22h )
22hContainerDave PoirierOxygenOxygen Extended Partition Table (see 21h )
23hYesFile systemMicrosoftWindows MobileWindows Mobile boot XIP
24hMBRCHSx86File system NEC NEC MS-DOS 3.30 Logical sectored FAT12 or FAT16 [11] [nb 3] (see NEC MBR)
27hService FS Microsoft Windows Windows Recovery Environment (RE) partition (hidden NTFS partition type 07h ) [12]
MBRLBAYesService FS Acer D2D eRecoveryRescue partition (Hidden NTFS labeled "PQService", corresponds to 07h )
YesServiceMikroTikLinux (RouterBOARD 500)RooterBOOT kernel partition (contains a raw ELF Linux kernel, no file system)
2AhFile systemKurt Skauen AtheOS AtheOS file system (AthFS, AFS) (an extension of BFS, see 2Bh and EBh )
MBR, EBRLBAx86File systemReserved (see CAh )
2BhFile systemKristian van der Vliet SyllableOS SyllableSecure (SylStor), a variant of AthFS (an extension of BFS, see 2Ah and EBh )
30hMBRCHSx86File system Digital Research Personal CP/M-86 Found in some OEM Siemens systems instead of DBh . [13] Filesystem parameters are in the following sector (LBA 1), not the partition itself.
31hMicrosoft, IBMReserved
33hMicrosoft, IBMReserved
34hMicrosoft, IBMReserved
35hMBR, EBRCHS, LBANoFile systemIBMOS/2 Warp Server / eComStation JFS (OS/2 implementation of AIX Journaling File system)
36hMicrosoft, IBMReserved
38hFile systemTimothy Williams THEOS THEOS version 3.2, 2 GB partition
39hContainer Bell Labs Plan 9 Plan 9 edition 3 partition (sub-partitions described in second sector of partition)
File systemTimothy WilliamsTHEOSTHEOS version 4 spanned partition
3AhFile systemTimothy WilliamsTHEOSTHEOS version 4, 4 GB partition
3BhContainerTimothy WilliamsTHEOSTHEOS version 4 extended partition
3ChService PowerQuest PartitionMagic PqRP (PartitionMagic or DriveImage in progress) [14]
3DhHidden FSPowerQuestPartitionMagicHidden NetWare
40hPICK Systems PICK PICK R83
VenturCom Venix Venix 80286
41hYesPersonal RISCPersonal RISC Boot
Linux LinuxOld Linux/Minix (disk shared with DR DOS 6.0) (corresponds with 81h )
PowerPCPowerPCPowerPCPPC PReP (Power PC Reference Platform) Boot
42hSecured FS Peter Gutmann SFSSecure File system (SFS)
NoLinuxLinuxOld Linux swap (disk shared with DR DOS 6.0) (corresponds with 82h )
ContainerMicrosoftWindows 2000, XP, etc. Dynamic extended partition marker [4] [5]
43hYesFile systemLinuxLinuxOld Linux native (disk shared with DR DOS 6.0) (corresponds with 83h )
44hWildfile GoBack Norton GoBack, WildFile GoBack, Adaptec GoBack, Roxio GoBack
45hCHS Priam Priam (see also 5Ch )
MBRCHSYesBoot-USBoot-US boot manager (1 cylinder)
Jochen Liedtke, GMD EUMEL/ELAN EUMEL/ELAN (L2)
46hJochen Liedtke, GMDEUMEL/ELANEUMEL/ELAN (L2)
47hJochen Liedtke, GMDEUMEL/ELANEUMEL/ELAN (L2)
48hJochen Liedtke, GMDEUMEL/ELANEUMEL/ELAN (L2), ERGOS L3
4AhMBRYesNick RobertsAdaOSAquila (see 7Fh )
MBR, EBRCHS, LBANoFile systemMark AitchisonALFS/THINALFS/THIN advanced lightweight file system for DOS
4Ch ETH Zürich ETH Oberon Aos (A2) file system (76)
4Dh Quantum Software Systems QNX 4.x, NeutrinoPrimary QNX POSIX volume on disk (77) [6] [nb 2]
4EhQuantum Software SystemsQNX 4.x, NeutrinoSecondary QNX POSIX volume on disk (78) [6] [nb 2]
4FhQuantum Software SystemsQNX 4.x, NeutrinoTertiary QNX POSIX volume on disk (79) [6] [nb 2]
YesETH ZürichETH OberonBoot / native file system (79)
50hETH ZürichETH OberonAlternative native file system (80)
NoOntrack Disk Manager 4Read-only partition (old)
LynxOS Lynx RTOS
Novell
51hNovell
NoOntrackDisk Manager 4-6Read-write partition (Aux 1)
52hMBRCHSFile system Digital Research CP/M-80 CP/M-80
Microport System V/AT, V/386
53hOntrackDisk Manager 6Auxiliary 3 (WO)
54hOntrackDisk Manager 6Dynamic Drive Overlay (DDO)
55hMicroHouse / StorageSoftEZ-DriveEZ-Drive, Maxtor, MaxBlast, or DriveGuide INT 13h redirector volume
56h AT&T AT&T MS-DOS 3.x Logical sectored FAT12 or FAT16 [nb 3]
MicroHouse / StorageSoftEZ-DriveDisk Manager partition converted to EZ-BIOS
Golden BowVFeatureVFeature partitioned volume
57hMicroHouse / StorageSoftDrivePro
NovellVNDI partition
59hMBR, EBRCHS, LBAYesFile systemYoctoyocOSyocFS
5ChCHSContainer Priam EDISK Priam EDisk Partitioned Volume (see also 45h )
61hMBRCHSHidden FSStorage DimensionsSpeedStorHidden FAT12 (corresponds to E1h ) [nb 6]
63hCHSFile systemAT&TSCO Unix, ISC, UnixWare, AT&T System V/386, ix, MtXinu BSD 4.3 on Mach
CHSYesFile system Mach and BSD [15] [16] GNU/HurdOld GNU/Hurd with UFS [15] support (corresponds with 83h )
MBRCHSHidden FSStorage DimensionsSpeedStorHidden read-only FAT12 (corresponds to E3h ) [nb 6]
64h ?Storage DimensionsSpeedStorHidden FAT16 (corresponds to E4h ) [nb 6]
File system Novell NetWare NetWare File System 286/2 [3]
Secured FSSolomonPC-ARMOUR
65hFile systemNovellNetWare NetWare File System 386
66h ?NovellNetWareStorage Management Services (SMS)
MBRCHSHidden FSStorage DimensionsSpeedStorHidden read-only FAT16 (corresponds to E6h ) [nb 6]
67h ?NovellNetWareWolf Mountain cluster
68h ?NovellNetWare
69h ?NovellNetWare 5
 ?NovellNetWare Novell Storage Services (NSS)
6ChMBRCHS, LBAx86Container DragonFly BSD BSD BSD slice (DragonFly BSD) [17]
70hServiceDiskSecureDiskSecure multiboot
71hMicrosoft, IBMReserved
72hMBR, EBRCHSx86Policy FSAPTI conformant systemsAPTI alternative FAT12 (CHS, SFN) (corresponds with 01h )
File systemNordierUnix V7/x86V7/x86
73hMicrosoft, IBMReserved
74hMBRCHSHidden FSStorage DimensionsSpeedStorHidden FAT16B (corresponds to F4h ) [nb 6]
75hFile systemIBM PC/IX [3]
76hStorage DimensionsSpeedStorHidden read-only FAT16B (corresponds to F6h ) [nb 6]
77hFile systemNovellVNDI, M2FS, M2CS
78hYesFile systemGeurt Vos XOSL bootloader file system
79hMBR, EBRCHSx86Policy FSAPTI conformant systemsAPTI alternative FAT16 (CHS, SFN) (corresponds with 04h )
7AhMBR, EBRLBAx86Policy FSAPTI conformant systemsAPTI alternative FAT16 (LBA, SFN) (corresponds with 0Eh )
7BhMBR, EBRCHSx86Policy FSAPTI conformant systemsAPTI alternative FAT16B (CHS, SFN) (corresponds with 06h )
7ChMBR, EBRLBAx86Policy FSAPTI conformant systemsAPTI alternative FAT32 (LBA, SFN) (corresponds with 0Ch )
7DhMBR, EBRCHSx86Policy FSAPTI conformant systemsAPTI alternative FAT32 (CHS, SFN) (corresponds with 0Bh )
7EhMBR, EBRNoCacheRomex SoftwarePrimoCacheLevel 2 cache
7FhMBR, EBRAlternative OS Development Partition Standard Reserved for individual or local use and temporary or experimental projects [2]
80hFile system Andrew Tanenbaum Minix 1.1-1.4a MINIX file system (old)
81hFile systemAndrew TanenbaumMinix 1.4b+MINIX file system (corresponds with 41h )
82hNoSwapLinuxLinux Linux swap space (corresponds with 42h )
NoSwapLinuxGNU/Hurd GNU/Hurd (Hurd uses the same Linux swap file system)
x86Container Sun Microsystems Solaris x86 (for Sun disklabels up to 2005) (see BFh )
83hYesFile systemLinuxLinuxAny native Linux file system (see 93h , corresponds with 43h )
YesFile systemLinuxGNU/Hurd GNU/Hurd (Hurd and GRUB use the same Linux ext2 file system to run and it no longer supports UFS [15] file system, corresponds with 63h )
84hNoHibernationMicrosoft ? APM hibernation (suspend to disk, S2D) [5] [7] [18]
Hidden FSIBMOS/2Hidden C: (FAT16)(corresponds to either 04h or 06h)
HibernationIntelRapid Start technologyRapid Start hibernation data [19] (possibly iFFS; possibly used for Intel SRT SSD cache as well)
85hNo, AAPContainerLinuxLinuxLinux extended [20] (corresponds with 05h )
86hFile systemMicrosoftWindows NT 4 Server Fault-tolerant FAT16B mirrored volume set (see B6h and C6h , corresponds with 06h ) [4] [5]
ServiceLinuxLinuxLinux RAID superblock with auto-detect (old) (see FDh )[ citation needed ]
87hFile systemMicrosoftWindows NT 4 ServerFault-tolerant HPFS/NTFS mirrored volume set (see B7h and C7h , corresponds with 07h ) [4] [5]
88hServiceLinuxLinuxLinux plaintext partition table
8AhServiceMartin KiewitzAirBootAirBoot is a track0 Boot Manager with on-the-fly partition detection [21]
8BhFile systemMicrosoftWindows NT 4 ServerLegacy fault-tolerant FAT32 mirrored volume set (see BBh and CBh , corresponds with 0Bh ) [4]
8ChFile systemMicrosoftWindows NT 4 ServerLegacy fault-tolerant FAT32 mirrored volume set (see BCh and CCh , corresponds with 0Ch ) [4]
8DhMBR, EBRCHS, LBAx86, 68000, 8080/Z80Hidden FS FreeDOS Free FDISK Hidden FAT12 (corresponds with 01h ) [nb 7]
8EhContainerLinuxLinux Linux LVM since 1999 (see FEh )[ citation needed ]
90hMBR, EBRCHS, LBAx86, 68000, 8080/Z80Hidden FSFreeDOSFree FDISKHidden FAT16 (corresponds with 04h ) [nb 7]
91hMBR, EBRCHS, LBANo, AAPHidden containerFreeDOSFree FDISKHidden extended partition with CHS addressing (corresponds with 05h ) [nb 7]
92hMBR, EBRCHS, LBAx86Hidden FSFreeDOSFree FDISKHidden FAT16B (corresponds with 06h ) [nb 7]
93hFile system Andrew S. Tanenbaum Amoeba Amoeba native file system
Hidden FSLinuxHidden Linux file system (see 83h )
94hServiceAndrew S. TanenbaumAmoebaAmoeba bad block table
95hFile systemMITEXOPCEXOPC native
96hFile system ?CHRP ISO-9660 file system [22]
97hMBR, EBRCHS, LBAx86Hidden FSFreeDOSFree FDISKHidden FAT32 (corresponds with 0Bh ) [nb 7]
98hMBR, EBRLBAx86Hidden FSFreeDOSFree FDISKHidden FAT32 (corresponds with 0Ch ) [nb 7]
MBRCHS, LBAx86Service FSDatalightROM-DOSService partition (bootable FAT) ROM-DOS SuperBoot (see 12h )
MBRCHS, LBAx86Service FSIntel ?Service partition (bootable FAT) [7] (see 12h )
99hFile system ? ?Early Unix[ citation needed ]
9AhMBR, EBRLBAx86Hidden FSFreeDOSFree FDISKHidden FAT16 (corresponds with 0Eh ) [nb 7]
9BhMBR, EBRLBANo, AAPHidden containerFreeDOSFree FDISKHidden extended partition with LBA (corresponds with 0Fh ) [nb 7]
9EhFile systemAndy Valencia VSTa [ citation needed ]
File systemAndy ValenciaForthOSForthOS (eForth port) [23]
9Fh ? ?BSD/OS 3.0+, BSDI (see B7h and B8h )
A0hMBRService FS Hewlett-Packard  ?Diagnostic partition for HP laptops [7]
HibernationPhoenix, IBM, Toshiba, Sony ?Hibernate partition [5]
A1h ?Hewlett-PackardHP Volume Expansion [nb 5]
HibernationPhoenix, NEC ?Hibernate partition
A2hMBRCHS, LBAARMImage Altera Cyclone VHard Processor System (HPS) ARM preloader [24]
A3h ?Hewlett-PackardHP Volume Expansion [nb 5]
A4h ?Hewlett-PackardHP Volume Expansion [nb 5]
A5hMBRContainer FreeBSD BSD BSD slice (BSD/386, 386BSD, NetBSD (before 1998-02-19), FreeBSD) [25]
A6h ?Hewlett-PackardHP Volume Expansion [nb 5]
MBRContainer OpenBSD OpenBSD OpenBSD slice
A7h386File system NeXT NeXTSTEP[ citation needed ]
A8hFile system Apple Darwin, Mac OS XApple Darwin, Mac OS X UFS [nb 8]
A9hMBRContainer NetBSD NetBSD NetBSD slice [26]
AAhMBRCHS ?File system Olivetti MS-DOSOlivetti MS-DOS FAT12 (1.44 MB) (corresponds with 06h )
ABhYesServiceAppleDarwin, Mac OS XApple Darwin, Mac OS X boot [nb 8]
File systemStanislav KarchebnyGO! OSGO!
AChYesServiceAppleDarwin, Mac OS XApple RAID, Mac OS X RAID [nb 8]
ADhFile systemBen Avison, AcornRISC OS ADFS / FileCore format
AEhx86File systemFrank BarrusShagOSShagOS file system
AFh ?File systemAppleMac OS X HFS and HFS+ [nb 8]
NoSwapFrank BarrusShagOSShagOS swap
B0hMBRCHS, LBAx86BlockerStar-ToolsBoot-StarBoot-Star dummy partition
B1h ? Hewlett-Packard HP Volume Expansion [nb 5]
File system QNX Software Systems QNX 6.x QNX Neutrino power-safe file system [nb 2]
B2hFile systemQNX Software SystemsQNX 6.xQNX Neutrino power-safe file system [nb 2]
B3h ? Hewlett-Packard HP Volume Expansion [nb 5]
File systemQNX Software SystemsQNX 6.xQNX Neutrino power-safe file system [nb 2]
B4h ?Hewlett-PackardHP Volume Expansion [nb 5]
B6h ?Hewlett-PackardHP Volume Expansion [nb 5]
EBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant FAT16B mirrored master volume (see C6h and 86h , corresponds with 06h )
B7hFile systemBSDI (before 3.0)BSDI native file system / swap (see B8h and 9Fh )
EBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant HPFS/NTFS mirrored master volume (see C7h and 87h , corresponds with 07h )
B8hFile systemBSDI (before 3.0)BSDI swap / native file system (see B7h and 9Fh )
BBhHidden FS PhysTechSoft, Acronis, SWsoft BootWizard, OS Selector PTS BootWizard 4 / OS Selector 5 for hidden partitions other than 01h , 04h , 06h , 07h , 0Bh , 0Ch , 0Eh and unformatted partitions
MBRService FSAcronis Acronis True Image OEM Secure Zone (corresponds to BCh )
EBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant FAT32 mirrored master volume (see CBh and 8Bh , corresponds with 0Bh )
BChEBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant FAT32 mirrored master volume (see CCh and 8Ch , corresponds with 0Ch )
MBRLBAService FSAcronisAcronis True Image Acronis Secure Zone
MBR, EBRService FS Paragon Software Group Backup CapsuleBackup Capsule[ citation needed ]
BDhFile system ?BonnyDOS/286[ citation needed ]
BEhYesFile system Sun Microsystems Solaris 8Solaris 8 boot
BFhx86ContainerSun MicrosystemsSolarisSolaris x86 (for Sun disklabels, since 2005) (see 82h )
C0hMBRCHS, LBAx86Secured container Novell, IMS DR-DOS, Multiuser DOS, REAL/32 Secured FAT partition (smaller than 32 MB) [nb 9] [nb 10]
C1hMBR, EBRCHS, LBAx86Secured FS Digital Research DR DOS 6.0+Secured FAT12 (corresponds with 01h ) [nb 9]
C2hYesHidden FSBlueSky InnovationsPower BootHidden Linux native file system
C3hNoHidden swapBlueSky InnovationsPower BootHidden Linux swap
C4hMBR, EBRCHS, LBAx86Secured FSDigital ResearchDR DOS 6.0+Secured FAT16 (corresponds with 04h ) [nb 9]
C5hMBR, EBRCHS, LBANo, AAPSecured containerDigital ResearchDR DOS 6.0+Secured extended partition with CHS addressing (corresponds with 05h ) [nb 9]
C6hMBR, EBRCHS, LBAx86Secured FSDigital ResearchDR DOS 6.0+Secured FAT16B (corresponds with 06h ) [nb 9]
EBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant FAT16B mirrored slave volume (see B6h and 86h , corresponds with 06h )
C7hMBRYesFile systemSyrinxSyrinx boot
EBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant HPFS/NTFS mirrored slave volume (see B7h and 87h , corresponds with 07h )
C8h ?Reserved for DR-DOS since 1997[ citation needed ]
C9h ?Reserved for DR-DOS since 1997[ citation needed ]
CAh ?Reserved for DR-DOS since 1997[ citation needed ]
CBhMBR, EBRCHS, LBAx86Secured FS Caldera DR-DOS 7.0xSecured FAT32 (corresponds with 0Bh ) [nb 9]
EBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant FAT32 mirrored slave volume (see BBh and 8Bh , corresponds with 0Bh )
CChMBR, EBRLBAx86Secured FSCalderaDR-DOS 7.0xSecured FAT32 (corresponds with 0Ch ) [nb 9]
EBRFile systemMicrosoftWindows NT 4 ServerCorrupted fault-tolerant FAT32 mirrored slave volume (see BCh and 8Ch , corresponds with 0Ch )
CDhNoServiceConvergent Technologies, UnisysCTOSMemory dump (see DDh and DBh )
MBRLBAx86File system openSUSE LinuxopenSUSE ISOHybrid ISO9660 partition (from openSUSE Leap "Live" x86 images) [27]
CEhMBR, EBRLBAx86Secured FSCalderaDR-DOS 7.0xSecured FAT16B (corresponds with 0Eh ) [nb 9]
CFhMBR, EBRLBANo, AAPSecured containerCalderaDR-DOS 7.0xSecured extended partition with LBA (corresponds with 0Fh ) [nb 9]
D0hMBRCHS, LBA386Secured container Novell, IMS Multiuser DOS, REAL/32Secured FAT partition (larger than 32 MB) [nb 11] [nb 10]
D1hMBR, EBRCHS386Secured FSNovellMultiuser DOSSecured FAT12 (corresponds with 01h ) [nb 11]
D4hMBR, EBRCHS386Secured FSNovellMultiuser DOSSecured FAT16 (corresponds with 04h ) [nb 11]
D5hMBR, EBRCHSNoSecured containerNovellMultiuser DOSSecured extended partition with CHS addressing (corresponds with 05h ) [nb 11]
D6hMBR, EBRCHS386Secured FSNovellMultiuser DOSSecured FAT16B (corresponds with 06h ) [nb 11]
D8hMBRCHSFile system Digital Research CP/M-86 CP/M-86 (see DBh )[ citation needed ]
DAhNoServiceJohn HardinNon-file system data
Secured FS DataPower Powercopy BackupShielded disk
DBhMBRCHSx86File system Digital Research CP/M-86, Concurrent CP/M-86, Concurrent DOS [13] (see D8h ) [3]
 ? Convergent Technologies, Unisys CTOS  ? (see CDh and DDh )[ citation needed ]
x86ServiceKDG TelemetryD800boot image for x86 supervisor CPU (SCPU) module
MBRCHS, LBAx86Service FS Dell DRMK FAT32 system restore partition (DSR) (see DEh )
DDhNoServiceConvergent Technologies, UnisysCTOSHidden memory dump (see CDh and DBh )
DEhMBRCHS, LBAx86Hidden FS Dell FAT16 utility/diagnostic partition [5] [7] [28]
DFh ? Data General DG/UX DG/UX virtual disk manager[ citation needed ]
MBRBlocker TeraByte Unlimited BootIt EMBRM[ citation needed ]
 ? ?Aviion[ citation needed ]
E0hFile system STMicroelectronics ST AVFS
E1hMBRCHSFile systemStorage DimensionsSpeedStorFAT12 (≤16 MB) (corresponds to 01h ) [nb 6]
E3hFile systemStorage DimensionsSpeedStorRead-only FAT12 (corresponds to E1h ) [nb 6]
E4hMBRCHSFile systemStorage DimensionsSpeedStorFAT16 (≤32 MB) (corresponds to 04h ) [nb 6]
E5hMBRCHSx86File system Tandy Tandy MS-DOS Logical sectored FAT12 or FAT16 [nb 3]
E6hFile SystemStorage DimensionsSpeedStorRead-only FAT16 (corresponds to E4h ) [nb 6]
E8hMBR, EBRCHS, LBANoServiceLinux LUKS Linux Unified Key Setup [29]
EBh386File system Be Inc. BeOS, Haiku BFS (see 2Ah and 2Bh )
EChFile systemRobert Szeleney SkyOS SkyFS
EDhMBR, EBRCHS, LBAx86ServiceMatthias R. PaulSprytixEDC loader
MBRCHS, LBAx86 Hewlett-Packard EFIWas proposed for GPT hybrid MBR [nb 12]
EEhMBRNoBlocker Microsoft EFI GPT protective MBR [1] [5] (see EFh )
EFhMBRService FS Intel EFI EFI system partition. Can be a FAT12, FAT16, FAT32 (or other) file system [5] (see EEh )
F0hCHSServiceLinux PA-RISC Linux boot loader; must reside in first physical 2 GB
F2hMBRCHSx86File system Sperry IT, Unisys, Digital Research Sperry IT MS-DOS 3.x, Unisys MS-DOS 3.3, Digital Research DOS Plus  2.1 Logical sectored FAT12 or FAT16 [nb 3] secondary partition
F4hMBRCHSFile systemStorage DimensionsSpeedStorFAT16B (corresponds to 06h ) [nb 6]
File system ?PrologueSingle volume partition for NGF or TwinFS
F5hContainer ?PrologueMD0-MD9 multi volume partition for NGF or TwinFS
F6hMBRFile systemStorage DimensionsSpeedStorRead-only FAT16B (corresponds to F4h ) [nb 6]
F7hFile systemNatalia PortilloO.S.G.EFAT
File systemDDRdriveX1 Solid State file system
F8hMBRServiceArmArm EBBR 1.0 [30] Protective partition for the area containing system firmware
F9hCacheALC PressLinuxpCache ext2/ext3 persistent cache [31]
FBhNoFile system VMware VMware ESX VMware VMFS file system partition
FChNoSwapVMwareVMware ESXVMware swap / VMKCORE kernel dump partition
FDhServiceLinuxLinuxLinux RAID superblock with auto-detect (see 86h )
FEhServiceIBMPS/2 PS/2 IML partition [5] [7]
MBRCHS, LBAx86Service FSIBMPS/2PS/2 recovery partition (FAT12 reference disk floppy image), (corresponds with 01h if activated, all other partitions +10h then) [5]
ServiceLinuxLinuxOld Linux LVM (see 8Eh )
FFhMBRCHSNoService Microsoft XENIXXENIX bad block table (see 02h and 03h ) [3]

See also

Notes

  1. MS-DOS/PC DOS 2.0-3.1 cannot cope with hard disk partitions outside the first 32 MB of the disk. Therefore, FAT12 and FAT16 volumes in primary partitions physically residing outside this area must not use partition IDs 01h and 04h , even if they were otherwise small enough to be recognized by these DOS versions. In order to hide these volumes from these DOS issues 06h can be used instead. DOS distinguishes FAT types by their number of clusters, not by their partition ID, therefore, this does not cause any problems for DOS 3.31 and higher except for a possibly wrong file system type display in FDISK.
  2. 1 2 3 4 5 6 7 8 9 QNX partition IDs 07h , 08h , 09h , 4Dh (77), 4Eh (78), 4Fh (79), as well as B1h (177), B2h (178) and B3h (179).
  3. 1 2 3 4 5 6 7 Known partition IDs for logical sectored FATs include: 08h (Commodore MS-DOS 3.x), 11h (Leading Edge MS-DOS 3.x), 14h (AST MS-DOS 3.x), 24h (NEC MS-DOS 3.30), 56h (AT&T MS-DOS 3.x), E5h (Tandy MS-DOS), F2h (Sperry IT MS-DOS 3.x, Unisys MS-DOS 3.3 also used by Digital Research DOS Plus 2.1). While non-standard and sub-optimal these FAT variants are perfectly valid according to the specifications of the file system itself, although default issues of MS-DOS / PC DOS 3.x were not able to cope with them. Most of these vendor specific FAT12 and FAT16 variants can be mounted by more flexible file system implementations in operating systems such as DR-DOS simply by changing the partition ID to one of the recognized types. Also, if they no longer need to be recognized by their original operating systems, existing partitions can be "converted" into FAT12 and FAT16 volumes compliant with versions of MS-DOS/PC DOS like 5.0-6.3, which do not support logical sector sizes different from 512 bytes, by switching to a BPB with 32-bit entry for the number of sectors, as introduced since DOS 3.31, keeping the cluster size and reducing the logical sector size in the BPB down to 512 bytes, while at the same time increasing the counts of logical sectors per cluster, reserved logical sectors, total logical sectors, and logical sectors per FAT by the same factor.
  4. 1 2 3 4 5 6 7 8 9 10 11 12 13 Used by OS/2 Boot Manager: 0Ah , 11h , 14h , 15h , 16h , 17h , 1Bh , 1Ch , 1Eh , 1Fh .
  5. 1 2 3 4 5 6 7 8 9 HP Volume Expansion is a variant of SpeedStor and uses partition IDs 21h , A1h , A3h , A4h , A6h , B1h , B3h , B4h , and B6h .
  6. 1 2 3 4 5 6 7 8 9 10 11 12 SpeedStor is an extended storage support driver for DOS for IBM PC/XT (v. 6.03) and IBM PC/AT (v. 6.5). Its custom partition types are E1h , E4h and F4h which can be marked read-only (becoming E3h , E6h , F6h ), hidden ( 61h , 64h , 74h ) or hidden read-only ( 63h , 66h , 76h ).
  7. 1 2 3 4 5 6 7 8 Used by Free FDISK of FreeDOS: 8Dh , 90h , 91h , 92h , 97h , 98h , 9Ah , 9Bh .
  8. 1 2 3 4 Apple Mac OS X uses partition IDs A8h , ABh , ACh , and AFh .
  9. 1 2 3 4 5 6 7 8 9 Versions of DR DOS 6.0 and higher use several of these partition IDs for secured FAT partitions with single-user security: C0h , C1h , C4h , C5h , C6h , CBh , CCh , CEh , CFh .
  10. 1 2 Versions of IMS REAL/32 use partition IDs C0h and D0h for multi-user security.
  11. 1 2 3 4 5 Versions of Multiuser DOS use these partition IDs for secured FAT partitions with multi-user security: D0h , D1h , D4h , D5h , D6h .
  12. Was suggested in now-superseded T13 EDD 4 proposal e09127r1 Archived 2017-08-19 at the Wayback Machine (2009). The successor e09127r3 Archived 2018-05-01 at the Wayback Machine (2010) now recommends to use a normal partition type (the one that a legacy OS would see) instead of this special value.

    Related Research Articles

    NT File System (NTFS) is a proprietary journaling file system developed by Microsoft in the 1990s.

    File Allocation Table (FAT) is a file system developed for personal computers and was the default filesystem for MS-DOS and Windows 9x operating systems. Originally developed in 1977 for use on floppy disks, it was adapted for use on hard disks and other devices. The increase in disk drives capacity required four major variants: FAT12, FAT16, FAT32, and ExFAT. FAT was replaced with NTFS as the default file system on Microsoft operating systems starting with Windows XP. Nevertheless, FAT continues to be used on flash and other solid-state memory cards and modules, many portable and embedded devices because of its compatibility and ease of implementation.

    <span class="mw-page-title-main">Disk partitioning</span> Creation of separate accessible storage areas on a secondary computer storage device

    Disk partitioning or disk slicing is the creation of one or more regions on secondary storage, so that each region can be managed separately. These regions are called partitions. It is typically the first step of preparing a newly installed disk after a partitioning scheme is chosen for the new disk before any file system is created. The disk stores the information about the partitions' locations and sizes in an area known as the partition table that the operating system reads before any other part of the disk. Each partition then appears to the operating system as a distinct "logical" disk that uses part of the actual disk. System administrators use a program called a partition editor to create, resize, delete, and manipulate the partitions. Partitioning allows the use of different filesystems to be installed for different kinds of files. Separating user data from system data can prevent the system partition from becoming full and rendering the system unusable. Partitioning can also make backing up easier. A disadvantage is that it can be difficult to properly size partitions, resulting in having one partition with too much free space and another nearly totally allocated.

    <span class="mw-page-title-main">Boot sector</span> Sector of a persistent data storage device

    A boot sector is the sector of a persistent data storage device which contains machine code to be loaded into random-access memory (RAM) and then executed by a computer system's built-in firmware.

    Disk formatting is the process of preparing a data storage device such as a hard disk drive, solid-state drive, floppy disk, memory card or USB flash drive for initial use. In some cases, the formatting operation may also create one or more new file systems. The first part of the formatting process that performs basic medium preparation is often referred to as "low-level formatting". Partitioning is the common term for the second part of the process, dividing the device into several sub-devices and, in some cases, writing information to the device allowing an operating system to be booted from it. The third part of the process, usually termed "high-level formatting" most often refers to the process of generating a new file system. In some operating systems all or parts of these three processes can be combined or repeated at different levels and the term "format" is understood to mean an operation in which a new disk medium is fully prepared to store files. Some formatting utilities allow distinguishing between a quick format, which does not erase all existing data and a long option that does erase all existing data.

    fdisk Command line utility of DOS and Microsoft Windows operating systems

    fdisk is a command-line utility for disk partitioning. It has been part of DOS, DR FlexOS, IBM OS/2, and early versions of Microsoft Windows, as well as certain ports of FreeBSD, NetBSD, OpenBSD, DragonFly BSD and macOS for compatibility reasons. Windows 2000 and its successors have replaced fdisk with a more advanced tool called diskpart.

    <span class="mw-page-title-main">Bootloader</span> Software responsible for starting the Computer and Load other software to the CPU memory

    A bootloader, also spelled as boot loader or called bootstrap loader, is a computer program that is responsible for booting a computer. If it also provides an interactive menu with multiple boot choices then it's often called a boot manager.

    In computing, the BIOS parameter block, often shortened to BPB, is a data structure in the volume boot record (VBR) describing the physical layout of a data storage volume. On partitioned devices, such as hard disks, the BPB describes the volume partition, whereas, on unpartitioned devices, such as floppy disks, it describes the entire medium. A basic BPB can appear and be used on any partition, including floppy disks where its presence is often necessary; however, certain filesystems also make use of it in describing basic filesystem structures. Filesystems making use of a BIOS parameter block include FAT12, FAT16, FAT32, HPFS, and NTFS. Due to different types of fields and the amount of data they contain, the length of the BPB is different for FAT16, FAT32, and NTFS boot sectors. Combined with the 11-byte data structure at the very start of volume boot records immediately preceding the BPB or EBPB, this is also called FDC descriptor or extended FDC descriptor in ECMA-107 or ISO/IEC 9293.

    This article details versions of MS-DOS, IBM PC DOS, and at least partially compatible disk operating systems. It does not include the many other operating systems called "DOS" which are unrelated to IBM PC compatibles.

    <span class="mw-page-title-main">GUID Partition Table</span> Computer disk partitioning standard

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

    An extended boot record (EBR), or extended partition boot record (EPBR), is a descriptor for a logical partition under the common DOS disk drive partitioning system. In that system, when one partition record entry in the master boot record (MBR) is designated an extended partition, then that partition can be subdivided into a number of logical partitions. The actual structure of that extended partition is described by one or more EBRs, which are located inside the extended partition. The first EBR will always be located on the first sector of the extended partition.

    A volume boot record (VBR) is a type of boot sector introduced by the IBM Personal Computer. It may be found on a partitioned data storage device, such as a hard disk, or an unpartitioned device, such as a floppy disk, and contains machine code for bootstrapping programs stored in other parts of the device. On non-partitioned storage devices, it is the first sector of the device. On partitioned devices, it is the first sector of an individual partition on the device, with the first sector of the entire device being a Master Boot Record (MBR) containing the partition table.

    In BSD-derived computer operating systems and in related operating systems such as SunOS, a disklabel is a record stored on a data storage device such as a hard disk that contains information about the location of the partitions on the disk. Disklabels were introduced in the 4.3BSD-Tahoe release. Disklabels are usually edited using the disklabel utility. In later versions of FreeBSD, this was renamed as bsdlabel.

    In Microsoft operating systems, when using basic disk partitioned with GUID Partition Table (GPT) layout, a basic data partition (BDP) is any partition identified with Globally Unique Identifier (GUID) of EBD0A0A2-B9E5-4433-87C0-68B6B72699C7.

    gpart is a software utility which scans a storage device, examining the data in order to detect partitions which may exist but are absent from the disk's partition tables. Gpart was written by Michail Brzitwa of Germany. The release on the author's website is now older than the releases some distributions are using. It appears that Michail Brzitwa does not actively maintain the code, instead the various distributions appear to maintain their own versions.

    In computing, label is a command included with some operating systems. It is used to create, change, or delete a volume label on a logical drive, such as a hard disk partition or a floppy disk. Used without parameters, label changes the current volume label or deletes the existing label.

    format (command)

    In computing, format is a command-line utility that carries out disk formatting. It is a component of various operating systems, including 86-DOS, MS-DOS, IBM PC DOS and OS/2, Microsoft Windows and ReactOS.

    <span class="mw-page-title-main">DOS</span> Family of IBM PC-compatible operating systems

    DOS is a family of disk-based operating systems for IBM PC compatible computers. The DOS family primarily consists of IBM PC DOS and a rebranded version, Microsoft's MS-DOS, both of which were introduced in 1981. Later compatible systems from other manufacturers include DR-DOS (1988), ROM-DOS (1989), PTS-DOS (1993), and FreeDOS (1998). MS-DOS dominated the IBM PC compatible market between 1981 and 1995.

    A master boot record (MBR) is a type of boot sector in the first block of partitioned computer mass storage devices like fixed disks or removable drives intended for use with IBM PC-compatible systems and beyond. The concept of MBRs was publicly introduced in 1983 with PC DOS 2.0.

    The FAT file system is a file system used on MS-DOS and Windows 9x family of operating systems. It continues to be used on mobile devices and embedded systems, and thus is a well-suited file system for data exchange between computers and devices of almost any type and age from 1981 through to the present.

    References

    1. 1 2 3 "Windows and GPT FAQ". Microsoft Developer Network . Microsoft. 2011-06-15. Retrieved 2011-07-24.
    2. 1 2 Martineau, Stéphane (2002-08-11). "Partition Type ID (The RESULTs)". alt.os.development. Retrieved 2017-08-20.
    3. 1 2 3 4 5 6 7 8 9 10 11 Chappell, Geoff (January 1994). Schulman, Andrew; Pedersen, Amorette (eds.). DOS Internals. The Andrew Schulman Programming Series (1st printing, 1st ed.). Addison Wesley Publishing Company. ISBN   978-0-201-60835-9. (xxvi+738+iv pages, 3.5"-floppy ) Errata:
    4. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 "Disk Concepts and Troubleshooting". Windows 2000 Server. Microsoft TechNet. 2008-09-11. Retrieved 2014-06-15.
    5. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 "Troubleshooting Disks and File Systems". Microsoft TechNet. 2005-11-05. Retrieved 2014-06-15.
    6. 1 2 3 4 5 6 QNX partition types
    7. 1 2 3 4 5 6 7 8 9 10 "Virtual Disk Service (VDS advanced clean method)". Microsoft Developer Network . Microsoft. 2011-09-07. Retrieved 2011-09-14.
    8. "Compaq Setup partition". NotebookReview. Retrieved 2018-02-14.
    9. 1 2 Thygesen, Lasse Krogh. "Maverick - The Operating System - File System Identifiers". www.maverick-os.dk. Retrieved 2017-08-19.
    10. "RE Creating Recovery Partition". ASUS Republic of Gamers. 2011-07-03.
    11. FYI - Installing DR DOS on NEC DOS 3.3 Partitions, Novell, 1993-01-05, FYI.M.1101, retrieved 2014-08-12
    12. "BIOS-Based Disk-Partition Configurations". Microsoft Developer Network . Microsoft. 2009-10-22. Retrieved 2011-07-24.
    13. 1 2 Elliott, John C. (1998). "CP/M-86 disc formats". Seasip.info.
    14. "About PqRP". HowToFixComputers. 2003-07-26. Archived from the original on 2013-01-25. Retrieved 2011-10-14.
    15. 1 2 3 "GNU Hurd: Remove UFS support".
    16. "GNU Hurd: NEWS 1995".
    17. DragonFly BSD commit 794d80a: Change legacy MBR partition type from 0xA5 to 0x6C
    18. "Drive Letters Assigned to Unsupported Partition Types". Microsoft Knowledge Base . Microsoft. 2007-02-27.
    19. Intel Rapid Start technology
    20. Andries Brouwer (2004). "Extended and logical partitions". Large Disk HOWTO. Retrieved 2011-07-19.
    21. AirBoot: Martin Kiewitz Boot Manager with on-the-fly partition detection
    22. "PowerPC Microprocessor Common Hardware Reference Platform (CHRP)" (PDF). 1996-09-23. Retrieved 2023-10-28.
    23. "ForthOS setup instructions". Archived from the original on 2017-07-19. Retrieved 2017-12-31.
    24. "Altera Cyclone V Device Handbook - Hard Processor System Technical Reference Manual" (PDF) (cv_5v4 ed.). Altera Corporation. 2014-06-30. Archived from the original (PDF) on 2014-09-07. Retrieved 2014-09-07.
    25. "Disk Organization". FreeBSD Handbook. FreeBSD. 2011. Retrieved 2011-07-30.
    26. "Partitions". The NetBSD Guide. NetBSD. 2011. Retrieved 2011-12-30.
    27. "openSUSE Leap 15.3 LIVE XFCE x86 ISO (first 512 bytes)". openSUSE. 2022-03-28. Retrieved 2022-04-05.[ permanent dead link ]
    28. "Create Multiple Partitions on a Device". Microsoft TechNet. 2009-01-07. Retrieved 2015-04-19.
    29. "/sbin/fdisk: add LUKS partition type code to fdisk". Debian. 2014-11-19. Archived from the original on 2019-05-03. Retrieved 2019-05-03.
    30. "Embedded Base Boot Requirements (EBBR) Specification Release v1.0". Arm Limited and Contributors. 2019-05-31. Retrieved 2020-06-18.
    31. Sawicki, Ed; May, David (2003-08-08). "Proposal for pCache". ALCPress.com. Accelerated Learning Center. Archived from the original on 2016-03-08. Retrieved 2016-11-29.

    Further reading