NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NETGEAR ReadyNAS 2304 (RR2304) RR230400 Volume Degraded Notification and Can't Connect to NAS
I am receiving email notifications from my ReadyNAS 2304 that indicated: "Volume data health changed from Redundant to Degraded." and then received a second email notification: "Disk Model:ST4000V...
Thanks so much for the response and suggestions.
I am going out of town for the next two weeks, but will try those out as soon as I am back.
The kids did not drop them from what I see, I assume that since they were still in the server rack just loosened. I pushed them back in to secure them back in place.
I am hoping it can be resolved by just connecting to the hard drives with Seatools.
I did not try RAIDar, but will try that too and report back.
Much appreciated!
Leo
These are the steps that I followed:
1) Downloaded and installed SeaTools on my PC
2) Connected each of the 2 x NAS to my PC and ran the Long Self Test on each hard drive independently. They both passed the test.
3) Shutdown the server and inserted the NAS drives back in, then restarted.
4) Downloaded and installed RAIDar 6.5.0 software (thought I had this installed already, but it appears not).
5) Started RAIDar and was able to click the "Admin Page" button to open the browser and connect to the server.
6) On the Admin Page I navigated to the "Volumes" Tab within the "System" Tab and see some error messages in the Alarms Log (see attached picture).
7) On the Logs page it shows the following, seems the issue started on 30CT2023.
| Nov 15, 2023 11:16:35 PM | System: Antivirus scanner definition file was updated to 62.27094. | |
| Nov 15, 2023 11:05:37 PM | Volume: Disk test started for volume data. | |
| Nov 15, 2023 10:59:07 PM | System: ReadyNASOS background service started. | |
| Nov 15, 2023 10:59:05 PM | System: ReadyNASOS service or process (systemd,connman) was restarted. | |
| Oct 31, 2023 08:40:11 AM | Volume: Resyncing started for Volume data. | |
| Oct 31, 2023 08:40:03 AM | System: ReadyNASOS background service started. | |
| Oct 31, 2023 08:40:00 AM | Volume: Volume data is Degraded. | |
| Oct 31, 2023 08:39:58 AM | System: ReadyNASOS service or process was restarted. | |
| Oct 30, 2023 09:20:53 PM | Disk: Disk Model:ST4000VN008-2DR166 Serial:ZDH4A73Q was removed from Channel 2 of the head unit. | |
| Oct 30, 2023 09:19:07 PM | Volume: Volume data health changed from Redundant to Degraded. | |
| Oct 30, 2023 07:18:12 PM | System: Antivirus scanner definition file was updated to 62.27077. | |
| Oct 30, 2023 07:01:46 PM | System: ReadyNASOS background service started. | |
| Oct 30, 2023 12:00:10 AM | System: The system is shutting down. | |
| Oct 29, 2023 10:18:27 AM | System: Antivirus scanner definition file was updated to 62.27076. |
I am getting the error "No volumes exist" when I select "Shares" Tab to view the hard drives. I am thinking the worse at this point.
Any thought on how to resolve this?
Thanks,
Leo
Download the full log zip from the logs page.
If you need help interpreting it, you can send the full zip to me via a private message (PM). Do that using the envelope icon in the upper right of the forum page.
You can't directly attach the zip, but you can upload it to cloud storage (dropbox, google drive, etc) and include a download link in the PM. Make sure the link permissions allow anyone with the link to download.
While the full log will give more information, the log you posted shows the ReadyNASOS process re-starting on Oct31 and again on Nov 15. Are these associated with you shutting down the unit? Possible forcefully? Or maybe by schedule? There are no entries between Oct 31 and Nov 15, so was the unit off during that period?
If you didn't shut it down, suffer a power loss, or have a power-down schedule, then something caused the OS to re-start. While I've never seen something associated with a drive failure cause that, I suppose it's possible. More often, though, a bad drive ends up making the NAS unresponsive and the user does a forced re-start. While there often isn't much else that could have been done, that can create a corrupted volume.
I'm making some guesses here, and your answers to my questions may fill in some gaps, but this appears to be what happened:
- Drive 2 failed on Oct 30, and the OS believed the drive was removed, so the failure was significant.
- On Oct 30, you re-started the NAS with drive 2 still installed. At that point, the NAS saw drive 2 again (it may have recovered some due to cooling down) and started to try and add it back to the array. But it really still wasn't healthy, so that sync would have been very labored.
- At some point after the re-sync started, probably on Oct 31, you again shut the unit down. You did that in mid-sync (that was likely to fail anyway), and that's a very bad thing to do. During sync of a RAID5, you have no redundancy and the volume is very susceptible to damage.
- So when you powered on again Nov 15, your volume was dead.
To answer the questions:
Are these associated with you shutting down the unit? Possible forcefully? Or maybe by schedule? There are no entries between Oct 31 and Nov 15, so was the unit off during that period?
I did not shut down the server, but it is scheduled to shut down at midnight 12AM Mon - Thu and 1AM on Fri and Sat. I do not know what would have shut it down and I am not aware of any power outages, I am in FL and we tend to have power outages often.
Its possible that my kids popped the drive out on Oct 30th, I did find two of the four drives popped out days later. I did not shut down, it would have been on the power schedule.
AFAIK, the unit shouldn't shut down in mid-sync. But I now disable auto shut-down before swapping out a drive so it doesn't turn off as soon as it finishes (I like to go in and make sure all is OK first), so I'm relying on memory from some time ago on that. But if yours kids popped one out during a sync, that might cause a problem because the NAS was in mid-write at the time. Popping out a second drive when no writing is occurring normally does no harm, as the volume will go offline preventing damage.
Let StephenB see what tale your full logs tell. A lot is absent from the log in the GUI.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
.jpg){kind=link}
