102.1 Design hard disk layout

Introduction

This lesson is about planning disk layout before installation.

The main question is:

How should you split disk space so the system stays usable, easy to recover, and easy to grow?

For LPIC-1, you should understand the logic behind a layout, not just memorize one scheme.

What you should be able to do after this lesson:

• Explain what /, /home, /var, /boot, the ESP, and swap are for.
• Choose a simple partition layout for different system roles.
• Understand why LVM is useful.
• Avoid common beginner mistakes such as "one tiny root partition for everything".

Big Idea: A Good Layout Matches the Job

There is no single "perfect" partition scheme. A laptop, a web server, and a virtual machine may need different layouts.

Ask these questions first:

• Is this a desktop, server, or VM?
• Will users store many personal files?
• Will logs grow quickly?
• Do I need easy resizing later?
• Is the system BIOS or UEFI?

The Most Important Mount Points

/ (root filesystem)

This is the main filesystem. Linux cannot boot into a normal working state without it.

/home

This is where user data usually lives. Putting it on a separate partition can make reinstalls easier.

/var

This is where changing data often lives:

• logs
• package cache
• mail spools
• databases

On a busy server, /var can grow fast.

/boot

This stores boot files such as the kernel and initramfs. Some systems keep it inside /, but a separate /boot can make boot setups simpler.

EFI System Partition (ESP)

UEFI systems need an EFI System Partition. It is usually a small FAT-based partition used by firmware to start bootloaders.

swap

Swap is disk space used when RAM pressure grows. It can also support hibernation on some systems.

Simple Example Layout

Here is a sanitized example from a real Linux machine:

NAME          SIZE TYPE FSTYPE MOUNTPOINTS
nvme0n1     953.9G disk
|-nvme0n1p1     1G part vfat   /boot
|-nvme0n1p2    50G part ext4   /
\-nvme0n1p3 902.9G part ext4   /home
zram0           4G disk swap   [SWAP]

Why this layout makes sense:

• /boot is small and separate
• / has enough space for the OS and packages
• /home gets most of the disk because user data usually grows most
• swap exists separately from normal filesystems
• this example shows one valid pattern, not the only valid pattern

Example output from swapon --show:

NAME       TYPE      SIZE  USED PRIO
/dev/zram0 partition   4G 98.9M  100

What this shows:

• swap is active on the system
• this machine uses zram instead of a classic swap partition
• Linux can use swap in more than one form

Common Layout Patterns

Simple desktop or laptop

• ESP
• /
• /home
• swap

Good when:

• user files matter
• you want easier reinstall without wiping home data

Small VM

• ESP if using UEFI
• /
• swap

Good when:

• the system is small
• there are few moving parts
• simplicity matters more than separation

Server with growing logs or app data

• ESP if using UEFI
• /
• /var
• /home if needed
• swap

Good when:

• logs, package cache, or databases may fill /var

/boot and Hardware Requirements

LPIC expects you to know that booting method affects layout.

BIOS systems

Usually boot from an MBR-based path or BIOS-compatible boot setup.

UEFI systems

Need an EFI System Partition (ESP).

That means:

• if the machine uses UEFI, your layout must include an ESP
• if the system cannot find a proper boot partition, boot can fail before Linux even starts

LVM: The Beginner Version

LVM stands for Logical Volume Manager.

In simple words:

• normal partitions are fixed pieces of disk
• LVM adds a flexible layer between the disk and the filesystem

Why people like LVM:

• easier resizing later
• easier to combine storage
• easier snapshots on some setups

You do not need deep LVM commands here. For LPIC-1 101-500, the main idea is:

LVM makes storage planning more flexible than plain fixed partitions

Practical Design Rules

• Give / enough space for the OS, updates, and packages.
• Separate /home when user data matters.
• Separate /var on servers where logs or application data can grow.
• Include an ESP on UEFI systems.
• Do not make too many tiny partitions without a reason.
• If you expect change, LVM is often better than a rigid layout.

A Good Planning Order

1. Identify the boot mode: BIOS or UEFI.
2. Decide which mount points really need separation.
3. Decide whether plain partitions are enough or LVM is better.
4. Leave reasonable free space for growth.
5. Only then create partitions.

Practice Step by Step

1) Plan a simple laptop layout

1. Boot mode: UEFI.
2. Need user data separation: yes.
3. Good plan: ESP + / + /home + swap.
4. Give most space to /home.

2) Plan a small lab VM

1. Keep it simple.
2. Use: ESP if needed + / + swap.
3. Add /home only if there is a clear need.

3) Plan a log-heavy server

1. Assume logs may grow fast.
2. Use: ESP if needed + / + /var + swap.
3. Consider LVM if storage may need resizing later.

Cheat Sheet

• / = main root filesystem
• /home = user data
• /var = changing system data such as logs and caches
• /boot = boot files such as kernel and initramfs
• ESP = EFI System Partition for UEFI boot
• swap = disk-backed memory support
• separate partitions help isolation and recovery
• LVM adds flexibility for resizing and storage management