[SOLVED] NFS shares not mounting at boot time

2handband · 01-15-2010, 12:58 PM

I've got a mostly Debian Lenny network but I've set one machine up with Squeeze. One the Squeeze machine I can mount my NFS shares manually but can't get them to mount at boot time. Here's my /etc/fstab file:

Code:

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/mapper/elizabeth-root /               ext3    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=a076b57d-ce60-4d6f-bf3e-5bb7d1bba4c8 /boot           ext2    defaults        0       2
/dev/mapper/elizabeth-home /home           ext3    defaults        0       2
/dev/mapper/elizabeth-tmp /tmp            ext3    defaults        0       2
/dev/mapper/elizabeth-usr /usr            ext3    defaults        0       2
/dev/mapper/elizabeth-var /var            ext3    defaults        0       2
/dev/mapper/elizabeth-swap_1 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
192.168.1.101:/home     /mnt/nfs/home   nfs     rw,async,hard,intr,ndev 0      0
192.168.1.101:/data     /mnt/nfs/data   nfs     rw,async,hard,intr,ndev 0      0

Can anyone see anything wrong? The Lenny boxes all auto mount witout any problems.

slacker_et · 01-15-2010, 01:02 PM

Any errors being displayed in the logs ?

--ET

2handband · 01-15-2010, 01:40 PM

None that I can find but I admit I'm not very experienced at reading the logs.

slacker_et · 01-15-2010, 02:18 PM

There should be SOMETHING in the log files.
Maybe the network connection isn't ready by the time the system attempts to do the mounts ??

--ET

2handband · 01-15-2010, 02:22 PM

I just looked through the logs again and I think that IS the problem. Anything I can do about it?

slacker_et · 01-15-2010, 02:41 PM

You might be able to:
1) Rename (ie renumber) the symbolic links in the proper runlevel directories.

Or

2) Enable "parallel execution" out the boot scripts. And modify the startup scripts so that the mounting script depends upon the networking script.

But I'm not all that familiar with Debian.
I don't know if it supports "parallel execution".
(Which may be a Suse only feature.)

Can any Debian users lend a hand ?

--ET

2handband · 01-15-2010, 02:46 PM

Quick update... as near as I can determine from the log, it's mounting the ext3 partitions on the box itself and not even attempting to mount the nfs shares; there's simply no output regarding nfs mounts at all.

It is doing the mount process for the other stuff before it sets up the network.

2handband · 01-15-2010, 04:30 PM

Here's something from syslog:

Code:

Jan 15 16:18:40 elizabeth automount[1878]: syntax error in nsswitch config near [ syntax error ]

Here's nsswitch.conf:

Code:

# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:         compat
group:          compat
shadow:         compat

hosts:          files dns
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

2handband · 01-15-2010, 05:48 PM

Okay, I'm an idiot. Take a close look at those fstab lines. I misspelled nodev... TWICE! Problem solved, thanks for the responses.