fstab Error
Linux Linux
Severity: CriticalWhat Does This Error Mean?
The /etc/fstab file tells Linux which partitions and drives to mount at boot. If this file has an error — a typo, a reference to a drive that no longer exists, or a removed external drive — Linux may fail to boot completely or drop to an emergency shell. Fixing fstab requires editing the file to correct the error.
Affected Models
- Ubuntu
- Debian
- Fedora
- CentOS
- Arch Linux
- Linux Mint
- openSUSE
Common Causes
- A typo or syntax error was introduced when manually editing /etc/fstab
- A UUID in fstab refers to a drive that has been replaced, removed, or reformatted
- An external drive that was added to fstab is not connected at boot time
- A line was added for a network share that is not available at startup
- The wrong partition was specified — pointing fstab at a non-existent device path
How to Fix It
-
Use the emergency shell. When the boot fails, Linux drops to an emergency shell. Type the root password (or just press Enter if there is no password). Now you have terminal access to fix fstab.
The emergency shell gives you full access to the system as root. This is how you fix most boot-time configuration errors.
-
Remount the root filesystem as read-write. The emergency shell mounts the root filesystem read-only by default. Run: sudo mount -o remount,rw / to make it writable.
Without this step, you cannot save changes to /etc/fstab.
-
Edit the fstab file. Run: sudo nano /etc/fstab to open the file. Find the line causing the error. Either fix the typo, correct the UUID, or comment it out by adding a # at the start of the line.
Commenting out the problematic line (with #) is the safest first step — it disables that mount without deleting the entry.
-
Verify UUIDs are correct. Run: blkid to see the current UUIDs of all partitions. Compare them to what is in /etc/fstab. If they do not match, update fstab with the correct UUID.
UUIDs change when a partition is reformatted. Always use UUIDs in fstab rather than /dev/sdX names — UUIDs do not change between boots.
-
Add the nofail option for non-critical mounts. If the problematic entry is for an external drive or network share, add the 'nofail' option to that line in fstab. This makes Linux skip the mount if the device is not present.
With nofail, a missing external drive or NAS will no longer prevent boot. The drive is simply not mounted if unavailable.
When to Call a Professional
fstab errors are fixable from the emergency shell or a live USB. If you are not comfortable with a text editor in a terminal, ask a Linux-savvy friend or consult online resources. Your files are safe — fstab errors only prevent mounting, they do not delete data.
Frequently Asked Questions
What is /etc/fstab?
/etc/fstab is a plain text configuration file that Linux reads at boot to know which drives and partitions to mount. Each line represents one mount: the device, where to mount it, the file system type, and options. It is one of the most important configuration files on a Linux system.
How do I test my fstab changes before rebooting?
Run: sudo mount -a to try mounting everything listed in fstab without rebooting. If this command fails, fstab still has an error. If it succeeds, your changes are correct and a reboot should work.
I added an external drive to fstab and now my computer will not boot without it. How do I fix this?
Edit /etc/fstab and add the 'nofail' option to the external drive's line. Change a line like: /dev/sdb1 /mnt/backup ext4 defaults 0 2 To: /dev/sdb1 /mnt/backup ext4 defaults,nofail 0 2 Now Linux will skip mounting it if the drive is not connected.