Understanding the disk Partitions

Computer storage refers to the hardware and associated structures used to store data, programs, and instructions for processing. Storage devices can be broadly categorized into primary (volatile, e.g., RAM) and secondary (non-volatile, e.g., hard drives, SSDs) storage. This article focuses on secondary storage, specifically disks and partitions, which are critical for organizing and managing data in a computer system.

Disks are physical or virtual storage devices that hold data, while partitions are logical divisions of a disk that allow it to be treated as multiple independent storage units.

Disks

A disk is a physical or virtual storage device that stores data in a non-volatile manner, meaning the data persists even when the device is powered off. Disks are the foundation of secondary storage in most computing systems.

Types of Disks

  1. Hard Disk Drives (HDDs):
    • Description: HDDs are mechanical devices that store data on spinning magnetic platters. A read/write head accesses data by moving across the platters.
    • Characteristics:
      • High storage capacity (e.g., terabytes).
      • Slower read/write speeds compared to SSDs.
      • Cost-effective for large-scale storage.
      • Susceptible to mechanical failure due to moving parts.
    • Use Cases: Bulk storage, archival data, servers, and desktops.
  2. Solid-State Drives (SSDs):
    • Description: SSDs use flash memory to store data, with no moving parts.
    • Characteristics:
      • Faster read/write speeds than HDDs.
      • More expensive per gigabyte.
      • More durable due to lack of mechanical components.
      • Lower power consumption.
    • Use Cases: Operating system drives, high-performance applications, laptops.
  3. Optical Disks:
    • Description: These include CDs, DVDs, and Blu-ray discs, which store data using laser-based technology.
    • Characteristics:
      • Read-only, write-once, or rewritable formats.
      • Limited capacity (e.g., 700 MB for CDs, up to 50 GB for dual-layer Blu-ray).
      • Slow access speeds.
    • Use Cases: Media distribution, backups (less common today).
  4. Virtual Disks:
    • Description: Software-based disks that emulate physical disks, often used in virtual machines or cloud environments.
    • Characteristics:
      • Flexible size and configuration.
      • Dependent on underlying physical storage.
    • Use Cases: Virtualization, cloud computing.
  5. NVMe Drives:
    • Description: A type of SSD that uses the Non-Volatile Memory Express (NVMe) protocol over PCIe for faster data transfer.
    • Characteristics:
      • Extremely high speeds (e.g., 3-7 GB/s read/write).
      • Low latency.
      • Higher cost than SATA SSDs.
    • Use Cases: High-performance computing, gaming, data centers.

Disk Structure

  • Sectors: The smallest addressable unit on a disk, typically 512 bytes or 4 KB in modern drives.
  • Tracks: Concentric circles on a platter (in HDDs) where data is stored.
  • Cylinders: A group of tracks across multiple platters aligned vertically (in HDDs).
  • Blocks: Logical units used by the operating system, often comprising multiple sectors.

Disk partitions are a fundamental concept in computer storage management, allowing a single physical disk to be divided into multiple logical sections. Each partition functions as an independent unit, enabling better organization, security, and performance.

What is a Partition

A partition is a defined portion of a physical storage device (e.g., hard disk drive (HDD), solid-state drive (SSD), or USB drive) that is treated as a separate entity by the operating system (OS). Each partition can have its own filesystem, be assigned a drive letter (e.g., C:, D:), or be mounted to a specific directory (e.g., /home in Linux). Partitions allow users to organize data, install multiple operating systems, or isolate specific types of data (e.g., system files vs. user data).

Purpose of Disk Partitions

Partitions serve several critical purposes:

  1. Organization: Partitions help organize data by separating system files, user data, applications, or backups. For example, a user might keep the OS on one partition and personal files on another.
  2. Multiple Operating Systems: Partitions allow multiple OSes (e.g., Windows and Linux) to coexist on the same disk, each in its own partition.
  3. Performance Optimization: Separating frequently accessed data (e.g., OS files) from less frequently accessed data (e.g., archives) can improve disk performance.
  4. Data Security and Isolation: Partitions can isolate sensitive data or system files, reducing the risk of corruption. For example, a corrupted user data partition won’t necessarily affect the OS partition.
  5. Backup and Recovery: Dedicated partitions for backups or recovery data make it easier to restore a system without affecting other data.
  6. Filesystem Flexibility: Different partitions can use different filesystems (e.g., NTFS, ext4, FAT32) optimized for specific tasks.

Types of Partitions

There are several types of partitions, categorized based on their role and the partitioning scheme used. The two primary categories are primary and extended partitions, with additional types like logical partitions and specialized partitions.

1. Primary Partition

  • A primary partition is a directly accessible partition on a disk that can contain an operating system or other data.
  • A disk can have up to four primary partitions in the traditional Master Boot Record (MBR) partitioning scheme due to limitations in the partition table.
  • Primary partitions are typically used to boot an OS or store critical data.
  • Example: The C: drive in Windows is often a primary partition.

2. Extended Partition

  • An extended partition is a special type of primary partition that acts as a container for logical partitions.
  • It allows users to bypass the MBR’s limit of four primary partitions by hosting multiple logical partitions within it.
  • Only one extended partition is allowed per disk in the MBR scheme.

3. Logical Partition

  • Logical partitions reside within an extended partition and are used to store data or additional filesystems.
  • There is no strict limit on the number of logical partitions (beyond disk space and OS limitations).
  • Logical partitions are commonly used for non-bootable data, such as user files or secondary OS installations.

4. Specialized Partitions

  • System Partition: Contains boot files (e.g., Windows Boot Manager or GRUB) required to start the OS.
  • Boot Partition: Contains the OS kernel and core system files.
  • Recovery Partition: A small partition used by manufacturers to store recovery tools or a factory image for system restoration.
  • Swap Partition: Used in Linux systems as virtual memory to supplement RAM.
  • EFI System Partition (ESP): Used in UEFI-based systems to store boot loaders and other firmware-related files. Required for GUID Partition Table (GPT) disks.

Partitioning Schemes

Disk partitions are managed using a partitioning scheme, which defines how partitions are organized and accessed. The two most common schemes are MBR and GPT.

1. Master Boot Record (MBR)

  • Overview: MBR is an older partitioning scheme introduced in the 1980s, widely used in legacy systems.
  • Structure:
    • The MBR resides in the first sector of the disk (512 bytes).
    • It contains a boot loader (code to initiate booting) and a partition table (describing up to four primary partitions).
  • Limitations:
    • Supports only four primary partitions (or three primary + one extended with logical partitions).
    • Maximum disk size of 2 terabytes (due to 32-bit addressing).
    • Limited support for modern features like UEFI.
  • Use Cases: Common in older systems or devices with smaller disks.

2. GUID Partition Table (GPT)

  • Overview: GPT is a modern partitioning scheme, part of the UEFI specification, designed to overcome MBR limitations.
  • Structure:
    • Uses globally unique identifiers (GUIDs) to define partitions.
    • Stores partition information in multiple locations for redundancy, reducing the risk of data loss.
  • Advantages:
    • Supports up to 128 partitions by default (extendable with software).
    • Supports disks larger than 2 terabytes (up to 9.4 zettabytes).
    • Compatible with UEFI, enabling secure boot and faster startup.
  • Use Cases: Standard for modern systems, large disks, and UEFI-based computers.

Partition Table Structure

The partition table is a data structure stored on the disk that defines the partitions. Its structure depends on the partitioning scheme.

MBR Partition Table

  • Located in the first 512 bytes of the disk.
  • Contains:
    • Boot Loader Code: Instructions to load the OS.
    • Partition Entries: Four entries, each 16 bytes, describing the start, end, type, and size of each primary partition.
    • Signature: A 2-byte marker (0x55AA) indicating a valid MBR.
  • If an extended partition exists, it contains a secondary partition table (Extended Boot Record, EBR) for logical partitions.

GPT Partition Table

  • Located in the first few sectors of the disk, with a backup copy at the end.
  • Contains:
    • Protective MBR: A legacy MBR for compatibility with older systems.
    • GPT Header: Metadata about the partition table, including the number of partitions and their GUIDs.
    • Partition Entries: Each entry (typically 128 bytes) describes a partition’s GUID, type, start/end sectors, and attributes.
  • Supports advanced features like partition naming and attributes (e.g., bootable, hidden).

Filesystems and Partitions

Each partition typically has a filesystem, which determines how data is stored and accessed. Common filesystems include:

  • NTFS: Used by Windows for high performance and security.
  • FAT32: Widely compatible but limited to 4GB file sizes and 2TB partitions.
  • exFAT: Optimized for flash drives, supporting large files and partitions.
  • ext4: Common in Linux for reliability and performance.
  • APFS: Apple’s filesystem for macOS and iOS devices.
  • Btrfs: A modern Linux filesystem with snapshotting and redundancy features.

A partition can also be unformatted (raw) or used for specialized purposes like swap space, which doesn’t require a traditional filesystem.

Partition Management Tools

To create, modify, or delete partitions, users rely on partition management tools. These tools vary by operating system:

  • Windows:
    • Disk Management: A built-in GUI tool for creating, resizing, and formatting partitions.
    • diskpart: A command-line tool for advanced partitioning tasks.
  • Linux:
    • fdisk: A command-line tool for MBR and GPT partitioning.
    • parted: A versatile tool for both MBR and GPT.
    • GParted: A graphical tool for user-friendly partition management.
  • macOS:
    • Disk Utility: A GUI tool for managing partitions and filesystems.
    • diskutil: A command-line utility for advanced tasks.
  • Third-Party Tools:
    • Tools like EaseUS Partition Master, MiniTool Partition Wizard, or Paragon Hard Disk Manager offer advanced features for cross-platform partitioning.

MBR Partition Table

The Master Boot Record (MBR) partition table is a legacy partitioning scheme used to organize and manage partitions on a storage device, such as a hard disk drive (HDD) or solid-state drive (SSD). Introduced in the early 1980s with IBM PC DOS, MBR is one of the oldest and most widely supported partitioning schemes, though it has been largely superseded by the GUID Partition Table (GPT) for modern systems due to its limitations.

The MBR is a special boot sector located at the very beginning of a storage device (typically the first 512 bytes, or sector 0). It serves two primary purposes:

  1. Bootstrapping: It contains a small piece of executable code called the boot loader, which initiates the process of loading the operating system (OS).
  2. Partitioning: It includes a partition table that defines the layout of partitions on the disk, allowing the OS to locate and access them.

The MBR is used in systems with the BIOS (Basic Input/Output System) firmware and is compatible with older operating systems and hardware. It is still relevant for legacy systems or devices with smaller storage capacities.

Structure of the MBR

The MBR resides in the first 512 bytes of a disk and is divided into three main components:

  1. Bootstrap Code (446 bytes):
    • This is the executable code that the BIOS loads to start the boot process.
    • It typically includes the first stage of the boot loader (e.g., code to locate and load the OS or a secondary boot loader like GRUB or Windows Boot Manager).
    • The bootstrap code scans the partition table to identify the active (bootable) partition and transfers control to the boot sector of that partition.
  2. Partition Table (64 bytes):
    • The partition table consists of four entries, each 16 bytes, describing up to four primary partitions (or three primary and one extended partition).
    • Each partition entry contains:
      • Status (1 byte): Indicates whether the partition is bootable (e.g., 0x80 for active, 0x00 for inactive).
      • Starting CHS Address (3 bytes): Specifies the starting sector using the Cylinder-Head-Sector (CHS) addressing scheme, used by older systems.
      • Partition Type (1 byte): Identifies the type of partition or filesystem (e.g., 0x07 for NTFS, 0x83 for ext2/ext3/ext4, 0x05 for extended).
      • Ending CHS Address (3 bytes): Specifies the ending sector in CHS format.
      • Starting LBA Address (4 bytes): Specifies the starting sector using Logical Block Addressing (LBA), which is more modern and precise.
      • Partition Size (4 bytes): Indicates the number of sectors in the partition.
    • The partition table is limited to describing four primary partitions, a key constraint of the MBR scheme.
  3. MBR Signature (2 bytes):
    • The last two bytes of the MBR are a fixed signature (0x55AA), which indicates that the sector is a valid MBR.
    • This signature helps the BIOS verify the integrity of the MBR.

Total Size: 446 (bootstrap) + 64 (partition table) + 2 (signature) = 512 bytes.

Extended Partitions and Logical Partitions

Because the MBR partition table is limited to four primary partitions, the extended partition was introduced to allow more partitions. Here’s how it works:

  • An extended partition is a special type of primary partition that acts as a container for logical partitions.
  • Only one extended partition is allowed per disk, and it occupies one of the four slots in the MBR partition table.
  • Inside the extended partition, a linked list of Extended Boot Records (EBRs) defines logical partitions. Each EBR is similar to the MBR and contains:
    • A boot code section (often unused).
    • A partition table with one or two entries: one for the logical partition and another pointing to the next EBR (if any).
  • Logical partitions are chained together via EBRs, allowing theoretically unlimited logical partitions (though practical limits depend on the OS and disk space).

Example:

  • A disk might have three primary partitions and one extended partition.
  • The extended partition could contain multiple logical partitions, each defined by an EBR.

How the MBR Works

The MBR plays a critical role in the boot process and partition management:

  1. Boot Process:
    • When a computer with BIOS firmware starts, the BIOS loads the MBR from the first sector of the bootable disk.
    • The bootstrap code in the MBR executes, identifies the active partition (marked as bootable), and loads the boot sector of that partition.
    • The boot sector then loads the OS or a secondary boot loader.
  2. Partition Access:
    • The OS reads the MBR partition table to identify the location, size, and type of each partition.
    • Partitions are assigned drive letters (e.g., C:, D:) in Windows or mounted to directories (e.g., /home, /var) in Linux.

Partition Types in MBR

The partition type field in the partition table identifies the intended use or filesystem of the partition. Common partition type codes include:

  • 0x07: NTFS (Windows)
  • 0x0B: FAT32 (Windows, widely compatible)
  • 0x0C: FAT32 with LBA support
  • 0x83: Linux (ext2/ext3/ext4)
  • 0x82: Linux swap
  • 0x05: Extended partition
  • 0x0F: Extended partition with LBA support
  • 0xEE: GPT protective partition (used to indicate a GPT disk in MBR for compatibility)

The full list of partition type codes is maintained by various standards and OS documentation.

Advantages of the MBR Partition Table

  1. Wide Compatibility:
    • MBR is supported by virtually all operating systems (Windows, Linux, macOS) and legacy BIOS systems.
    • It is ideal for older hardware or systems that do not support UEFI or GPT.
  2. Simplicity:
    • The MBR structure is straightforward, making it easy to implement and understand.
    • Tools for managing MBR partitions are widely available and mature.
  3. Small Overhead:
    • The MBR occupies only 512 bytes, leaving nearly all disk space for partitions.

Limitations of the MBR Partition Table

The MBR scheme has significant limitations, which have led to its replacement by GPT in modern systems:

  1. Four-Partition Limit:
    • The MBR can define only four primary partitions. While extended and logical partitions can bypass this, they add complexity.
  2. 2-Terabyte Disk Size Limit:
    • MBR uses 32-bit addressing for LBA, limiting the maximum disk size to 2 terabytes (2^32 sectors × 512 bytes per sector).
    • Larger disks require GPT to utilize their full capacity.
  3. No Redundancy:
    • The MBR is stored in a single sector with no built-in backup. If the MBR is corrupted (e.g., due to disk errors or malware), the partition table may become unreadable, leading to data loss.
  4. Limited Features:
    • MBR does not support modern features like secure boot, partition naming, or advanced attributes.
    • It is incompatible with UEFI systems unless a compatibility mode (CSM) is enabled.
  5. CHS Addressing Obsolescence:
    • The CHS addressing scheme, included for legacy compatibility, is outdated and limited compared to LBA.

MBR vs. GPT

To provide context, here’s a brief comparison of MBR and GPT:

  • Partition Limit: MBR supports 4 primary partitions (plus logical partitions); GPT supports up to 128 partitions by default.
  • Disk Size: MBR is limited to 2TB; GPT supports up to 9.4 zettabytes.
  • Boot Support: MBR works with BIOS; GPT is designed for UEFI but can work with BIOS in some cases.
  • Redundancy: MBR has no backup; GPT stores a backup partition table at the end of the disk.
  • Compatibility: MBR is more compatible with older systems; GPT is standard for modern systems.

Use Cases for MBR

MBR is still used in specific scenarios:

  1. Legacy Systems: Older computers with BIOS firmware rely on MBR for booting and partitioning.
  2. Small Disks: For disks under 2TB, MBR is sufficient and simpler to manage in some cases.
  3. Embedded Systems or USB Drives: Many USB drives and embedded devices use MBR due to its simplicity and compatibility.
  4. Dual-Boot Configurations on Older Hardware: MBR is often used when installing multiple OSes on legacy systems.

Managing MBR Partitions

Several tools allow users to create, modify, or delete MBR partitions:

  • Windows:
    • Disk Management: A GUI tool for creating, formatting, and resizing partitions.
    • diskpart: A command-line tool for advanced partitioning tasks.
  • Linux:
    • fdisk: A command-line tool for creating and managing MBR partitions.
    • parted: Supports both MBR and GPT partitioning.
    • GParted: A graphical tool for user-friendly partition management.
  • macOS:
    • Disk Utility: Can manage MBR partitions for external drives.
    • diskutil: Command-line utility for partitioning tasks.
  • Third-Party Tools:
    • Tools like EaseUS Partition Master, MiniTool Partition Wizard, or Paragon Hard Disk Manager support MBR partitioning.

Risks and Considerations

When working with MBR partitions, keep the following in mind:

  1. Data Loss: Partitioning operations (e.g., creating, resizing, or deleting partitions) can erase data. Always back up critical data before modifying the partition table.
  2. Corruption Risk: Since the MBR is stored in a single sector, corruption (e.g., due to disk errors or malware) can render the disk inaccessible. Tools like TestDisk can sometimes recover corrupted MBRs.
  3. Boot Issues: Incorrectly configuring the active partition or boot loader can prevent the system from booting.
  4. Compatibility: Ensure the OS and hardware support MBR if you plan to use it. For UEFI systems, GPT is typically required unless compatibility mode is enabled.
  5. Partition Alignment: For SSDs, align partitions to the drive’s erase block size (e.g., 4KB) to optimize performance.

Example MBR Partition Table

Here’s a simplified example of an MBR partition table layout:

  • Disk: 1TB HDD
  • Partition 1 (Primary): 100GB, NTFS, bootable (Windows C: drive, type 0x07).
  • Partition 2 (Primary): 200GB, ext4 (Linux root, type 0x83).
  • Partition 3 (Extended): 700GB, containing:
    • Logical Partition 1: 500GB, NTFS (data storage, type 0x07).
    • Logical Partition 2: 200GB, FAT32 (shared storage, type 0x0B).
  • MBR Contents:
    • Bootstrap code (446 bytes): Loads Windows or Linux boot loader.
    • Partition table (64 bytes): Defines the two primary partitions and one extended partition.
    • Signature (2 bytes): 0x55AA.

The extended partition contains EBRs that define the logical partitions.

GPT Partition Table

The GUID Partition Table (GPT) is a modern partitioning scheme used to define the layout of partitions on a storage device, such as a hard disk drive (HDD) or solid-state drive (SSD). It is part of the Unified Extensible Firmware Interface (UEFI) specification and was designed to overcome the limitations of the older Master Boot Record (MBR) partitioning scheme. GPT is now the standard for most modern operating systems and hardware, especially for disks larger than 2 terabytes and systems using UEFI firmware.

The GPT is a partitioning scheme that uses Globally Unique Identifiers (GUIDs) to define partitions on a disk. It is stored in the first few sectors of the disk and includes a backup copy at the end for redundancy. GPT serves two main purposes:

  1. Partition Management: It defines the location, size, type, and attributes of partitions, allowing the operating system (OS) to access them.
  2. Boot Support: For UEFI systems, GPT includes an EFI System Partition (ESP) that stores boot loaders and firmware-related files, enabling the system to boot.

GPT is widely used in modern systems due to its support for large disks, a higher number of partitions, and advanced features like redundancy and secure boot.

Structure of the GPT

The GPT is spread across multiple sectors at the beginning of the disk, with a backup copy at the end. It uses Logical Block Addressing (LBA) to define partition locations, replacing the outdated Cylinder-Head-Sector (CHS) addressing used in MBR. Below is a detailed breakdown of the GPT structure:

  1. LBA 0: Protective MBR (512 bytes):
    • The first sector of a GPT disk contains a protective MBR, which is a legacy MBR for compatibility with older systems that expect an MBR.
    • The protective MBR typically defines a single partition (type 0xEE) that spans the entire disk (or up to 2TB), indicating that the disk uses GPT.
    • This ensures that legacy tools or BIOS systems do not misinterpret the disk as unpartitioned or attempt to overwrite the GPT.
  2. LBA 1: GPT Header (512 bytes):
    • The GPT header contains metadata about the partition table, including:
      • Signature: An 8-byte value (“EFI PART”) that identifies the disk as GPT.
      • Revision: The version of the GPT specification (e.g., 1.0).
      • Header Size: Typically 92 bytes, though the sector is 512 bytes.
      • CRC32 Checksum: A checksum of the GPT header to detect corruption.
      • Primary GPT LBA: The location of the primary GPT header (usually LBA 1).
      • Backup GPT LBA: The location of the backup GPT header (usually at the end of the disk).
      • First and Last Usable LBA: The range of sectors available for partitions.
      • Disk GUID: A unique identifier for the disk.
      • Partition Entry Array LBA: The starting LBA of the partition entries (usually LBA 2).
      • Number of Partition Entries: Typically 128, allowing up to 128 partitions.
      • Size of Partition Entry: Typically 128 bytes per entry.
      • Partition Array CRC32: A checksum of the partition entry array to ensure integrity.
    • The GPT header is critical for interpreting the partition table and is duplicated at the end of the disk for redundancy.
  3. LBA 2–33 (or more): Partition Entry Array:
    • The partition entry array contains a list of partition entries, each describing a single partition.
    • By default, GPT supports 128 partition entries, each 128 bytes, stored in LBA 2–33 (assuming 512-byte sectors).
    • Each partition entry includes:
      • Partition Type GUID: A 16-byte GUID indicating the type of partition (e.g., EFI System Partition, Windows Data, Linux Filesystem).
      • Unique Partition GUID: A 16-byte GUID uniquely identifying the partition.
      • Starting LBA: The first sector of the partition.
      • Ending LBA: The last sector of the partition.
      • Attributes: A 64-bit field defining partition properties (e.g., bootable, read-only, hidden).
      • Partition Name: A 36-character (72-byte) Unicode name for the partition (e.g., “Windows System”).
    • The number of partition entries can be extended by allocating more sectors, but 128 is the standard default.
  4. Backup GPT:
    • A duplicate of the GPT header and partition entry array is stored at the end of the disk (e.g., LBA -1 for the header, LBA -2 to -33 for the partition entries).
    • This redundancy ensures that if the primary GPT is corrupted, the backup can be used to recover the partition table.

Total Overhead:

  • The GPT typically occupies the first 34 sectors (LBA 0–33) for the protective MBR, primary GPT header, and partition entry array.
  • A similar number of sectors is reserved at the end of the disk for the backup GPT.
  • For a 512-byte sector disk, this is approximately 17KB for the primary GPT and 17KB for the backup.

Key Features of GPT

GPT offers several advanced features compared to MBR:

  1. Large Disk Support:
    • GPT uses 64-bit LBA addressing, supporting disk sizes up to 9.4 zettabytes (2^64 sectors × 512 bytes).
    • This far exceeds the 2TB limit of MBR.
  2. High Partition Count:
    • GPT supports up to 128 partitions by default, with no need for extended or logical partitions.
    • This can be extended by allocating more sectors to the partition entry array.
  3. Redundancy:
    • The backup GPT header and partition table at the end of the disk provide protection against corruption.
    • Tools can use the backup to restore a damaged primary GPT.
  4. Unique Identifiers:
    • GUIDs for the disk and each partition ensure uniqueness, reducing conflicts in multi-disk systems.
  5. Partition Attributes:
    • GPT supports a 64-bit attribute field for each partition, allowing fine-grained control (e.g., bootable, read-only, hidden).
  6. Unicode Names:
    • Partitions can have human-readable names, improving usability.
  7. UEFI Compatibility:
    • GPT is designed for UEFI systems, supporting secure boot and faster boot times.
    • It requires an EFI System Partition (ESP) for booting, typically 100–300MB, formatted as FAT32.

Common Partition Types in GPT

Each partition in GPT is identified by a Partition Type GUID, which specifies its purpose or filesystem. Some common partition types include:

  • EFI System Partition: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (required for UEFI booting, contains boot loaders).
  • Microsoft Basic Data: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (used for NTFS or FAT32 data partitions in Windows).
  • Linux Filesystem: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (used for ext4, Btrfs, etc.).
  • Linux Swap: 0657FD31-A4AB-43C4-84E5-0933C84B4F4F.
  • Windows Recovery: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC.
  • Apple HFS+: 48465300-0000-11AA-AA11-00306543ECAC (used in macOS).

A full list of partition type GUIDs is maintained by the UEFI specification and OS documentation.

How GPT Works

  1. Boot Process (UEFI Systems):
    • The UEFI firmware reads the GPT header and partition entry array to locate the EFI System Partition (ESP).
    • The ESP contains boot loaders (e.g., GRUB, Windows Boot Manager) or EFI applications, which the firmware executes to load the OS.
    • The firmware uses the partition type GUID and attributes to identify the bootable partition.
  2. Partition Access:
    • The OS reads the GPT header and partition entry array to identify the location, size, and type of each partition.
    • Partitions are mounted (e.g., /home in Linux) or assigned drive letters (e.g., C: in Windows) based on their GUIDs and filesystems.

Advantages of GPT

  1. Large Disk Support:
    • GPT supports disks up to 9.4 zettabytes, making it suitable for modern high-capacity drives.
  2. High Partition Count:
    • Up to 128 partitions (extendable) without the complexity of extended/logical partitions required in MBR.
  3. Redundancy:
    • The backup GPT header and partition table protect against corruption, improving reliability.
  4. UEFI Compatibility:
    • Designed for UEFI, GPT supports secure boot, faster boot times, and modern firmware features.
  5. Flexibility:
    • Partition attributes and Unicode names provide greater control and usability.
  6. Cross-Platform Support:
    • Supported by modern OSes (Windows, Linux, macOS) and widely used in servers, desktops, and laptops.

Limitations of GPT

  1. Compatibility with Legacy Systems:
    • GPT is not natively supported by older BIOS-based systems, which require MBR.
    • Some UEFI systems offer a Compatibility Support Module (CSM) to boot GPT disks in legacy mode, but this is not universal.
  2. Complexity:
    • GPT is more complex than MBR, requiring UEFI firmware and compatible tools for management.
  3. Overhead:
    • GPT uses more disk space for its header and partition table (approximately 34KB total) compared to MBR’s 512 bytes, though this is negligible on modern disks.
  4. Tool Support:
    • Older partitioning tools may not fully support GPT, requiring modern tools like parted, gdisk, or Windows Disk Management.

GPT vs. MBR

Here’s a detailed comparison of GPT and MBR:

  • Partition Limit: GPT supports 128 partitions (extendable); MBR supports 4 primary partitions (or 3 primary + 1 extended with logical partitions).
  • Disk Size: GPT supports up to 9.4 zettabytes; MBR is limited to 2TB.
  • Boot Support: GPT is designed for UEFI; MBR is designed for BIOS but can work with UEFI in CSM mode.
  • Redundancy: GPT has a backup header and partition table; MBR has no redundancy.
  • Addressing: GPT uses 64-bit LBA; MBR uses 32-bit LBA and legacy CHS.
  • Compatibility: MBR is better for legacy systems; GPT is standard for modern systems.

Use Cases for GPT

GPT is the preferred partitioning scheme for:

  1. Modern Systems: Computers with UEFI firmware, including most laptops, desktops, and servers manufactured after 2010.
  2. Large Disks: Disks larger than 2TB, common in modern HDDs and SSDs.
  3. Multi-OS Environments: GPT supports complex setups with multiple operating systems (e.g., Windows, Linux, macOS) via the EFI System Partition.
  4. High Partition Count: Systems requiring many partitions, such as servers or advanced workstations.
  5. Secure Boot: GPT is required for UEFI secure boot, which verifies the integrity of boot loaders.

Managing GPT Partitions

Several tools allow users to create, modify, or delete GPT partitions:

  • Windows:
    • Disk Management: A GUI tool for creating, formatting, and resizing GPT partitions.
    • diskpart: A command-line tool for advanced GPT partitioning tasks.
  • Linux:
    • gdisk: A GPT-specific version of fdisk for managing GPT partitions.
    • parted: Supports both MBR and GPT partitioning.
    • GParted: A graphical tool for user-friendly GPT partition management.
  • macOS:
    • Disk Utility: A GUI tool for managing GPT partitions on internal and external drives.
    • diskutil: A command-line utility for advanced GPT tasks.
  • Third-Party Tools:
    • Tools like EaseUS Partition Master, MiniTool Partition Wizard, or Paragon Hard Disk Manager support GPT partitioning.

Risks and Considerations

  1. Data Loss: Partitioning operations (e.g., creating, resizing, or deleting partitions) can erase data. Always back up critical data before modifying the GPT.
  2. Corruption Recovery: While GPT’s backup table improves reliability, corruption of both primary and backup GPTs can lead to data loss. Tools like gdisk or TestDisk can help recover corrupted GPTs.
  3. UEFI Requirement: GPT requires UEFI firmware for booting. Legacy BIOS systems may not boot GPT disks without CSM.
  4. Partition Alignment: For SSDs, align partitions to the drive’s erase block size (e.g., 4MB) to optimize performance.
  5. EFI System Partition: Ensure the ESP is correctly configured (FAT32, 100–300MB) for UEFI booting.

Example GPT Partition Table

Here’s a simplified example of a GPT partition table for a 4TB disk:

  • Protective MBR (LBA 0): Single partition (type 0xEE) indicating GPT.
  • GPT Header (LBA 1): Defines the disk GUID, partition entry array (LBA 2–33), and backup GPT location.
  • Partition Entry Array (LBA 2–33):
    • Partition 1: EFI System Partition, 200MB, FAT32, type C12A7328-F81F-11D2-BA4B-00A0C93EC93B.
    • Partition 2: Windows System, 100GB, NTFS, type EBD0A0A2-B9E5-4433-87C0-68B6B72699C7.
    • Partition 3: Linux Filesystem, 500GB, ext4, type 0FC63DAF-8483-4772-8E79-3D69D8477DE4.
    • Partition 4: Data Partition, 3.4TB, NTFS, type EBD0A0A2-B9E5-4433-87C0-68B6B72699C7.
  • Backup GPT: Stored at the end of the disk (e.g., LBA -1 to -33).

Technical specifications of the Partition

The technical specifications of a partition, whether in the Master Boot Record (MBR) or GUID Partition Table (GPT) partitioning scheme, define how partitions are structured, stored, and managed on a storage device such as a hard disk drive (HDD) or solid-state drive (SSD). These specifications include details about the partition table entries, addressing mechanisms, size limits, attributes, and other metadata.

Overview of Partition Specifications

A partition is a logically defined section of a storage device, specified in a partition table. The technical specifications of a partition depend on the partitioning scheme (MBR or GPT), which determines how partitions are described, addressed, and managed. The key components include:

  • Partition Table Entry: Metadata describing the partition’s location, size, type, and attributes.
  • Addressing Mechanism: How the partition’s start and end locations are specified (e.g., CHS or LBA).
  • Size Limits: Maximum partition size, influenced by the partitioning scheme and filesystem.
  • Partition Types/Attributes: Identifiers or flags indicating the partition’s purpose (e.g., bootable, filesystem type).
  • Filesystem: The structure used to organize data within the partition (e.g., NTFS, ext4).

1. MBR Partition Specifications

The MBR partitioning scheme is a legacy standard, with partitions defined in a 64-byte partition table within the first 512-byte sector (LBA 0) of the disk. The specifications for MBR partitions are constrained by the simplicity and age of the scheme.

Partition Table Entry (16 Bytes per Partition)

The MBR partition table contains up to four entries, each 16 bytes, describing primary or extended partitions. The structure of each entry is as follows:

  • Byte 0: Status (1 byte):
    • Indicates whether the partition is bootable.
    • Values:
      • 0x80: Bootable (active) partition.
      • 0x00: Non-bootable partition.
  • Bytes 1–3: Starting CHS Address (3 bytes):
    • Specifies the starting sector using Cylinder-Head-Sector (CHS) addressing, a legacy method.
    • Format: 8 bits for head, 10 bits for cylinder, 6 bits for sector.
    • Limited to addressing ~8GB due to CHS constraints (1024 cylinders × 256 heads × 63 sectors × 512 bytes).
  • Byte 4: Partition Type (1 byte):
    • Identifies the partition’s purpose or filesystem.
    • Examples:
      • 0x07: NTFS (Windows).
      • 0x0B: FAT32.
      • 0x83: Linux (ext2/ext3/ext4).
      • 0x05 or 0x0F: Extended partition (CHS or LBA).
      • 0x82: Linux swap.
    • Full list maintained by OS standards (e.g., Microsoft, Linux).
  • Bytes 5–7: Ending CHS Address (3 bytes):
    • Specifies the ending sector in CHS format.
    • Same limitations as the starting CHS address.
  • Bytes 8–11: Starting LBA Address (4 bytes):
    • Specifies the starting sector using Logical Block Addressing (LBA), a modern addressing method.
    • 32-bit value, supporting up to 2^32 sectors (2TB with 512-byte sectors).
  • Bytes 12–15: Partition Size (4 bytes):
    • Number of sectors in the partition (32-bit value).
    • Maximum partition size: 2TB (2^32 × 512 bytes).

Total Partition Table Size: 4 entries × 16 bytes = 64 bytes, located at offset 446–509 in the MBR sector.

Extended Partitions and Logical Partitions

  • Extended Partition:
    • Occupies one of the four primary partition slots.
    • Acts as a container for logical partitions.
    • Type code: 0x05 (CHS) or 0x0F (LBA).
  • Logical Partitions:
    • Defined within an extended partition using Extended Boot Records (EBRs).
    • Each EBR is a 512-byte sector with a structure similar to the MBR:
      • Bootstrap code (446 bytes, often unused).
      • Partition table (64 bytes, typically two entries):
        • First entry: Describes the logical partition (16 bytes, same format as MBR partition entry).
        • Second entry: Points to the next EBR (if any) for additional logical partitions.
      • Signature (2 bytes): 0x55AA.
    • Logical partitions are chained via EBRs, allowing theoretically unlimited logical partitions (limited by disk space and OS).

Addressing Mechanisms

  • CHS Addressing:
    • Legacy method using cylinder, head, and sector coordinates.
    • Limited to ~8GB due to 1024 cylinders, 256 heads, and 63 sectors.
    • Largely obsolete but included for backward compatibility.
  • LBA Addressing:
    • Modern method using a 32-bit sector number.
    • Supports up to 2^32 sectors (2TB with 512-byte sectors or 4TB with 4KB sectors).

Size Limits

  • Maximum Partition Size: 2TB (2^32 × 512 bytes).
  • Maximum Disk Size: 2TB, as the MBR partition table uses 32-bit LBA addressing.
  • Maximum Partitions: 4 primary partitions, or 3 primary + 1 extended with multiple logical partitions.

Attributes/Flags

  • The only attribute in MBR is the bootable flag (0x80 in the status byte).
  • No support for advanced attributes like read-only or hidden.

Filesystem Support

  • The partition type code indicates the intended filesystem (e.g., NTFS, FAT32, ext4).
  • Common filesystems:
    • NTFS (0x07): Windows, high performance, supports large files.
    • FAT32 (0x0B, 0x0C): Cross-platform, limited to 4GB files and 2TB partitions.
    • ext4 (0x83): Linux, reliable and efficient.
    • Swap (0x82): Linux virtual memory.

Other Specifications

  • Sector Size: Typically 512 bytes (legacy standard). Some modern drives use 4KB sectors, but MBR tools often emulate 512-byte sectors.
  • Location: MBR resides in LBA 0 (first 512 bytes).
  • Signature: Last 2 bytes of the MBR sector are 0x55AA, indicating a valid MBR.
  • No Redundancy: The MBR partition table is stored in a single sector, with no backup.

2. GPT Partition Specifications

The GPT partitioning scheme is a modern standard, part of the UEFI specification, designed for large disks and advanced features. The partition table is stored across multiple sectors at the beginning of the disk, with a backup at the end.

Partition Table Entry (128 Bytes per Partition)

The GPT partition table supports up to 128 partitions by default, with each partition described by a 128-byte entry in the partition entry array (LBA 2–33). The structure of each entry is as follows:

  • Bytes 0–15: Partition Type GUID (16 bytes):
    • A 16-byte globally unique identifier specifying the partition’s purpose or filesystem.
    • Examples:
      • C12A7328-F81F-11D2-BA4B-00A0C93EC93B: EFI System Partition.
      • EBD0A0A2-B9E5-4433-87C0-68B6B72699C7: Microsoft Basic Data (NTFS/FAT32).
      • 0FC63DAF-8483-4772-8E79-3D69D8477DE4: Linux Filesystem (ext4, Btrfs).
      • 0657FD31-A4AB-43C4-84E5-0933C84B4F4F: Linux Swap.
  • Bytes 16–31: Unique Partition GUID (16 bytes):
    • A unique identifier for the partition, ensuring no conflicts across disks.
  • Bytes 32–39: Starting LBA (8 bytes):
    • Specifies the starting sector using 64-bit LBA addressing.
    • Supports up to 2^64 sectors (9.4 zettabytes with 512-byte sectors).
  • Bytes 40–47: Ending LBA (8 bytes):
    • Specifies the ending sector (inclusive) using 64-bit LBA.
  • Bytes 48–55: Attributes (8 bytes):
    • A 64-bit field defining partition properties. Common bits:
      • Bit 0: System partition (required for booting).
      • Bit 2: Legacy BIOS bootable.
      • Bit 60: Read-only.
      • Bit 62: Hidden.
      • Bit 63: Do not automount.
    • Specific attributes vary by OS (e.g., Windows, Linux, macOS).
  • Bytes 56–127: Partition Name (72 bytes):
    • A 36-character Unicode name (UTF-16LE) for the partition (e.g., “Windows System”, “Data”).
    • Optional but improves usability.

Total Partition Table Size:

  • 128 entries × 128 bytes = 16,384 bytes (16KB).
  • Stored in LBA 2–33 (32 sectors with 512-byte sectors).

GPT Header (512 Bytes)

The GPT header, located at LBA 1 (with a backup at the disk’s end), provides metadata about the partition table:

  • Bytes 0–7: Signature (8 bytes): “EFI PART” (ASCII).
  • Bytes 8–11: Revision (4 bytes): GPT specification version (e.g., 1.0).
  • Bytes 12–15: Header Size (4 bytes): Typically 92 bytes (padded to 512 bytes).
  • Bytes 16–19: CRC32 Checksum (4 bytes): Checksum of the GPT header.
  • Bytes 20–23: Reserved (4 bytes): Must be zero.
  • Bytes 24–31: Primary GPT LBA (8 bytes): Location of the primary GPT header (usually LBA 1).
  • Bytes 32–39: Backup GPT LBA (8 bytes): Location of the backup GPT header (usually last LBA).
  • Bytes 40–47: First Usable LBA (8 bytes): First sector available for partitions (usually LBA 34).
  • Bytes 48–55: Last Usable LBA (8 bytes): Last sector available for partitions.
  • Bytes 56–71: Disk GUID (16 bytes): Unique identifier for the disk.
  • Bytes 72–79: Partition Entry Array LBA (8 bytes): Start of partition entries (usually LBA 2).
  • Bytes 80–83: Number of Partition Entries (4 bytes): Typically 128.
  • Bytes 84–87: Size of Partition Entry (4 bytes): Typically 128 bytes.
  • Bytes 88–91: Partition Array CRC32 (4 bytes): Checksum of the partition entry array.
  • Bytes 92–511: Reserved (420 bytes): Must be zero.

Protective MBR (LBA 0, 512 Bytes)

  • A legacy MBR for compatibility with older systems.
  • Contains a single partition entry (type 0xEE) spanning the disk (or up to 2TB), indicating that the disk uses GPT.
  • Structure is identical to a standard MBR (see MBR section above).

Addressing Mechanism

  • LBA Addressing:
    • GPT uses 64-bit LBA addressing exclusively.
    • Supports up to 2^64 sectors (9.4 zettabytes with 512-byte sectors or 75.6 zettabytes with 4KB sectors).
    • No CHS addressing, as it’s obsolete.

Size Limits

  • Maximum Partition Size: 9.4 zettabytes (2^64 × 512 bytes).
  • Maximum Disk Size: 9.4 zettabytes, limited by 64-bit LBA addressing.
  • Maximum Partitions: 128 by default (extendable by allocating more sectors to the partition entry array).

Attributes/Flags

  • 64-bit attribute field per partition, supporting advanced properties like:
    • System partition (required for UEFI booting).
    • Legacy BIOS bootable.
    • Read-only, hidden, or no-automount flags.
    • OS-specific attributes (e.g., Windows recovery, Linux RAID).

Filesystem Support

  • GPT supports any filesystem compatible with the OS, identified by the partition type GUID.
  • Common filesystems:
    • NTFS: Windows data partitions.
    • FAT32: EFI System Partition (required for UEFI booting).
    • ext4/Btrfs: Linux filesystems.
    • HFS+/APFS: macOS filesystems.
    • exFAT: Cross-platform for large files.

Other Specifications

  • Sector Size: Typically 512 bytes (legacy) or 4KB (modern drives). GPT supports both natively.
  • Location:
    • Primary GPT: LBA 0 (protective MBR), LBA 1 (header), LBA 2–33 (partition entries).
    • Backup GPT: Last 33 sectors of the disk (header at last LBA, entries before it).
  • Redundancy: Backup GPT header and partition table ensure recoverability.
  • EFI System Partition (ESP):
    • Required for UEFI booting.
    • Typically 100–300MB, formatted as FAT32, type GUID C12A7328-F81F-11D2-BA4B-00A0C93EC93B.

General Partition Specifications

Some specifications apply to both MBR and GPT partitions:

  • Alignment:
    • Partitions should be aligned to the disk’s physical sector boundaries (e.g., 4KB or 1MB) for optimal performance, especially on SSDs.
    • GPT tools typically align partitions to 1MB boundaries by default to accommodate 4KB-sector drives.
  • Filesystem Limits:
    • The partition size may be limited by the filesystem, not just the partitioning scheme.
    • Example: FAT32 supports up to 2TB partitions and 4GB files, even on GPT disks.
  • Bootability:
    • MBR: Requires a bootable flag (0x80) in the partition entry.
    • GPT: Requires an EFI System Partition and UEFI firmware for booting.
  • Partition Naming:
    • MBR: No naming support; partitions are identified by type code or drive letter/mount point.
    • GPT: Supports 36-character Unicode names per partition.
  • Management Tools:
    • MBR: fdisk, diskpart, Disk Management, GParted.
    • GPT: gdisk, parted, Disk Management, Disk Utility, GParted.
  • Sector Size Impact:
    • Most specifications assume 512-byte sectors (legacy standard).
    • Modern drives with 4KB sectors (Advanced Format) are supported, but tools must handle emulation (512e) correctly.

Practical Example: Partitioning a Disk

1. Example 1: Partitioning a Disk for a Single Operating System (Windows)

Scenario: You have a new 1 TB SSD and want to set it up for a Windows 11 installation with separate partitions for the OS, user data, and backups.

Objective:

  • Create a bootable partition for Windows 11.
  • Allocate separate partitions for user data and backups.
  • Use the GPT partitioning scheme for modern UEFI systems.

Tools:

  • Windows Disk Management (built-in GUI tool).
  • Alternatively, DiskPart (command-line) or third-party tools like EaseUS Partition Master.

Steps:

  1. Prepare the Disk:
    • Connect the 1 TB SSD to your computer.
    • Boot into the Windows 11 installation media (USB/DVD).
    • During installation, select “Custom” to access the disk partitioning interface.
  2. Initialize the Disk:
    • If the disk is new, initialize it as GPT (required for UEFI systems).
    • In the Windows setup, select the unallocated space and click “New” to create partitions.
  3. Create Partitions:
    • EFI System Partition (ESP):
      • Size: 100 MB.
      • File System: FAT32 (Windows auto-formats this).
      • Purpose: Stores bootloader files for UEFI.
    • Microsoft Reserved Partition (MSR):
      • Size: 16 MB (created automatically by Windows).
      • Purpose: Reserved for system use.
    • Windows OS Partition:
      • Size: 120 GB (recommended for OS and applications).
      • File System: NTFS.
      • Purpose: Windows 11 system files and programs.
    • User Data Partition:
      • Size: 400 GB.
      • File System: NTFS.
      • Purpose: Personal files (documents, media, etc.).
    • Backup Partition:
      • Size: ~480 GB (remaining space).
      • File System: NTFS.
      • Purpose: Backups or archival storage.
  4. Format and Install:
    • Format each partition with the appropriate file system during the Windows setup.
    • Select the 120 GB NTFS partition for Windows installation.
    • Complete the Windows installation process.
  5. Post-Installation:
    • Open Disk Management (diskmgmt.msc).
    • Verify that all partitions are correctly formatted and labeled (e.g., “Data” for user data, “Backup” for backups).
    • Assign drive letters (e.g., C: for OS, D: for Data, E: for Backup).

Considerations:

  • Backup: Ensure no critical data is on the disk, as partitioning erases existing data.
  • Partition Sizes: Allocate enough space for Windows updates (at least 100 GB for the OS partition).
  • Alignment: Modern SSDs require 4K alignment, which Windows handles automatically for GPT.
  • Performance: Separating OS and data improves organization and can reduce fragmentation.

Outcome: The 1 TB SSD is partitioned into a bootable Windows OS partition, a user data partition, and a backup partition, all using NTFS (except the ESP, which uses FAT32). The system is organized and ready for use.

2. Example 2: Partitioning a Disk for Dual-Booting Windows and Linux

Scenario: You have a 1 TB SSD and want to set up a dual-boot system with Windows 11 and Ubuntu 24.04 LTS, sharing some storage space for data accessible by both OSes.

Objective:

  • Create partitions for Windows 11, Ubuntu, and a shared data partition.
  • Use GPT for compatibility with UEFI.
  • Include a swap partition for Linux.

Tools:

  • Windows Installation Media (for Windows setup).
  • Ubuntu Live USB (for Ubuntu setup and partitioning with GParted).
  • GParted (GUI tool for partitioning, available on Ubuntu Live USB).

Steps:

  1. Prepare the Disk:
    • Connect the 1 TB SSD.
    • Boot into the Ubuntu Live USB to use GParted for partitioning (recommended for precise control).
  2. Initialize the Disk:
    • In GParted, select the SSD (/dev/sda or similar).
    • Initialize it as GPT if not already done (Device > Create Partition Table > GPT).
  3. Create Partitions:
    • EFI System Partition (ESP):
      • Size: 300 MB.
      • File System: FAT32.
      • Flags: boot, esp.
      • Purpose: Shared bootloader for both OSes.
    • Windows OS Partition:
      • Size: 150 GB.
      • File System: NTFS.
      • Purpose: Windows 11 installation.
    • Ubuntu Root Partition:
      • Size: 30 GB.
      • File System: ext4.
      • Mount Point: /.
      • Purpose: Ubuntu system files.
    • Ubuntu Home Partition:
      • Size: 100 GB.
      • File System: ext4.
      • Mount Point: /home.
      • Purpose: User data for Linux.
    • Swap Partition:
      • Size: 8 GB.
      • File System: swap.
      • Purpose: Virtual memory for Ubuntu.
    • Shared Data Partition:
      • Size: ~712 GB (remaining space).
      • File System: exFAT (compatible with both Windows and Linux).
      • Purpose: Shared storage for files accessible by both OSes.
  4. Install Windows First:
    • Boot into the Windows 11 installation media.
    • Select the 150 GB NTFS partition for installation.
    • Windows will use the existing ESP and create an MSR partition automatically.
    • Complete the Windows installation.
  5. Install Ubuntu:
    • Boot into the Ubuntu Live USB.
    • Choose “Install Ubuntu” and select “Something Else” for manual partitioning.
    • Configure the partitions:
      • Set the 30 GB ext4 partition as /.
      • Set the 100 GB ext4 partition as /home.
      • Set the 8 GB swap partition as swap area.
      • Select the 300 MB FAT32 partition as the EFI partition.
    • Install GRUB bootloader to the disk (/dev/sda) to manage dual-booting.
    • Complete the Ubuntu installation.
  6. Post-Installation:
    • Boot into Ubuntu and verify that GRUB allows you to choose between Windows and Ubuntu.
    • Mount the exFAT partition in both OSes:
      • In Windows: Assign a drive letter via Disk Management.
      • In Ubuntu: Mount automatically by editing /etc/fstab (e.g., UUID=XXXX /mnt/data exfat defaults 0 0).

Considerations:

  • Boot Order: Install Windows first, as it overwrites the bootloader. Ubuntu’s GRUB can then manage both OSes.
  • File System for Shared Data: exFAT is ideal for cross-platform compatibility; NTFS is also viable but requires additional configuration in Linux for write access.
  • Backup: Partitioning erases data, so back up any existing data.
  • UEFI Settings: Ensure the system is in UEFI mode (not Legacy/BIOS) for GPT.

Outcome: The SSD is partitioned for dual-booting Windows 11 and Ubuntu, with a shared exFAT partition for data accessible by both systems. GRUB manages the boot process, and the swap partition supports Linux’s memory needs.