Forum Discussion

Aspirant

May 06, 2021

Solved

Remove inactive volumes

I got a new NAS today. And, max unluck, my old NAS failed today. How can I get this old nas up and go so i can copy my files. ( i have backup, but backup is incremental since 2009 and that wi...

littomalt
May 08, 2021
HALLELUJA, NAS IS UP!

Why did I not think about root... thanks

Here is what happened when I run the command
btrfs rescue zero-log /dev/md126
Last login: Mon Jan 11 16:19:31 2021 from 192.168.11.2
root@Modesty:~# btrfs rescue zero-log /dev/md126
parent transid verify failed on 3764097646592 wanted 396573 found 396569
parent transid verify failed on 3764097646592 wanted 396573 found 396569
parent transid verify failed on 3764097646592 wanted 396573 found 396569
Clearing log on /dev/md126, previous log_root 3764097646592, level 0
root@Modesty:~# ^C

HALLELUJA, NAS IS UP!
THANKS rn_enthusiast do you have a donation option, if yes, send it to me!

rn_enthusiast

Virtuoso

May 07, 2021

Hi littomalt

Thanks for the logs.

Your raid and your disks are OK. Healthy. The issue is that the BTRFS filesystem cannot mount and thus you see the cryptic "Remove inactive volumes" message.

Your issue looks to be pretty much exactly the same as this user here:

https://community.netgear.com/t5/New-ReadyNAS-Users-General/rndp6000-inactive-volume-data/m-p/2093064#M45660

The NAS cannot mount your filesystem because the journal (log tree) seems to be messed up or corrupt.

May 06 20:32:08 Modesty kernel: BTRFS error (device md126): parent transid verify failed on 3764097646592 wanted 396573 found 396569
May 06 20:32:08 Modesty kernel: BTRFS error (device md126): parent transid verify failed on 3764097646592 wanted 396573 found 396569
May 06 20:32:08 Modesty kernel: BTRFS warning (device md126): failed to read log tree
May 06 20:32:08 Modesty kernel: BTRFS error (device md126): open_ctree failed

I will give you the exact same advise as I gave the user, in the above post - have a read at it. You also have issues with the same raid device, md126 so everything I said to that user, applies to you as well.

Any questions, let me know :)

Cheers

littomalt

Aspirant

May 08, 2021

Thanks for your rapid answer rn_enthusiast

I ssh to NAS as admin but comand did not kick in

admin@Modesty:~$ btrfs rescue zero-log /dev/md126
-bash: btrfs: command not found

Something I dont understand?

StephenB
Guru - Experienced User
May 08, 2021
littomalt wrote:

I ssh to NAS as admin but comand did not kick in

admin@Modesty:~$ btrfs rescue zero-log /dev/md126
-bash: btrfs: command not found

Log in as root, and use the NAS admin password.
- littomalt
  Aspirant
  May 08, 2021
  HALLELUJA, NAS IS UP!
  
  Why did I not think about root... thanks
  
  Here is what happened when I run the command
  btrfs rescue zero-log /dev/md126
  Last login: Mon Jan 11 16:19:31 2021 from 192.168.11.2
  root@Modesty:~# btrfs rescue zero-log /dev/md126
  parent transid verify failed on 3764097646592 wanted 396573 found 396569
  parent transid verify failed on 3764097646592 wanted 396573 found 396569
  parent transid verify failed on 3764097646592 wanted 396573 found 396569
  Clearing log on /dev/md126, previous log_root 3764097646592, level 0
  root@Modesty:~# ^C
  
  HALLELUJA, NAS IS UP!
  THANKS rn_enthusiast do you have a donation option, if yes, send it to me!
  - rn_enthusiast
    Virtuoso
    May 08, 2021
    Hi littomalt
    
    Glad to hear the NAS is back online. I would advise you to get a backup sorted, for the important data, now that you have access again.
    No donations here, we all just try and help each other out :D
    
    Cheers