NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dorian50
Apr 14, 2018Aspirant
ReadyNAS Duo V1 file share permissions broken, can't create/delete files
Had my ReadyNAS Duo V1 for a few years now. File share permissions were working fine. Now, as of a couple weeks ago, I can't write or delete files from the shares. I still have read permissions it...
- Apr 19, 2018
dorian50 wrote:
Repaired sectors is also 0.
Do you mean reallocated sectors?
Pending sectors and command timeouts also matter.
dorian50 wrote:
Volume scan just fixes issus w/ the file system, not the disk, right?
Yes. And it is possible for the file system to have issues even when the disks are healthy. One scenario for this is when the NAS power is cut (so there is no clean shutdown).
StephenB
Apr 16, 2018Guru - Experienced User
dorian50 wrote:
I was able to mount the drive on my Windows machine but still no write access.
Did you try the specific commands I suggested above?
This is almost certainly related to the use of guest credentials to access the NAS. Windows policy changes (and possibly similar changes in OSX) are generally at the root of it.
If those commands work, then it confirms that diagnosis, and we could then proceed to giving your your options to fix it.
dorian50 wrote:
Currently, I took out one of the drives to debug this. Will try shutting down and booting from the other one.
Do you have some theory of the problem that you want to test? If so, what is it?
dorian50
Apr 17, 2018Aspirant
When I mounted the volume on Windows laptop, I used the commands you gave. So I was connected with admin credentials instead of guest, right? I'm curious about the guest credentials, because they never seemed to work in the past.
My theory was to isolate which drive was bad, so I took out disk 2 and booted with just disk 1. Disk 1 was usable and I had read/write again. I moved some files around and lost write permissions during my test. I then rebooted and performed a volume scan. The logs indicate the volume scan found and corrected errors. Moved files around, still have write permissions. Then I hot-added Disk 2. RAID sync finished successfully.
I think the conclusion is that bad sectors/errors are the root of my issues.
- StephenBApr 18, 2018Guru - Experienced User
dorian50 wrote:
So I was connected with admin credentials instead of guest, right?
Correct.
dorian50 wrote:
My theory was to isolate which drive was bad, so I took out disk 2 and booted with just disk 1. Disk 1 was usable and I had read/write again. I moved some files around and lost write permissions during my test. I then rebooted and performed a volume scan. The logs indicate the volume scan found and corrected errors. Moved files around, still have write permissions. Then I hot-added Disk 2. RAID sync finished successfully.
I think the conclusion is that bad sectors/errors are the root of my issues.
Certainly there were issues with the file system, but I don't think you've proved there are bad sectors. Did you look at the SMART stats?
- dorian50Apr 18, 2018Aspirant
Checking SMART for both disks, ATA Error Count is 0 for both. Repaired sectors is also 0. Any other values I should check?
Volume scan just fixes issus w/ the file system, not the disk, right?
- StephenBApr 19, 2018Guru - Experienced User
dorian50 wrote:
Repaired sectors is also 0.
Do you mean reallocated sectors?
Pending sectors and command timeouts also matter.
dorian50 wrote:
Volume scan just fixes issus w/ the file system, not the disk, right?
Yes. And it is possible for the file system to have issues even when the disks are healthy. One scenario for this is when the NAS power is cut (so there is no clean shutdown).
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!