Study guide

11.1 List, Create, and Delete Partitions on GPT Disks

Red Hat Certified System Administrator RHCSA

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Lab Setup & Performance-Based Study Strategy

2 Essential Tools: Shell, Redirection & Text Analysis

2.1 Shell Prompt and Command Syntax 2.2 Input-Output Redirection and Pipes 2.3 grep and Regular Expressions for Text Analysis

3 Essential Tools: Remote Access, Users & Text Editing

3.1 Access Remote Systems Using SSH 3.2 Log In and Switch Users in Multiuser Targets 3.3 Create and Edit Text Files

4 Essential Tools: Files, Links & Archives

4.1 Create, Delete, Copy, and Move Files and Directories 4.2 Hard and Soft Links 4.3 Archive and Compress with tar, gzip, and bzip2

5 Essential Tools: Permissions & System Documentation

5.1 List, Set, and Change Standard ugo/rwx Permissions 5.2 System Documentation: man, info, and /usr/share/doc

6 Manage Software: RPM and Flatpak

6.1 Configure Access to RPM Repositories 6.2 Install and Remove RPM Software Packages 6.3 Configure Access to Flatpak Repositories 6.4 Install and Remove Flatpak Software Packages

7 Create Simple Shell Scripts

7.1 Conditional Execution: if, test, and [] 7.2 Looping Constructs for Files and Input 7.3 Process Script Inputs ($1, $2, and Beyond) 7.4 Process Shell Command Output in Scripts

8 Operate Running Systems: Boot and Recovery

8.1 Boot, Reboot, and Shut Down a System Normally 8.2 Boot Systems into Different Targets Manually 8.3 Interrupt the Boot Process to Gain Access

9 Operate Running Systems: Processes and Tuning

9.1 Identify and Kill CPU/Memory Intensive Processes 9.2 Adjust Process Scheduling 9.3 Manage Tuning Profiles

10 Operate Running Systems: Logs, Services & File Transfer

10.1 Locate and Interpret System Log Files and Journals 10.2 Preserve System Journals 10.3 Start, Stop, and Check Status of Network Services 10.4 Securely Transfer Files Between Systems

11 Configure Local Storage: Partitions and LVM

11.1 List, Create, and Delete Partitions on GPT Disks 11.2 Create and Remove Physical Volumes 11.3 Assign Physical Volumes to Volume Groups 11.4 Create and Delete Logical Volumes

12 Configure Local Storage: Mounting and Expansion

12.1 Mount File Systems at Boot by UUID or Label 12.2 Add Partitions, Logical Volumes, and Swap Non-Destructively

13 Create and Configure File Systems: Local FS and Permissions

13.1 Create, Mount, and Use VFAT, ext4, and XFS File Systems 13.2 Extend Existing Logical Volumes 13.3 Diagnose and Correct File Permission Problems

14 Create and Configure File Systems: NFS and autofs

14.1 Mount and Unmount Network File Systems Using NFS 14.2 Configure autofs

15 Deploy and Maintain: Scheduling, Services & Targets

15.1 Schedule Tasks with at, cron, and systemd Timers 15.2 Start, Stop, and Enable Services at Boot 15.3 Configure Systems to Boot into a Specific Target

16 Deploy and Maintain: Time, Software Updates & Bootloader

16.1 Configure Time Service Clients 16.2 Install and Update Software from CDN, Remote Repos, and Local Files 16.3 Modify the System Bootloader

17 Manage Basic Networking

17.1 Configure IPv4 and IPv6 Addresses 17.2 Configure Hostname Resolution 17.3 Configure Network Services to Start Automatically at Boot 17.4 Restrict Network Access Using firewalld and firewall-cmd

18 Manage Users and Groups

18.1 Create, Delete, and Modify Local User Accounts 18.2 Change Passwords and Adjust Password Aging 18.3 Create, Delete, and Modify Local Groups and Memberships 18.4 Configure Privileged Access

19 Manage Security: Firewall, umask & SSH Keys

19.1 Configure Firewall Settings with firewall-cmd and firewalld 19.2 Manage Default File Permissions 19.3 Configure Key-Based Authentication for SSH

20 Manage Security: SELinux Modes and Contexts

20.1 Set Enforcing and Permissive Modes for SELinux 20.2 List and Identify SELinux File and Process Contexts 20.3 Restore Default File Contexts

21 Manage Security: SELinux Ports and Booleans

21.1 Manage SELinux Port Labels 21.2 Use Boolean Settings to Modify SELinux Settings

11.1 List, Create, and Delete Partitions on GPT Disks

Key Takeaways Explain This Topic AI

On RHEL 10 exam systems, prefer GPT (GUID Partition Table) for new disks; list layout with lsblk, blkid, parted -l, and fdisk -l.

Create and delete GPT partitions with parted (mkpart/rm), gdisk, or fdisk in GPT mode; set type codes (Linux filesystem, LVM, swap) correctly for the task.

Kernel partition table re-read uses partprobe, partx, or a careful reboot when devices do not appear; never assume /dev/sdXN exists without checking.

EX200 storage work is non-destructive by default: identify free disks or free space, avoid wiping the root disk, and verify before rm/mkpart on production-like layouts.

Partitioning alone does not create a filesystem or LVM volume—follow with mkfs, pvcreate, or swap setup in later steps; persist mounts via fstab/UUID in related objectives.

Last updated: August 2026

11.1 List, Create, and Delete Partitions on GPT Disks

Quick Answer: Inventory disks with lsblk , fdisk -l , and parted -l . On GPT disks, create partitions with parted ( mkpart ), gdisk , or fdisk (GPT label). Delete with parted rm , gdisk d , or fdisk d . Re-read the table with partprobe / partx if nodes are missing. On EX200, work only on the intended free disk or free space —never casually reinitialize the system root disk.

Why GPT partitioning is on EX200

Under Configure local storage , Red Hat expects you to list, create, and delete partitions on GPT disks . Typical lab language:

  • “On the unused disk /dev/sdb , create a 2 GiB GPT partition for a filesystem.”
  • “Create two partitions: one for LVM and one for swap.”
  • “Remove the second partition on /dev/sdc without destroying the first.”

You are graded on the end layout : correct disk, sizes (within reasonable rounding), GPT label, and partition type/flags when the task cares. Filesystems and LVM come next; this section is the partition table skill.

GPT vs MBR in one minute

  • Feature MBR (msdos) GPT
  • Max practical size legacy 2 TiB classic limit Multi-pebibyte class disks
  • Partition count 4 primary (or 3 + extended/logical) Many partitions (typically 128 entries)
  • ID style 1-byte type codes GUID type GUIDs
  • Exam default for new work Legacy; still appear Prefer GPT for new disks

RHEL installers and modern VMs usually present GPT . If a task says “GPT disk,” do not leave an msdos label. If a disk is empty, you may need to create a GPT label first.

  • Discover disks and current layout
  • Always list before you write : lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS,UUID,MODEL
  • lsblk -f
  • sudo fdisk -l
  • sudo parted -l
  • cat /proc/partitions
  • Tool Best for
  • lsblk Tree of disks, partitions, LVs, mounts
  • fdisk -l Partition tables and sizes
  • parted -l Labels (gpt/msdos), flags, sizes
  • blkid Filesystem/PV UUIDs on existing nodes
  • udevadm info Detailed device properties
  • Identify the root disk (holds / or /boot ) and leave it alone unless the task explicitly targets it: findmnt /
  • lsblk -o NAME,MOUNTPOINTS
  • df -h /

Exam disks for extra storage are often /dev/sdb , /dev/sdc , /dev/vdb , /dev/nvme0n1 , or similar second devices— confirm size and emptiness against the task wording.

Device naming quick map

  • Pattern Meaning
  • /dev/sda , /dev/sdb SCSI/SATA/virtio-scsi style disks
  • /dev/vda , /dev/vdb virtio-blk virtual disks
  • /dev/nvme0n1 NVMe namespace; partitions nvme0n1p1
  • /dev/sda1 Partition 1 on sda
  • /dev/mapper/... Device-mapper names (LVM, multipath)—not raw GPT slots

NVMe partition nodes use a p before the number ( nvme0n1p1 ). Do not invent nvme0n11 .

Create a GPT label on a blank disk

Warning: Labeling wipes the partition table. Only on the disk the task authorizes.

  • parted sudo parted /dev/sdb --script mklabel gpt
  • sudo parted /dev/sdb print
  • gdisk sudo gdisk /dev/sdb
  • # o → create new empty GUID partition table
  • # y → confirm
  • # w → write and exit
  • fdisk (GPT) sudo fdisk /dev/sdb
  • # g → create a new empty GPT partition table
  • # w → write

Interactive tools only write when you w (or parted --script runs immediately). You can quit with q to abort if you opened the wrong disk.

  • Create partitions
  • parted (scriptable—excellent under time pressure) # Units: use MiB/GiB boundaries to avoid alignment surprises
  • sudo parted /dev/sdb --script mkpart primary 1MiB 2049MiB

# Or named partition with explicit FS hint (type string varies by use):

  • sudo parted /dev/sdb --script mkpart dataext4 1MiB 100%
  • sudo parted /dev/sdb --script mkpart lvmpart 1MiB 50%
  • sudo parted /dev/sdb --script mkpart swappart 50% 100%
  • Set partition flags/types when needed: sudo parted /dev/sdb set 1 lvm on
  • sudo parted /dev/sdb set 2 swap on
  • sudo parted /dev/sdb print

For a pure Linux filesystem partition, a normal GPT “Linux filesystem” type is enough; for LVM PVs, set the LVM type/flag so later tools and humans recognize intent.

  • Interactive parted: sudo parted /dev/sdb
  • (parted) unit MiB
  • (parted) print
  • (parted) mkpart primary 1 2049
  • (parted) set 1 lvm on
  • (parted) quit
  • gdisk sudo gdisk /dev/sdb
  • # n → new partition
  • # accept partition number, first sector defaults
  • # size: +2G
  • # type: 8300 Linux filesystem, 8e00 Linux LVM, 8200 Linux swap
  • # p → print
  • # w → write

Memorize common gdisk type codes :

  • Code Use
  • 8300 Linux filesystem
  • 8e00 Linux LVM
  • 8200 Linux swap
  • ef00 EFI System Partition (ESP)—only if task needs UEFI boot work
  • fdisk GPT mode sudo fdisk /dev/sdb
  • # n new partition
  • # accept defaults or set size (+2G)
  • # t change type (31 Linux LVM, 19 Linux swap, 20 Linux filesystem—codes listed by L)
  • # p print
  • # w write

fdisk type hex codes differ from gdisk’s four-digit codes—use L inside fdisk to list, do not mix tables from memory under stress.

Delete partitions

Only delete what the task names. Order matters when you later recreate: deleting partition 2 does not renumber partition 1 on GPT the way some people fear—numbers stay as assigned until reused. # parted

sudo parted /dev/sdb rm 2

  • # gdisk: d then partition number, then w
  • # fdisk: d then partition number, then w

Non-destructive mindset: If the partition holds a PV, filesystem, or swap that is still in use, unmount/disable first ( umount , swapoff , vgchange -an as appropriate). Deleting a busy partition is a classic “I finished the task and the system hung” failure mode.

  • Kernel re-read and missing device nodes
  • After writing a table: lsblk /dev/sdb
  • sudo partprobe /dev/sdb
  • # or
  • sudo partx -u /dev/sdb
  • # or
  • sudo udevadm settle

If /dev/sdb1 still missing, check dmesg | tail and whether something still holds the old table. A reboot is a valid exam recovery when partprobe cannot refresh a busy disk—but prefer live re-read to save time.

  • Sizing, units, and free space
  • Tasks say “2G,” “500M,” or “use the whole disk.” sudo parted /dev/sdb unit GiB print free
  • sudo parted /dev/sdb print free

Leave a small gap at the start (1 MiB) for alignment when creating the first partition— parted examples above use 1MiB start. Using 0% / 100% is common and acceptable when the task allows full-disk use: sudo parted /dev/sdb --script mkpart primary 0% 100%

If a disk already has a partition and free space at the end, create the next partition only in free space—do not mklabel again.

  • End-to-end exam scenarios
  • Scenario A — One GPT data partition on empty disk
  • Task: Initialize /dev/sdb as GPT; create one partition using all space for a future XFS filesystem. lsblk
  • sudo parted /dev/sdb --script mklabel gpt
  • sudo parted /dev/sdb --script mkpart primary 1MiB 100%
  • sudo partprobe /dev/sdb
  • lsblk /dev/sdb
  • # Next chapter skills: mkfs.xfs /dev/sdb1 and fstab—not required merely to “create partition”
  • Scenario B — LVM-ready partition
  • Task: On /dev/vdb , create a 5 GiB partition of type LVM. sudo parted /dev/vdb --script mklabel gpt
  • sudo parted /dev/vdb --script mkpart primary 1MiB 5121MiB
  • sudo parted /dev/vdb --script set 1 lvm on
  • # or gdisk type 8e00
  • lsblk -o NAME,SIZE,TYPE,PARTTYPE /dev/vdb
  • Scenario C — Delete without touching sibling
  • Task: Remove only partition 2 on /dev/sdc . sudo parted /dev/sdc print
  • sudo parted /dev/sdc rm 2
  • sudo partprobe /dev/sdc
  • lsblk /dev/sdc

Verify partition 1 size and contents unchanged ( blkid /dev/sdc1 ).

Scenario D — Wrong tool panic

You opened fdisk /dev/sda (root). Do not write. Press q and re-identify with lsblk .

Partitions vs LVM vs filesystems (scope control)

  • Layer Question it answers Tools (this / next sections)
  • Partition table How is the disk sliced? parted, gdisk, fdisk
  • Physical volume Is this device an LVM PV? pvcreate (11.2)
  • Volume group / LV How is capacity pooled/carved? vg*/lv* (11.3–11.4)
  • Filesystem / mount How do users store files? mkfs, mount, fstab (later)

Creating a partition of type LVM does not run pvcreate for you. Creating a partition does not format XFS/ext4. Do exactly the layer the task asks; do not “helpfully” format when only a partition was requested—and do not stop at a partition when the task says “create an XFS filesystem on a new partition.”

Persistence and scoring

The GPT table is stored on the disk itself. After a correct w / mklabel + mkpart , the layout survives reboot without /etc edits. You still re-check with lsblk after reboot in practice labs. Mount points and swap activation need separate persistent config (fstab, systemd mount units)—out of scope for pure partition creation, but remember the overall EX200 rule: configuration must survive reboot when the task creates usable storage.

Common traps

mklabel on the wrong disk — instant data loss; list twice.

MBR vs GPT — task says GPT but you left msdos .

Wrong type code — filesystem tools work on 8300; LVM tasks expect PV-capable type and then pvcreate .

Forgetting partprobe — scripts fail with “no such device.”

Overlapping partitions or free-space math errors — use print free .

Deleting a mounted partition — unmount first.

Assuming /dev/sdb1 after creating on /dev/nvme0n1 — wrong name pattern.

Using /dev/mapper/... as if it were a GPT partition — mapper names are logical devices above the partition/PV layer.

Section checkpoint

You should inventory block devices, create a GPT label when required, add and remove partitions with parted/gdisk/fdisk, set Linux filesystem / LVM / swap types, refresh the kernel partition table, and practice a non-destructive exam workflow that protects the root disk. That is the EX200 bar for listing, creating, and deleting GPT partitions.