NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
core1024
Jun 01, 2011Aspirant
NTFS file permissions
Hi Guys, I have a ReadyNAS Ultra 4 Plus running RAIDiator 4.2.16. I'm using windows 7. Everything was working fine until recently. I had an old backup disk, NTFS formatted, from a computer...
Sandshark
Aug 09, 2011Sensei
just in case anyone else has the same problem; the only way I was able to solve this was to backup the drive to another share, using the "change ownership" option during the backup, and then rename the share, deleting the old one.
Yikes! Not an acceptible "solution". I, too, have a recently acquired Ultra4 Plus (U4+ from here on) with a similar problem. I updated to 4.2.17 before doing anything and have created a couple users and groups. I connect to CIFS shares in XP using one of those user accounts.
I've copied my files (almost 3TB) from my NV+ media folder to the U4+ media folder. Media folder options on the U4+ are the default. NV+ is still using Share access. I started a backup task to move some (pulling from the more-powerful U4+ using Remote Windows/NAS Timestamp) and moved others manually. All files and folders moved by the backup task cannot be moved, deleted, or renamed using a non-admin account. Can't add anything to folders created by backup task with non-admin account. Files and folders moved manually are fine. Still using XP and have not installed SSH access or any other easy way to confirm ownership and permissions. But "Users and Groups" shows all the space allocated to my user account and my primary group (which I find odd, since I did not use my account info anywhere in the backup task). So even if the "open" nature of the share is flawed, I should have these permissions under my own account.
Tried resetting permissions and, just liike the OP, got the spinning busy for a few seconds and it said it was done. No way it changed 3TB of files' owners and permissions in a few seconds. If there was disk access, it was so fast I didn't notice.
Though I got there in a different way, I seem to be in the same place as the OP. The feature present to fix this type of problem simply does not work as advertised.
Is there a real solution to this issue? I'm thinking of enabling root SSH and seeing what I can do there. Worst case, I reload the firmware or factory default it and start over.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!