ReadyNAS 104 Write Protection Issue

Question

I have a ReadyNAS 104 fw 6.10.7. I have had it for many years and it has been extremely reliable. I have the NAS plugged into a dedicated UPS and all of my network gear is on a different UPS. Lately I have an issue when I try to write files from my PC to a Mapped Network Drive on the NAS - it gives me a Write Protect Error. I checked permissions and all folders are available to read/write. If I reboot the NAS the issue goes away. Any ideas on how to fix this? My PC OS is Windows 10 Pro. This is a home environment not a business. Any advice would be appreciated.

StephenB · Answer

pekhaqun&nbsp;wrote:

&nbsp;Lately I have an issue when I try to write files from my PC to a Mapped Network Drive on the NAS - it gives me a Write Protect Error. I checked permissions and all folders are available to read/write. If I reboot the NAS the issue goes away.&nbsp;

The next time you see this, log into the NAS and make sure that the NAS has not set the volume to read-only mode.&nbsp; If it has, then there is something going on with the volume that needs immediate attention.
&nbsp;
Also, instead of rebooting the NAS, try rebooting the PC, and see if that also resolves the problem.

StephenB · Answer

Sinistar914&nbsp;wrote:
Sep 14, 2022 05:48:10 PM Volume: The volume data encountered an error and was made read-only. It is recommended to backup your data.

First thing to do is follow this advice, and back up your data without delay.
&nbsp;
After that, download the log zip file (which has a lot more information than what is shown in the web ui).&nbsp; It's possible that the best response is to recreate the volume and shares, and then reload data from backup.&nbsp; But first priority now is data safety.

StephenB · Answer

Sinistar914&nbsp;wrote:
I have all of the important files backed up already.&nbsp; Here is a link to my Log file;
&nbsp;
Whats the next step? Is there a recovery utility for the drives or do I have to reformat and start over?
&nbsp;

Most of the logs have rotated, but dmesg.log is showing this as the cause:
[Wed Sep 14 17:19:28 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13631, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:21:33 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13632, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:21:33 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13633, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:23:38 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13634, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:23:38 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13635, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:25:38 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13636, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:27:37 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13637, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:29:37 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13638, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:29:37 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13639, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:31:36 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13640, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:33:36 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13641, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:35:35 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13642, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:35:35 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13643, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:37:34 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13644, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:37:34 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13645, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:39:36 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13646, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:39:38 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13647, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:41:38 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13648, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:41:38 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13649, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:43:38 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13650, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:45:37 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686836, rd 13651, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:46:51 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686837, rd 13651, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:46:51 2022] BTRFS error (device md126): bdev /dev/md127 errs: wr 3686838, rd 13651, flush 0, corrupt 0, gen 0
[Wed Sep 14 17:46:51 2022] BTRFS: error (device md126) in btrfs_commit_transaction:2249: errno=-5 IO failure (Error while writing out transaction)
[Wed Sep 14 17:46:51 2022] BTRFS info (device md126): forced readonly
Unfortunately we can't see what disk generated the error, and whatever happened isn't reflected in the SMART stats.&nbsp; If you have ssh enabled, you could look with smartctl -x.
&nbsp;
Recovery might be possible, but there is no surefire way to know that that you've fully resolved the problem.&nbsp; I suggest testing the disks in a PC (using seatools for the two seagate disks and dashboard for the two western digital ones).&nbsp; That would require either connecting the disks with SATA or using a SATA-&gt;USB adapter or dock.
&nbsp;
If the disks look ok, then try destroying and then recreating the volume.&nbsp; You will need to recreate shares and reinstall your apps (since the apps are installed onto the data volume).

michaelkenward · Answer

pekhaqun&nbsp;wrote:

I have a ReadyNAS 104 fw 6.10.7.

While many questions about routers are generic and could be answered anywhere, some things need specialist knowledge.
&nbsp;
ReadyNAS is not a router so you might get more help, and find earlier questions and answers specific to your device, in the appropriate section for your hardware. That's probably here: ReadyNAS Network Storage: Official NETGEAR CommunityI will ask the Netgear moderator to move your message.In the meantime you could visit the support pages:Support | NETGEARFeed in your model number and check the documentation for your hardware. Look at the label on the device for the model number.Check for various troubleshooting tips.You may have done this already. I can't tell from your message. I mention it because Netgear stopped supplying printed manuals and CD versions some years ago and people sometimes miss the downloads.

Sinistar914 · Answer

Thanks for responding to my question - I was the OP of this question on Reddit - I don't know who @pekhaqun is but thanks for reposting it here.

Anyway - I just had the problem again, logged into my NAS and I see that it is indeed set to read-only.

My drives are all green. I had 4x 2TB SATA Drives in RAID5 config. I have 1.18TB free and 4.26tb of data on my drives.

Here are the last couple of entries in my log - any suggestions on how to fix this?

Sep 17, 2022 01:00:31 AM System: Download firmware version () failed.
Sep 14, 2022 05:48:10 PM Volume: The volume data encountered an error and was made read-only. It is recommended to backup your data.
Sep 14, 2022 05:19:11 PM System: ReadyNASOS background service started.
Sep 14, 2022 05:18:44 PM System: Alert message failed to send.
Sep 14, 2022 05:18:44 PM Volume: Less than 20% of volume data's capacity is free. Performance on volume data will degrade if additional capacity is consumed. NETGEAR recommends that you add capacity to avoid performance degradation.
Sep 14, 2022 05:13:44 PM System: The system is rebooting.
Sep 14, 2022 04:28:03 AM Volume: The volume data encountered an error and was made read-only. It is recommended to backup your data.

Forum Discussion

ReadyNAS 104 Write Protection Issue

8 Replies

Related Content

NETGEAR Nighthawk - Protection Engine Feature FAQ

Loop protection

External Drive is now Write-Protected

How to get volume back to read-write mode

DDoS protection

NETGEAR Academy

ProSupport for Business