Not able to mount NAS on startup using cifs

AdiLQ123 · 10-06-2015, 03:11 PM

Quote:

Originally Posted by jpollard

What is the error message recorded in the log file?

Good point

Code:

Oct  3 22:10:40 prettysweetpc kernel: [   17.386989] CIFS VFS: Error connecting to socket. Aborting operation.
Oct  3 22:10:40 prettysweetpc kernel: [   17.387102] CIFS VFS: cifs_mount failed w/return code = -101

Consulting Google, looks like a generic error with various potential causes

ponce · 10-06-2015, 03:35 PM

Quote:

Originally Posted by AdiLQ123

//192.168.0.7/NetBackup /mnt/SynologyNAS cifs username=XXXXXX,password=XXXXXX 0 0

Quote:

Originally Posted by AdiLQ123

Still have not got it working. I've tried:

1. Replaced comma with percentage sign

sorry, but I haven't written that: regarding the entry in /etc/fstab (I got one entry in mine with the same syntax that I use with a Lacie NAS too) I wrote

Code:

//192.168.0.7/NetBackup /mnt/SynologyNAS cifs user=your_username%your_password 0 0

(substitute "your_username" with your smb user name and "your_password" with your smb password)

AdiLQ123 · 10-06-2015, 04:55 PM

Quote:

Originally Posted by ponce

sorry, but I haven't written that: regarding the entry in /etc/fstab (I got one entry in mine with the same syntax that I use with a Lacie NAS too) I wrote

Code:

//192.168.0.7/NetBackup /mnt/SynologyNAS cifs user=your_username%your_password 0 0

(substitute "your_username" with your smb user name and "your_password" with your smb password)

No good.

I turned logging for CIFS and noticed the below:

Code:

[18.112679] CIFS VFS: cifs_mount failed w/return code = -101
[   18.463632] NET: Registered protocol family 10
[   18.464130] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.568695] CIFS VFS: Error connecting to socket. Aborting operation.
[   18.568796] CIFS VFS: cifs_mount failed w/return code = -101

Which suggests it is a timing issue.

Still digging.

chris.willing · 10-07-2015, 06:36 AM

Quote:

Originally Posted by AdiLQ123

I turned logging for CIFS and noticed the below:

Code:

[18.112679] CIFS VFS: cifs_mount failed w/return code = -101
[   18.463632] NET: Registered protocol family 10
[   18.464130] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.568695] CIFS VFS: Error connecting to socket. Aborting operation.
[   18.568796] CIFS VFS: cifs_mount failed w/return code = -101

Which suggests it is a timing issue.

Still digging.

I had a similar timing problem with some nfs mounts. I happen to use NetworkManager and it can run scripts whenever various network events take place. I fixed my problem by inserting a script at /etc/NetworkManager/dispatcher.d/90_nfsmounts.sh that contains:

Code:

#!/bin/sh

IF=$1
STATUS=$2


if [ "$IF" = "eth0" ]; then
  case "$STATUS" in
    up)
      logger "Network Manager UP triggered on $IF - mounting -t nfs now"
      # Should do /nfs/scratch & /nfs/storage
      mount -a -t nfs
      ;;
     *)
      logger "Network Manager $STATUS triggered on $IF"
     ;;
  esac
fi

.
It means whenever my eth0 comes up, all nfs directories are mounted. The script name isn't significant, just the location. For a full rundown on how such scripts work and what they can contain, look for the "DISPATCHER SCRIPTS" section in the NetworkManager man page.

If you're running NetworkManager, you could try something like that.

chris

bassmadrigal · 10-07-2015, 07:40 AM

Just to clarify, the /etc/fstab entry works properly if you issue mount -a after you've booted, but it just doesn't work during the bootup process, correct? If so, I think we need to get back to how you connect to your network and make sure you're getting connected before it tries to mount the share (if you want a quick and dirty solution, you could just throw /usr/bin/mount -a into your /etc/rc.d/rc.local file, however, I would only do this as a temporary measure if it is extremely bothersome to not have it mount on boot).

Quote:

Originally Posted by AdiLQ123

I have the below entry in my rc.inet1. Is this the best way to handle my IP address.

Code:

# Config information for ath0
IFNAME[1]="ath0"
IPADDR[1]="XXX.XXX.X.X"
NETMASK[1]="255.255.255.0"
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]="XXXXXX"
GATEWAY="XXX.XXX.X.X"

Ok, so to go back to your networking setup, the information here seems to conflict? Do you have the actual IP, hostname, and gateway listed or are they just Xs? Because if you do have the addresses, you also have it listed to use DHCP. And just to clarify, is this rc.inet1 or rc.inet1.conf (I'd assume the latter, but you listed it as just rc.inet1)?

How do you connect to your network? With the ath0, I'm assuming it is wirelessly instead of wired (since wired are typically eth0), however, if this is the case, it seems to be missing the wireless info. Can you provide as much info about how you connect and the various configs (you should only need to blank out an SSID/password, as any IPs should be internal IPs which means only people connected to your router can use them, meaning there's no security issue with posting them, however, it's up to you).

neymac · 10-07-2015, 01:46 PM

deleted