RN3220: Netgear NAS "MGMT Service is offline", looks like Enclosure RAID5 & DB is down too #28163337

[ehartchr]

Hi, we have an issue with a RN3220  with "VMware lost Access to NAS Storage, Netgear NAS "MGMT Service is offline", looks like Enclosure RAID5 is lost and therefor DB is down too", OS Re-Install did not help - does anyone have other ideas for fixing the issue?

################################################################################################################################

Infos from Logs:
[2015/09/21 06:09:51] Updated from ReadyNASOS 6.1.8 () to 6.2.4 (ReadyNASOS)
[16/11/06 20:37:45] warning:volume:LOGMSG_VOLUME_USAGE_WARN Volume 'RAID5' usage exceeds 95 % of size (40.0 TB).
[16/12/07 12:15:28] event_push.c:169 Cannot start transaction
[16/12/07 12:16:12] event_push.c:186 md_event readynasd <xs:update-s resource-type="Volume">  <VolumeEvent EventName="DegradedArray" DevName="md127" SecondDevName="none"/></xs:update-s> 0 0 ==> ec=0
[17/02/26 03:33:51] event_push.c:186 md_event readynasd <xs:update-s resource-type="Volume">  <VolumeEvent EventName="Fail" DevName="md127" SecondDevName="/dev/sdj3"/></xs:update-s> 0 0 ==> ec=0
=> Initiated Reboot
[17/02/27 15:32:25] event_push.c:186 rnutil readynasd <xs:add-s resource-type="Device">
  <CommandName>Reboot</CommandName>
=> Initiated OS Install
[2017/02/28 21:40:54] Updated from ReadyNASOS 6.2.4 (ReadyNASOS) to 6.2.4 (ReadyNASOS).

################################################################################################################################

Errors during Boot Up:
[DEPEND] Dependency failed for /RAID5.
[DEPEND] Dependency failed for Apps Directory.
[DEPEND] Dependency failed for Home Directory.
[DEPEND] Dependency failed for Local File Systems.
exportfs[2994]: exportfs: Failed to stat /RAID5/Veeam_Replica: No such file or d
exportfs[2994]: exportfs: Failed to stat /run/nfs4/RAID5/Veeam_Replica: No such
exportfs[2994]: exportfs: Failed to stat /run/nfs4: No such file or directory
[FAILED] Failed to start ReadyNAS System Daemon.

################################################################################################################################

readynasd.service                                                                      loaded activating start   ReadyNAS System Daemon
start-raids.service                                                                    loaded active     exited         MD arrays

################################################################################################################################

root@NAS01:/var/log/readynasd# systemctl status readynasd.service
readynasd.service - ReadyNAS System Daemon
          Loaded: loaded (/lib/systemd/system/readynasd.service; enabled)
          Active: activating (start) since Fri, 03 Mar 2017 10:53:04 +0100; 44s ago
        Main PID: 4360 (readynasd)
          Status: "Importing DB"
          CGroup: name=systemd:/system/readynasd.service
                  + 4360 /usr/sbin/readynasd -v 3 -t

Mar 03 10:53:04 NAS01 readynasd[4360]: readynasd log started
Mar 03 10:53:04 NAS01 readynasd[4360]: readynasd started. (restarted=0)
Mar 03 10:53:04 NAS01 readynasd[4360]: DB (main) schema version: 18 ==> 18
Mar 03 10:53:04 NAS01 readynasd[4360]: rndb_create() ==> 3 (0ms)
Mar 03 10:53:04 NAS01 readynasd[4360]: Error create table (db)
Mar 03 10:53:04 NAS01 readynasd[4360]: dba create failed

################################################################################################################################

root@NAS01:/var/log/readynasd# systemctl status start-raids.service
start-raids.service - MD arrays
          Loaded: loaded (/lib/systemd/system/start-raids.service; static)
          Active: active (exited) since Fri, 03 Mar 2017 09:34:53 +0100; 1h 18min ago
         Process: 1784 ExecStart=/usr/bin/start_raids (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/start-raids.service

Mar 03 09:34:53 NAS01 start_raids[1784]: mdadm: NOT forcing event count in /dev/sdj3(1) from 1527356 up to 1527369
Mar 03 09:34:53 NAS01 start_raids[1784]: mdadm: You can use --really-force to do that (DANGEROUS)
Mar 03 09:34:53 NAS01 start_raids[1784]: mdadm: failed to RUN_ARRAY /dev/md/RAID5-0: Input/output error
Mar 03 09:34:53 NAS01 start_raids[1784]: mdadm: Not enough devices to start the array.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Thanks,

Christian

[jak0lantash]

[16/12/07 12:16:12] event_push.c:186 md_event readynasd <xs:update-s resource-type="Volume">  <VolumeEvent EventName="DegradedArray" DevName="md127" SecondDevName="none"/></xs:update-s> 0 0 ==> ec=0
[17/02/26 03:33:51] event_push.c:186 md_event readynasd <xs:update-s resource-type="Volume">  <VolumeEvent EventName="Fail" DevName="md127" SecondDevName="/dev/sdj3"/></xs:update-s> 0 0 ==> ec=0

Dual disk failure in RAID5?

What does this give you:

mdadm -E /dev/sd?3

[mdgm-ntgr]

Also do you have a backup of your data on the NAS?

I see you have an open support case. It's probably best to continue working with support on this.