# Extended boot record

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 (and only 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 (and sometimes only) EBR will always be located on the first sector of the extended partition.
Unlike primary partitions, which are all described by a single partition table within the MBR, and thus limited in number, each EBR precedes the logical partition it describes. If another logical partition follows, then the first EBR will contain an entry pointing to the next EBR; thus, multiple EBRs form a linked list. This means the number of logical drives that can be formed within an extended partition is limited only by the amount of available disk space in the given extended partition.
While in Windows versions up to XP logical partitions within the extended partition were aligned following conventions called "drive geometry" or "CHS", since Windows Vista they are aligned to a 1-MiB boundary. Due to this difference in alignment, the Logical Disk Manager of XP (Disk Management) may delete these extended partitions without warning.

## EBR structure and values

EBRs have essentially the same structure as the MBR; except only the first two entries of the partition table are supposed to be used, besides having the mandatory boot record signature (or magic number) of 0xAA55 at the end of the sector. This 2-byte signature appears in a disk editor as 0x55 first and 0xAA last, because IBM-compatible PCs store hexadecimal words in little-endian order (see table below).

### Structures

Common Structure of Extended Boot Records: :
| Offsets within EBR sectors | Offsets within EBR sectors | Contents | Size |
| Hex | Dec | Contents | bytes |
| 000 – 1BD | 000 – 445 | Generally unused; normally filled with zeroes; may contain another boot loader i.e. a partition boot record, for example in conjunction with Advanced Active Partitions | 446 |
| 1BE – 1CD | 446 – 461 | Partition table's first entry | 16 |
| 1CE – 1DD | 462 – 477 | Partition table's second entry | 16 |
| 1DE – 1ED | 478 – 493 | Unused third entry filled with zeroes | 16 |
| 1EE – 1FD | 494 – 509 | Unused fourth entry filled with zeroes | 16 |
| 1FE - 1FF | 510 - 511 | Signature 55AAh in big-endian network order, same as little-endian 0xAA55. On disk: 0x55 at offset 510 and 0xAA at offset 511. | 2 |
| EBR, total size: 446 +(4×16) +2 = | EBR, total size: 446 +(4×16) +2 = | EBR, total size: 446 +(4×16) +2 = | 512 |
The IBM Boot Manager (included with OS/2 operating systems and some early versions of Partition Magic), adds at least one 9-byte entry (starting at offset 0x18A) to each EBR sector. The entry consists of a flag value byte (indicating if the partition is on the IBM Boot Manager menu) followed by an 8-byte ASCII string which is the name to be used on the menu. If the partition is not included on the boot menu (such as data only partitions), the flag byte is zero; in which case, the following 8-byte field may contain an ASCII representation of that partition's starting sector number (in hexadecimal).
Structure of an MBR or EBR 16-byte Partition Table Entry: :
| Offsets | within entry | Bytes | Description |
| Hex | Dec | Bytes | Description |
| 1?E$^1$ | 0 | 1 | Boot indicator (80h for active; otherwise, 00h) |
| 1?F - 1?1 | 1 – 3 | 3 | CHS cylinder-head-sector address: partition start |
| 1?2 | 4 | 1 | Partition type code |
| 1?3 - 1?5 | 5 – 7 | 3 | CHS cylinder-head-sector address: partition end |
| 1?6 - 1?9 | 8 – 11 | 4 | LBA logical block address: partition start |
| 1?A - 1?D | 12 – 15 | 4 | Partition size (in sectors) |
| $^1$: For 1?E read 1BE or 1CE to get the hex. offset of the first or second entry, respectively ||||
The partition type of an extended partition is 0x05 (CHS addressing) or 0x0F (LBA addressing). DR DOS 6.0 and higher support secured extended partitions using 0xC5, which are invisible to other operating systems. Since non-LBA-enabled versions of DR-DOS up to including 7.03 do not recognize the 0x0F partition type and other operating systems do not recognize the 0xC5 type, this can also be utilized to occupy space up to the first 8 GB of the disk for use under DR-DOS (for logical drives in secured or non-secured partitions), and still use 0x0F to allocate the remainder of the disk for LBA-enabled operating systems in a non-conflictive fashion. Similarly, Linux supports the concept of a second extended partition chain with type 0x85 — this type is hidden (unknown) for other operating systems supporting only one chain. Other extended partition types which may hold EBRs include the deliberately hidden types 0x15, 0x1F, 0x91 and 0x9B, the access-restricted types 0x5E and 0x5F, and the secured types 0xCF and 0xD5. However, these should be treated private to the operating systems and tools supporting them and should not be mounted otherwise.
The CHS addresses of a partition are hard to interpret without knowledge of the (virtual) disk geometry, because CHS to LBA translations are based on the number of heads and the number of sectors per track. However, the given LBA start address and the given partition size in sectors permit to calculate a disk geometry matching the given CHS addresses where that is at all possible. CHS addressing with 24 bits always uses 6 bits for up to 63 sectors per track (1...63), and INT 13h disk access generally uses 8 bits for up to 256 heads (0...255), leaving 10 bits for up to 1024 cylinders (0...1023). ATA CHS addresses always use 4 bits for up to 16 heads (0...15), this leaves 14 bits for up to 16,383 cylinders ({{{1}}}) in ATA-5 24 bits CHS address translations.

### Values

The following are general rules that apply only to values found in the 4-byte fields of an EBR's partition table entries (cf. tables above). These values depend upon the partitioning tool(s) used to create or alter them, and in fact, most operating systems that use the extended partitioning scheme (including Microsoft MS-DOS and Windows, and Linux) ignore the "partition size" value in entries which point to another EBR sector. One exception is that value must be one or greater for Linux operating systems.
The first entry of an EBR partition table points to the logical partition belonging to that EBR:
   * Starting sector = relative offset between this EBR sector and the first sector of the logical partition
       Note: This is often the same value for each EBR on the same hard disk; usually 63 for Windows XP or older.
   * Number of sectors = total count of sectors for this logical partition
       Note: Any unused sectors between EBR and logical drive are not considered part of the logical drive.
The second entry of an EBR partition table will contain zero-bytes if it's the last EBR in the extended partition; otherwise, it points to the next EBR in the EBR chain.
   * Partition type code = 0x05 (CHS addressing) or 0x0F (LBA addressing).
       in other words, the EBR must have a valid partition type, just as a partition must have a valid partition type.
   * Starting sector = relative address of next EBR within extended partition
       in other words: Starting sector = LBA address of next EBR minus LBA address of extended partition's first EBR
   * Number of sectors = total count of sectors for next logical partition, but count starts from the next EBR sector
       Note: Unlike the first entry in an EBR's partition table, this number of sectors count includes the next logical partition's EBR sector along with the other sectors in its otherwise unused track. (Compare Diagram 1 and 2 below.)
Remarks: The diagrams above are not to scale: The thin white lines between each "EBR" and its logical "partition" represent the remainder of an unused area usually 63 sectors in length; including the single EBR sector (shown at a greatly exaggerated size).
On some systems, a large gap of unused space may exist between the end of a logical partition and the next EBR, or between the last logical partition and the end of the whole extended partition itself, if any previously created logical partition has been deleted or resized (shrunk).
The interleaving of EBRs and partitions shown above is typical but not required. It is legitimate to have two or more consecutive EBRs followed by two or more regions of partition data.

### Naming

Linux and similar operating systems designate IDE hard disks as /dev/hda for the first hard disk, /dev/hdb for the second hard disk, and so on. Likewise SCSI and in later kernels also IDE and SATA hard disks are identified as /dev/sda for the first disk, etc.
The up to four partitions defined in the master boot record are designated as /dev/hda1 ... /dev/hda4 for /dev/hda. The fifth partition in this scheme, e.g., /dev/hda5, corresponds to the first logical drive. The sixth partition /dev/hda6 would then correspond to the second logical drive, or in other words, the extended partition containers are not counted. Only the outermost extended partition defined in the MBR (one of /dev/hda1 ... /dev/hda4) has a name in this scheme.
    Further information: Device_file § Linux_naming_conventions

## Examples

This shows an extended partition with 6,000 sectors and 3 logical partitions. Remark: Neither a tiny extended partition with only 3 MB nor a hard drive with 20 sectors per track are realistic but these values have been chosen to make this example more readable.

### Snapshot

The following output of a command line tool shows the layout of a disk with two logical drives. Details for the FAT and NTFS partitions stripped, the line annotated with Linux is /dev/hda6 with an extended file system. The begin of /dev/hda5 shows that the involved operating systems PC DOS 7, Windows NT, and Debian do not insist on any extended partition alignment with a gap:
For another example see the "Linux Partition HOWTO".

## Footnotes

* ↑ This term is used by PowerQuest's (now Symantec) diagnostic software programs, such as their PartitionInfo utility (included with Partition Magic), when extended partition information is displayed.
* 1 2 The EBR is located on the very first sector of an otherwise unused area which is equal to the number of sectors per track; normally, 63 sectors. In this regard, each logical partition mimicks the layout of a hard disk's structure for its first primary partition, since the MBR is located on the very first sector of the disk, the first sector of Track 0 (normally followed by 62 unused sectors) and then the boot sector of its first primary partition.
* ↑ Therefore, any operating system or utility program that must access or enumerate all logical drive partitions, must follow this chain of entries until the last EBR, containing only one entry, has been read.
* ↑ Under most DOS and earlier Windows operating systems, the number of logical drives in an extended partition was limited to 23, because the FDISK program couldn't create any more drives than it could assign a drive letter to; thus, assuming C: is a primary drive, the DOS drive letters D: through Z: allow for only 23 more drives. This limitation does not exist in DR-DOS FDISK, since it does not associate partitions with drive letters (except for primary partitions). Advanced features like secured or compressed volumes and multi-platform support result in more complex drive letter assignment rules, making it impractical or even misleading to associate drive letters with partitions inside FDISK. Also, the fact that DR-DOS FDISK does not only partition but also format freshly created partitions, makes it less important to know the corresponding drive letter. Further, Novell DOS 7 and higher officially support up to 32 volumes using the LASTDRIVE=32 CONFIG.SYS directive. Under Windows NT and later, an unlimited number of logical partitions can be created using the Computer Management's, Disk Management Extension; though in practice, users rarely created more than 23, since the Windows NT shell (user interface) was still limited to accessing only those drives with an A: through Z: drive letter. Newer releases of Windows support Unix-like mounting of partitions to paths in another filesystem, instead of a letter, and also allow UNC-style paths such as \\?\Volume{uuid}\.