If I've not given enough detail, please let me know.
The problem is that my rndp6000 is giving me the message "Remove inactive volumes to use the disk. Disk #1,2,3,4,5,6,1,2,3,4,5,6,2,3,5,6.".
Is this retrievable? If so, how?
It's on firmware 6.10.5 Hot fix 1. I can send the logs if needed.
I know a little unix, but haven't used it for sometime. I haven't gone into the box. But, I can do if given the instructions to do so. I'll keep it off until someone tells me it's safe (ish) to start it up.
@ipb_uk wrote: Can anybody tell me what I'm doing wrong? When I try to post my question it never shows up
There's an automated spam filter, and something in your post must be triggering it. I just manually released the most recent one. FWIW, someone else will likely release the other two.
The problem is that my rndp6000 is giving me the message "Remove inactive volumes to use the disk. Disk #1,2,3,4,5,6,1,2,3,4,5,6,2,3,5,6.". Is this retrievable? If so, how? It's on firmware 6.10.5 Hot fix 1. I can send the logs if needed.
It might be retrievable, depending on what went wrong. @rn_enthusiast might be willing to look at your logs, and offer some advice.
As StephenB said, I can take a look at the logs for you. When you access the NAS Web Interface, go to: System > Logs and here you will see a button called "Download Logs" on the right-hand side. Click this and it will download a zip file with all the NAS logs inside.
Take this zip file and upload to your Dropbox, Google Drive or similar and then make a link where I can download the log zip file. PM me this link please. Then I will have a look to see what is going on.
Hello, If you want a newer set of logs, let me know and I will boot the box up and get them. Would it be a good idea to change the tile of the post to something more sensible? And what to do with the two posts gobbled up by the spam filter. Thanks Ian
If you and rn_enthusiast think this thread is best then the others can die a peaceful death. If on the other hand one of the others makes better sense for historic purposes, then release one of them and we can continue on that thread. I'll let you guys make the judgement call. Thanks very much. Ian
Your data raid and disks are OK, so that is good. I was a little worried about this, as you mentioned the NAS had some unexpected shutdowns due to a thunderstorm. But the hardware looks OK at least.
I can also see that the reason for the cryptic message of: "Remove inactive volumes" happens because the NAS cannot mount the data volume, despite the raid running fine. This would indicate filesystem issues and indeed, the kernel log confirms that the BTRFS (filesystem) log tree is damaged. As BTRFS is a journaled filesystem, the NAS would have tried to do a journal check post the unexpected shutdown, but it seems the filesystem journal got corrupted or damaged during those shutdowns.
Jul 20 20:37:43 Pro kernel: BTRFS info (device md125): has skinny extents
Jul 20 20:38:42 Pro kernel: BTRFS info (device md125): start tree-log replay
Jul 20 20:38:42 Pro kernel: BTRFS error (device md125): parent transid verify failed on 25029252612096 wanted 8127492 found 8126807
Jul 20 20:38:42 Pro kernel: BTRFS error (device md125): parent transid verify failed on 25029252612096 wanted 8127492 found 8126807
Jul 20 20:38:42 Pro kernel: BTRFS warning (device md125): failed to read log tree
Jul 20 20:38:42 Pro kernel: BTRFS error (device md125): open_ctree failed
This should be easy enough to fix as you can simply reset the filesystem journal. You will need to log into the NAS over SSH (via the root user). Not sure if you have used SSH before?
The command to reset the log tree/journal is:
btrfs rescue zero-log /dev/md125
Afterwards, reboot the NAS gracefully from the Web Interface.
If you need help accessing the NAS over SSH, let us know.
Then there are more issues than just log tree problems.
In this case, you likely need to mount with auto recovery mode from a different tree root.
Attempting to mount like this, should be safe as it is read-only:
btrfs device scan
mount -o ro,usebackuproot /dev/md125 /Dual
ReadyNAS uses a pretty old version of BTRFS so "usebackuproot" might not work or even be an option on your NAS. If it spews "unrecognised command" errrors (or similar), you can instead try the original mount recovery method:
mount -o ro,recovery /dev/md125 /Dual
If that doesn't work, then you likely need to recover the data using BTRFS restore, but you are entering serious data recovery territory at that point, which Netgear can't help with given you are running OS6 on an OS4 box 🙂
Anyway, try and mount like the above first and see if that works. It will be a read-only mount but at least it will show you if the volume can be mounted at all.
root@Pro:~# btrfs device scan Scanning for Btrfs filesystems
root@Pro:~# mount -o ro,usebackuproot /dev/md125 /Dual mount: wrong fs type, bad option, bad superblock on /dev/md125, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
Just for the sake it of, try to do a dry-run of BTRFS restore, to see if files can be recovered. This is a non-destructive method for attempting to recover data from an unmountable filesystem. It will not attempt to repair the filesystem, which means that you don't cause further damage by running it. First, do a dry run to see if it is even possible to restore anything using this method (you can stop the dry run at any time with CTRL+C).
btrfs restore -DviF /dev/md125 /dev/null
What do you see when running this command? Does it start to spew-out files names in the terminal? Or what happens? It is just a dry-run so leave it run just to get a feel for whether it is actually recovers anything you recognise. And then just stop it with CTRL+C
BTRFS sticks together all 3 raids, into a BTRFS volume.
Label: '33eb0773: Dual' uuid: 29bccc98-ff07-426d-a82d-1a79b34131a3
Total devices 3 FS bytes used 21.57TiB
devid 1 size 7.26TiB used 6.49TiB path /dev/md127
devid 2 size 14.55TiB used 12.34TiB path /dev/md126
devid 3 size 10.91TiB used 2.80TiB path /dev/md125
You can use any of the 3 devices to mount. As you can see by his Kernel logs that I posted earlier, the NAS itself tries to mount md125 as well, but it doesn't matter which device of the 3 that you use for the mount. Running btrfs device scan first allows BTRFS to scan for volumes and it will then know by FS superblocks/metadata information which devices belong together.
BTRFS will see md125, md126 and md127 as regular individual devices (like disks essentially). It is not aware of any underlying raids as that is all MDADM.
It can fetch files 🙂 Now, these first files you saw are all config and internal ReadyNAS files but if you left if run long enough, you would see files from your shares start to show (as you noticed).
BTRFS restore is method for taking a non-mountable volume and dumping the data somewhere else (USB, network share, etc.). I guess you are left with 2 options:
1. Try to repair the filesystem (BTRFSCK) which might not work either and can cause more damage than good.
2. Dump the data somewhere else via BTRFS restore (giving you a backup essentially). Then verify all is good with the backup and then factory reset the NAS and thereafter you can restore form the backup.
The problem is that you need at least 21.63 TiB (23.8 TB) of storage somewhere else, where you can dump the data.
devid 1 size 7.26TiB used 6.49TiB path /dev/md127
devid 2 size 14.55TiB used 12.34TiB path /dev/md126
devid 3 size 10.91TiB used 2.80TiB path /dev/md125
If you don't care about all of it, you can select which data to restore though the BTRFS restore tool. This will reduce the amount of data you need to dump.
Lastly, there are people who know much more about BTRFS than I do, so you could also use the mailing list to see if those guys have any ideas on how to get the volume repaired/mountable so that you don't have to use BTRFS restore to dump the data somewhere else. Actually, you probably should ask the guys in the mailing list as well 🙂
Hi, There is a longer log at the net address I PM'd you. I have 4 x 6TB, 3 x 2TB, 3 x 1.5TB and 1 x 500GB to play with. I can but one at a time into a usb cradle, or do I need to it differently? I have some Bits & Bobs in one folder (and it's subfolders) I would like to save as this is the only one not totally backed-up. Should I point them (btrfs mailing list) to this thread? They ask for five commands to be done. The fourth one " btrfs fi df /home # Replace /home with the mount point of your btrfs-filesystem", What is my mount point? If it's /dev/md125, then I get "ERROR: not a btrfs filesystem: /dev/md125" The fifth one ask for dmesg can I use the one from the nas's logs? root@Pro:~# uname -a Linux Pro 4.4.218.x86_64.1 #1 SMP Mon Jan 11 06:25:23 UTC 2021 x86_64 GNU/Linux root@Pro:~# btrfs --version btrfs-progs v4.16 root@Pro:~# btrfs fi show Label: '33eb0773:root' uuid: 13624a2a-e24e-48ae-ad2b-f786913ec748 Total devices 1 FS bytes used 1.03GiB devid 1 size 4.00GiB used 4.00GiB path /dev/md0 Label: '33eb0773:Dual' uuid: 29bccc98-ff07-426d-a82d-1a79b34131a3 Total devices 3 FS bytes used 21.57TiB devid 1 size 7.26TiB used 6.49TiB path /dev/md127 devid 2 size 14.55TiB used 12.34TiB path /dev/md126 devid 3 size 10.91TiB used 2.80TiB path /dev/md125 root@Pro:~# btrfs fi df /dev/md125 ERROR: not a btrfs filesystem: /dev/md125 Which I guess is the problem! Cheers, Ian
