I made a slight boo-boo when trying to set the permissions of a folder and its subfolder.  I only had a single folder with wrong permissions, so I didn't use the Fix Common Problems function.

 

But I miswrote the command. Instead of writing:

find ./ -type d -exec chmod 777 {} \;

 

I wrote:

find /. -type d -exec chmod 777 {} \;

 

Effectively it started changing the folder permissions of every folder in the system from root and onwards.  I stopped it after perhaps 10 seconds, but I see now that several folders in root now have permissions "777".  I don't know what they had earlier, though.

 

My question is what do I do about this?  I saw "operation not permitted" on a whole bunch of folders (that's what tipped me that I had made a mistake), but I guess that at least _some_ have changed permissions now.  Will Fix Common Problems fix this on a root level?  If not, have I exposed the system in such a way now that I ought to reinstall unRAID?

The folders that are in RAM, a reboot will fix it up for you.

 

If the system managed to hit the appdata share, then YMMV depending upon the app, etc.

 

For all the other shares, there's no problems with those permissions.