NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas not using full capacity
Hi, It seems like my readynas 314 will not expand to the new size. I started with 6tb - 2tb - 6tb - 2tb which gave me ~9tb of space Then I wanted to upgrade the 2tb disks to 4tb disks. I did thi...
It did something I've never seen before:
/dev/md/data-0:
Creation Time : Tue Sep 16 06:37:21 2014
Raid Level : raid5
Used Dev Size : 971910784 (926.89 GiB 995.24 GB)
/dev/md/data-1: Creation Time : Tue Sep 16 16:50:37 2014 Raid Level : raid5 Used Dev Size : 976622784 (931.38 GiB 1000.06 GB)
/dev/md/data-2: Creation Time : Tue Nov 7 05:15:19 2017 Raid Level : raid1 Used Dev Size : 3906876864 (3725.89 GiB 4000.64 GB) 0 8 21 0 active sync /dev/sdb5 1 8 37 1 active sync /dev/sdc5 /dev/md/data-3: Creation Time : Fri Jan 10 04:50:20 2020
Raid Level : raid1
Used Dev Size : 1953371840 (1862.88 GiB 2000.25 GB) 0 8 5 0 active sync /dev/sda5 2 8 53 1 active sync /dev/sdd5
Normally XRAID just won't expand when you add an intermediate size disk. But in your case, it apparently did create a jbod RAID group using the first 2 TB of the 4 TB drive, and then converted that to RAID-1 when you installed the second 4 TB drive. That explains the expansion you saw on the first upgrade, and also why the size didn't follow the normal capacity rule.
This apparently happened some months ago, so the info in rn_expand.log isn't relevant.
A factory reset is the best way to get the full volume space. You'll end up with two RAID groups - 2x4TB RAID-5 + 2x2TB RAID-1.
OK, so that final configuration is what I said was actually possible, but not implemented in XRAID. So, maybe Netgear has added some logic in a recent OS update to implement it. But using the extra 2TB of the first 4TB as JBOD was a really bad thing if you were assuming you had RAID redundancy, since that 2TB did not have redundancy until you added the second 4TB. At this point, it is anyone's guess what the next step would be if you were to further expand. Unless you need the additional space right away, you can hold off on the factory default. But I recommend that you figure out a good time to do it down the road, both to gain the full capacity and to align the volume with a more typical configuration.
I have already done the factory reset, I was just able to copy all the data onto the 6tb (which I pulled out of the NAS) and some extra space I had on my server. If I left this too long I wouldn't have the space to do the backup and factory reset.
Currently I have copied everything back and done a resync (auto task)
Now I have added the 6tb back and it is syncing again current config is 4-6-6-4tb
I have 30 hours to go before the resync has completed then I will hopefully have 12tb and I will report back here.
raid rebuild / resync completed and I have the 12.7TB as I expected.
here is the MDStat log after everything as finished.
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md126 : active raid1 sdd4[1] sdb4[0] 1953371904 blocks super 1.2 [2/2] [UU] md1 : active raid10 sdd2[3] sdc2[2] sdb2[1] sda2[0] 1044480 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU] md127 : active raid5 sdd3[3] sda3[0] sdc3[2] sdb3[1] 11706506496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] md0 : active raid1 sdd1[3] sdc1[2] sdb1[1] sda1[0] 4190208 blocks super 1.2 [4/4] [UUUU] unused devices: <none> /dev/md/0: Version : 1.2 Creation Time : Thu May 7 11:10:07 2020 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 : Sun May 10 09:40:56 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Consistency Policy : unknown Name : 7c6ee9a2:0 (local to host 7c6ee9a2) UUID : e29d0677:78f09251:4917514b:cbce50eb Events : 134 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 2 8 33 2 active sync /dev/sdc1 3 8 49 3 active sync /dev/sdd1 /dev/md/data-0: Version : 1.2 Creation Time : Thu May 7 11:10:36 2020 Raid Level : raid5 Array Size : 11706506496 (11164.19 GiB 11987.46 GB) Used Dev Size : 3902168832 (3721.40 GiB 3995.82 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sun May 10 09:26:58 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Name : 7c6ee9a2:data-0 (local to host 7c6ee9a2) UUID : dd00049d:d35c5667:9aeb3863:c3de4e2c Events : 10616 Number Major Minor RaidDevice State 0 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 2 8 35 2 active sync /dev/sdc3 3 8 51 3 active sync /dev/sdd3 /dev/md/data-1: Version : 1.2 Creation Time : Fri May 8 18:48:37 2020 Raid Level : raid1 Array Size : 1953371904 (1862.88 GiB 2000.25 GB) Used Dev Size : 1953371904 (1862.88 GiB 2000.25 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Sun May 10 09:26:58 2020 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Consistency Policy : unknown Name : 7c6ee9a2:data-1 (local to host 7c6ee9a2) UUID : 0b38887a:4f6c5565:b1923aa9:fbbc49d7 Events : 73 Number Major Minor RaidDevice State 0 8 20 0 active sync /dev/sdb4 1 8 52 1 active sync /dev/sdd4it looks like the only solution for this was to do a factory reset if anyone has the same issue later.
FYI my NAS was around 6 years old an ever had a reset, so if yours is new and you are having this issue then it might be something else.
Thx for following up. Your mdstat log shows the configuration we'd expect to see with 2x6TB+2x4TB.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
