I have a user who brilliantly decided to play with the linux shares in /mnt/user/.  So, now, all user shares no longer show in the GUI, and are not accessible via SMB.  I do still see the shares in the CLI, just not the GUI.  I'm thinking permissions are screwed up, but I'm not exactly sure how.  I tried running New Permissions, but not luck.  Here's what I see:

 

 

 

gramunraid-diagnostics-20200316-1314.zip

Edited March 16, 20206 yr by cgram23

5 minutes ago, cgram23 said:

I have a user who brilliantly decided to play with the linux shares in /mnt/user/

Do you have any details about what exactly they did?

 

11 minutes ago, cgram23 said:

 

That looks normal to me.

 

Have you tried stopping and starting the array?

Just now, trurl said:

Do you have any details about what exactly they did?

 

That looks normal to me.

 

Have you tried stopping and starting the array?

To my knowledge, they were having issues mounting shares in OSX, and they may have tried a chmod....no idea what parameters, though.

 

I have stopped and started the array, and rebooted.

That folder named test isn't right, but I assume you created it from the root account. The others look OK as I said.

 

Your diagnostics thinks the shares have files on various disks.

 

What do you get with this?

ls -lah /boot

 

1 minute ago, trurl said:

What do you get with this?

ls -lah /boot

 

Some additional information.

 

I ran New Permissions once more, and it seemed to run through everything and reset all permissions correctly.  Still no love.  I then shutdown the server and moved the usb from an internal USB3 slot to an external USB2 slot, hoping that somehow USB3 was causing issues.  No love.

 

Also, dockers are able to access the mappings just fine.  I have plex up and running from /mnt/user/Media with no issues.

 

I'm at a loss.  Any help would be greatly appreciated.

 

Under   Settings   >>>  Disk Settings  did they turn off the 'Enable auto start'? 

 

Your problem is right here.  The permissions are wrong for  mnt/user.  They should be:

 

Edited March 17, 20206 yr by Frank1940

38 minutes ago, Frank1940 said:

 

Your problem is right here.  The permissions are wrong for  mnt/user.  They should be:

 

Yatzee!!

 

Thanks man.  This was driving me nuts.

I think im having this same issue, how did you fix it?

On 3/16/2020 at 11:42 PM, cgram23 said:

Yatzee!!

 

Thanks man.  This was driving me nuts.

 

1 hour ago, rlmarin said:

I think im having this same issue, how did you fix it?

What evidence do you have that you have the same issue? The ultimate explanation for his problem was 

 

On 3/16/2020 at 11:03 PM, Frank1940 said:

 

Your problem is right here.  The permissions are wrong for  mnt/user.  They should be:

 

 

What are your permissions for /mnt/user?

I see you had another thread about this. Glad you got it sorted.

great , this file permission on the mnt/user directory worked for me. 

 

thanks

On 3/16/2020 at 10:03 PM, Frank1940 said:

 

Your problem is right here.  The permissions are wrong for  mnt/user.  They should be:

 

 

I have this issue.  Everything was working great until I rolled back to 6.8.3.  I couldn't stay on 6.9.2 because all of my drives would not spin down.

 

After the downgrade, I had no dockers, error saying could not start, and I am missing shares.  I found this thread and found that my /mnt/user permissions don't look right.  I looked at the flash drive and the conf files for all of my shares are still there.  

 

 

Based on this thread, it looks like I need to change the permissions to look like this,

 

I don't play much at the command prompt so can somebody kindly share the commands to fix these permissions?

No, those are the correct permissions for /mnt  and /mnt/user   (i.e., ../  and ./   )  See below:

 

You should really start your own thread as I don't think your issue and the OP's are the same problem.  You can request that a Moderator move your post and this one to a new thread.  After you do that, get your Diagnostics file  Tools   >>>  Diagnostics   and post it up in  a new post to that thread.  You can edit the first post of that thread and indicate the problem is "no dockers, error saying could not start,  missing shares".

ok, thanks. I did start a new thread