I can umount and re- mount the shares using the command line (sudo umount -a and sudo mount -a) and it works successfully. I get nautilus sessions opening for each mounted drive every time I do this, which is very annoying!
I can do the following:
hamish@ht-laptop:~$ sudo mount -t cifs //192.168.73.10/<sharename> /home/hamish/nas_<sharename>
Password:
And it works successfully :-)
I *really* think that the problem is to do with the system attempting to read the /etc/fstab file and mount the drives *before* the network is up, and the reverse on the dismounts at shutdown/restart.
This works OK, as I get the drives mounted and then a separate nautilus session opens for each connected drive (which as I said previously is very annoying!), but we have the errors in the logs to prove that not all is good with this system of mounting drives.
Hi Chuck
I can umount and re- mount the shares using the command line (sudo umount -a and sudo mount -a) and it works successfully. I get nautilus sessions opening for each mounted drive every time I do this, which is very annoying!
I can do the following: 73.10/< sharename> /home/hamish/ nas_<sharename>
hamish@ht-laptop:~$ sudo mount -t cifs //192.168.
Password:
And it works successfully :-)
I *really* think that the problem is to do with the system attempting to read the /etc/fstab file and mount the drives *before* the network is up, and the reverse on the dismounts at shutdown/restart.
hamish@ ht-laptop: /etc/rc2. d$ ls xorg-input- wacom S20hotkey-setup S89anacron S99stop-readahead
README S12dbus S20powernowd S89cron
S01policykit S18avahi-daemon S20rsync S98usplash
S05vbesave S20apmd S24dhcdbd S99acpi-support
S10acpid S20apport S24hal S99laptop-mode
S10powernowd.early S20atieventsd S25pulseaudio S99rc.local
S10sysklogd S20cupsys S30gdm S99rmnologin
S10xserver-
S11klogd S20nvidia-kernel S89atd
This works OK, as I get the drives mounted and then a separate nautilus session opens for each connected drive (which as I said previously is very annoying!), but we have the errors in the logs to prove that not all is good with this system of mounting drives.
hamish@ ht-laptop: /etc/rc0. d$ ls restricted- modules- common S90halt
K01gdm K39ufw S20sendsigs
K01usplash K50alsa-utils S30urandom
K16dhcdbd K59mountoverflowtmp S31umountnfs.sh
K20apport K99laptop-mode S40umountfs
K20atieventsd README S60umountroot
K20avahi-daemon S01linux-
K25hwclock.sh S15wpa-ifupdown
hamish@ ht-laptop: /etc/rc6. d$ ls restricted- modules- common S90reboot
K01gdm K39ufw S20sendsigs
K01usplash K50alsa-utils S30urandom
K16dhcdbd K59mountoverflowtmp S31umountnfs.sh
K20apport K99laptop-mode S40umountfs
K20atieventsd README S60umountroot
K20avahi-daemon S01linux-
K25hwclock.sh S15wpa-ifupdown
As you can see, S40umountfs is *after* S15wpa-ifupdown in both the above rc0.d and rc6.d. I *strongly* believe this is the problem.
Hope this helps
Hamish