Story / scenario opener
You are installing Fedora on a machine that already holds Windows, or you are setting up a fresh drive and want full control over where your data lives. The automatic partitioning option grabs the whole disk and hands you a single root volume. That works for a quick test. It fails when you need a separate /home partition, want to preserve an existing data drive, or plan to use LVM and Btrfs. You click "I will configure partitions manually" and suddenly face a grid of mount points, filesystem types, and device selectors. One wrong choice leaves you with an unbootable system or a drive that fills up in a week.
What's actually happening
Partitioning divides a physical block device into logical sections. Each section gets a filesystem format and a mount point. The mount point tells the kernel where to attach that filesystem in the directory tree. The root partition (/) holds the operating system binaries and configuration files. The /boot partition stores the kernel and bootloader files. The /home partition holds user documents, downloads, and application settings. Swap space handles memory overflow when RAM runs out.
Think of the disk as a warehouse. Automatic partitioning builds one giant room and throws everything in. Manual partitioning builds separate rooms with labeled doors. You decide which room gets the servers, which gets the archives, and which stays empty for overflow. The installer writes a partition table to the disk, formats each section, and records the mount points in /etc/fstab. When the system boots, the initramfs reads that table, mounts the root filesystem, and hands control to the kernel.
Modern Fedora installations use GPT partition tables by default. GPT supports disks larger than 2 TB and stores backup partition tables at the end of the drive. Legacy BIOS systems require MBR, but you will rarely encounter them outside of embedded hardware or machines older than ten years. The installer handles the table format automatically. You only need to worry about mount points, filesystem types, and volume sizes.
Config files in /etc/ are user-modified. Files in /usr/lib/ ship with the package. The installer writes /etc/fstab based on your manual layout. Never edit /usr/lib/ files. Manual edits drift across updates. Trust the package manager and let the installer generate the mount table.
The fix or how-to
Planning the layout before you touch the installer saves hours of troubleshooting. Boot the Fedora installation media and open a terminal before starting the graphical installer. Check the current disk layout and identify the target drive.
lsblk -f
# Shows device names, sizes, filesystem types, and mount points
# Identifies which drive is empty or holds your target space
# Avoids accidentally wiping the wrong disk
Note the device name, usually /dev/sda or /dev/nvme0n1. Close the terminal and start the installer. Navigate to the Installation Destination screen. Select the target drive. Switch the allocation method from "Automatic" to "Custom". Click Done to open the manual partitioning interface.
The interface shows a list of existing partitions and a button to add new ones. Click "Add mount point". A dialog appears asking for the mount point, filesystem type, and size. Enter / for the root partition. Choose xfs or btrfs as the filesystem. Set a size of at least 30 GB. Click OK.
Add a second partition for /boot. Set the filesystem to ext4. Size it to 1 GB. The bootloader needs a simple, widely compatible filesystem here. Btrfs and XFS work on modern systems, but ext4 guarantees compatibility with older firmware and recovery tools.
Add a third partition for /home. Choose your preferred filesystem. Set the size to use all remaining space, or leave room for a separate data partition. Click OK.
If you are on a UEFI system, the installer usually creates an EFI System Partition automatically. If it does not, add a partition with mount point /boot/efi, filesystem vfat, and size 512 MB. The bootloader writes its configuration files here. Without it, the system will not start on UEFI hardware.
Review the layout in the main window. Every partition shows its device, mount point, filesystem, and size. Click Done to apply the changes. The installer warns you that existing data on the selected drive will be destroyed. Confirm the warning. The installer formats the partitions, writes the partition table, and begins copying files.
If you plan to use LVM, add a partition with mount point pvcreate or select the LVM option in the installer. LVM sits between the physical disk and the logical volumes. It lets you resize partitions without rebooting and adds encryption layers. Create a physical volume, then a volume group, then logical volumes for /, /home, and swap. The installer handles the LVM metadata automatically.
Fedora enables zram by default, which compresses RAM instead of writing to disk. You do not need a traditional swap partition unless you plan to hibernate. If you add a swap partition anyway, the system will use both. The zram service handles active memory pressure. The disk swap handles hibernation. Do not disable zram unless you have a specific reason.
Verify it worked
Reboot into the newly installed system. Open a terminal and check the mount table.
findmnt -t filesystem
# Lists all mounted filesystems and their mount points
# Confirms the installer wrote /etc/fstab correctly
# Shows actual device names instead of generic labels
Check the disk usage to ensure the sizes match your plan.
df -hT
# Displays human-readable sizes and filesystem types
# Verifies that /, /boot, and /home are separate volumes
# Catches cases where the installer merged partitions unexpectedly
If the output matches your layout, the partitioning succeeded. Run lsblk again to see the device tree. The structure should mirror what you defined in the installer. Check the filesystem UUIDs to confirm they match the entries in /etc/fstab.
blkid
# Prints UUIDs and filesystem types for every block device
# Matches the identifiers used in /etc/fstab
# Prevents mount failures after disk replacement
Reboot before you debug. Half the time the symptom is gone.
Common pitfalls and what the error looks like
The most common mistake is leaving /boot on the same partition as / while using LVM or Btrfs subvolumes. The bootloader cannot read complex volume structures during early boot. You will see a black screen with a blinking cursor, or the GRUB menu will load but fail to find the kernel. The error prints error: unknown filesystem or grub rescue> in the terminal. The fix requires booting from installation media, mounting the root volume, and recreating a dedicated /boot partition.
Another frequent issue is mismatched EFI partitions. If you dual boot with Windows, Windows already owns the EFI partition. Creating a second one confuses the firmware. The system boots into the wrong OS or drops to a GRUB rescue prompt. Check for an existing vfat partition labeled EFI before adding a new one. Mount it to /boot/efi and let the installer reuse it.
Filesystem selection matters for performance and compatibility. XFS handles large files and high throughput well. Btrfs offers snapshots and transparent compression. Ext4 remains the safest choice for /boot and recovery environments. Pick one and stick with it. Mixing filesystems across partitions works, but increases backup complexity.
SELinux denials show up in journalctl -t setroubleshoot with a one-line summary. Read those before disabling SELinux. A mislabeled mount point after manual partitioning triggers access denials on /home or /var. Run restorecon -Rv /mount/point to fix context labels. Trust the package manager. Manual file edits drift, snapshots stay.
When to use this vs alternatives
Use automatic partitioning when you are installing Fedora on a fresh drive and do not need separate data volumes. Use manual partitioning when you need a dedicated /home partition, want to preserve existing data drives, or plan to use LVM and Btrfs. Use LVM when you need to resize volumes later, add encryption, or span multiple physical disks. Use Btrfs subvolumes when you want instant snapshots and easy rollback without extra tools. Stay on the default layout if you only deviate from the defaults occasionally.