![]() In the first place, it causes almost every Synology package that depends on the User Home service to fail. This fact have several consequences, all of them dangerous for our files, for DSM’s stability, and therefore for our NAS reliability. ![]() It is important to note that, although the user still has its home folder that works, the user homes created this way are outside the disk array and in the operating system’s filesystem. Not only you can see where it points, but also the l flag on the folder permissions, meaning link, instead of a d from directory. Lrwxr-xr-x 6 root root 4096 Feb 5 08:10 homes -> /volume1/homes We can check it by doing SSH to the $ ls -lda homes Instead, in this case the homes folder was created in that location directly, as a regular folder ( /var/services/homes). The problem is that the user homes’ hosting folder, named homes, should be created in one of the main volumes inside the disk array, for instance, /volume1/homes, and a symbolic link back should be created at /var/services/homes. If you try to disable and re-enable User Homes Service, DSM shows a sad and brief “Operation Failed” error pop up, and in Log Center you just see a useless message “User home service disable failed” like the one below: In the above picture you should see a folder for each user under homes, plus a home directory that would host your files (it’s like a symbolic link dynamically created when you log in to the NAS through DSM or DS File). Or, if you just enabled it to use home folders via SSH, although you land on a home directory when you log in through SSH, you can’t see it through DS File or File Station: Although you activate it, the dependent package keeps asking you to enable it. I came across the cause of the problem and its solution keep reading to know more.Īt some point you need to activate User Home service as per the requirements of some other package (for example, Synology Mail), or just because you want to work through SSH, or any other valid reason. Judging from the amount of Google results, the User Home service gets somehow broken quite often the first time it is activated, and neither is detected by some other services that use it as a dependency, nor can it be deactivated. I tried some weird thing just to see what happened like chmod 777 the admin’s shared directory but without any luck.If you have a Synology NAS and you are a technology enthusiast, or have some interest in using such machines as home servers, you may run into a problem that is quite common. I’m using a folder inside the home directory of each user /volume/homes/user/Drive/Syncthing and not the so my users can have access to their Synching directory from their phone. stignore: permission deniedįailed to create folder root directory stat So first just to clarify this: my non admin users doesn’t have any issue after I set the sc-syncthing user/app permissions (read and write) on their synching folder.īut if I try the same thing for my account (with admin privileges) I have the standard: Loading ignores: lstat. Hi everyone! Yep it’s a permission issue thread again
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |