NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rn214not expanding
i have a readynas 214 with 1x 4tb an thd 3 x 3tb hoever the capacity is coming outon the admin page as 6.35 tb i think i should be getting in the region of 7.4tb based on the readynas calculator giv...
many thanks for the reply
cant remember the very original drive cobination but befr the most recent change i hink it was 4tb,3,2tb,3tb
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md126 : active raid5 sda4[4] sdd4[3] sdb4[1]
3906745856 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
resync=DELAYED
md127 : active raid5 sda3[6] sdd3[4] sdc3[5] sdb3[1]
2915738496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
[==================>..] resync = 90.5% (880496640/971912832) finish=46.4min speed=32810K/sec
md1 : active raid10 sda2[0] sdd2[3] sdc2[2] sdb2[1]
1046528 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
md0 : active raid1 sda1[6] sdd1[4] sdc1[5] sdb1[1]
4190208 blocks super 1.2 [4/4] [UUUU]
unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Tue Feb 20 20:47:29 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 : Sat Sep 5 08:02:34 2020
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Consistency Policy : unknown
Name : 568aca8b:0 (local to host 568aca8b)
UUID : 6ca489e0:ea2dfd6f:1330a41a:83693582
Events : 5723
Number Major Minor RaidDevice State
6 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
5 8 33 2 active sync /dev/sdc1
4 8 49 3 active sync /dev/sdd1
/dev/md/1:
Version : 1.2
Creation Time : Thu Sep 3 19:36:40 2020
Raid Level : raid10
Array Size : 1046528 (1022.00 MiB 1071.64 MB)
Used Dev Size : 523264 (511.00 MiB 535.82 MB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Sat Sep 5 07:54:47 2020
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : near=2
Chunk Size : 512K
Consistency Policy : unknown
Name : 568aca8b:1 (local to host 568aca8b)
UUID : e083319b:882c0819:3d5e4ae3:d4d4c232
Events : 19
Number Major Minor RaidDevice State
0 8 2 0 active sync set-A /dev/sda2
1 8 18 1 active sync set-B /dev/sdb2
2 8 34 2 active sync set-A /dev/sdc2
3 8 50 3 active sync set-B /dev/sdd2
/dev/md/data-0:
Version : 1.2
Creation Time : Tue Feb 20 20:48:03 2018
Raid Level : raid5
Array Size : 2915738496 (2780.66 GiB 2985.72 GB)
Used Dev Size : 971912832 (926.89 GiB 995.24 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Sat Sep 5 08:02:38 2020
State : clean, resyncing
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Consistency Policy : unknown
Resync Status : 90% complete
Name : 568aca8b:data-0 (local to host 568aca8b)
UUID : 55af480e:f05a8c92:bc26929e:bd16d3eb
Events : 72474
Number Major Minor RaidDevice State
6 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
5 8 35 2 active sync /dev/sdc3
4 8 51 3 active sync /dev/sdd3
/dev/md/data-1:
Version : 1.2
Creation Time : Wed Feb 21 04:51:56 2018
Raid Level : raid5
Array Size : 3906745856 (3725.76 GiB 4000.51 GB)
Used Dev Size : 1953372928 (1862.88 GiB 2000.25 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Sat Sep 5 08:02:38 2020
State : clean, resyncing (DELAYED)
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Consistency Policy : unknown
Name : 568aca8b:data-1 (local to host 568aca8b)
UUID : 9e75db3f:24081c6f:d1515f20:e59052df
Events : 130022
Number Major Minor RaidDevice State
4 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
3 8 52 2 active sync /dev/sdd4
Did you just replace the disk? If so, you just needed to wait longer (likely it is already expanding by now).
Also, what disk models do you have?
This is the original RAID group, which is still resyncing (which looks like you just replaced a disk).
md127 : active raid5 sda3[6] sdd3[4] sdc3[5] sdb3[1]
2915738496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
[==================>..] resync = 90.5% (880496640/971912832) finish=46.4min speed=32810K/sec
After this completes, the expansion step will begin.
md126 : active raid5 sda4[4] sdd4[3] sdb4[1]
3906745856 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
resync=DELAYED
according to the admin pgsges is stopped resyncing a good few days ago it has ximpleted the resync without moving onto expansion it would seem
drive models are:
- wdwdc w040efax-6h 68jh4n0
- wd wdc030efrx-68euzn0
- toshiba hdwd130
- toshiba hdwd130
Petroc wrote:
according to the admin pgsges is stopped resyncing a good few days ago
What is the current mdstat?
Petroc wrote:- wdc wd40efax-6h 68jh4n0
I was wondering about that. That is an SMR drive, which is not well suited for RAID. I have no idea what WDC was thinking when they used that technology in a NAS-purposed drive. The newer "WD Red Plus" line has the WD40EFRX, which doesn't have that problem.
so sounds like if i reoplace the 1st drive the wd smar drive i might be able to use full capacity what is the conflict between smr and raid?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
