SOLVED Sharing no longer works

[vamfoom]

Hi,

I upgraded to FreeNAS-11.2-U6 and now my shares don't work. Clicking on NFS, SMB, AFP, etc. in the Sharing section doesn't do anything. I can't list any of my shares and my clients cannot mount the shares. The pools are all healthy. In /var/log/messages, I see mount requests are denied but I can't get into the settings to check on this (at least via the GUI).

 

[eshwayri]

I was thinking of upgrading to U6 to see if it fixes the issues I have with the iSCSI access groups, but this sounds much worse. What version were you upgrading from?

 

[vamfoom]

I was going from U5.

 

[TrumanHW]

Wait, you saying that's a bug or a feature ..? ;) [NOTHING works for me... either]

NFS via Windows says: A file with any name I can think of "already exists"
NFS via Mac | same permissions | same username ... works.
SMB can't start via 11.2 -- U5 nor U6




I'm grateful & impressed freepaininNASS exists.
But -- it's frustrating to deal with the... Luxury of Security... (whether I need it, want it, or not) .

The option to turn down security -- making the OS easier to administrate | setup & probably more reliable, is welcomed.
It's enough of a struggle for me to figure out how to use things that WORK. But debugging things? MERCY FreeNAS !

Synology / QNAP's Linux distros don't appear to get pwned; yet aren't difficult to admin. Maybe some people appreciate the fault tolerance of FreeNAS, yet lack a need for protection against a brigade of tireless hackers breaking in all day - who don't exist?

 

[vamfoom]

How do I fix this? I'm not able to get into the share settings and I can't mount via SMB, NFS, etc.

I had to use sshfs from my Windows and Linux system to get around this issue in the meantime but it's no longer a working NAS.

 

[eshwayri]

How do I fix this? I'm not able to get into the share settings and I can't mount via SMB, NFS, etc.

I had to use sshfs from my Windows and Linux system to get around this issue in the meantime but it's no longer a working NAS.

Try clearing your browser cache. Try a different browser (Chrome or Firefox). Try both the new GUI and the old GUI. If none of that works, boot the old version that worked, then set the boot environment to use the old version. You won't know what's wrong, but you will have your NAS back.

 

[TrumanHW]

The first version of FreeNAS that I've used was 11.2 u5 ... NFS had been working from Windows -- and stopped ...
Even REINSTALLING Windows didn't work; let alone, clearing my browser...
...and of course - I've tried from multiple computers.

Updated to 11.2 u6 -- hoped for some form of improvement in at least one of the protocols, however, there were no changes. :-(

 

[vamfoom]

The actual issue was actually due to my browser.

Thanks @eshwayri for your help. I'm now unblocked and my NAS is back in business.

 

[eshwayri]

The first version of FreeNAS that I've used was 11.2 u5 ... NFS had been working from Windows -- and stopped ...
Even REINSTALLING Windows didn't work; let alone, clearing my browser...
...and of course - I've tried from multiple computers.

Updated to 11.2 u6 -- hoped for some form of improvement in at least one of the protocols, however, there were no changes. :-(

I have never tried the Windows NFS client, so I don't know what peculiarities it may introduce. I have NFS shares I use both in VMWare and in Linux (KVM); they are working fine in U5. There are 3 places in the GUI you need to go for the settings: "Edit Options" / "Edit Permissions" on the directory you are trying to share, and the NFS panel under Shares.

If you can actually see the contents of the share, the most likely cause of your problem is a permissions issue. Windows uses SIDs, while Unix uses Unix IDs. Something has to map between the two for things to work. Somehow Windows has to come up with a Unix user ID and group ID to initiate the mount. Macs I think are a BSD variant so they don't have to translate, but also need to chose a Unix user ID and group ID for the mount. Once they connect to FreeNAS, what they can and can't do depends on the ownership and permissions on the directory. The user/group id Windows/MAC mount the share as is the FreeNAS **local** (cat /etc/passwd; cat /etc/group) user id and group id it uses for all operations. This can be very problematic if the user id used by say Windows doesn't exist on FreeNAS. It gets even worse if each OS or user on the OS uses a different ID.

The easiest way to deal with all of this is to use the advanced features mapalluser and mapallgroup. What you do is you set the permissions on the directory you are trying to share as a local FreeNAS user/group of your choice. For example on my system I created vdsm:kvm. You give these local accounts full control of the files in this directory and propagate permissions. On the share configuration you set the mapalluser to the local user you chose, and mapallgroup to the local group you chose. What this does is make FreeNAS take whatever ID the incoming mount connection is made as and force it (map it) to the user id and group you told it to. This means that you irrespective of what user on Windows or the MAC connects, irrespective of how they map the users or chose IDs, on FreeNAS they are always connected as the local user you set. I will attach screenshots of my KVM NFS share.

There are more complicated solutions that use LDAP to dynamically map users and groups between the different systems you are trying to connect, but unless you have the need (ie-corporate environment) then I would just stick to mapalluser and mapallgroup.