ReadyNAS 104 - volume data encountered an error and was made read-only
Last month and this month, I received the error "volume data encountered an error and was made read-only" when Scrub started. I restarted the NAS (since I'm calling it an unreliable backup right now), and the volume restarted as read/write. I'm currently having Aomei Backupper check my backup files, but, that can take a while. Last month, I had a corrupt backup.
I've had *numerous* issues with this box in the past 3 years, where the filesystem would just decide to be corrupt and I lose all data. It was to the point, I bought a new setup with the competition and decided to use this as a backup device.
Apparently, it doesn't want to work as a backup device.
Does anyone have any idea what is going on so I can have it be somewhat stable?
Device: ReadyNAS 104
Software Version: 6.10.1
Drives: (4) 6TB WD Red (WD60EFRX)
No apps or anything running. In fact, it was factory reset (again) in May or June after the last filesystem corruption that couldn't be saved.
I was going to attach logs for the last two events, but, apparently .zip isn't a valid extension 🙂
Re: ReadyNAS 104 - volume data encountered an error and was made read-only
Hi @SmplyUnprdctble, you might want to read through my collected experiences with RN104 and see, whether anything of the recommendations might help in your situation. Kind regards
I was going to attach logs for the last two events, but, apparently .zip isn't a valid extension 🙂
You shouldn't post the full log zip publicly anyway - there's information in there that shouldn't be shared.
You can put the log zip into cloud storage (google drive, dropbox, etc) and send a link to one of the mods ( @JohnCM_S or @Marc_V ) and ask them to analyze them. Do that via PM (private message) by clicking on the envelope icon in the upper right of the forum.
You can also copy/paste a section of a log into a reply here. I suggest using the "insert code" tool for that.
FWIW, I recently found a failed WD60EFRX in my own NAS that had good SMART stats. One thing you could try is enabling ssh and running smartctl -x on each drive. Look in the "SMART Extended Comprehensive Error Log" section.
I found stuff like this:
Error 12 [11] occurred at disk power-on lifetime: 36166 hours (1506 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 0c 27 df 40 40 00 Error: UNC at LBA = 0x0c27df40 = 203939648
If you see anything like that for one of your drives, then connect it to a Windows PC and test it with lifeguard. Run the full non-destructive test, and if that passes then test it again with the full write-zeros test.
