Another ReadyNAS or something else?

IN MY EXPERIANCE ID SAY SOMETHING ELSE!!!!! I'VE SPENT ALMOST A WEEK TO GET THIS SLOW POS REANYNAS TO WORK RIGHT AND ALL MY TIME WAS WASTED IT DOESNT WORK!!!

Be very careful when moving away from a ReadyNAS. I was lured in by the nice glossy interface and promises of easy add-on servers and applications for the Synology NAS (DS213+, DSM4.3) and it sure looked nice and seemed to work very well during the week I tested it. The problem is when trying to set file permissions on shared folders.

The default permissions on shares is 777, just to make them work nicely with all other systems. There are no "setfacl"/"getfacl" commands, only the "synoacltool" which is undocumented.

I read as much as I possibly could on the Synology forum, posted my own question and contacted support, but nothing could really be done. The "smb.conf" the Synology uses is overwritten by secret values stored in some obscure file on every reboot, so it does not matter if you try to fix the permissions yourself, as soon as you reboot they are back to the default again.

This was the reply I got from their support department:
Since the rules you would like to setup will cause conflicts due to the privilege priority is as follow: No access > Read/Write > Read only.
- RW: users group
- NA: everyone (Please be noticed all users account belong to users group by default)
Which means everyone is NOT possible to access the shared folder include admin.

In our current design, the default shared folder permission is 777 since we also need to handle different type of permission controls across various platform (windows,Mac and Linux).

I have had a ReadyNAS Duo v1 for many years now and the share permission settings just worked the first time I configured it and has continued to work ever since... I think I understood from the manual of ReadyNAS OS 6 that the permissions are still handled the same way, maybe someone can confirm this? :)

MoonSire wrote:
I have had a ReadyNAS Duo v1 for many years now and the share permission settings just worked the first time I configured it and has continued to work ever since... I think I understood from the manual of ReadyNAS OS 6 that the permissions are still handled the same way, maybe someone can confirm this? :)

The permissions with the new OS don't seem to work the same way, out of the box, as the old. I've been having a bear off a time getting access to all files after the first migration of files. I thought I had it right until the first time I tried to push an rsync backup to a readynas ultra. It changed the owner of the files to a random UID, which never could get sorted.

Pulling all my backups with the Ultra has solved it on an interim basis, but evidently I need to set up some chron jobs to maintain ownership and permissions. That really does need to be fixed.

Sent from my GT-N8000 using Tapatalk 4

DeeCee52 wrote:

MoonSire wrote: I have had a ReadyNAS Duo v1 for many years now and the share permission settings just worked the first time I configured it and has continued to work ever since... I think I understood from the manual of ReadyNAS OS 6 that the permissions are still handled the same way, maybe someone can confirm this? :) The permissions with the new OS don't seem to work the same way, out of the box, as the old. I've been having a bear off a time getting access to all files after the first migration of files. I thought I had it right until the first time I tried to push an rsync backup to a readynas ultra. It changed the owner of the files to a random UID, which never could get sorted. Pulling all my backups with the Ultra has solved it on an interim basis, but evidently I need to set up some chron jobs to maintain ownership and permissions. That really does need to be fixed. Sent from my GT-N8000 using Tapatalk 4

Hmmm, that is good to know, thank you. I will probably replace both my old v1:s with 31X:s at the same time, so hopefully they will be able to maintain the permissions properly between themselves.

My RN102 is used mainly for backup, and I am pulling the backups from the OS6 system.

DeeCee52 - what was the "random UID" that the files were being set to?

I don't think the UID problem is exactly the same as file permission handling. The issue is more about mapping user accounts across systems that don't have the same UIDs.

One problem is that the OS6 systems use different UIDs/GIDs for nobody/nogroup (99 for OS6, 65534 for OS4), which can create problems if you are backing up to/from the older systems. I worked around this by avoiding nobody/nogroup on my pro.

You could also try resetting the username to match the share owner in the OS6 backup job. Though early on there was a bug with that setting, so you'd need to test it.

I would get a random low number UID that didn't correspond to a group or user on my windows workgroup. Everyone was then kicked out unless the share is set to everyone.

Swyped from my Galaxy Nexus using Tapatalk 4

I didn't see a case where the OS6 system just made up a random UID/GID.

I have seen it preserve the OS4 UID/GID instead of mapping it by name to the corresponding OS6 value. That was with pre-release beta firmware.

StephenB wrote:
I didn't see a case where the OS6 system just made up a random UID/GID. I have seen it preserve the OS4 UID/GID instead of mapping it by name to the corresponding OS6 value. That was with pre-release beta firmware.

These were completely different UID and they were not from OS 4 either. I've been traveling and haven't been able to consistently be available to respond to support, so I decided to pull back ups instead off push them.

Back on the topic off sticking with readynas / netgear, at the end off the day, even with my frustrations with the system, the EOL of muy still under warranty Ultra unit, my experience with Netgear when things go terribly wrong has been exemplary.

My unmanaged switch died and it was replaced quickly with little fuss. And off course the NASs have been rock solid running 24/7.

Sent from my GT-N8000 using Tapatalk 4