I had the same phenomena. I followed Hark's instruction then it booted well.
Option nobootwait is invalid, not solve the issue. Besides, I tested like
this. I let it mount from non-existing server, means invalid mount point, then
mount.nfs4 report that "No such device" then halted forever. I do
Why is this bug marked as invalid? I also have this bug in Lucid.
Servers with nfs4 mounts in fstab hang forever while booting, unless I
put 'nfs' in /etc/modules. I think this is an important bug!
--
karmic indefinitely waits for nfs4-mount
https://bugs.launchpad.net/bugs/501678
You received thi
Update for whoever gets here:
I triet with "bobootwait" but it failed like I anticipated it.
After some digging and source-reading I found out the following: mountall tries
to mount the network volume and if it does not work, it will wait for the
device by waiting for a SIGUSR. upstart sends SI
Hi Mr. Remnant
Setting fstab to "nobootwait" is not a solution. /home has to be there before
any user gets a login
If there is no home directory for the user and gdm and login will fail.
And my users complain heavily and start to press the reset button or c-a-del
every time they get "waiting for
If you do not want it to wait for /home, add "nobootwait" to the options
for that mountpoint in fstab
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
karmic indefinitely waits for nfs4-mount
https://bugs.launchpad.net/bugs/501678
You received this bug notification because you a
