Can't mount smb shares with FW >= 6.4.1

[Retired_Member]

I can't mount any smb shares from my RN102 running a firmware from 6.4.1 on (including 6.4.2-T72).

No matter what user credentials I'm trying, I always get "error 13 - permission denied" when mounting a share to my Debian-Testing box.

I already tried all kinds of settings for the share network/file access permissions, including allowing r/w access to everyone and allowing anonymous access - nothing worked.

Downgrading to 6.4.0 helped. I can now mount again like before.

From smbd.log:

  Copyright Andrew Tridgell and the Samba Team 1992-2014
[2016/01/14 20:00:00.441418,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2016/01/14 20:15:37.089666,  2] ../source3/auth/auth.c:305(auth_check_ntlm_password)
  check_ntlm_password:  authentication for user [steffens] -> [steffens] -> [steffens] succeeded
[2016/01/14 20:15:37.217742,  0] ../source3/auth/pampass.c:89(smb_pam_error_handler)
  smb_pam_error_handler: PAM: session setup failed : Permission denied

[Skywalker · Accepted solution]

Cool!  So, that was indeed the root cause.  6.4.2-RC1 will include a change to not be as sensitive to /home directory issues, so it will go back to behaving like 6.4.0 in this condition.

[Skywalker]

That tells me that "steffens" does not have a home directory, and we were unable to create one.  Most likely there is something wrong with your /home mount point.  It should be a bind mount to the /home directory in your data volume.

[AlexPe]

Steffens,

instead of mounting it can you look into just listing the directory structure?

Try using this command here from your debian machine,

#smbclient -L ipaddrofnas -U admin

Also, make sure you change the admin password, it will not allow you to use the admin user if you are still using the default password.

AlexPe

Community SME

[Retired_Member]

That tells me that "steffens" does not have a home directory, and we were unable to create one.

Just to clarify: mounting is impossible for any share, not just the special "home" share.

Most likely there is something wrong with your /home mount point.  It should be a bind mount to the /home directory in your data volume.

Not sure what that means exactly.

The NAS has 2 disks as JBOD, so there is not a single data volume.

Should /home point to some directory on any of the disks?

I don't have access to the machine right now so I can't have a look...

[Retired_Member]

instead of mounting it can you look into just listing the directory structure?

Yes. Anonymous access is possible. Just mounting as a user doesn't work.

I'll try listing the shares as admin once I'm back home.

Also, make sure you change the admin password, it will not allow you to use the admin user if you are still using the default password.

Admin password was changed long ago.

There are 3 user accounts setup on the NAS in addition to the admin account. None of them is allowed to mount a share with FW >= 6.4.1 but everything works with 6.4.0.

[mdgm-ntgr]

When there are multiple volumes, the mount point for home and apps will be a bind mount to a directory on one of your data volumes.

Can you send in your logs (see the Sending Logs link in my sig)?

[Retired_Member]

Try using this command here from your debian machine,
 
#smbclient -L ipaddrofnas -U admin

With 6.4.0 this works, listing my shares.

With 6.4.2-T72 I get:

session setup failed: NT_STATUS_LOGON_FAILURE

[Retired_Member]

Can you send in your logs (see the Sending Logs link in my sig)?

I just updated to 6.4.2-T72 again, tried to list shares with smbclient (failed) and mount a share (failed).

Then I downloaded logs and sent them.

[Retired_Member]

I just did the following (using ssh connection):

• Create a new "home" directory in one of the disk volumes (/data2/home)
• Setup a bind mount in /etc/fstab for "/home" pointing to this directory
• Mount the /home

After this, I was able to mount my shares again from the Debian box!

So there was definitely a problem with /home, which was just a directory before that:

# ls -l /
...
drwxr-xr-x 2 root root 4096 Jun 17 2012 home
lrwxrwxrwx 1 root root 5 Feb 26 2014 homes -> /home
...

After mounting some share, I can see that there is a new directory for the user under /home.

[Skywalker · Accepted solution]

Cool!  So, that was indeed the root cause.  6.4.2-RC1 will include a change to not be as sensitive to /home directory issues, so it will go back to behaving like 6.4.0 in this condition.

[Retired_Member]

Yes, thank you all very much for resolving this!

One question remains though:

How was the /home mount supposed to be setup?

There was nothing in /etc/fstab. And with my own entry, I can get the working /home by running

mount -a

but after a reboot the mount is gone again, so I have to manually issue the "mount -a" once more.

I thought these entries in fstab should be mounted on startup? Is there some systemd service you normally use to setup the mounts?

[Retired_Member]

It seems like some services rely on the primary data volume to be mounted on /data.

Somehow, after replacing the first of my two disks with a larger one, my data volumes are mounted on /data2 and /data4.

I had to adapt the "home.mount" and "apps.mount" systemd files to fix these two mounts.

Now everything seems to work normally again.

[mdgm-ntgr]

Yes, the data volume is specified in those mount files.

"data" is the default volume name and some older apps may rely on that volume name or use that by default.