NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
BorisMM
Nov 27, 2020Aspirant
ReadyNas Volume inactive or dead
Sory of my english. I have a RN214 and RAID 10 encryptynt, after restart NAS say Volume is Inactive or Dead.
Please Help
msdata.log
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid10 sda3[0] sdd3[3] sdc3[2] sdb3[1]
3897329664 blocks super 1.2 64K chunks 2 near-copies [4/4] [UUUU]
md1 : active raid1 sda2[0] sdc2[2] sdb2[1]
523712 blocks super 1.2 [3/3] [UUU]
md0 : active raid1 sda1[4] sdd1[3] sdc1[6] sdb1[5]
4190208 blocks super 1.2 [4/4] [UUUU]
unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Fri Mar 9 18:02:42 2018
Raid Level : raid1
Array Size : 4190208 (4.00 GiB 4.29 GB)
Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Fri Nov 27 10:47:17 2020
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Name : 568ac913:0 (local to host 568ac913)
UUID : e614484a:c36f8540:efe607d1:f001c5c7
Events : 179
Number Major Minor RaidDevice State
4 8 1 0 active sync /dev/sda1
5 8 17 1 active sync /dev/sdb1
6 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
/dev/md/1:
Version : 1.2
Creation Time : Mon Mar 12 16:10:15 2018
Raid Level : raid1
Array Size : 523712 (511.44 MiB 536.28 MB)
Used Dev Size : 523712 (511.44 MiB 536.28 MB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Thu Nov 26 16:09:12 2020
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Name : 568ac913:1 (local to host 568ac913)
UUID : a2f3f20b:49577d05:12713290:d385590c
Events : 19
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 34 2 active sync /dev/sdc2
/dev/md/DATA-0:
Version : 1.2
Creation Time : Mon Mar 12 10:36:52 2018
Raid Level : raid10
Array Size : 3897329664 (3716.78 GiB 3990.87 GB)
Used Dev Size : 1948664832 (1858.39 GiB 1995.43 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Fri Nov 27 09:41:54 2020
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : near=2
Chunk Size : 64K
Name : 568ac913:DATA-0 (local to host 568ac913)
UUID : 64bd0f1b:27243de7:b21c496f:6c6575fa
Events : 83
Number Major Minor RaidDevice State
0 8 3 0 active sync set-A /dev/sda3
1 8 19 1 active sync set-B /dev/sdb3
2 8 35 2 active sync set-A /dev/sdc3
3 8 51 3 active sync set-B /dev/sdd3
- Thx, I can recover my data. - Solution - 1. Do image my btrfs, comand dd on terminal. - 2. Mount image, program OSForensiks - 3. Recovery lost data. Reclami file recovery or Recovery explorer profesional. Recovery explorer best result. 
5 Replies
Replies have been turned off for this discussion
- BorisMMAspirant<redacted download link to log zip file> LoG - StephenBGuru - Experienced UserPlease don't post your logs publicly - there is some privacy leakage. I've redacted your download link. Do you have a backup of the data? There are btrfs errors on the volume that are preventing it from being mounted: Nov 27 10:01:59 SERVER_DB kernel: BTRFS: device label 568ac913:DATA devid 1 transid 872625 /dev/dm-0 Nov 27 10:02:00 SERVER_DB kernel: BTRFS info (device dm-0): setting nodatasum Nov 27 10:02:00 SERVER_DB kernel: BTRFS info (device dm-0): has skinny extents Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 7909885094943733730 17950356111360 Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 7909885094943733730 17950356111360 Nov 27 10:02:00 SERVER_DB kernel: BTRFS warning (device dm-0): failed to read tree root Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 7909885094943733730 17950356111360 Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 7909885094943733730 17950356111360 Nov 27 10:02:00 SERVER_DB kernel: BTRFS warning (device dm-0): failed to read tree root Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 14399094478400985867 17950316724224 Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 14399094478400985867 17950316724224 Nov 27 10:02:00 SERVER_DB kernel: BTRFS warning (device dm-0): failed to read tree root Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 11221268990985196159 17950313840640 Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 11221268990985196159 17950313840640 Nov 27 10:02:00 SERVER_DB kernel: BTRFS warning (device dm-0): failed to read tree root Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 16618288268865450296 17950312431616 Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): bad tree block start 16618288268865450296 17950312431616 Nov 27 10:02:00 SERVER_DB kernel: BTRFS warning (device dm-0): failed to read tree root Nov 27 10:02:00 SERVER_DB kernel: BTRFS error (device dm-0): open_ctree failed You could engage Netgear paid support for data recovery: https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service If you have linux skills, you could also use ssh and attempt to repair it yourself. - BorisMMAspirantHow i can get Netgear paid support for data recovery ? 
 
 
Related Content
NETGEAR Academy
 
 Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 
Join Us!
