RN104 says inactive volume

Question

I found my RN104 frozen a few days ago.&nbsp; Last email I saw from it was that a balance had started.&nbsp;When I found it frozen, it was unreachble via ssh, or even responding to ping.&nbsp; Power button had no effect.&nbsp; I had to pull the plug.Upon restart, it froze again, during boot, at 39%.&nbsp; I had to pull the plug again.Next restart, it finishes booting, but the raid array is gone.&nbsp; It sees all 4 drives, all are reported as healthy.Log into admin, and it says "Remove inactive volumes to use the disk. Disk #1, 2, 3, 4."What do I do?&nbsp; I see some posts suggesting factory defaulting it, but I just don't want to do anything that might make the situation worse.&nbsp;dmesg log at&nbsp;https://dumptext.com/6gt64u7v/raw/&nbsp;Thanks in advance!&nbsp;&nbsp;

mdgm-ntgr · Answer

I can see you're on old firmware (don't update the firmware with the NAS in this state).
&nbsp;
I can also see this in your dmesg.log
&nbsp;
[   17.575851] BTRFS: device label 0e343298:data devid 2 transid 146384 /dev/md126
[   18.381179] BTRFS (device md126): bad tree block start 11637558493067324903 17973882290176
[   18.382106] BTRFS (device md126): bad tree block start 11637558493067324903 17973882290176
[   18.382157] BTRFS: failed to read tree root on md126
[   18.430349] BTRFS: open_ctree failed
Have you tried booting into volume read-only mode?&nbsp;
&nbsp;
Is your backup up to date?
&nbsp;
A factory default (wipes all data, settings, everything) is fine to do if you have a good up to date backup that you can restore from afterwards.
&nbsp;
If not, you may wish to contact support if booting into volume read-only mode doesn't resolve the problem.

borgchick · Answer

So I tried the readonly mode, no effect.&nbsp; Same error in dmesg.&nbsp;I did a bit more poking around.&nbsp; So each disk has 4 partitions, and if I use mdadm --examine on each set, there appear to be 4 raid set ups&nbsp;/dev/sd*1 is raid 1
/dev/sd*2 is raid 6
/dev/sd*3 is raid 5
/dev/sd*4 is raid 5If I look at the raid states:root@nas:~# mdadm --examine /dev/sd*1|grep "State"                       
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
root@nas:~# mdadm --examine /dev/sd*2|grep "State"                       
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
root@nas:~# mdadm --examine /dev/sd*3|grep "State"                       
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
root@nas:~# mdadm --examine /dev/sd*4|grep "State"                       
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  
          State : clean                                                  
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)  So everything is clean.&nbsp;But if I try to mount the file system, even in degraded mode, it fails:root@nas:~# mount -t btrfs -o degraded /dev/md127 /var/recover/
mount: wrong fs type, bad option, bad superblock on /dev/md127,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so.
root@nas:~# mount -t btrfs /dev/md127 /var/recover/
mount: wrong fs type, bad option, bad superblock on /dev/md127,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so.If I look at dmesg, it is the btrfs ctree error:[ 3847.552053] BTRFS (device md126): bad tree block start 11637558493067324903 17973882290176
[ 3847.552446] BTRFS (device md126): bad tree block start 11637558493067324903 17973882290176
[ 3847.552481] BTRFS: failed to read tree root on md126
[ 3847.580455] BTRFS: open_ctree failed
[ 3852.027911] BTRFS (device md126): bad tree block start 11637558493067324903 17973882290176
[ 3852.028306] BTRFS (device md126): bad tree block start 11637558493067324903 17973882290176
[ 3852.028342] BTRFS: failed to read tree root on md126
[ 3852.070223] BTRFS: open_ctree failedSo, it seems to me that this is some sort of btrfs corruption issue.&nbsp;btrfs fi show&nbsp;Label: '0e343298:data'  uuid: 92ecd2e0-45da-425b-87a8-0f626e5ef889
        Total devices 2 FS bytes used 5.04TiB
        devid    1 size 2.71TiB used 2.53TiB path /dev/md127
        devid    2 size 2.73TiB used 2.54TiB path /dev/md126Now I don't know why there are two md raid set ups, from other digging (dry run) I see md127 thinks device 2 is missing, whatever that is, is that the second drive? the second raid set (/dev/md126?)oot@nas:~# btrfs restore -F -i -D -v /dev/md127 /dev/null
checksum verify failed on 17973882290176 found 28166D04 wanted 8B8262A2
checksum verify failed on 17973882290176 found 28166D04 wanted 8B8262A2
checksum verify failed on 17973882290176 found 46A24E6E wanted 51485848
checksum verify failed on 17973882290176 found 46A24E6E wanted 51485848
bytenr mismatch, want=17973882290176, have=3707086136388172086
Couldn't read tree root
Could not open root, trying backup super
warning, device 2 is missing
checksum verify failed on 17973882290176 found 46A24E6E wanted 51485848
checksum verify failed on 17973882290176 found 46A24E6E wanted 51485848
bytenr mismatch, want=17973882290176, have=3707086136388172086
Couldn't read tree root
Could not open root, trying backup super
warning, device 2 is missing
checksum verify failed on 17973882290176 found 46A24E6E wanted 51485848
checksum verify failed on 17973882290176 found 46A24E6E wanted 51485848
bytenr mismatch, want=17973882290176, have=3707086136388172086
Couldn't read tree root
Could not open root, trying backup superAny suggestions?I do have a backup, but I really would like to take this as a learning opportunity.&nbsp;Thanks!&nbsp;&nbsp;

mdgm-ntgr · Answer

As it's on multiple arrays a
# btrfs device scan
is needed before attempting to mount the data volume. However with the system booted normally the system would have already run that command.If your backup is up to date I'd follow the suggestion I gave for that scenario in my previous post.

borgchick · Answer

I did a btrfs device scan --all-devices, it returns nothing, just says:Scanning for Btrfs filesystemsNo additional errors in dmesg from the scan.&nbsp;I am working on making&nbsp;a backup of my backup, just in case something fails.Again, I reiterate my desire to learn more about this situation, because there is no guarantee that this won't happen again a week after I restore from backup.&nbsp; Since the drives appear fine, and the raid array appears fine, I'd rather learn how to with btrfs tools to perhaps remount the set up.&nbsp; Even if nothing more than so I know what I can do in the worse case scenario.&nbsp;Can you explain the purpose of the md127 and md126 arrays?&nbsp; Is this how the XRaid feature is implemented?&nbsp;

StephenB · Answer

borgchick wrote:
&nbsp;
Can you explain the purpose of the md127 and md126 arrays?&nbsp; Is this how the XRaid feature is implemented?
&nbsp;

Your volume has two RAID groups, that are both created with mdadm.&nbsp; One is md126, the second is md127.&nbsp; &nbsp;The two RAID groups are joined together into your volume.
&nbsp;
That is how XRAID creates arrays with mixed disk sizes.&nbsp; If you ever vertically expanded your RAID array (by upgrading to larger disks), then the system created a new RAID group to use the additional space.&nbsp; Once created, that group is kept until the volume is destroyed (even if all the disks eventually are the same size).&nbsp; &nbsp;

Forum Discussion

RN104 says inactive volume

5 Replies

Related Content

RN104 Remove inactive volumes Disk 3,4

ReadyNAS 314 - inactive volumes error.

Remove inactive volumes after hard drive upgrade RN104

ReadyNAS RN104 Remove Inactive Volumes

ReadyNAS RN104 Remove Inactive Volumes

NETGEAR Academy

ProSupport for Business