A couple of weeks ago, I received an alert from my RN104 that the volume had "degraded". Shortly thereafterI had one of the four drives in my RAID 10 setup remove itself then add itself back to the unit. Soon after a second drive removed itself, but the system went into RESYNC. While I could still see the volume and directories, I decided to shut the unit off until I could figure out what happened.
Fast forward to this week, I decided to check the two questionable drives directly, one at a time, just to see their status. I did NOT allow any OS to initialize or format the disks. Neither reported any problems, although they are older firmware than the two that did not report any issues. Upon returning them to the NAS and powering back up, the NAS no longer recognizes the RAID array. This despite the fact that the two questionable drives are not the same drives on the RAID set (e.g. DISK1 (A) + DISK2(B) / DISK3 (A) + DISK4 (B) :: DISK2 and DISK3 reported issues).
The NAS looks like it still sees the construction of the RAID, just not the RAID itself. I can see the share directory structure, but the data mount point is empty. Inside the admin page, I see this:
However, all of the drives are RED status and it's requiring me to remove inactive volumes to proceed.
Any shot at recovering the data on this RAID array?
- In case you have a backup, you might want to restore your data from there after performing a factory reset on you RN104. You need to decide, whether you want to go with your old harddisks and whether you truely need RAID10 in this case.
- Should there be no backup and you desparately need the data back, go for external help by data recovery specialists, which might turn out to be expensive.
To improve performance and stability of RN10X in general there might be some hints following the link below
I wouldn't say it's bricked, since it is powering up and booting normally. The issue is "just" the RAID array. If you do have a backup, I'd destroy the volume, create a new one, and the reload the files from backup.
If not, then perhaps send a PM to a Netgear mod (for instance @mdgm-ntgr ) and ask if they are willing to review your logs.
RAID recovery is expensive (Netgear's service is here: https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service ). If you have a Windows PC, you could also look at ReclaiMe software. Several users have had success with it, though I don't recall any off-hand that were using RAID-10. ReclaiMe has the benefit that you can see if it can recover data prior to purchase.
You could try contacting support at my.netgear.com, and ask if they can try to remount the RAID array w/o data recovery (using per-incident support). I don't know if they'd do that or not, but I think it is worth having the conversation.
I would follow @StephenB 's advise on getting the NAS back and working. On Data recovery if you are comfortable of doing the procedure then you can try recovery using a PC. Otherwise, we can check if the RAID is still mountable but you will still have to contact support regarding getting it done. You can always create a ticket through the Support page. If you don't have a contract a Pay-per Incident Support is available. Data Recovery service has a different charge though.
You can send us the logs through the link on the Sig.
@Marc_V , I've sent a copy of my logs from the unit. At this point all options are on the table, although going the PC route might be a bit of a challenge since we're a Mac shop. I'd either have to buy or borrow a Windows machine to do that, but it's not beyond reason to do so. I did note that on the ReclaiMe site, they have a different tool for non XRAID configurations to address RAID 10 - I'm not sure if anyone has any experience with that to let me know if it's as viable as their more mainstream product.
Regardless, I think I'd like to at least get an assessment of how hosed this array is before choosing a path.
This does look like a data recovery situation. Hope you have a good backup.
kernel.log:
May 21 10:11:23 ReadyNAS104 kernel: md/raid10:md127: not enough operational mirrors.
status.log:
[18/05/19 12:00:50 CDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST4000NM0033-9ZM170 was added to Channel 2 of the head unit.
[18/05/19 12:05:20 CDT] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.
[18/05/19 12:08:28 CDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[18/05/19 12:41:00 CDT] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST4000NM0033-9ZM170 was removed from Channel 4 of the head unit.
[18/05/19 12:46:46 CDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST4000NM0033-9ZM170 was added to Channel 4 of the head unit.
[18/05/19 13:14:18 CDT] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.
[18/05/21 10:13:35 CDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[18/05/21 10:32:06 CDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST4000NM0033-9ZM170 was added to Channel 4 of the head unit.
[18/05/21 10:33:07 CDT] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 4 (Internal) changed state from RESYNC to ONLINE.
[18/05/21 10:57:32 CDT] notice:disk:LOGMSG_ADD_DISK Disk Model:ST4000NM0033-9ZM170 was added to Channel 2 of the head unit.
[18/05/21 10:59:26 CDT] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 3 (Internal) changed state from RESYNC to ONLINE.
@mdgm-ntgr, thanks for the analysis. Is this a situation where Netgear would be confident in the recovery if paid to do so? I know there’s no such thing as a guarantee, but I guess I’d like to gauge a confidence factor.
Fair enough. I will open a paid support ticket and schedule some time for detailed inspection. Is there any additional information I should know or supply as part of the request?
