Partitioning your disk for Manjaro Linux requires careful planning to ensure optimal performance and system stability. By dividing the storage into logical segments, you can separate your operating system, user data, and swap space effectively. This guide walks you through the essential steps to create a robust partition layout tailored for Manjaro installations.
Preparation and Backup
Before making any changes to your disk structure, it is critical to back up all important data. Partitioning involves rewriting the table of contents for your drive, which can result in permanent data loss if interrupted or configured incorrectly. Ensure you have an external drive or cloud backup ready. Additionally, verify that you are booting from a live USB environment rather than your current installed system. This prevents file locks and ensures the target disks are not in use by the running kernel.
Identifying Your Storage Devices
Once booted into the Manjaro live environment, open a terminal to identify your physical drives. Use the command
lsblk to list all block devices along with their sizes and mount points. Look for devices like
sda,
nvme0n1, or
vda. Be extremely careful to select the correct drive, as targeting the wrong device will erase existing data on other systems. You can also use
fdisk -l for detailed partition information. Note the device name, as you will need it for subsequent commands.
Choosing a Partition Scheme
The most common and recommended scheme for modern Manjaro installations is GPT (GUID Partition Table) with UEFI boot support. If you are using legacy BIOS, MBR (Master Boot Record) may still be applicable, but GPT is preferred for drives larger than 2TB. Within this scheme, you typically need three main partitions: one for the EFI System Partition, one for the root filesystem, and optionally one for swap space. For newer kernels, a dedicated swap file is often preferred over a swap partition, allowing dynamic resizing. However, a traditional swap partition remains a valid choice for users who prefer fixed allocation or hibernation support.
Creating Partitions with cfdisk
Manjaro includes
cfdisk as its primary partitioning tool due to its user-friendly interface. Launch it by typing
cfdisk /dev/sdX, replacing
X with your identified drive letter. The screen will display a text-based menu where you can select actions. Choose "New" to create a new partition. First, create the EFI partition, typically sized between 512MB and 1GB, with the type set to "EFI System". Next, create the root partition, assigning the majority of the remaining space to it, usually formatted as ext4 or btrfs. If you choose to use a swap partition, create it with the appropriate size and type "Linux swap". Finally, write these changes to the disk by selecting "Write", confirming with "yes", and then quit the program.
Formatting the Filesystems
After creating the partitions, they must be formatted with a filesystem. For the EFI partition, use
mkfs.fat -F 32 /dev/sdXY, where XY represents the specific partition number. For the root partition, use
mkfs.ext4 /dev/sdXZ or
mkfs.btrfs /dev/sdXZ depending on your preference. If you created a swap partition, initialize it with
mkswap /dev/sdXW. These commands prepare the raw blocks for data storage. Verify the formatting by checking the output for success messages. Proper formatting ensures that the bootloader and kernel can read and write data correctly during installation.
Mounting and Installation
Before launching the Manjaro installer, mount your partitions to a directory, typically
/mnt. Mount the root partition first:
mount /dev/sdXZ /mnt. Then create the EFI directory and mount the EFI partition:
mkdir /mnt/boot/efi followed by
mount /dev/sdXY /mnt/boot/efi. If using a swap partition, activate it with
swapon /dev/sdXW. With the drives mounted, you can proceed with the graphical installer or manual setup. The installer will detect the mounted targets and configure the bootloader accordingly. This step bridges the gap between raw disk geometry and a bootable operating system.
For more advanced configuration, consider reading about
Installing Newer Video Drivers on Manjaro/Arch: A Tech Support Guide to ensure your hardware is fully supported post-installation. Additionally, understanding how to manage sparse files can help optimize storage usage after installation, as detailed in
How to Shrink Sparse Files in Linux After Copying Them Without the -S Operator.
Frequently Asked Questions
Can I install Manjaro without a separate EFI partition?
No, if you are using UEFI firmware, a dedicated EFI System Partition is mandatory for the bootloader to function. Legacy BIOS systems do not require this, but UEFI strictly expects a FAT32 formatted partition flagged as EFI. Skipping this step will prevent the system from booting after installation.
Is it better to use a swap partition or a swap file?
Modern Manjaro releases recommend using a swap file instead of a partition because it allows flexible resizing without repartitioning. Swap files are easier to manage and integrate well with compressed swap features. However, if you require hibernation, a dedicated swap partition is often more reliable and simpler to configure.
What happens if I format the wrong partition?
Formatting the wrong partition will permanently erase all data stored on that specific segment of the disk. This action cannot be undone easily, leading to potential data loss for your operating system or personal files. Always double-check the device names and sizes before confirming any format command.
Can I use Btrfs for the root partition?
Yes, Btrfs is a highly recommended filesystem for Manjaro due to its built-in snapshot capabilities and compression. It allows you to roll back to previous states if an update breaks your system. Many users prefer Btrfs for its flexibility and advanced features compared to traditional ext4.
Do I need to defragment my SSD after partitioning?
No, defragmentation is unnecessary and potentially harmful for Solid State Drives (SSDs). SSDs handle data placement differently than mechanical hard drives and do not benefit from defragging. In fact, excessive writes from defragmentation can reduce the lifespan of your SSD.