NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
"No Volume Exists" After 6.9.3 Lockup
Hi,
Recently updated my NAS to 6.9.3 and found it locked up.
Unable to reboot it I had to drop power.
Not have the message "No Volume Exists"
Checked logs
dmesg.log
[Sun Mar 25 22:40:52 2018] md/raid:md127: raid level 5 active with 6 out of 6 devices, algorithm 2 [Sun Mar 25 22:40:52 2018] RAID conf printout: [Sun Mar 25 22:40:52 2018] --- level:5 rd:6 wd:6 [Sun Mar 25 22:40:52 2018] disk 0, o:1, dev:sda3 [Sun Mar 25 22:40:52 2018] disk 1, o:1, dev:sdb3 [Sun Mar 25 22:40:52 2018] disk 2, o:1, dev:sdc3 [Sun Mar 25 22:40:52 2018] disk 3, o:1, dev:sdd3 [Sun Mar 25 22:40:52 2018] disk 4, o:1, dev:sde3 [Sun Mar 25 22:40:52 2018] disk 5, o:1, dev:sdf3 [Sun Mar 25 22:40:52 2018] md127: detected capacity change from 0 to 4976193699840 [Sun Mar 25 22:40:52 2018] Adding 1046524k swap on /dev/md1. Priority:-1 extents:1 across:1046524k [Sun Mar 25 22:40:53 2018] BTRFS: device label 33eac55b:data devid 1 transid 12663 /dev/md127 [Sun Mar 25 22:40:53 2018] BTRFS info (device md127): has skinny extents [Sun Mar 25 22:40:56 2018] BTRFS error (device md127): parent transid verify failed on 1982502338560 wanted 12664 found 12435 [Sun Mar 25 22:40:56 2018] BTRFS error (device md127): parent transid verify failed on 1982502338560 wanted 12664 found 12435 [Sun Mar 25 22:40:56 2018] BTRFS warning (device md127): failed to read log tree [Sun Mar 25 22:40:56 2018] BTRFS error (device md127): open_ctree failed
Check volume with ubuntu and was able to see data still there (plugged all 6 drives into test rig)
put back into nas and ran
btrfs check --repair /dev/md127
rebooted once completed and all data is back again.
8 Replies
Replies have been turned off for this discussion
Logged in via ssh to try and mount read only (hopefully correct command)
# mount -t btrfs -o ro /dev/md127 /mnt mount: /dev/md127: can't read superblock
Then Check Disk
# btrfs check /dev/md127 parent transid verify failed on 1982502338560 wanted 12664 found 12435 parent transid verify failed on 1982502338560 wanted 12664 found 12435 parent transid verify failed on 1982502338560 wanted 12664 found 12435 Checking filesystem on /dev/md127 UUID: 6b2226c9-adf5-455b-bfff-a218cd7a0588 checking extents checking free space cache checking fs roots checking csums checking root refs checking quota groups Counts for qgroup id: 0/261 are different
Few similar errors after above.
Disks all say active and no errors from what I have worked out.
A little worried about not getting data back since cant mount (assuming I used the correct command)
So your backup is not up to date?
Based on what you've posted above you should contact support.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
