NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Extra Space after upgrading disks
HI
I have a readynas 314. i initialy set it up with X-Raid on the following disks.
2 X 6TB
2 X 3TB
This went With out any issues.
i then proceded to upgrade the two 3TB disk with 4TB disk. The first 4TB disk i put in syncd fine but did not expand the free space. The second 4TB drivei put it synced fine and expanded giving me more free space.
The total space i see with 2 x 6Tb & 2 x 4TB in X-Raid is 11.81TB i was exspecting to see 12.5-7 TB
I have 2 other ready nas for over 5 years and not had this issue
any sugestions ?
(3*3+1*1+1*3)*1000^4/1024^4 = 11.82 TiB
Allow for things like the root volume, swap partition and overheads and you'd get 11.81TiB.
You've got a 4x3TB layer, a 2x1TB layer and a 2x3TB layer. To get the most expansion you would've needed to add the 4TB disks before the 6TB disks not afterwards. You could replace the 4TB disks with 6TB disks done the track to get further vertical expansion.
4 Replies
Replies have been turned off for this discussion
What does your mdstat.log look like?
Hi mdgm
here is the Mdsytat.log
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md125 : active raid1 sdc4[2] sdd4[1]
976620928 blocks super 1.2 [2/2] [UU]
md126 : active raid5 sda3[0] sdd3[5] sdc3[4] sdb3[1]
8776250496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md127 : active raid1 sda4[0] sdb4[1]
2930124928 blocks super 1.2 [2/2] [UU]
md1 : active raid10 sda2[0] sdc2[3] sdd2[2] sdb2[1]
1046528 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
md0 : active raid1 sda1[0] sdc1[4] sdd1[5] sdb1[1]
4190208 blocks super 1.2 [4/4] [UUUU]
unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Tue May 23 17:19:34 2017
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 Jun 10 09:12:21 2017
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Name : 2fe5643e:0 (local to host 2fe5643e)
UUID : dd7426fc:d9feec72:819b559c:c2f2448f
Events : 457
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
5 8 49 2 active sync /dev/sdd1
4 8 33 3 active sync /dev/sdc1
/dev/md/1:
Version : 1.2
Creation Time : Sat Jun 3 00:53:00 2017
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 Jun 3 14:24:43 2017
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : near=2
Chunk Size : 512K
Name : 2fe5643e:1 (local to host 2fe5643e)
UUID : 5e5bfb5d:08b4f394:933b6c05:9488609c
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 50 2 active sync set-A /dev/sdd2
3 8 34 3 active sync set-B /dev/sdc2
/dev/md/data-0:
Version : 1.2
Creation Time : Tue May 23 17:20:00 2017
Raid Level : raid5
Array Size : 8776250496 (8369.68 GiB 8986.88 GB)
Used Dev Size : 2925416832 (2789.89 GiB 2995.63 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Sat Jun 10 02:48:12 2017
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : 2fe5643e:data-0 (local to host 2fe5643e)
UUID : cc58c691:97e7f98c:d24a4e4f:ced7e493
Events : 2600
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
4 8 35 2 active sync /dev/sdc3
5 8 51 3 active sync /dev/sdd3
/dev/md/data-1:
Version : 1.2
Creation Time : Tue May 23 17:21:19 2017
Raid Level : raid1
Array Size : 2930124928 (2794.38 GiB 3000.45 GB)
Used Dev Size : 2930124928 (2794.38 GiB 3000.45 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sat Jun 10 02:48:12 2017
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : 2fe5643e:data-1 (local to host 2fe5643e)
UUID : 5550356e:a1343995:3fb490f6:6dc5a6df
Events : 103
Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
/dev/md/data-2:
Version : 1.2
Creation Time : Fri Jun 2 20:53:08 2017
Raid Level : raid1
Array Size : 976620928 (931.38 GiB 1000.06 GB)
Used Dev Size : 976620928 (931.38 GiB 1000.06 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sat Jun 10 02:48:12 2017
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : 2fe5643e:data-2 (local to host 2fe5643e)
UUID : bd7afb10:852f9f27:093210bf:4da895cd
Events : 192
Number Major Minor RaidDevice State
2 8 36 0 active sync /dev/sdc4
1 8 52 1 active sync /dev/sdd4(3*3+1*1+1*3)*1000^4/1024^4 = 11.82 TiB
Allow for things like the root volume, swap partition and overheads and you'd get 11.81TiB.
You've got a 4x3TB layer, a 2x1TB layer and a 2x3TB layer. To get the most expansion you would've needed to add the 4TB disks before the 6TB disks not afterwards. You could replace the 4TB disks with 6TB disks done the track to get further vertical expansion.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
