NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Missing volume after hard reboot
After losing access (no web, ssh, mounts, anything) from my ReadyNAS Pro 6 running 6.7.4 firmware, I decided to hard-reboot it by holding down the power button until it powered off. after booting back up, I was confronted by no data and two volumes (zero bytes each).
A quick search turned up this post:
https://community.netgear.com/t5/Using-your-ReadyNAS/Missing-volume-after-power-failure/td-p/1246361
However the troubleshooting steps in it do not match my experience (my /mnt/data/ is empty)...
Any help would be greatly appreciated.
I've uploaded the logs from today here:
https://drive.google.com/drive/folders/0BwD0UWci-5MxOU5Sc0lNS3IzWWM?usp=sharing
I'm going to consider the data lost, and rebuild/factory reset back down to 4.2 for stability.
I think this is the answer without getting into costly data recovery services, or massive time investment.
8 Replies
Replies have been turned off for this discussion
It looks like there's some file corruption. Per Kernel.log
Jul 12 20:27:09 readynas01 kernel: BTRFS: device label 33ea999f:data devid 1 transid 1431232 /dev/md127
Jul 12 20:27:09 readynas01 kernel: BTRFS info (device md127): has skinny extents
Jul 12 20:27:10 readynas01 kernel: BTRFS critical (device md127): corrupt leaf, slot offset bad: block=2291416563712, root=1, slot=77
Jul 12 20:27:10 readynas01 kernel: BTRFS error (device md127): failed to read block groups: -5
Jul 12 20:27:10 readynas01 kernel: BTRFS critical (device md127): corrupt leaf, slot offset bad: block=2291416563712, root=1, slot=77
Jul 12 20:27:10 readynas01 kernel: BTRFS error (device md127): failed to read block groups: -5
Jul 12 20:27:10 readynas01 kernel: BTRFS critical (device md127): corrupt leaf, slot offset bad: block=2291416563712, root=1, slot=77
Jul 12 20:27:10 readynas01 kernel: BTRFS error (device md127): failed to read block groups: -5
Jul 12 20:27:10 readynas01 kernel: BTRFS critical (device md127): corrupt leaf, slot offset bad: block=2291416563712, root=1, slot=77
Jul 12 20:27:10 readynas01 kernel: BTRFS error (device md127): failed to read block groups: -5
Jul 12 20:27:10 readynas01 kernel: BTRFS critical (device md127): corrupt leaf, slot offset bad: block=2291416563712, root=1, slot=77
Jul 12 20:27:10 readynas01 kernel: BTRFS error (device md127): failed to read block groups: -5Jul 12 20:27:10 readynas01 kernel: BTRFS error (device md127): open_ctree failed
jak0lantash might have some suggestions on next steps.
That seems... not good. :(
I bought a QNAP and am trying to get data restored manually for now. Luckily I have online backups of the critical stuff (10+ years of photography shoots and proofs).
Regardless of the outcome, I think I'll roll-back the firmware to the "officially" supported version 4.x. Ever since upgrading to the unsupported 6.x, I've noticed it locks up fairly often - I even setup a cron job to reboot it nightly to try and reduce the impact.
I know any OS dis-likes hard-reset... and it's been restarted this way a few times in the past couple months.
My wife thinks it's because she gave it the middle finger before powering it off...
I'm taking a look at the logs now. But you should remove them for Google Drive. There is your serial number in there.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
