As will become apparent I am a bumbling fool, but if someone could take pity on me I would greatly appreciate it. 

 

Running unraid as a NAS and seedbox, my config pretty much extends to installing RuTorrent and adding a SMB share. All was well until Rutorrent started randomly setting permissions to read only on unzipped torrents. Should've just left it....

 

Recommended action was to install Fix Common Problems, which I did, and it didnt find any. Problems that is. 

 

Not so recommended was me fumbling around in the GUI and finding the New Permissions in tools, which I ran on my only share, only to find that the mapped network drive now refuses to let me connect altogether. This is true for both accounts I have created, and as a hail Mary I tried the root account as well. I've tried setting the share to Public, no dice, tried removing and re-adding the users from the share, no luck. Before I worsen the problem, thankful for any help I can get.

Edited March 5, 20197 yr by viqous

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

tower-diagnostics-20190305-0330.zip

root has only guest access to network shares, and root access to the webUI and command line. Other users you create in Unraid only have access to network shares, as determined by the settings for each share. A Public share should be accessible to everyone.

 

New Permissions isn't recommended to run on your docker appdata, but otherwise it shouldn't break anything. Maybe just try unmapping the drive and deleting your credentials on the client machine so they can be renegotiated.

 

I personally never map drives and haven't seen any need to do so in many years. Windows Explorer and most applications can browse the network.

 

Forgot to mention, I didn't notice anything obvious in your diagnostics.

Thank you for taking a look. Client credentials are reset, although while doing this I noticed something that might hint that I broke more than just Permissions. Going to \\192.168.1.100 I get the 3 shares I always got. appdata, flash, and hb (The usershare i made). I can connect and browse to appdata, which as far as I can tell has stricter security, but not to my own usershare, which is set to public. 

At the terminal, what do you get with this?

ls -lah /mnt/user/hb

 

root@Tower:~# ls -lah /mnt/user/hb
total 28K
d-wx-wx-wx 1 nobody users  121 Jan  9 16:24 ./
drwxrwxrwx 1 nobody users   96 Mar  5 00:45 ../
drwxrwxrwx 1 nobody users  130 Dec  8 17:27 Bilder/
drwxrwxrwx 1 nobody users 4.0K Mar  4 20:20 Download/
drwxrwxrwx 1 nobody users  279 Mar  4 20:19 Hämtade\ filer/
drwxrwxrwx 1 nobody users  16K Mar  4 20:57 Keep/
drwxrwxrwx 1 nobody users   27 Sep 18 15:39 MP3/
drwxrwxrwx 1 nobody users   29 Jan  9 16:26 Plex/
drwxrwxrwx 1 nobody users   30 Jan 18 01:40 Projekt/
drwxrwxrwx 1 nobody users  219 Aug 21  2018 RAW\ footage/
drwxrwxrwx 1 nobody users   54 Mar  3 17:57 SERIES/
drwxrwxrwx 1 nobody users   88 Feb 18 09:32 Trailers/
drwxrwxrwx 1 nobody users 4.0K Aug 21  2018 VIKTIGT/

And what do you get with this?

ls -lah /mnt/user

 

root@Tower:~# ls -lah /mnt/user
total 0
drwxrwxrwx 1 nobody users  96 Mar  5 00:45 ./
drwxr-xr-x 8 root   root  160 Mar  4 23:32 ../
drwxrwxrwx 1 nobody users  68 Jan  9 16:09 appdata/
drwxrwxrwx 1 nobody users   6 Jan  9 15:36 domains/
d-wx-wx-wx 1 nobody users 121 Jan  9 16:24 hb/
drwxrwxrwx 1 nobody users   6 Aug 20  2018 isos/
drwxrwxrwx 1 nobody users  47 Aug 20  2018 system/

That doesn't look right. But I don't know how you would have gotten it like that.

 

Try this:

chmod -R 777 /mnt/user/hb

 

Took about 20 min to run, but I think that fixed it. Ran the two previous commands, and no change what I could tell, but I can access the drive again. If you're ever in Sweden, I'll buy you a beverage of your choosing. Thank you!

 

// Also, saw the command while googling about permissions in unraid, was too stupid to realize the -R had to be capitalized.

Edited March 5, 20197 yr by viqous