NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Volume: The volume XXXX encountered an error and was made read-only. It is recommended to backup
Hello, I have just received this notification: Volume: The volume Volume1TB encountered an error and was made read-only. It is recommended to backup your data I just checked and the volume is mark...
Well, end of the story. For posterity:
when it happens, do not attempt anything except a backup copy.
Files should be ok (they were all fine in my case, no data loss), as someone else said in another similar thread office files won't open, but I think it's because office tries to lock them and it is not able to write on the share, but if you copy them somewhere else they will be ok.
But don't do anything else, after I tried to reboot the volume was completely gone, together with the data.
If this failure happens in the volume including the first disk, applications are lost too. Lesson learned here (it took a while): backup all configurations in a share, which is backed up again.
My two 6-months new WD HDD are now moved to external USB units for automatic backup and two new Seagate Ironwolf disks are in.
Rebuilding is in progress (my personal discovery, copy files from backup USB unit to volumes is a lot faster if done from SSH), let's hope it will last for a while...
Thanks again to StephenB for the support!
The WD40EFAX might be part of the equation. It uses SMR technology (which WD finally admitted last April), SMR drives slow down significantly during sustained writes, so they aren't great for RAID arrays. https://www.servethehome.com/wd-red-smr-vs-cmr-tested-avoid-red-smr/2/ Personally I would replace it. You could reach out to WD, not sure if they would exchange it for a WD40EFRX or not. Given the controversy, and the fact that you are having some problems with your array, they might be open to that.
gpaolo wrote:
Oct 01 01:09:06 NAS4-CASA-GP kernel: BTRFS warning (device md126): Skipping commit of aborted transaction. Oct 01 01:09:06 NAS4-CASA-GP kernel: BTRFS: error (device md126) in cleanup_transaction:1864: errno=-5 IO failure
This of course is the error. There is a disk test function on the volume tab that you might want to run. But it is possible that the IO failure was a timeout of some kind (because of the major write slowdown SMRs can suffer from).
While it is likely possible that you could recover the volume with ssh, the best approach is to rebuild the array with s factory reset. If you are skilled with ssh, we can provide you with some steps to recover the array.
BTW, it isn't a great idea to post the log zip file publicly, as there is some leakage of private information. I've taken the liberty of redacting your download link.
StephenB wrote:
While it is likely possible that you could recover the volume with ssh, the best approach is to rebuild the array with s factory reset. If you are skilled with ssh, we can provide you with some steps to recover the array.
Honestly I would hope to avoid another factory reset. I had to do another one a few months ago when the previous volume failed... Also because the other volume is ok. And then I would need to do another one again if I change the drives, I guess.
If there is a way to try to recover the volume I would like to try it, please. Of course, once the backup is finished.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
