NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Rn314 update to 6.10.1 made volume to read only
I upgraded to the current relase 6.10.1 and after reboot I recived the message:Volume: The volume data encountered an error and was made read-only. It is recommended to backup your data.
Has anyone else experienced this?
Is the only way to recitfy this issue is to default the box back to factory and rebuild the raid?
Can I rebuild the raid with out having to factory the unit?
Is doesn't show any hard drive errors at all.
tglazier wrote:
So it looks like disk 3 is the problem, is it possible to just replace the disk and let the raid rebuilt itself? And when it's done will it become writeable once again?
Normally a failed disk won't result in a read-only volume - so I'm not sure if replacing the disk is enough. You could try booting up without disk 3, and see if volume still ends up read-only. If it doesn't, then hot-insert the replacement disk.
9 Replies
tglazier wrote:
I upgraded to the current relase 6.10.1 and after reboot I recived the message:Volume: The volume data encountered an error and was made read-only. It is recommended to backup your data.
Begin by backing up your data. Don't try to figure it out until that's taken care of.
tglazier wrote:
Is doesn't show any hard drive errors at all.
It wouldn't. Try downloading the log zip file, and look in system.log and kernel.log. Look for disk-related issues and btrfs errors.
tglazier wrote:
Is the only way to recitfy this issue is to default the box back to factory and rebuild the raid?
Can I rebuild the raid with out having to factory the unit?
Let's see what the errors are first, and then figure out the best way to fix them.
But generally it's safest to do a factory default, as you will end up with a completely clean filesystem when you do that.
I am not so worried about the data as this box is a DR box and not our primary NAS so I can retrieve it from our off site facility and default it and rebuild it.
Thanks for the log info. I found this in the Kernel log.
May 29 10:12:17 matrix-nas-rmt kernel: BTRFS error (device md127): parent transid verify failed on 304545792 wanted 749219 found 773951
May 29 10:12:17 matrix-nas-rmt kernel: BTRFS error (device md127): parent transid verify failed on 304545792 wanted 749219 found 773951
May 29 10:12:17 matrix-nas-rmt kernel: BTRFS warning (device md127): Skipping commit of aborted transaction.
May 29 10:12:17 matrix-nas-rmt kernel: BTRFS: error (device md127) in cleanup_transaction:1864: errno=-5 IO failure
May 29 10:12:17 matrix-nas-rmt kernel: BTRFS info (device md127): forced readonly
May 29 10:12:17 matrix-nas-rmt kernel: BTRFS info (device md127): delayed_refs has NO entry
May 29 10:12:17 matrix-nas-rmt kernel: VFS:Filesystem freeze failed
May 29 10:12:19 matrix-nas-rmt kernel: BTRFS error (device md127): Remounting read-write after error is not allowedSo you do have btrfs errors and a disk i/o failure.
If rebuilding is easy, I'd just do that. If you have a lot of users to configure, you can destroy the data volume and recreate it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
