NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
alan-hollmotz
May 06, 2021Follower
ReadyNAS 3220 - Remove inactive volumes to use the disk - disks 1-12
Sometime within the last few weeks, when I logon to the web interface, I see an error message stating "remove inactive volumes to use the disk - disks 1 - 12. the ReadyNAS 3220 is a 12 disk NAS setu...
- May 10, 2021
Thanks for the logs.
You disks and raid are healthy. The reason for the cryptic "Remove inactive volumes message" is due to the filesystem not being able to mount. We we can see below, it seems there is some corrupt leafs in the root tree when it tries to mount.
-- Reboot -- May 05 08:48:20 dltk-msp-archiv kernel: Btrfs loaded, crc32c=crc32c-intel May 05 08:48:20 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:root devid 1 transid 2208377 /dev/md0 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:data devid 1 transid 208725 /dev/md127 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:22 dltk-msp-archiv kernel: BTRFS error (device md127): open_ctree failed -- Reboot -- May 06 08:40:13 dltk-msp-archiv kernel: Btrfs loaded, crc32c=crc32c-intel May 06 08:40:13 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:root devid 1 transid 2210259 /dev/md0 May 06 08:40:13 dltk-msp-archiv kernel: BTRFS info (device md0): checking UUID tree May 06 08:40:14 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:data devid 1 transid 208725 /dev/md127 May 06 08:40:14 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:14 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS error (device md127): open_ctree failed
The logs still show me good information about your filesystem and I can see you have used about 8 TiB. So, it is good that the NAS can retrieve this metadata information.
Label: '33ea851f:data' uuid: 13562dc5-4c5e-479e-b09d-5e07a2154623 Total devices 2 FS bytes used 8.38TiB devid 1 size 9.07TiB used 6.36TiB path /dev/md127 devid 2 size 5.46TiB used 2.78TiB path /dev/md126
I think a simple mount of the volume with recovery option (mounting as read-only) might solve this.
mount -v -o ro,recovery /dev/md127 /data
If that does not work, then a BTRFS restore is probably the way to go, at least to get a backup done but it requires some place where you can dump the data to. A filesystem repair job can also be attempted but the prio should be taking a backup first. The BTRFS filesystem repair job can potentially make it worse.
None of the above are things to be attempted over a user forum. I would suggest to contact Netgear support and get some paid support to have their Level 3 look at this. My feeling is that this is recoverable but you need people who knows about the BTRFS filesystem. So, Netgear paid support is the best option here, in my opinion.
Cheers
rn_enthusiast
May 06, 2021Virtuoso
Throw the logs over to me and I can have a look. System > Logs > Downlaod Logs. It will give you a zip file with the NAS logs. Upload this zip file to a Google Drive, Dopbox or similar and PM me the link.
Then I will see what is going on. But this is not caused by a firmware update. There is another underlying problem.
rn_enthusiast
May 10, 2021Virtuoso
Thanks for the logs.
You disks and raid are healthy. The reason for the cryptic "Remove inactive volumes message" is due to the filesystem not being able to mount. We we can see below, it seems there is some corrupt leafs in the root tree when it tries to mount.
-- Reboot -- May 05 08:48:20 dltk-msp-archiv kernel: Btrfs loaded, crc32c=crc32c-intel May 05 08:48:20 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:root devid 1 transid 2208377 /dev/md0 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:data devid 1 transid 208725 /dev/md127 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:21 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 05 08:48:22 dltk-msp-archiv kernel: BTRFS error (device md127): open_ctree failed -- Reboot -- May 06 08:40:13 dltk-msp-archiv kernel: Btrfs loaded, crc32c=crc32c-intel May 06 08:40:13 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:root devid 1 transid 2210259 /dev/md0 May 06 08:40:13 dltk-msp-archiv kernel: BTRFS info (device md0): checking UUID tree May 06 08:40:14 dltk-msp-archiv kernel: BTRFS: device label 7c6ebad2:data devid 1 transid 208725 /dev/md127 May 06 08:40:14 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:14 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS critical (device md127): corrupt leaf, unaligned key offset for csum item: block=16470295986176, root=1, slot=30 May 06 08:40:15 dltk-msp-archiv kernel: BTRFS error (device md127): open_ctree failed
The logs still show me good information about your filesystem and I can see you have used about 8 TiB. So, it is good that the NAS can retrieve this metadata information.
Label: '33ea851f:data' uuid: 13562dc5-4c5e-479e-b09d-5e07a2154623 Total devices 2 FS bytes used 8.38TiB devid 1 size 9.07TiB used 6.36TiB path /dev/md127 devid 2 size 5.46TiB used 2.78TiB path /dev/md126
I think a simple mount of the volume with recovery option (mounting as read-only) might solve this.
mount -v -o ro,recovery /dev/md127 /data
If that does not work, then a BTRFS restore is probably the way to go, at least to get a backup done but it requires some place where you can dump the data to. A filesystem repair job can also be attempted but the prio should be taking a backup first. The BTRFS filesystem repair job can potentially make it worse.
None of the above are things to be attempted over a user forum. I would suggest to contact Netgear support and get some paid support to have their Level 3 look at this. My feeling is that this is recoverable but you need people who knows about the BTRFS filesystem. So, Netgear paid support is the best option here, in my opinion.
Cheers
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!