NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tbspray7
Jul 20, 2020Aspirant
RR3312 Copying Errors
Hello, We have ReadyNAS 3312 (RR 3312 w/ 12 bay, Firmware: 6.10.3) that has been throwing volume alert message reading: "The volume data encountered an error and was made read-only. It is recomme...
tbspray7
Jul 21, 2020Aspirant
We don't anticipate that the drive filled up, the data being moved over was on the order of GB when it has happened. So far, none of the drives have indicated any errors.
How do we determine the root cause of the volume error? We prefer not to proceed with the rebuild until we know the root cause, and can ensure it won't happen again in the future. We do have backups of all the data, but there is so much data involved it takes a month to restore from the backups and validate the accuracy of the restoration. This ReadyNAS is less than a year old, so hopefully we don't have to completely rebuild ever year.
Thank you for the response! I greatly appreciate it.
Sandshark
Jul 21, 2020Sensei
Logs in the downloaded .zip file are a good place to look to see if there is a hard drive that's giving you problems. Unfortunately, even new drives can fail.
I'm assuming that in a use case like yours, you have an UPS that is monitored by the NAS,. so a power interruption during a write operation isn't a possibility.
- tbspray7Jul 21, 2020Aspirant
Hmm. It doesn't look like there are any disk errors recorded. The file repeats the following 12 times as expected (given the Channel and serial number change).
Device: sdd
Controller: 0
Channel: 0
Model: ST16000VN001-2RV103
Serial: ZL20BQB5
Firmware: SC61
Class: SATA
RPM: 7200
Sectors: 31251759104
Pool: data
PoolType: RAID 6
PoolState: 1
PoolHostId: a450594
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 35
Start/Stop Count: 12
Power-On Hours: 6753
Power Cycle Count: 12
Load Cycle Count: 43945Correct, the server is on a UPS that is monitored by the NAS.
- SandsharkJul 22, 2020Sensei
Well, then I can't point to anything that I think could have caused it, though i suppose there could still be an issue with the NAS hardware. I can say that it's atypical and I don't think you should be concerned you'll be encountering it periodically. I've used a variety of ReadyNAS over the years, including my current use of legacy rack-mount systems converted to OS6, and I have only seen this once. And that was mostly my fault -- the eSATA cable between an RN516 and EDA500 was loose, causing a lot of data issues. (I say mostly my fault because the choice of connector for eSATA is just a really bad engineering decision -- not Netgear's, mind you, but by whoever designed the interface standard. )
Occurrences of similar issues reported in this forum typically have an identifiable cause (usually a failing drive with at least ATA errors or lack of proper UPS protection).
Since I knew what caused it and that it was corrected, I thought I could save the volume. That's where I got the experience to say don't even try. No matter what I did, the volume was read-only again within minutes. Since my corrupt volume was on the EDA, I could just destroy and re-create it and not touch the primary volume. I feel your pain in the data restoration -- the EDA500 is extremely slow due to the eSATA interface, and I had 5x6TB in it in RAID5. But it was mostly archival data, so that probably made it a little less painful than yours will be if you are without current working data for any period of time.
The volume rebuild process will also be a good gauge of whether you do have a hardware issue, so check the logs after that completes.
- tbspray7Jul 23, 2020Aspirant
We were doubting it was hardware, but still a small possibilty. Thank you for advice and all of the help. We will try the rebuild and post back here if we get something figured out. Oddly enough, I have a friend has seen this error thrown on their other two ReadyNAS servers, but has never been able figure out why it happened on their end, only that its periodically occured.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!