NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NAS 104 Locked Up
NAS has locked up. Can not access. Can not even ping. See attached photo of the display. Will not soft shutdown using power button. Any ideas?
So i power cycled the NAS. It came back and all looked OK. A few days later a new message appeared,
"btrfs_search_forward+2ac"
Again NAS totally locked up. power cycled again. Now NAS shows a popup which says "No volume exists" with a warning message "Remove inactive volumes to use the disk. Disk #1,2,3,4."!!!!!!!!!!!!
Lookes like I have lost all my data again.... Anyway to recover?
logs attached.
This is the third time with a Netgear NAS.
Hi
I have tried re-booting into read only mode. Still no volume.
I want to SSH into the unit to check if the data is still there and try a re-mount. I get a connection refused. i went to settings in admin and see under services that SSH is not selcted. I am unable to enable SSH, when I try it says "cannot start service without a volume"!! Is there any way I get enable SSH or get in bypassing the admin setup? How about the tech mode in the boot menu?
Thanks
Adam
You could telnet into the NAS in tech support mode, and then use the linux CLI.
Log in as root with password infr8ntdebug.
Start RAID and chroot with
# rnutil chroot
The normal steps to mount the data volume will likely fail, but are
# btrfs device scan # btrfs fi show # mount /dev/md127 /data
You could potentially try running
# btrfs check /dev/md127
before you try to do the mount. That won't repair anything, it will just check the volume.
Here are the results. Any further ideas...
3EP134E501109 login: root
Password:
# rnutil chroot
mdadm: /dev/md/0 has been started with 4 drives.
mdadm: /dev/md/1 has been started with 4 drives.
mdadm: /dev/md/data-0 has been started with 4 drives.
mount: mounting LABEL=0e346740:data on /data failed: No such file or directory
root@3EP134E501109:/#
root@3EP134E501109:/# btrfs check /dev/md127
checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8
checksum verify failed on 27623876067328 found 7B90F733 wanted 317347E8
checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4
checksum verify failed on 27623876067328 found 092ADC2A wanted 80665FC4
bytenr mismatch, want=27623876067328, have=6109277914453778088
Couldn't read tree root
Couldn't open file system
root@3EP134E501109:/# btrfs device scan
Scanning for Btrfs filesystems
root@3EP134E501109:/# btrfs fi show
Label: '0e346740:data' uuid: a5008274-7a77-450f-b098-dff8dd3dc285
Total devices 1 FS bytes used 20.10TiB
devid 1 size 21.82TiB used 21.77TiB path /dev/md127
root@3EP134E501109:/# mount /dev/md127 /data
mount: wrong fs type, bad option, bad superblock on /dev/md127,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
root@3EP134E501109:/# dmesg | tail
[ 153.836981] disk 2, o:1, dev:sdc3
[ 153.836988] disk 3, o:1, dev:sdd3
[ 153.837203] md127: detected capacity change from 0 to 23989784936448
[ 154.337435] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 229.016409] BTRFS: device label 0e346740:data devid 1 transid 1575622 /dev/md127
[ 270.024702] BTRFS: has skinny extents
[ 270.241458] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328
[ 270.241879] BTRFS (device md127): bad tree block start 17761992830035128566 27623876067328
[ 270.241917] BTRFS: failed to read tree root on md127
[ 270.300229] BTRFS: open_ctree failed
root@3EP134E501109:/#
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
