NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
timhood
Jul 24, 2024Star
How to get volume back to read-write mode
I have a ReadyNAS 428 with two RAID5 Flex-RAID volumes. One volume experienced a disk failure and the volume was changed to read-only. I replaced the disk, formatted it, added it to the volume, and w...
- Jul 25, 2024
I had that happen to me. In my case, I knew it was because my EDA500 came unplugged during a write operation, and it was fixed. But everything I tried to make it read/write would not "take" -- it went back to read-only. It sounds like you already have a backup, which is good. Just make sure it's up to date and destroy and re-create the volume. I wouldn't trust the volume to not have a hidden remaining issue if you do anything else. The NAS makes the volume read-only to keep you from doing something that may destroy it but give you a chance to back it up. Take the hint.
timhood
Jul 24, 2024Star
I have a #ReadyNAS #RN428 with two RAID5 Flex-RAID volumes. One volume experienced a disk failure and the volume was changed to read-only. I replaced the disk, formatted it, added it to the volume, and waited for ReadyNAS to rebuild it. When complete, the volume status changed to "healthy," but the volume is still read-only. I rebooted the ReadyNAS and it's still read-only. How can I mark the volume read-write, as it should be fine? I do not want to reset the entire ReadyNAS due to the time required to rebuild and restore both volumes (8TB data) and because the other volume is perfectly fine. If absolutely necessary, I could destroy and rebuild the affected volume that is currently read-only, but surely there's an easier way.
StephenB
Jul 24, 2024Guru - Experienced User
timhood wrote:
I have a #ReadyNAS #RN428 with two RAID5 Flex-RAID volumes. One volume experienced a disk failure and the volume was changed to read-only.
A normal disk failure won't change the volume to read-only. Something else must also have gone wrong.
The safest thing to do is to destroy the volume, recreate it, and restore data from backup.
Maybe download the full log zip, and look for errors. My guess is that there are some btrfs errors on the volume.
- SandsharkJul 25, 2024Sensei - Experienced User
I had that happen to me. In my case, I knew it was because my EDA500 came unplugged during a write operation, and it was fixed. But everything I tried to make it read/write would not "take" -- it went back to read-only. It sounds like you already have a backup, which is good. Just make sure it's up to date and destroy and re-create the volume. I wouldn't trust the volume to not have a hidden remaining issue if you do anything else. The NAS makes the volume read-only to keep you from doing something that may destroy it but give you a chance to back it up. Take the hint.
- timhoodJul 25, 2024Star
Thanks. I'm OK with destroying the volume, because the rebuild/recovery process is manageable in my case. I had seen a previous solution that suggested resetting the entire ReadyNAS back to factory state and starting from scratch, which would not be acceptable, as the time to recover would be far too long. I destroyed and re-created the volume and it began a resyncing process.
Interestingly, looking at the logs, it seems there were several issues compounded that played a role. First was a drive that was failing and may have ultimately completely failed. Second was changes to an e-mail password that caused me not to receive the alerts about the failing drive. Third was when I did a firmware upgrade, after the reboot, that was ultimately when the OS didn't like the state of the volume and put it in read-only mode. Even after replacing the drive and resyncing, it stayed in read-only mode.
- timhoodJul 25, 2024Star
My concern, based on reading another "accepted solution", was that I would have to reset the entire NAS. I've taken the suggestion of destroying and re-creating the volume. Thanks for confirming that simply destroying the volume was enough in this case.
- StephenBJul 25, 2024Guru - Experienced User
timhood wrote:
My concern, based on reading another "accepted solution", was that I would have to reset the entire NAS.
I have recommended this when people have only one volume, or when the corrupted volume is the OS partition. But if only one volume is damaged, destroying and recreating it is enough.
If you have any apps installed, then you should figure out what volume holds the .apps folder.
Related Content
NETGEAR Academy

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