Linux /etc/fstab Generator & Validator
Generate and validate Linux /etc/fstab mount entries with persistent UUIDs, mount options, and boot safety linting — entirely on this device.
Configure Linux filesystem mounts with persistent UUIDs, performance mount flags, and automated boot safety linting.
Generated /etc/fstab
Safe Verification Command
Always verify your fstab configuration before rebooting to prevent emergency recovery mode:
sudo findmnt --verify && sudo mount -aDo it offline:$
How to use it
- Load an architecture preset (NVMe dual boot, Btrfs subvolumes, or NAS NFS share) or add a custom entry.
- Choose your device identifier format: UUID (recommended), PARTUUID, filesystem LABEL, or remote NFS share.
- Define mount point directory (e.g., /, /home, /boot/efi, or /mnt/storage).
- Select the filesystem type (ext4, btrfs, xfs, vfat, ntfs3, nfs, cifs, or swap) and specify mount options.
- Review automated boot safety linting (preventing non-root pass=1 errors and missing network nofail guards).
- Copy the aligned /etc/fstab content and run the safe validation command (sudo findmnt --verify && sudo mount -a) before rebooting.
Generate and validate Linux /etc/fstab mount configurations. Ensure persistent UUID device addressing, performance mount options (noatime, zstd compression), and boot safety rules.
How it works
The /etc/fstab file is read by systemd and mount at boot time to construct the Linux unified directory hierarchy.
Using UUID= instead of volatile device paths (/dev/sda1) prevents boot failures caused by disk controller order changes or hotplug reordering.
The fsck pass parameter specifies filesystem check ordering: 1 for the root filesystem, 2 for other local partitions, and 0 to skip checking (required for swap, tmpfs, network shares, and copy-on-write filesystems like Btrfs).
Network mounts (NFS, CIFS) require _netdev and nofail options so systemd waits for network connectivity and avoids dropping into emergency recovery mode if a server is offline.
Examples
Every example on this page is executed against the same engine that powers the tool, on every build.
Gotchas worth knowing
Common errors
FAQ
Why should I avoid using /dev/sda1 in /etc/fstab?
Linux assigns device names (/dev/sdX, /dev/nvmeX) dynamically during hardware probing at boot. Adding or removing a drive, connecting a USB device, or changing motherboard SATA/NVMe ports can reorder device names, causing the wrong disk to be mounted or boot failure. UUIDs remain persistent across reboots.
What does the 'noatime' mount option do?
By default, Linux updates a file's access timestamp (atime) every time it is read, generating unnecessary disk write operations. The 'noatime' option disables access time updates, dramatically improving filesystem I/O throughput and extending SSD lifespan.
How do I test my /etc/fstab edits before rebooting?
Always run 'sudo findmnt --verify' to check for syntax errors and non-existent mount points, followed by 'sudo mount -a' to mount all filesystems. If either command outputs errors, fix them before rebooting to prevent getting stuck in emergency maintenance mode.