LevitateOS documentation
Disk Preparation
Installation steps 1-5: Boot the live environment and prepare your disk. See Installation for an overview.
1. Boot the Live Environment
Boot from the LevitateOS ISO (see Getting Started). The install screen is a root terminal on the left and this guide on the right. Type the commands in the terminal; Ctrl-] switches between the panes. For each part of the install you choose one way: a helper app, or the commands by hand.
ls /sys/firmware/efi/efivars If /sys/firmware/efi/efivars doesn't exist, you booted in legacy BIOS mode. LevitateOS requires UEFI. Reboot and select UEFI boot in your firmware settings.
loadkeys us WiFi Connection (Optional)
Installation is fully offline - no network required. NetworkManager configures a wired connection by itself. Skip this if you don't need network access.
nmcli device wifi list nmcli --ask device wifi connect "YOUR_NETWORK" If no wireless device appears, the card may need firmware the system does not ship.
2. Identify Target Disk
disk-plan lists the disks, lets you choose A/B or mutable and erase the whole disk or edit its partitions (for example to keep Windows), shows the plan and every command, runs recpart's safety checks, and partitions, formats and mounts the disk once you confirm. When it says the disk is ready, go straight to Base System. Option 2, by hand: skip disk-plan and use the commands below, which do the same with recpart directly.disk-plan disk-plan partitioned and mounted the disk, go to Base System.recpart list-disks Output
recpart candidate disks
/dev/nvme0n1
size: 2000398934016 bytes (logical 512 / physical 512)
model: Samsung SSD 990 PRO 2TB | transport: nvme | read-only: no recpart inspect --disk /dev/nvme0n1 This guide uses /dev/nvme0n1 as an example. Replace it with your actual device. NVMe partitions are named nvme0n1p1, nvme0n1p2 and so on; SATA and virtio disks are /dev/sda or /dev/vda with partitions sda1, vda1.
3. Plan the Partitions
disk-plan already planned the layout.recpart plan shows the layout, the exact sfdisk script and every command, without touching the disk. The default A/B layout:
| Partition | Size | Filesystem (label) | Mount |
|---|---|---|---|
| /dev/nvme0n1p1 | 1 GiB | FAT (EFI) | /boot |
| /dev/nvme0n1p2 | 20 GiB | ext4 (ROOT_A) | / (root A) |
| /dev/nvme0n1p3 | 20 GiB | ext4 (ROOT_B) | not mounted (root B) |
| /dev/nvme0n1p4 | Remainder | ext4 (STATE) | /var |
recpart plan --disk /dev/nvme0n1 /var holds shared persistent data, including homes in /var/home. See A/B Roots for how a change lands.- Sizes:
--efi-size-mb,--root-a-size-mb,--root-b-size-mband--state-size-mbchange them; both roots must be the same size. - Mutable layout:
--mode mutablecreates only EFI and one root (label ROOT). - Dual boot: don't erase the disk. Use
disk-plan's editor, or pass an explicit layout with--layout layout.json, to keep the existing EFI partition and Windows, shrink a partition to make room, and create the two roots and the state partition in the free space.
4. Partition, Format and Mount
disk-plan already partitioned, formatted and mounted the disk once you confirmed.WARNING: the default layout erases all data on the disk. Review the steps with --dry-run first; the real run needs the confirmation token DESTROY.
recpart apply --disk /dev/nvme0n1 --dry-run recpart apply --disk /dev/nvme0n1 --confirm DESTROY recpart writes the partition table, formats each partition with its label, and mounts the new system: root A at /mnt, the EFI partition at /mnt/boot and the state partition at /mnt/var. Root B stays unmounted. Its output ends with the install target and each mount.
/dev/nvme0n1p2 and root B /dev/nvme0n1p3. 16. Install the Boot Loader and Entries needs both. recpart apply --json reports them as slot_a_device and slot_b_device.5. Check the Mounts
findmnt -R /mnt Run this after either way. You should see root A on /mnt, the EFI partition on /mnt/boot and the state partition on /mnt/var.
Continue to Base System (steps 6-9).
Manual Partitioning (Alternative)
disk-plan. Do not run it after either.If you would rather partition by hand, do this instead of the plan and apply steps. It creates the same layout and labels as recpart, with util-linux's sfdisk.
sfdisk /dev/nvme0n1 <<'EOF'
label: gpt
size=1GiB, type=U
size=20GiB, type=L
size=20GiB, type=L
type=L
EOF mkfs.fat -F32 -n EFI /dev/nvme0n1p1
mkfs.ext4 -L ROOT_A /dev/nvme0n1p2
mkfs.ext4 -L ROOT_B /dev/nvme0n1p3
mkfs.ext4 -L STATE /dev/nvme0n1p4 mount /dev/nvme0n1p2 /mnt
mkdir -p /mnt/boot /mnt/var
mount /dev/nvme0n1p1 /mnt/boot
mount /dev/nvme0n1p4 /mnt/var Leave root B unmounted. The installer fills it as a copy of root A.