>>Nope. I didn't. But I had the rights to give myself the rights, so I specifically added my username to the list of users granted full privileges on the folder, and then it all worked fine. It may sound stupid, and I did feel like an idiot each time I had to do that, but it worked every time.
>
>I do remember the first time I'd deployed openmediavault I kept running into wonky rights issues. It appears that the out-of-box configuration is only meant to have very basic access policy -- you either hand access or not. Once you tried to fiddle with configuration that resembled group membership rules, things got wonky pretty quickly. Was eventually able to correct the problems by simply going "old school" and configuring the underlying Linux and Samba through more "traditional" means and forgo using the web-based managment system it used. I also had to use chown at the Linux level to make sure the ownership was correctly set.

I managed to have such issues on linux alone. I somehow hated that the other disks, which didn't get included during installation, had to be mounted in folders like /media/username/volumename, thinking the life would be easier if I could mount them somewhere below root, like some of my friends did thirty years ago. No go. Then I wanted to have them mounted as /home/volumename, and that worked until I realized that any file copying went with new timestamps - the system would create a copy, with the default timestamp, and then didn't have permission to change the timestamp to that of the source file. Then I realized that the owner of all such files is root (!). Tried to chown them in bulk, or whole folders, or top level folders and it kind of worked for a while, but on next login they belonged to root again.

So eventually I put them back under /media and I'm happy now, except that I lost timestamps on a dozen thousand files (they were originally on an 11 old disk, which was finally reaching its EOL).