Disk Partitioning without LVM¶
The No LVM feature allows you to install the operating system on a server using classic disk partitioning without LVM (Logical Volume Manager). This can be useful for simplifying the file system and enhancing performance in certain use cases.
Note
The feature is available only for Bare Metal servers (physical/hardware servers). It's not an option for virtual servers (VPS).
The No LVM option is accessible in the server reinstallation interface under Advanced options:

Disk Partitioning Scheme¶
General Principles¶
- Uses an MBR (msdos) partition table.
- Creates a swap file instead of a separate
swappartition.
For HDD/SSD Disks:¶
| Partition | Start | Size | Purpose |
|---|---|---|---|
| ESP | 1 MiB | 512 MiB | EFI System Partition |
| Boot | 512 MiB | ~1.5 GiB | Boot partition |
| Root | 2 GiB | Remaining space | Root file system |
For NVMe Disks:¶
| Partition | Start | Size | Purpose |
|---|---|---|---|
| Boot | 1 MiB | ~2 GiB | Boot partition |
| Root | 2 GiB | Remaining space | Root file system |
Swap Configuration¶
Instead of a separate swap partition, a swap file (/swap_file) is created in the root file system:
- Location:
/swap_file - Size:
- 4096 MiB (4 GB) if RAM is 2 GB or more
- Double the amount of RAM if RAM is less than 2 GB
Usage Recommendations¶
Choose No LVM if:¶
- It's a test/temporary server where simplicity and predictability are important.
- The disk size is fixed, and you don't plan to expand/change the partitioning scheme.
- Quick and simple recovery access is critical (e.g., moving the disk to another machine or simply mounting the partition).
- You want to minimize layers (partition → filesystem) and potential boot issues.
Plus: simplicity, reliability, ease of recovery.
Minus: inability to flexibly modify volumes without significant manipulation.
Choose LVM if:¶
- The server is intended for long-term use with potential growth in requirements.
- There's a chance you'll add new disks and combine them into a unified storage system.
- You need snapshots for on-the-fly backup.
- Flexibility in managing volumes is required (e.g., moving space between
/varand/home).
Plus: flexibility, scalability, convenient snapshots.
Minus: complexity of architecture, potential overhead, and more complex recovery during failures.
Some of the content on this page was created or translated using AI.