FreeBSD doesn't boot after failing to mount nfs

[hakova]

Hi,
As part of upgrading from 14.3-RELEASE to 14.4-RELEASE i rebooted this particular machine, which now fails to boot. The boot process is normal until the error message shows up about not being able to mount remote nfs share and timeout. I would expect that the machine would complete the boot without mounting the nfs share, but what ends up happening is the boot process arrests at that point and never continues. Unfortunately, this is before ssh service is launched so I cannot login to it remotely to modify /etc/fstab. Is there any way to resume the boot process somehow? What options do I have?

Thanks!

 

[cracauer@]

Control-C

 

[SirDice]

The boot process is normal until the error message shows up about not being able to mount remote nfs share and timeout.

How are you able to see this? It implies you have access to the console.

Unfortunately, this is before ssh service is launched so I cannot login to it remotely to modify /etc/fstab

You have console access, fix it there. Boot to single user mode, remove the entry from /etc/fstab.

I would expect that the machine would complete the boot without mounting the nfs share

If a filesystem in /etc/fstab fails to mount (for whatever reason) the system will ALWAYS fail to boot and drop to single user mode.

 

[T-Daemon]

To avoid such a failure in the future, specify for filesystems not vital to boot the root system with the fstab(5) mount option "failok".

If a filesystem marked as "failok" cannot be mounted, it will not make the system drop into single-user mode, and, without an active SSH service, unaccessible to a remotely managed system.

fstab(5)

     If the option “failok” is specified, the system will ignore any error
     which happens during the mount of that filesystem, which would otherwise
     cause the system to drop into single user mode.  This option is
     implemented by the mount(8) command and will not be passed to the kernel.

 

[SirDice]

To avoid such a failure in the future, specify for filesystems not vital to boot the root system with the fstab(5) mount option "failok".

For NFS or other networked filesystems you're probably better off with autofs(4)/automount(8).

 

[hakova]

Thank you so much for all the suggestions. I am confident I will fix the problem tonight with your guidance. A few comments for now to answer questions and clarify:

How are you able to see this? It implies you have access to the console.

I do, but the machine and keyboard are in a room whereas the monitor/screen is in another. They are connected by a cable through the wall in between; therefore I cannot see what I am typing and the response to it since the monitor is in another room.

For NFS or other networked filesystems you're probably better off with autofs(4)/automount(8).

I need to do some reading to learn about these options. Thanks for the recommendation!

 

[Maturin]

I cannot see what I am typing and the response to it since the monitor is in another room.

Say what?! (sorry)
Why would anybody do that?
What's logical to me is to separate the machine from the I/O periphery. But separating the keyboard from the monitor makes no sense at all whatsoever.
What I can think of is a system where the monitor is used as some kind of presentation, like for showing ads in a public area (mall, airport), while the machine is in a locked room behind that wall. But even so I had a second small, cheap (can be bought used for five bucks) extra monitor in that room, either directly attached to the machine's VGA port (if the motherboard does not come with one, every primitive, cheap graphics card today come with more than a single port. I have three or four twenty year old ones in my spare parts box in the attic - 'want one?), or at least ready by hand to exchange it with the main monitor for maintenence.
You don't need a GUI like a X server running on that, just a TTY. So any crappy old junk monitor with defective colors which ain't complete toast will do.
Other solution could be a wireless (radio) KB - depending on the distance and the wall.
Ever thought of what time (and nerves) that running cost compared to the price of a second monitor?
...but okay, running constantly between monitor and keyboard keeps one in shape...