NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GJSchaller
Jan 13, 2020Guide
RN214 on 6.10.2: The volume data encountered an error and was made read-only.
This past weekend, my ReadyNAS gave the following error: The volume data encountered an error and was made read-only. It is recommended to backup your data. There's no indication what the actual...
- Jan 13, 2020
Those BTRFS errors might be able to fixed on the backend but it would be best if you start over. Cause of this errors might be due to dirty reboots that caused transactions to not complete. Not really sure how to explain but if you have any chances of outages or power loss or disk failures while in use then that can contribute.
HTH
Regards
GJSchaller
Jan 13, 2020Guide
Status.log, volume.log both look good.
dmesg.log has some warnings about my Ethernet - I did just switch how the device is connected to my network, but I didn't think that would impact the file system.... to be safe, I'll revert those changes and be sure.
As noted, I do have a backup, I just hate resetting a device without having an understanting of what failed and why.
GJSchaller
Jan 13, 2020Guide
OK, now we're getting somewhere.... found this in dmesg.log:
[Sun Jan 12 17:18:29 2020] BTRFS error (device md127): parent transid verify failed on 7765871394816 wanted 4157903 found 4225465 [Sun Jan 12 17:18:29 2020] BTRFS error (device md127): parent transid verify failed on 7765871394816 wanted 4157903 found 4225465 [Sun Jan 12 17:18:29 2020] BTRFS warning (device md127): Skipping commit of aborted transaction. [Sun Jan 12 17:18:29 2020] BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure [Sun Jan 12 17:18:29 2020] BTRFS info (device md127): forced readonly [Sun Jan 12 17:18:29 2020] BTRFS: error (device md127) in btrfs_drop_snapshot:9412: errno=-5 IO failure [Sun Jan 12 17:18:29 2020] BTRFS error (device md127): could not do orphan cleanup -30 [Sun Jan 12 17:18:29 2020] BTRFS info (device md127): delayed_refs has NO entry
- Marc_VJan 13, 2020NETGEAR Employee Retired
Those BTRFS errors might be able to fixed on the backend but it would be best if you start over. Cause of this errors might be due to dirty reboots that caused transactions to not complete. Not really sure how to explain but if you have any chances of outages or power loss or disk failures while in use then that can contribute.
HTH
Regards
- GJSchallerJan 13, 2020Guide
I have a UPS configured and in use, so power outages shouldn't be a cause / issue. I have backups, I'll just make sure they are good before I do a Factory Reset and restore my data.
My main concern will be my RNXtras apps, but hopefully that'll be easy to remedy.
- SandsharkJan 14, 2020Sensei - Experienced User
If you've lost the installation file for your RNXtras apps, you can always log into your account there and re-download. Depending on the app, there might even be a free update.
Related Content
NETGEAR Academy

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