Stan Berry's picture

I have (last 3 lines)

  1. //storageServer/working.Stan-and-Jeanne.com/Family    /Stan-and-Jeanne.com/family    cifs    credentials=/home/storageServerAdmin/.smbcredentials,exec    0    0
  2. //storageServer/working.Stan-and-Jeanne.com/OOFrames    /Stan-and-Jeanne.com/ooframes    cifs    credentials=/home/storageServerAdmin/.smbcredentials,exec    0    0
  3. //storageServer/PicturesMaster    /Stan-and-Jeanne.com/pictures    cifs    credentials=/home/storageServerAdmin/.smbcredentials,ro    0    0

in fstab.  /home/storageServerAdmin/.smbcredentials (on this machine) has the userid and password (of the system administrator of storageServer).

I boot the machine and list the contents of /Stan-and-Jeanne.com/family and it is empty, as is /Stan-and-Jeanne.com/ooframes and /Stan-and-Jeanne.com/pictures.  I run 'mount -a' and see no errors.  I list the contents of /Stan-and-Jeanne.com/family, /Stan-and-Jeanne.com/ooframes and /Stan-and-Jeanne.com/pictures and they all contain the contents that I expected after boot.

storageServer is at 192.168.48.2, this machine is at 192.168.67.48.  If I put this machine at 192.168.48.67, same subnet, it makes no difference.

This (fstab) used to work ... sometime before tkLAMP v12.  Since I reboot the web server so seldom I just ran 'mount -a' after and sort of forgot about it.  But now I'm bringing up a new version and I tripped over this again.

I don't know what to look for.  Suggestions?

Thanks,
Stan 

Forum: 
Jeremy Davis's picture

Although some might call it a feature! IIRC it is caused by the introduction of synchronous boot processing. Basically, fstab is being processed before networking has finished coming online so fstab just skips any mounts that require networking.

I just had a quick google and it looks like you need to set the mountnfs.sh script to run asynchronously. See the details here.

Stan Berry's picture

I added AUTOMOUNTNFS=no to the end of /etc/default/rcS.  No change (that I could see).


Jeremy Davis's picture

I noticed that some other TurnKey users have also previously commented that that didn't work (although there experience was different to you) so sorry about that.

I suggest that you have a google and just keep in mind that TurnKey v13 is basically Debian Wheezy (aka 7) under the hood. From my reading there are a few different work arounds that people have used. I was under the impression that the "ASYNCMOUNTNFS=no" was the 'proper' solution, but it seems not...

Add new comment