Forum Discussion

Tutor

Jul 20, 2016

Solved

btrfs_merge_bio_hook+a0 error, recovery possible?

Hi, I have a ReadyNAS 204 with the btrfs_merge_bio_hook+a0 error. After reboot I can ssh into the box, but the web interface does not load and the data volume is not mounted. Output of cat /p...

Other Discussions

edkedk
Aug 01, 2016
Eventually I used --path-regex to restore specific directories and it worked fine. Seems that everything I wanted was copied.

mdgm-ntgr

NETGEAR Employee Retired

Jul 21, 2016

Can you try booting your NAS into volume read-only mode (a boot menu option) and see if the data is then accessible?

edkedk

Tutor

Jul 21, 2016

HI,

Model no. is RN204, fw version 6.4.2

Booting into read-only mode results in btrfs_merge_bio_hook+a0 being displayed and the data volume not mounted.

If I move the disks to a PC running Linux, will I be able to mount the volume?

mdgm-ntgr
NETGEAR Employee Retired
Jul 21, 2016
Shell commands would have to be used to try and mount it or attempt to recover the data and these could just as easily be done via SSH on the RN204. However attempting to do that would be at your own risk.

Have you checked the smart stats of the disks for SMART errors?
- edkedk
  Tutor
  Jul 21, 2016
  I just checked smart values using smartctl and see no error on any disk.
  
  I'd like to try to manually mount the volume. Could you assist me with the required shell commands?
  - Hopchen
    Prodigy
    Jul 21, 2016
    Hi,
    
    As mdgm said, running commands from the terminal can be "dangerous" if you are not experienced/comfortable with Linux and BTRFS. So, just be careful :)
    
    I think you should wait mounting the volume. First check that it is not something benign (like a 100% full root/OS). Post the output of the command:
    df -h
    
    If the OS is not full, then I would suggest you do a read-only filesystem check on the data volume before attempting the mount. You can do this by running the command:
    btrfsck /dev/md127
    
    That might take some time. Please post the result of the FS check. The above command will not try to repair anything, it will just give us info about the state of the filesystem and the command can only be run on a non-mounted filesystem (so don't attempt to mount first).
    
    Thanks