kern/128448: 6.4-RC1 Boot Fails if NFS Hostname cannot be resolved (mount_nfs)

John Marshall john.marshall at
Tue Oct 28 23:30:02 UTC 2008

>Number:         128448
>Category:       kern
>Synopsis:       6.4-RC1 Boot Fails if NFS Hostname cannot be resolved (mount_nfs)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 28 23:30:01 UTC 2008
>Originator:     John Marshall
>Release:        FreeBSD 6.4-RC1 i386
Riverwillow Pty Ltd
System: FreeBSD rwpc08 6.4-RC1 FreeBSD 6.4-RC1 #0: Wed Oct 22 08:52:56 AEDT 2008 root at rwpc08:/build/obj/usr/src/sys/RWPC08 i386
In /etc/fstab I have...
mynfssrv:/kits  /kits  nfs  late,rw,-T,-b

Booting with no network available, I see:

 Mounting late file systems: mynfssrv: hostname nor servname provided, or not known
 Mounting /etc/fstab filesystem failed, startup aborted
 ERROR: ABORTING BOOT (sending SIGTERM to parent)!
 Oct 22 11:46:56 rwpc08 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
 Oct 22 11:46:56 rwpc08 init: can't get /dev/console for controlling terminal: Operation not permitted
 (only recourse at this stage is to hit the power button and boot single user)

If I comment out the nfs mount entry in /etc/fstab the system boots

If I replace the NFS server hostname with an IP address, I see the
familiar behaviour of the NFS mount giving up and backgrounding - and
the boot proceeding happily...  /kits  nfs  late,rw,-T,-b

 Mounting late file systems:[tcp] RPCPROG_NFS: RPC: Port mapper failure - RPC: unable t
 mount_nfs: Cannot immediately mount, backgrounding
 - Include an NFS mount in /etc/fstab (using hostname)
 - Unplug the network
 - Boot (at least, as far as it will go)
Workaround is to replace NFS server hostname with IP address in

More information about the freebsd-bugs mailing list