NETGEAR ReadyNAS 2304 (RR2304) RR230400 Volume Degraded Notification and Can't Connect to NAS

Thanks StephenB I hope I can trust you, since I am not 100% sure what sensitive information is stored in the logs. My server can not able to be accessed outside of my home network, so that should make it safe from public access.

Will send the link shortly.

---

L-Logic wrote:

I am not 100% sure what sensitive information is stored in the logs.

---

Some examples - your WAN IP address and email.  Names of shares, and potentially names of files (if the antivirus kicks in,or if there are errors).  Information on backup sources/destinations.  Apps running on the NAS.

FYI, one of the disks has 88 reallocated sectors.  Although it is passing the disk test, if it were my NAS I would replace it (after the main problem is dealt with).

Device:             sdd
Channel:            3
Model:              ST8000VN0022-2EL112
Serial:             ZA1DEGEG

  Reallocated Sectors:            88
  Reallocation Events:            88

The logs confirm that the resync started on 31 October never finished.

In particular, status.log

[23/10/30 21:20:53 EDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST4000VN008-2DR166 Serial:ZDH4A73Q was removed from Channel 2 of the head unit.
[23/10/31 08:39:58 EDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[23/10/31 08:40:00 EDT] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded.
[23/10/31 08:40:03 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[23/10/31 08:40:11 EDT] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume data.
[23/11/15 22:59:05 EST] info:system:LOGMSG_READYNASD_ABORTED ReadyNASOS service or process (systemd,connman) was restarted.

and volume.log

data        resilver   2023-07-08 14:06:03  2023-07-10 13:03:22  completed                                                                  
data        resilver   2023-10-31 08:40:11                                                                                                  
data        disk test  2023-11-15 23:05:37                                                                                                  
data        disk test  2023-11-15 23:48:52  2023-11-15 23:48:53  pass                                                                       
data        disk test  2023-11-15 23:55:43  2023-11-15 23:55:43  pass   

Note the resilver on 31 October has no end time, and doesn't show as completed (compare it with the resilver in July, which tool about 2 days to complete).

Most of the logs have rotated, so I cannot see much detail before 17 November.  I am seeing this:

[Fri Nov 17 19:00:47 2023] md: md127 stopped.
[Fri Nov 17 19:00:47 2023] md: bind<sda3>
[Fri Nov 17 19:00:47 2023] md: bind<sdb3>
[Fri Nov 17 19:00:47 2023] md: bind<sdc3>
[Fri Nov 17 19:00:47 2023] md: bind<sdd3>
[Fri Nov 17 19:00:47 2023] md: kicking non-fresh sdb3 from array!
[Fri Nov 17 19:00:47 2023] md: unbind<sdb3>
[Fri Nov 17 19:00:47 2023] md: export_rdev(sdb3)
[Fri Nov 17 19:00:47 2023] md: kicking non-fresh sda3 from array!
[Fri Nov 17 19:00:47 2023] md: unbind<sda3>
[Fri Nov 17 19:00:47 2023] md: export_rdev(sda3)
[Fri Nov 17 19:00:47 2023] md/raid:md127: device sdd3 operational as raid disk 2
[Fri Nov 17 19:00:47 2023] md/raid:md127: device sdc3 operational as raid disk 3
[Fri Nov 17 19:00:47 2023] md/raid:md127: allocated 4362kB
[Fri Nov 17 19:00:47 2023] md/raid:md127: not enough operational devices (2/4 failed)

The "non-fresh" status suggests that the NAS didn't shut down cleanly, and that some cached writes to sda and sdb were lost (never written to the drives).  

The three main options are

1. attempt to mount the volume in tech support mode, using the linux command line
2. recover data with RAID recovery software (for example, ReclaiMe),
3. recover data using a data recovery service.

The first option is free, the others obviously would cost.  Although I think it is likely that (1) will succeed with minimal (perhaps no) data loss, there is some risk.  The lost writes might result in file system corruption, and if you were to make a mistake in entering the linux commands you could inadvertently do more damage.

If you would like to proceed with (1), let me know and I can give you some guidance on the commands.

Thanks StephenB for taking a look at it. I am feeling daring, but I don't want to be ignorant and lose the files over the expense of recovery. 

I will try 1) if I could get your guidance or may try 2) ReClaiMe after doing my homework.

Let me know how best to do that with step by step so I can be clear on the details.

What are some of the things I need to prepare for this?

---

L-Logic wrote:

 

I will try 1) if I could get your guidance or may try 2) ReClaiMe after doing my homework.

 

---

I can give you the steps for (1) in a PM.  If something doesn't seem right when you go through them, it's best to post back with whatever issue you are seeing before proceeding to the next step.

Have you ever used the linux command line before?  If not, have you ever used CMD in windows?

Thanks StephenB ... was really busy during the holidays. I have a few weeks of critical work to do and then I will try to work on my server. For now I am just going to shutdown the server and remove it from the rack. I appreciate your support on this. I'll reach back out in a few weeks.