NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN104 data-0 inactive since April, still stuck after PSU fix - need assemble advice
Hi all, I have a ReadyNAS 104 (firmware 6.10.10) with a 4-bay X-RAID2 setup: two Seagate IronWolf 4TB drives and two WD Red 3TB drives. The 3TB baseline across all four disks forms a RAID5 volume...
Thanks for checking, that's a great question. I can answer it directly from the NAS's own logs: "data" carries its own RAID metadata showing a creation date of April 20, 2016, so it's a genuinely separate volume that has existed for about a decade, not something that appeared this month as a fallback naming workaround. Both "data" (931 GB, healthy after a recent resync) and "data-0" (8.17 TB, still inactive) are showing side by side in the interface right now. I haven't deleted anything called "data" or touched it in any way. Getting the full logs ready to send over to StephenB now, thank you both for the help.
For a vertically expanded volume, the MDADM RAID groups that make up the data BTRFS volume would normally be data-0 and data-1 if you have expanded once. There would be a data-2 if you had expanded twice. But you are mixing up RAID groups and volumes. The OS tries to separately assemble the part of the BTRFS volume that it could not include in the main one and reports it as data-0 in such a case, but that does not mean it's the data-0 RAID group. Yes, it can be confusing.
From your description, I believe you should have only one volume, data, and the data-0 VOLUME did just show up in the GUI following the failure and is a sign the volume cannot be fully assembled. Furthermore, I don't believe the BTRFS data volume is healthy. Can you actually access anything on it?
That data does still show up and you didn't delete it is good. Had you done so, the volume would be unrecoverable.
You were right, I tried mounting "data" over SMB from my Mac and it's empty, nothing browsable. So it sounds like the pooled BTRFS filesystem really can't be read while data-0 is inactive, even though the RAID1 side resynced at the disk level. Good catch, and thanks for pushing on that, I'd assumed "resynced" meant "accessible," which clearly isn't the case here.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
