NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN20400 died, not responsive. #27304635
Today my RN20400 (OS 6.05.01) was unresponsive. It was reporting the error "btrfs_merge_bio_hook+a0" on the display, and the blue power button was flashing.
I powered the unit off for 30 secon...
Hello Brian,
I did finally get a chance to try out the unit. My disks were transfered over, but upon bootup, It halted with the error "btrfs_merge_bio_hook+a0".
At this point I powered the unit off, and pulled all of the drives, except the 2TB disk that's in poisition 1, and powered it on again. It was able to boot, and load the ReadyNAS OS. When in the GUI, the disk in position 1 was RED, and it said that I needed to remove the existing data to create a new volume (maybe partition, I can't remember the nomenclature). Figuring that it just needed to see the rest of the disks, I place the remainder of the disks in their respective slots. They all came up red, so I just decided to remove the partitions, and start over.
When I finished with removing the partitions, I tried to make a new volume arcross all 4 disks, but it would not let me choose XRAID for the volume, and only the traditional RAIDs. I rebooted the RN20400, and it still only show the traditional RAIDs as a volume option. I then selected the factory default option from the GUI, and started over from scratch.
It took about 2 days for the disks to resync, and I copied my data back over to it. I hope this unit is more stable than my old one, I have never had a RAID that was so unreliable.
Hi Laserbait,
It's been almost a week since the replacement unit has been shipped to your premise. We would like to know if you're able to transfer your drives and test the unit if it's working fine.
Looking forward to your response.
Kind regards,
BrianL
NETGEAR Community Team
Hello Brian,
I did finally get a chance to try out the unit. My disks were transfered over, but upon bootup, It halted with the error "btrfs_merge_bio_hook+a0".
At this point I powered the unit off, and pulled all of the drives, except the 2TB disk that's in poisition 1, and powered it on again. It was able to boot, and load the ReadyNAS OS. When in the GUI, the disk in position 1 was RED, and it said that I needed to remove the existing data to create a new volume (maybe partition, I can't remember the nomenclature). Figuring that it just needed to see the rest of the disks, I place the remainder of the disks in their respective slots. They all came up red, so I just decided to remove the partitions, and start over.
When I finished with removing the partitions, I tried to make a new volume arcross all 4 disks, but it would not let me choose XRAID for the volume, and only the traditional RAIDs. I rebooted the RN20400, and it still only show the traditional RAIDs as a volume option. I then selected the factory default option from the GUI, and started over from scratch.
It took about 2 days for the disks to resync, and I copied my data back over to it. I hope this unit is more stable than my old one, I have never had a RAID that was so unreliable.
Hi Laserbait,
Can you still recall which Firmware version was installed on your old chassis and the one loaded on the replacement you just received? Since you've re-create your volume, I hope it'll be more stable and won't give you problems in the future.
Kind regards,
BrianL
NETGEAR Communty TeamMy old RN20400 was running 6.05.01, but I'm not sure what the new RN20400 came with. I do see in the log that it was upgraded to 6.05.01:
:
Hi Laserbait,
Thanks for posting back. You could've booted the unit in (volume) read-only mode to check if the data will be accessible before re-creating your volume. If you encounter the same error again, I suggest that you let us know or reach our support team through phone, chat or e-mail.
Kind regards,
BrianL
NETGEAR Community TeamHello Brian,
I'll keep that in mind. As I have not been able to trust the old unit, I do daily backups of it. So after seeing it come up with that "btrfs_merge_bio_hook+a0" error come up again, I didn't trust anything on the disks anyway. It was more expedient for me to reset to factory defaults, and restore from known good data.
Did you still want me to PM you the initrd.log file?
Hi Laserbait,
No worries. Just make sure that you will enable schedule volume maintenance on your system, make a backup of your data and keep your unit up to date. I no longer need that file. For your information, the initrd.log file will show you the Firmware histrory of your system.
Kind regards,
BrianL
NETGEAR Community TeamHi Laserbait,
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.
If your issue is now resolved we encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The Netgear community looks forward to hearing from you and being a helpful resource in the future!Thanks,
BrianL wrote:
Hi Laserbait,
No worries. Just make sure that you will enable schedule volume maintenance on your system, make a backup of your data and keep your unit up to date. I no longer needed that file. For your information, the initrd.log file will show you the Firmware histrory of your system.
Kind regards,
BrianL
NETGEAR Community TeamHello Brian,
I am unable to find "enable schedule volume maintenance". Can you tell me where that is?
Hi Laserbait,
Here's the support article you can look at.
Kind regards,
BrianL
NETGEAR Community TeamGot it, thanks. Yes, I do all of those (scrub, defrag, balance and disk test) once a week.
Hi Laserbait,
Great! Also, ensure that you have also a backup of your data (stored on your ReadyNAS) at all times.
Kind regards,
BrianL
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
