Release 4.1.9 - shares reverting to nobody/nogroup

[pugilares]

Same problem here.
My solution is to ssh into it and fix it.
But something must trigger it again, as I have already done it twice.

You will have to do it every time after you change anything in Frontview or restart ReadyNAS.

Solution is downgrade to 4.1.8 and make sure that automatic update in Frontview is off.

[Skywalker]

Ugh, that was an unfortunate oversight. I just posted a 4.1.10 beta that resolves the issue.

[sjw]

Just when I wasn't sure why all the posts about the buggy, share access changing 4.1.9 firmware were not being acted on, I saw this post.
So the exact same issues were actually posted in a 4.1.9 beta (what's the point of reporting them??) over 3 months ago - T6, then again in the T15 and even made it to public release. That defies belief.

Ugh, that was an unfortunate oversight. I just posted a 4.1.10 beta that resolves the issue.

Sorry skywalker, that's not an 'oversight', that's ignoring your customers (again) and the feedback they try to provide.

[pugilares]

Ugh, that was an unfortunate oversight. I just posted a 4.1.10 beta that resolves the issue.

This seems to be first word from Netgear that 4.1.9 is not ok. After 2 weeks of advertising this firmware and spreading it to all users having automatic update on. As we know now, that this firmware is unfortunate, this doesn't mean that this is not being advertised further as an official recommended firmware update. And also it is being pushed to automatic update configured ReadyNAS.

[supergedeon]

Hi
does this beta also resolve the readynas remote issue ?
thanks

answer : apparently not, still have the same issue. from iPhone application it logs in, it displays the name of the shares, if I select a share I get a login error.
it has worked for years and stopped working after 4.1.9 upgrade, the beta did not fix

[Deaf_Raiders]

How do you ssh into it? or downgrade back to 4.1.8 everytime i try to downgrade to 4.1.8 it saids local file failed

[rob@meerwijk.dk]

Just when I wasn't sure why all the posts about the buggy, share access changing 4.1.9 firmware were not being acted on, I saw this post.
So the exact same issues were actually posted in a 4.1.9 beta (what's the point of reporting them??) over 3 months ago - T6, then again in the T15 and even made it to public release. That defies belief.

Ugh, that was an unfortunate oversight. I just posted a 4.1.10 beta that resolves the issue.

Sorry skywalker, that's not an 'oversight', that's ignoring your customers (again) and the feedback they try to provide.

My next NAS will not be a ReadyNAS. It was rather expensive so you expect some support. One year ago smoke came out of the machine (litterally). Apparantly a design fault. And now a buggy official release with no solution from Netgear (I have cronned a scripped that restores ownership). I agree, this is ignoring your customers.

[mdgm]

The design fault was well documented in a Service Action back in 2007: http://www.readynas.com/forum/viewtopic.php?f=1&t=10259

They would have tried to recall units that were still at the distributor. Even now in many regions they still replace the PSU even on units well out of warranty and even though the product is discontinued.

There is a solution. How can you say there's no solution when you quoted Skywalker giving it? You can update to the 4.1.10 beta or downgrade to 4.1.8. Then use the Advanced Options tab to fix the ownership of the share. I even added a note in red to the top of the first post in the thread to say this.

[SONIC3D]

I got the same problem.

I solved it by Install ssh access addon,and use bitvise to connect this box,and open SFTP from bitvise.Then right click on the folder "/c/YOUR_SHARE_FOLDER_NAME",choose "property" in context menu,and modify the Group ID in "Permissions" tab to the group id show in web admin.Then the specific Share can be accessed again.

To those who have downgraded to 4.1.8 or upgraded to 4.1.10 beta,but still got this problem.You can use this method to solve it manually.

[pugilares]

I got the same problem.

I solved it by Install ssh access addon,and use bitvise to connect this box,and open SFTP from bitvise.Then right click on the folder "/c/YOUR_SHARE_FOLDER_NAME",choose "property" in context menu,and modify the Group ID in "Permissions" tab to the group id show in web admin.Then the specific Share can be accessed again.

To those who have downgraded to 4.1.8 or upgraded to 4.1.10 beta,but still got this problem.You can use this method to solve it manually.

Did you try to reboot to box and see who owns the shares after that?

[techman05]

Hi
does this beta also resolve the readynas remote issue ?
thanks

answer : apparently not, still have the same issue. from iPhone application it logs in, it displays the name of the shares, if I select a share I get a login error.
it has worked for years and stopped working after 4.1.9 upgrade, the beta did not fix

When has there been a noted issue on readynas remote with the current beta? Of a separate issue of my own is of not being able to re-register to remote.readynas.com . Did I just happen to fudge up at the wrong time?

[WSJ]

There is a solution. How can you say there's no solution when you quoted Skywalker giving it? You can update to the 4.1.10 beta or downgrade to 4.1.8.

Sorry to disagree.
4.1.8 has other bugs - that was the reason to release 4.1.9.
4.1.10 beta is not released for productive use - but that's what I've purchased my device for (which still has full warranty !!!)

Conclusion: no solution.
And it seems that the vendor does not bother at all.
Sorry, but I'm very disappointed.

[Skywalker]

The 4.1.10 final build should be up on the update server now.

[WSJ]

The 4.1.10 final build should be up on the update server now.

Yes - and it fixes the problem (I can confirm).
The only drawback is the fact that German umlauts (maybe all non-ASCII characters) are now broken on FrontViewer.

[Skywalker]

Well, that's no good. I took a look and this appears to have been fixed internally, but unfortunately after 4.1.10 was finalized. I'll see what I can do about getting a 4.1.11 release out soon.