This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have a ReadyNAS 104. It had 3 4TB drives in it that were filling up so I bought a 4th 4TB drive (they all match) and popped it in. The NAS did a re-synch for about 4 days and now all my data is gone (about 8TB of personal docs, videos, pics etc)
I have a ReadyNAS 104. It had 3 4TB drives in it that were filling up so I bought a 4th 4TB drive (they all match) and popped it in. The NAS did a re-synch for about 4 days and now all my data is gone (about 8TB of personal docs, videos, pics etc)
Did a disk fail during the resync?
Is it showing an inactive volume?
There are a couple of options you could pursue - unfortunately they are expensive.
Similarly, you could find another data recovery service that can handle BTRFS and RAID.
Yet another option is to use data recovery software. That will require you to connect the disks to a PC (likely using a USB chassis with multiple bays), and purchase the data recovery software. ReclaiMe is a package that sever folks here have used with success.
@rn_enthusiast is a poster here who has somtimes offered help in analyzing logs, and in cases where the fix appears to be fairly straightforward has offered advice. So you could also wait a little and see if he is able to respond with similar help.
I stupidly decided to remove the 4th disk again and now it's doing a resync again...
Not the best idea. But the fact that it is resyncing is encouraging. I think it suggests that there's a good chances of getting your data back with minimal loss.
Great news! rebooting remounted my volumes and my data is intact!
that being said, after adding my 4th 4TB drive, I still only have just under 8TB of space. Anyone know why the new disk doesn't seem to have been added to the volume?
md1 : active raid10 sdb2[0] sda2[3] sdd2[2] sdc2[1] 1044480 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
md0 : active raid1 sdd1[0] sda1[4] sdb1[3] sdc1[2] 4190208 blocks super 1.2 [4/4] [UUUU]
unused devices: <none> /dev/md/0: Version : 1.2 Creation Time : Tue Aug 12 18:35:30 2014 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 : Tue Dec 14 18:27:07 2021 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0
Consistency Policy : unknown
Name : 0e35f548:0 (local to host 0e35f548) UUID : 739c618f:77ddeea2:afbeefc8:84c39546 Events : 6109
Number Major Minor RaidDevice State 0 8 49 0 active sync /dev/sdd1 2 8 33 1 active sync /dev/sdc1 3 8 17 2 active sync /dev/sdb1 4 8 1 3 active sync /dev/sda1 /dev/md/1: Version : 1.2 Creation Time : Wed Dec 8 14:18:38 2021 Raid Level : raid10 Array Size : 1044480 (1020.00 MiB 1069.55 MB) Used Dev Size : 522240 (510.00 MiB 534.77 MB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent
Update Time : Tue Dec 14 18:27:09 2021 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0
Layout : near=2 Chunk Size : 512K
Consistency Policy : unknown
Name : 0e35f548:1 (local to host 0e35f548) UUID : d6b35c78:d1b29a7a:2a6a20a0:3fcce611 Events : 19
Number Major Minor RaidDevice State 0 8 18 0 active sync set-A /dev/sdb2 1 8 34 1 active sync set-B /dev/sdc2 2 8 50 2 active sync set-A /dev/sdd2 3 8 2 3 active sync set-B /dev/sda2 /dev/md/data-0: Version : 1.2 Creation Time : Tue Aug 12 18:35:31 2014 Raid Level : raid5 Array Size : 11706500352 (11164.19 GiB 11987.46 GB) Used Dev Size : 3902166784 (3721.40 GiB 3995.82 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent
Update Time : Tue Dec 14 18:19:09 2021 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0
Layout : left-symmetric Chunk Size : 64K
Consistency Policy : unknown
Name : 0e35f548:data-0 (local to host 0e35f548) UUID : bb53eb3e:7f6d1c7e:b8e3641b:7dc5aaa7 Events : 161745
Number Major Minor RaidDevice State 0 8 51 0 active sync /dev/sdd3 2 8 35 1 active sync /dev/sdc3 3 8 19 2 active sync /dev/sdb3 4 8 3 3 active sync /dev/sda3
The RAID seems to be the right size and healthy, but the BTRFS file system must not have expanded into it. A power cycle may help. If not, issue the following from ssh: btrfs filesystem resize max /data. If that still doesn't do it, we'll have to get some more information about the file system status.
