All directories stuck as read only

[Learn]

I have been using 9.2.1.9 successfully with a single volume and three directories. I setup 9.3 on a different thumbdrive to test.
Since I could not get 9.3 to support a UPnP server I reverted to my original 9.2.1.9 boot drive.

Since then I have not been able to write to my volume. I can read my files with Win explorer and sync software but when I attempt to write I get access denied, don't have permission.

I have spent twelve hours hammering this problem and now I question the sanity of trusting my data to this pool. I think I understand the basics of setting permissions via GUI. I had no problems setting up the original 9.2.1.9 but now I am stuck. The problem remains when I boot from 9.3 or 9.2.1.9

Explorer security properties show root and wheel have full permissions on all my files. I simply can't write to anything.

 

[anodos]

How is authentication handled? Are you using a local account on FreeNAS? Have you configured guest access?

Post the following information:

• /usr/local/etc/smb4.conf
• output of "getfacl <folder>" for your share
• any relevant messages from /var/log/messages and /var/log/samba4/log.smbd

 

[Learn]

Anodos, thank you for your prompt reply! I clearly am not able to figure this out alone.

 

[anodos]

Anodos, thank you for your prompt reply! I clearly am not able to figure this out alone.

Am I using CLI properly here?

Nope :)

getfacl should be given the path to the shared folder. I.e.

Code:

getfacl /mnt/ZFS_7.27_Z1/Photos

Without delving much into the problem, I'd say you need to look up the user you've mapped to the guest account and make it owner of all of your shares.

Wow, they really changed up the UI for 9.3. JKH can pry my 9.2 out of my cold, dead, hands.

 

[Learn]

I botched my cat command earlier. The samba4 log shows this error many times on every port for every directory:
WARNING: The "acl check permissions" option is deprecated
I see others have reported this as normal.

smb4.conf reports:
map to guest = Bad User

CIFS is set to "nobody"

I am not sure how to check guest account mapping. I only ticked allow guest access in the CIFS shares.
If you can point me to the proper way to fix the guest account I think we will have this fixed.

Code:

[root@freenas] ~#     getfacl /mnt/ZFS_7.27_Z1/Photos
# file: /mnt/ZFS_7.27_Z1/Photos
# owner: root
# group: wheel
            owner@:rwxpDdaARWcCos:fd----:allow
            group@:rwxpDdaARWcCos:fd----:allow
         everyone@:r-x---a-R-c---:fd----:allow

There are several reasons other than the UI that make me want to steer clear of 9.3.

 

[Learn]

I have apparently damaged my pool beyond repair by testing v9.3. If I boot from v9.2.1.9 or v9.2.1.5 it is impossible to see my server files on a Windows network now. The GUI and SSH connect but there is no sharing.

BTW, v9.3 claims to be able to revert easily to the previous version. The docs show a boot screen with all the installations to choose from. I only have v9.3 to choose from after the upgrade installation. It is further impossible to run MiniDLNA or use the server for UPnP purposes which is all I care about.

At least I could run MiniDLNA on v.9.2.1.5 but it was plagued by a fatal flaw in that CIFS could not be toggled off/on.

Unless someone can bail me out I will have to wipe a large pool and forget the last ten days of my life lost on this disastrous software.

 

[SweetAndLow]

you are fine, you just need to learn how permissions work. Who are you authenticating with over the wire? Do you shares allow guest access? Can you mount a share? can you create new files? can you modify already created files?

 

[Learn]

Hi SweetAndLow, thanks for chiming in. I have been sitting here all day following step by step instructions and watching video tutorials. I originally had no trouble configuring v9.2.1.9 and building a large volume. I updtaed to v9.3 and I have never seen my files on the network since.

As of this moment I just did a factory reset of v9.2.1.5 and I have my volume mounted. So to answer your questions, nothing is set now. I need to setup Windows CIFS shares of 3 directories to have access from multiple Windows, Linux and Android devices on my LAN. I am the only user and do not need password security to read/write these files. Just one user, one group on a LAN. I am trying to get this thing to behave like my 20TB Synology.

My understanding is that v9.2.1.5 was the last version that had MiniDLNA and would write a new directory name in the plugin jail when you create a share.

 

[Learn]

you are fine, you just need to learn how permissions work. Who are you authenticating with over the wire? Do you shares allow guest access? Can you mount a share? can you create new files? can you modify already created files?

I have tried every conceivable way to set the ACL. It originally worked with the default root/wheel combo. I don't think samba/CIFS is working now.

My shares are mounted with guest access ticked. I can create new shares. Before everything disappeared from my network I could only read, not write to the previously working shares.

 

[Learn]

As I suspected, Samba was corrupt. There was no possible way to get it working from the GUI. For those that might find themselves in this same position where sanity check on Samba is marked as failed at boot this is the answer:

1. Select 'shell' ### or ssh, putty, etc
2. execute the following commands
   [root@flatline ~]# zfs list | grep .samba4
   volume1/.samba4 2.61M 545G 2.61M /mnt/volume1/.samba4
   [root@flatline ~]# zfs destroy volume1/.samba4
   [root@flatline ~]# rm /var/db/samba4
3. Restart CIFS
   Select 'Services'
   Toggle cifs to 'on' position