Added a new drive but no space has been added to the X-RAID data volume.

[cbdejavu]

So I am running OS 6.7.5.

I created a new clean system with 3 - 3tb HDD.  It created a RAID 5 X-RAID setup.  The initial data volume size was around 5.4TB (essentially 6tb of usable space).  I added a 4th drive that was 3tb in size.  Once it was syncd I it properly expanded the volume to 8.17tb (essentially 9tb minus the rounding math drive manufacturers do).  Once that was all set I then added a 5th drive to the system and that is where the problem is.

The 5th drive is a 4tb drive.  It is my understanding that it should have added 3tb to the data volume and 1tb should be unusable since the drive is larger than the rest of the drives.  So my new volume should have expanded to something around 10.8tb (essentially adding the 2.7tb capacity that the other 3tb drives have) in final size however, after the drive synced up and it now shows as ONLINE, it didn't add any additional space to the data volume.  The data volume is still 8.17tb in size.  When I hover over the drive it shows that it is part of the data volume and says it is RAID5.  All 5 drives are showing up as Blue with the little green status lights in the graphic showing they are all online and all part of the RAID5 volume.

The "capacity" of the 3tb drives is 2.7tb, the "capacity" of the 4tb drive is 3.6tb, It is my understanding that the volume should have increased in size by 2.7tb with the remaining 0.9tb being unused but after several reboots the space still hasn't shown up on the voume.  It finished "syncing" earlier today so I'm wondering how long does it take for the additional space to show up?  When I added drive 4 to the system which was a 3tb drive the space showed up right after the sync or shortly thereafter.

Here is my msstat.log.  While I'm not very linux savy to me it looks like it is possibly using the new drive as a spare since it shows that there are 5 working devices, 4 raid devices and 1 spare device.  Is this the correct behavior? It was my understanding that is more of a RAID6 configuration but everything is showing as a RAID5 configuration in the GUI.  Is this the normal "default behavior" and is there anyway to not use this drive as a spare and instead let this 5th drive be part of the RAID 5 volume.

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid5 sda3[0] sde3[4](S) sdd3[3] sdc3[2] sdb3[1]
8776250496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

md1 : active raid10 sda2[0] sde2[4] sdd2[3] sdc2[2] sdb2[1]
1308160 blocks super 1.2 512K chunks 2 near-copies [5/5] [UUUUU]

md0 : active raid1 sda1[0] sde1[4] sdd1[3] sdc1[2] sdb1[1]
4190208 blocks super 1.2 [5/5] [UUUUU]

unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Sat Jul 1 15:59:01 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 : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Fri Jul 7 18:48:10 2017
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Name : 33eac487:0 (local to host 33eac487)
UUID : f0304e95:a23f910f:8a4d9014:e240a339
Events : 112

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
4 8 65 4 active sync /dev/sde1
/dev/md/1:
Version : 1.2
Creation Time : Thu Jul 6 12:05:25 2017
Raid Level : raid10
Array Size : 1308160 (1277.50 MiB 1339.56 MB)
Used Dev Size : 523264 (511.00 MiB 535.82 MB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Fri Jul 7 18:29:42 2017
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : near=2
Chunk Size : 512K

Name : 33eac487:1 (local to host 33eac487)
UUID : 660d1c47:3da37a31:4d4a39c5:a7e429f0
Events : 35

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
3 8 50 3 active sync /dev/sdd2
4 8 66 4 active sync /dev/sde2
/dev/md/data-0:
Version : 1.2
Creation Time : Sat Jul 1 15:59:16 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 : 5
Persistence : Superblock is persistent

Update Time : Fri Jul 7 18:48:35 2017
State : active
Active Devices : 4
Working Devices : 5
Failed Devices : 0
Spare Devices : 1

Layout : left-symmetric
Chunk Size : 64K

Name : 33eac487:data-0 (local to host 33eac487)
UUID : ce88fd0c:7149dc6f:3b995bfe:c26d39a2
Events : 17829

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

4 8 67 - spare /dev/sde3

[jak0lantash]

sde3 is marked as 'spare' instead of 'active sync'. Maybe try to unslot and insert that drive again, reboot, turn off and on X-RAID, etc.

Otherwise, it's possible to fix the RAID via SSH.

[cbdejavu]

Thanks for the reply.  I did a little research and am actually going down those lines now.

Since my post what I've done is:

run a balance

Turned off x-raid

run a balance again

rutned x-raid back on

ran another balance.

I've restarted and shutdown restarted the system a few times as well.

Last thing I did was remove the drive, connect it to a computer to reformat it so it was no longer part of NAS.

I re-inserted the drive and it is now syncing again.  I'm hoping it will sync up ok.

I did notice that the drive has a new id now (it was sde and now it is syncing as sdf so I'm hoping that I didn't make it worse).

[jak0lantash]

Unless your volume is fully allocated, no need to run balances, it's irrelevant in the context.

Download the logs again and check mdstat.log.

[cbdejavu]

Thanks for your input.  It looks like it finally sync'd up.  I guess the key was removing that drive, wiping the partition and then lettting the system try again.  I'm going to be adding one more drive to fill the last slot and it is a 5tb drive.  I'm hoping that last drive will go more smoothly.

Here is the mdstat.log as of now.  It looks like the id 4 drive which had been tagged spare is completely removed from the table and this drive became id 5 and is now in sync and behaving as expected.  This shouldn't impact my adding a 6th and final drive should it?

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid10 sde2[4] sdd2[3] sdc2[2] sdb2[1] sda2[0]
1308160 blocks super 1.2 512K chunks 2 near-copies [5/5] [UUUUU]

md127 : active raid5 sde3[5] sda3[0] sdd3[3] sdc3[2] sdb3[1]
11701667328 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]

md0 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
4190208 blocks super 1.2 [4/4] [UUUU]

unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Sat Jul 1 15:59:01 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 : Sun Jul 9 22:26:46 2017
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0

Name : 33eac487:0 (local to host 33eac487)
UUID : f0304e95:a23f910f:8a4d9014:e240a339
Events : 204

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 : Sat Jul 1 15:59:16 2017
Raid Level : raid5
Array Size : 11701667328 (11159.58 GiB 11982.51 GB)
Used Dev Size : 2925416832 (2789.89 GiB 2995.63 GB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Sun Jul 9 22:26:47 2017
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 64K

Name : 33eac487:data-0 (local to host 33eac487)
UUID : ce88fd0c:7149dc6f:3b995bfe:c26d39a2
Events : 93358

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
5 8 67 4 active sync /dev/sde3

[jak0lantash]

Yes md127 is fine now.
sde3 is 'active sync'.