If I mount a share such as "smb://bob:[email protected]/Oklahoma Sport Fencing" from a Mac running 10.9.1 or 10.7.5, I have permission to read, change a name, delete, or create files for a few minutes (5 to 10 minutes), afterwards I can only read files.  If I unmount and remount the share, I can still only read.  If stop and start the array, I can read, write, delete, and create for a few minutes.  The permissions seem to be changing for some reason.  Any suggestions on where to look, or how to fix?

 

My unraid server is running basic version 5.0.4, the problems started after upgrading from 5.0-beta10 about a week ago.

 

Between Jan  6 10:26 and Jan  6 10:31 I was able to mount-use-unmount the "Oklahoma Sport Fencing" share, I then mounted the "Music" share (configured and accessed the same way), but immediately had only read permission.  I then mounted the "Oklahoma Sport Fencing" share and had only read permission.

 

My syslog file is attached:

syslog.doc

 

While you're waiting for someone who has seen this before and already knows the solution, here are my two thoughts:

 

 

Try running the New Permissions fix.  (in the web interface under 'utils')

Its often prescribed when going from 4.x to 5.x, but it might help in this instance.

 

Also, be sure you have a 'user' role defined.

(In old unRAID, 'root' could access any share. Now root can define shares, but he can't see share contents unless authorized. Set up a normal 'user' and give him Read/Write access to your shares. Your Mac remembers logins and pswds, and may be using 'root' when it shouldn't)

You may have to restart your Mac to get this to 'take' by using 'GO/Connect to Server...', '192.168.1.99' and provide the user login and pswd.

See Check Disk FileSystems in my sig. Also see SYSTEM LOG before posting again.

Thank you to dgaschk.  Initially a bit terse, but following the suggestion led immediately to the solution.

 

For the record, if anyone is interested, in the past two weeks I made changes to both my desktop iMac and to the unRaid server; no one change was outrageous (I think).  I'm no longer sure of the order.

 

I upgraded my desktop for 10.8.5 to 10.9.1.  I had a failed disk (disk2) on the unRaid; rebuilt the data on it once while waiting for a replacement.  Replaced my parity drive with the new disk and rebuilt parity.  Replaced the failing disk2 with the old parity drive and rebuilt the data.  Upgraded the unRaid from 5.0-beta10 to 5.0.4 on a different thumb drive (old, but new to this service; original thumb drive is still available with version 5.0.4 on it).  At each step, shares would mount and I could read the data.  In the end, shares would mount, but during some writes I would get a permission error related to a file on my disk2.  I discovered that Mac OS 10.9.1 uses something like SMB2 with permissions issues; a work around is to force SMB1 protocol; no joy for me.  But, following dgaschk's help and running "reiserfsck --check" followed by "reiserfsck --rebuild-tree" (as directed) seems to have solved my problems.