How do I check a persistent Linux mount configuration before rebooting?
A persistent mount configuration can prevent normal boot if it references the wrong device or makes an unavailable mount mandatory. Validate the file and verify the actual storage identity before rebooting. A syntax check alone cannot prove that a remote filesystem or detachable device will be available at the next boot.
Before you start
- Authorised access to mount configuration and a known target mount.
Instructions
1. Compare configured and active mounts
Inspect the intended mount through findmnt rather than assuming an fstab line is currently active. The example uses a known existing data path.
findmnt -T /srv/data -o TARGET,SOURCE,FSTYPE,OPTIONS
findmnt --fstabCheck the source identifier, target, filesystem type and options. Do not share credential-bearing mount configuration publicly.
2. Run the non-mounting verification
Use the verifier after any approved edit and review warnings as well as errors. It does not mount every entry or validate every remote dependency.
sudo findmnt --verify --verboseResolve missing references, unsuitable options and syntax issues before a controlled mount test or reboot. On systemd, an approved fstab edit may also require manager configuration reload.
Check the result
- The exact entry verifies, its controlled mount test succeeds and the reboot plan includes working out-of-band access and application validation.
Troubleshooting
- Verification passes but the next boot hangs
- Remote availability, authentication, ordering or timeout policy may differ at boot. Inspect the failed mount unit and console evidence.
- A device name changed after reboot
- Use the storage scheme’s supported stable identifiers and verify them rather than assuming /dev naming is permanent.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.