Some maps i can't read some i can. Some maps i can delete. Some I can not. But most of all I can't wright nothing to Unraid.

All the times I get in dutch the message “U bent niet gemachtigd om deze bewerking uit te voeren”. Meaning “You are not authorized to perform this operation” in English. If I want to wright something to Unraid server or want to delete something. But this problems I don't have with my flash drive. I have all the settings correctly Giving user read and write access.

 

This problem is now going on four a few months. Out of nothing it began. Then version 4.7. I tried updating it to 5,0-rc4 and now 5,0-rc5. But the  The problem keeps the same.

 

So my question is what am I doing wrong? Or am I overlooking something?

I hope some one can help me =)

You probably haven't run the 'new permissions' upgrade utility while upgrading from 4.7 to 5.0. If you did, then after you may have run something with the wrong permissions. So run it again if you did.

I thought this thread was going to be about the Wright Brothers.

You probably haven't run the 'new permissions' upgrade utility while upgrading from 4.7 to 5.0. If you did, then after you may have run something with the wrong permissions. So run it again if you did.

 

Tried it many times over and over. But keep getting the same problems.

When you try to delete something, does anything show up in the logs? Also since there may be something wrong with the drives, I'd check the SMART reports.

You may also be able to delete the files on the server, if you know how to do those things, to see if that works.

 

I have to say that I also had this issue recently, I had run a parity-check, so I knew my system was okay. So, it had to do something with the files themselfs. So, I made a new folder, and moved everything I could into it, but one or two folders gave the error. Everything else was moved correctly though. When I checked the server, somehow the folder had a different user and group, changing those properties to the ones of the rest of the files, made the error go away.

 

In my case, I don't run any add-ons, but some of them can make files that you can't delete normally because of this, and it can also happen if you make folders on the server by yourself, because usually people log in as root.

 

Of course without knowing if there is anything in the logs etc, and if the filesystem is okay etc, there's no way to know, but I hope it is something like I said

Attach the syslog. zip if needed.