B2000/785 Hangs During Boot - NFS Client Subsystem

[David Sutton]

Don't use this workstaion often (probably obvious). Fired it up today and it hangs during boot, in the NFS Client Subsystem initialization. Message "NFS Server (pid695@/net) not responding still trying". I've never configured this system to use NFS. What can I do to get around this error? TIA.

[Jeffrey S. Sims]

David,

It sounds like the filesystem that you are attempting to mount doesn't exist any longer. What I would do is come up in single-user mode and check the /etc/fstab entries for remote filesystems. If you decide that you don't need any of the remote mounts I would remove them (but make sure that you have a backup just in case).

The remote mouth will look something like:
remote-host:remote-pathname local-mount-loc nfs options 0 0

I would suspect that it is doing a hard mount of the remote filesystem which is typical of a rw (read/write) filesystem mount. If this is a ro (read only) mount you can change hard to soft and it will error out if it isn't avaliable. Hard mounts will continue indefinately if the remote host isn't available.

You can just remove the unnecessary mounts that you do not need and see if that gets you up.

Hope this helps.

[Sridhar Bhaskarla]

David,

Get it to single user mode and disable NFS_CLIENT in the /etc/rc.config.d/nfsconf file. Then do an init 3|4" and get to the
multi-user mode. Then you can enable NFS and try if it is working or not. You may want to probably delete the stale entries from your /etc/fstab file that are pointing to NFS servers.

-Sri

[Sanjay_6]

Hi David,

Disable the automounter. To do that, press the break key to get a login prompt. Edit /etc/rc.config.d/nfsconf and look for the variable "AUTOMOUNT". It is probably set to "1". Set that to "0" and reboot the box.

AUTOMOUNT=0

Hope this helps.

thanks

[Steve Bonds]

This is probably the single most annoying default in all of HP-UX. Because automounter defaults to enabled, when you install some patches it will silently get re-enabled so that some future boot will cause the system to hang again.

This can be a real surprise sometimes.