NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tomiaurednik
Feb 22, 2019Tutor
No volume exists
Yesterday in the morning NAS started to behave extremely slow. Found out it was stuck in a rsync process for days (replication to another NAS), but I was unable to stop the process. So NAS was restarted. RSync was not working anymore, but wotking with it was still a nightmare.
Since it was begging for update for a few weeks already, I updated it to 6.9.5. After reboot everything went to normal - except speed. But I left it alone.
But today in the morning all the shares disappeared... Web interface announced
- No volume exists. Netgear recommends that you create a volume before configuring other settings.
- Remove inactive volumes to use disk #1,2,3,4,1,2,3,4.
- Volume is inactive or dead
Upgraded to 6.10.0 (RC1), multiple reboots, no change. Configuration : 4 x 6 TB HDD
dmesg output :
[ 72.906823] systemd[1]: Starting MD arrays...
[ 73.232007] md: md127 stopped.
[ 73.270323] md: bind<sdd3>
[ 73.284432] md: bind<sdb3>
[ 73.287420] md: bind<sda3>
[ 73.288151] md: bind<sdc3>
[ 73.298544] md/raid:md127: device sdc3 operational as raid disk 0
[ 73.298566] md/raid:md127: device sda3 operational as raid disk 3
[ 73.298575] md/raid:md127: device sdb3 operational as raid disk 2
[ 73.298583] md/raid:md127: device sdd3 operational as raid disk 1
[ 73.302839] md/raid:md127: allocated 4294kB
[ 73.314299] md/raid:md127: raid level 5 active with 4 out of 4 devices, algorithm 2
[ 73.314317] RAID conf printout:
[ 73.314325] --- level:5 rd:4 wd:4
[ 73.314334] disk 0, o:1, dev:sdc3
[ 73.314342] disk 1, o:1, dev:sdd3
[ 73.314349] disk 2, o:1, dev:sdb3
[ 73.314357] disk 3, o:1, dev:sda3
[ 73.314830] md127: detected capacity change from 0 to 11987456360448
[ 73.408064] systemd[1]: Started Journal Service.
[ 73.648881] BTRFS: device label 0e352432:data devid 1 transid 1251517 /dev/md127
[ 73.649826] systemd-journald[1086]: Received request to flush runtime journal from PID 1
[ 73.696635] Adding 1046524k swap on /dev/md1. Priority:-1 extents:1 across:1046524k
[ 73.955192] md: md126 stopped.
[ 73.966942] md: bind<sda4>
[ 73.967525] md: bind<sdd4>
[ 73.968059] md: bind<sdc4>
[ 73.968620] md: bind<sdb4>
[ 73.983011] md/raid:md126: device sdb4 operational as raid disk 0
[ 73.983032] md/raid:md126: device sdc4 operational as raid disk 3
[ 73.983041] md/raid:md126: device sdd4 operational as raid disk 2
[ 73.983050] md/raid:md126: device sda4 operational as raid disk 1
[ 73.984769] md/raid:md126: allocated 4294kB
[ 73.984959] md/raid:md126: raid level 5 active with 4 out of 4 devices, algorithm 2
[ 73.984970] RAID conf printout:
[ 73.984977] --- level:5 rd:4 wd:4
[ 73.984985] disk 0, o:1, dev:sdb4
[ 73.984993] disk 1, o:1, dev:sda4
[ 73.985000] disk 2, o:1, dev:sdd4
[ 73.985008] disk 3, o:1, dev:sdc4
[ 73.989401] md126: detected capacity change from 0 to 6000767729664
[ 74.336354] BTRFS: device label 0e352432:data devid 2 transid 1251517 /dev/md126
[ 74.824574] BTRFS info (device md126): setting nodatasum
[ 75.604171] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.604200] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624049] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624076] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624162] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624176] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624214] BTRFS warning (device md126): failed to read tree root
[ 75.624249] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624262] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624310] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624324] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624369] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624383] BTRFS critical (device md126): unable to find logical 9046860824576 len 4096
[ 75.624416] BTRFS warning (device md126): failed to read tree root
[ 75.624490] BTRFS critical (device md126): unable to find logical 9046856433664 len 4096
[ 75.624502] BTRFS critical (device md126): unable to find logical 9046856433664 len 4096
[ 75.624554] BTRFS critical (device md126): unable to find logical 9046856433664 len 4096
[ 75.624567] BTRFS critical (device md126): unable to find logical 9046856433664 len 4096
[ 75.624614] BTRFS critical (device md126): unable to find logical 9046856433664 len 4096
[ 75.624626] BTRFS critical (device md126): unable to find logical 9046856433664 len 4096
[ 75.624661] BTRFS warning (device md126): failed to read tree root
[ 75.624718] BTRFS critical (device md126): unable to find logical 9046852075520 len 4096
[ 75.624731] BTRFS critical (device md126): unable to find logical 9046852075520 len 4096
[ 75.624779] BTRFS critical (device md126): unable to find logical 9046852075520 len 4096
[ 75.624792] BTRFS critical (device md126): unable to find logical 9046852075520 len 4096
[ 75.624839] BTRFS critical (device md126): unable to find logical 9046852075520 len 4096
[ 75.624852] BTRFS critical (device md126): unable to find logical 9046852075520 len 4096
[ 75.624886] BTRFS warning (device md126): failed to read tree root
[ 75.624937] BTRFS critical (device md126): unable to find logical 9046846832640 len 4096
[ 75.624950] BTRFS critical (device md126): unable to find logical 9046846832640 len 4096
[ 75.625001] BTRFS critical (device md126): unable to find logical 9046846832640 len 4096
[ 75.625013] BTRFS critical (device md126): unable to find logical 9046846832640 len 4096
[ 75.625060] BTRFS critical (device md126): unable to find logical 9046846832640 len 4096
[ 75.625072] BTRFS critical (device md126): unable to find logical 9046846832640 len 4096
[ 75.625106] BTRFS warning (device md126): failed to read tree root
[ 75.800322] BTRFS error (device md126): open_ctree failed
Any idea how to get data back ?
7 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
It's best to use paid support (my.netgear.com) for this. Ask about per-incident support.
- HopchenProdigy
StephenB wrote:
It's best to use paid support (my.netgear.com) for this. Ask about per-incident support.
Yup, I agree with StephenB. This looks like filesystem corruption. Unless you are very familiar with BTRFS troubleshooting, I would think it is better that Netgear support takes a look at this. If you have backups you can of course factory reset the NAS and restore from the backups but otherwise it would be better to reach out to NTGR for assistance.
Maybe I am a bit stupid, but I cannot find anything else but call support. There's no pay-per-incident option for EU. Or am I missing something ?
Best regards
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!