Login
Sign Up|
Add this to /etc/fstab 192.168.1.12:/volume1/myNAS/OFFSITE /mnt/offsite nfs defaults,_netdev,nofail,x-systemd.automount,x-systemd.mount-timeout=10 0 0 Why these extra options matter:
If you use the standard entry I provided earlier without a few extra safety "flags," your system might hang or experience a long delay (up to 90 seconds or more) while waiting for the remote server. In some cases, if the system considers the mount "critical," it might even drop you into an emergency shell. To ensure your Rocky Linux system boots smoothly even if the NFS server is dead, you should add the nofail and x-systemd.automount options. The "Safe"
|
| Option | What it does for you |
| nofail | The most important one. Tells the system: "If this share isn't there, keep booting anyway. Don't stop or panic." |
| x-systemd.automount | Instead of mounting at the exact second the OS starts, it waits until the first time you actually try to open the folder. This makes boot-up much faster. |
| x-systemd.mount-timeout=10 | Tells the system to stop trying after 10 seconds. Without this, Linux might wait for the default 90 seconds before giving up. |
| _netdev | Ensures the system doesn't even try to look for the share until the network card is fully active. |
What happens during boot if the server is DOWN?
-
With the "Safe" options: Your computer will boot to the login screen as if nothing is wrong. If you try to
cd /mnt/remote_share, you will see an empty folder or get an error, but your server will be running fine. -
Without these options: You will likely see a black screen with a message saying
A start job is running for...with a timer. You might have to wait 1.5 to 3 minutes for it to time out before you can use your computer.
How to fix it if it's already "stuck"
If you find yourself stuck in an Emergency Mode shell because of a bad NFS entry:
-
Log in with your root password.
-
Mount the root partition as writable:
mount -o remount,rw / -
Edit the file:
nano /etc/fstab -
Put a
#at the start of the NFS line to disable it. -
Save and
reboot.
|
Add this to /etc/fstab 192.168.1.12:/volume1/myNAS/OFFSITE /mnt/offsite nfs defaults,_netdev,nofail,x-systemd.automount,x-systemd.mount-timeout=10 0 0 Why these extra options matter:
If you use the standard entry I provided earlier without a few extra safety "flags," your system might hang or experience a long delay (up to 90 seconds or more) while waiting for the remote server. In some cases, if the system considers the mount "critical," it might even drop you into an emergency shell. To ensure your Rocky Linux system boots smoothly even if the NFS server is dead, you should add the nofail and x-systemd.automount options. The "Safe"
|
| Option | What it does for you |
| nofail | The most important one. Tells the system: "If this share isn't there, keep booting anyway. Don't stop or panic." |
| x-systemd.automount | Instead of mounting at the exact second the OS starts, it waits until the first time you actually try to open the folder. This makes boot-up much faster. |
| x-systemd.mount-timeout=10 | Tells the system to stop trying after 10 seconds. Without this, Linux might wait for the default 90 seconds before giving up. |
| _netdev | Ensures the system doesn't even try to look for the share until the network card is fully active. |
What happens during boot if the server is DOWN?
-
With the "Safe" options: Your computer will boot to the login screen as if nothing is wrong. If you try to
cd /mnt/remote_share, you will see an empty folder or get an error, but your server will be running fine. -
Without these options: You will likely see a black screen with a message saying
A start job is running for...with a timer. You might have to wait 1.5 to 3 minutes for it to time out before you can use your computer.
How to fix it if it's already "stuck"
If you find yourself stuck in an Emergency Mode shell because of a bad NFS entry:
-
Log in with your root password.
-
Mount the root partition as writable:
mount -o remount,rw / -
Edit the file:
nano /etc/fstab -
Put a
#at the start of the NFS line to disable it. -
Save and
reboot.