This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
(Solved) Upgrade causes permission problem
-
jt01
- NewUser

- Posts: 3
- Joined: 23 Feb 2015 23:26
- Status: Offline
(Solved) Upgrade causes permission problem
Last night I upgraded from Nas4Free 10.1.0.2.1761 to 10.2.0.2.1803 using the embedded firmware method (X64). I am now no longer able to write to any drive from outside the server. SMB shares from several Windows 7 client machine will only allow read access and trying to sftp a file from a client machine to one of the server drives doesn't work either. The only method that does work is using File Manager (Quixplorer) through the gui. I regularly move files around on the server through Win 7 client machines and had no problem before the upgrade. No ZFS - all drives formatted UFS. Nothing critical on my server - just want all client machines to be able to read/write/delete anything, which is what I had before 10.2.0.2.1803. I've seen permission problems before, but they had easy fixes - what's the cure for this one? Can I revert back to 1761? Thank you in advance for all responses.
Last edited by jt01 on 27 Aug 2015 21:25, edited 1 time in total.
-
jt01
- NewUser

- Posts: 3
- Joined: 23 Feb 2015 23:26
- Status: Offline
Re: Upgrade causes permission problem
UPDATE: Ok, this one is my fault. Shortly before the upgrade, I had added a new much larger drive to my server, and had copied a large amount of data to it by ftp. I had not tried to write to the new drive prior to the upgrade, but that was the first thing I dd after the upgrade, and the copy bombed out because of permission issues. I have used the File Manager to change the permissions of each directory on the new drive, and am now able to write to them as needed. I'm sure this isn't the first time someone has bemoaned the permission structure of Nas4Free/FreeBSD/Unix/Linux, but, in my case, it would be a lot easier if permissions defaulted to anyone can do anything, and then security could be tightened up as needed. Right now, it seems to be the other way around.