Can’t change permissions – “The parameter is incorrect”

I guess the main theme here is that none of us want this issue to slip through the cracks. Speaking from my own perspective, this is the first time I have had to work with Netgear on an issue (our first ReadyNAS) and I don't have a high degree of trust built up yet that you guys will actually follow this through to resolution. The previous vendors we worked with (QNAP and Promise) also kept saying "we know it's a bug and we are working on it" for the quirky issues they had but I never saw resolution there after months of waiting (although they were pretty quick with a workaround in most cases) and eventually made the switch to Netgear. Now I am getting the same responses from Netgear. Do you have a bugzilla type site available so we can at least see that the bug is on the to-do list?

I really do not aim to offend you, Grievous, but I assume you are not the one actually fixing the problem. I assume you have relayed it to the developers and they are working on the issue, along with their many other feature requests, enhancements, bugs, etc. Sorry, but just taking your word for it doesn't do much for me (again, nothing personal).

No, we do not have a public bugzilla type database. As far as who is working on it, more accurately would be "I'm not the only one working on the problem". Like I've said before, this isn't something that can be taken care of quickly and even after we've got a fix in place we still need to make sure it doesn't break something else.

Ok, with the t-33 beta, we're only able to reproduce it with folders created prior to updating to t-33. Clearing the permissions on one of those folders and then re-creating them should work

Grievous wrote:
Ok, with the t-33 beta, we're only able to reproduce it with folders created prior to updating to t-33. Clearing the permissions on one of those folders and then re-creating them should work

Thank you for the update Grievous. I applied t-33 to a brand new 6310-200 and I still receive the error message. PLEASE help - I have a $25k project on hold because of this.

Cheers. :)

readynas_devotee wrote:
Grievous wrote: Ok, with the t-33 beta, we're only able to reproduce it with folders created prior to updating to t-33. Clearing the permissions on one of those folders and then re-creating them should work Thank you for the update Grievous. I applied t-33 to a brand new 6310-200 and I still receive the error message. PLEASE help - I have a $25k project on hold because of this. Cheers. :)

But is it happening with a NEW folder, or a folder that existed prior to updating to t-33?

Going to give T-33 a shot I think.

While I'm waiting for about 6TB to copy I thought I'd mention that I noticed I'm getting errors from our XenServer backup script (which is mounting via CIFS for reasons unknown :? ) that are reporting:

Error code: SR_BACKEND_FAILURE_44
Error parameters: , There is insufficient space,

This is strictly for new subfolders in a share that's been working fine until I upgraded to 4.2.15. Old directories are continuing to work perfectly. At the point the errors are thrown the script is attempting to export a snapshot to the ReadyNAS which has 2.75TB of free space available.

I doubt that's new info for you guys but it's marginally more illuminating than the errors Windows produce at least. I'll give it a go via NFS to once this backup run is finished.

Grievous wrote:
But is it happening with a NEW folder, or a folder that existed prior to updating to t-33?

Hi Grievous,

Brand new out of the box. Had immediate issues with new shares and folders. Reset to factory. Tried again - failed.
Reset to factory. Updated to T-33.

New share, new folder. Fail. Tried resetting to factory after the first failure with same result.

I am happy to help, so let me know if you need anything.

Cheers.

rob

We also have this problem, and worse!
Running a ReadyNAS Pro (RAIDiator 4.2.15 ) with all users documents on it; Offline-files of My Documents-folder.
Server 2003 R2 AD-domain with mix of XP and Win7 clients.
Server 2003, Server 2003 R2, Server 2008 and Server 2008 R2 is available as member-servers.

All of a sudden users are locked out of randomly selected folders with "Access denied". Not necesarilly all folder, but some. When we try to fix this the error "Parameter is incorrect" occures, what ever we try to do on that users folder.
At the same time the other 40+ users are working fine, so it's not likely to be an error in the root-folder.

C:\USERS shared as "\\READYNAS\Users" in AD domain mode.
All users folders directly under this folder and "My Document" redirected to "\\READYNAS\USERS\%USERNAME%"

We have ACL like this;
USERS-folder (standard set by RAIDiator i think);
administrator - Full control - This folder, subfolders and fles
Users (READYNAS\Users) - Special - This folder only
nogroup (UNIX Group\nogroup) - Special - This folder only
Everyone - Special - This folder only
CREATOR OWNER - Special - Subfolder and files only
CREATOR GROUP - Special - Subfolder and files only
Everyone - Special - Subfolder and files only

On Sub-folders, named %USERNAME% (firtstname.lastname) we have;
Domain Admins - Full control - This folder, subfolders and fles
%USERNAME% - Full control - This folder, subfolders and fles
Everyone - None - This folder, subfolders and fles
CREATOR OWNER - Special - Subfolder and files only
CREATOR GROUP - Special - Subfolder and files only
administrator - Special - This folder only

BUT we have set ONLY Domain Admins and %USERNAME%, nothing else!

In some cases other users and groups appear in the ACL's without we adding them!
For exampel I have a "35926 (Unix Group\35926)" added in some users folders ACL's, and that is not anything I put in there! not even the user... Also "root (Unix User\root)" is set in some ACL's.

In some folder the "Domain Users" group appear, but I dont see a pattern that it is this group that are the error (sorry). Some folders work fin despite having it in ACL, still there is some folders that stop working and dont have it in ACL.

ReadyNAS messes with ACL's, that's for sure.
Problem is that it changes! If we set correct permissions and it works, we cannot trust it to work "forever".

As I type this I got two users that cannot create folders anywhere in their "My Documents" but can read them all fine. One other user has one folder (of many) that is unaccessible with error "Access denied".
...and I cannot do ANYTHING to fix it!

I as an domain admin get "parameter incorrect" when trying to change ACL or take ownership, "access denied" when trying to copy mentioned folder above.

FRUSTRATING!

/Per Dahlström, IT-consultant and Netgear Partner
MCSE with 20 years of experience of Windows Servers (NT3.5 - to date)

perdahlstrom, that is not the same issue that we've been discussing in this thread. I would highly advise creating your own thread for this so we can keep it separate and avoid any confusion.

Grievous:

Are you consistently not seeing the problem on new shares on T33? I saw that post from that user who said he upgraded to T33, did a bunch of resets, and created new folders, and still ran into the issue. If you could provide a step by step for what you did coming from .15 firmware that exhibited the issue to get to T33 and not lose pre-existing shares, I'd appreciate it. I want to get to the new firmware, and know exactly what security mode I should be in, where to create a new share, what permissions to assign to the new share, what permissions to assign to the folders I want to copy (if any) etc.

Has the ISCSI implemtation in T33 been broken? That's my only concern with going to the beta. I don't use any plugins or addons, but I do use the device as an iSCSI target (without CHAP) to a XenServer host.

Thanks for your help, and I appreciate your interaction with this thread--even when you're in the unfortunate position of having to relay no news. Been there. Sucks.