X-RAID2 Expansion - or lack of

[iawa2k]

Firmware: 6.6.0

Some time ago I upgraded from an NV+ that had maxed out at it's 4x2TB limit. I backed up my data, bought a shiny new RN104, moved the drives over and restored the data.

I have over the last year or so been replacing the 2TB drives with 4TB drives (one at a time as and when I've had some free cash). Moving up to 3 x 4TB drives worked flawlessly; once it had sync'd it expanded out and all was good.

The 4th however I've not been as lucky.

I am not sure if this is the issue but with this one my hand was forced to buy a drive as the last 2TB drive had failed so the volume was degraded. I bought a 4TB drive and swapped out the 2TB drive.

It resynced and got back to 'Redundant' status, however it's at the old volume size still.

I have rebooted (several times) and shut the system down, discharged and then powered it back up and still the same.

The NAS seems happy but obviously it seems like a waste to have got a 4TB drive when it's not making it any bigger.

All the drives have 7814037168 sectors and all show as 3.6TB capacity so it's not that one is smaller than others etc.

Now the array is so large I don't really have an easy way to back it all up - I would not cry if I lost the array due to failure as most of it are backups of backups but I don't really want to actively destroy it all if I don't have to - if that makes sense.

Hopefully someone here can help?

[StephenB · Accepted solution]

Someone from Netgear might want to look at the logs, so maybe give them a chance.

One option is to remove the drive (which will degrade it again), and perhaps zero it using vendor tools in a PC, and then reinsert it. 

[StephenB]

What volume size are you seeing?  Did you try rebooting the NAS?

[iawa2k]

9.08TB

Yes, rebooted several times and powered off & discharged as well.

[StephenB · Accepted solution]

Someone from Netgear might want to look at the logs, so maybe give them a chance.

One option is to remove the drive (which will degrade it again), and perhaps zero it using vendor tools in a PC, and then reinsert it. 

[iawa2k]

Should I post the logs here? When I went round in circles on the support pages I just led me to a page that said try our knowledge base or post in these forums.

I was wondering if to remove the drive and see if the factory format it in anyway but the others I had purchased from the same manufacturer weren't even initialised (i.e. Completely zeroed).

Is there a way to check for partitions without removing from NAS?

[StephenB]

---

@iawa2k wrote:
Should I post the logs here? 

---

Wait for someone from netgear to ask, and then send them using the info here: http://kb.netgear.com/app/answers/detail/a_id/21543/~/how-do-i-send-all-logs-to-readynas-community-m...

---

@iawa2k wrote:



Is there a way to check for partitions without removing from NAS?

---

You can look via ssh, but probably not a good option if you don't know how to do that already.  

You could switch to flexraid, then remove/reinsert it with the NAS running - with no zeroing. The drive should then show up as not in the array.  You can then re-add it to the array from the web ui.

[iawa2k]

Ah ok thanks. Am comfortable with shell access but will wait for Netgear as I'm not in a mad rush and it's all working ok so not a problem waiting.

In the meantime I may try zeroing as you mentioned and may just help making it degraded by pulling the drive and not from one failing.

[mdgm-ntgr]

Well if you want to post some logs in the thread you'd be looking at e.g. mdstat.log

If you can send in the logs zip file (see the Sending Logs link in my sig) that would be good 

[iawa2k]

Thanks, I have sent the logs in and below is the mdstat.log readout for completness;

mdstat.log

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md126 : active raid5 sdb4[0] sdc4[3] sdd4[2] sda4[1]
5860124736 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

md127 : active raid5 sda3[0] sdd3[5] sdc3[6] sdb3[4]
5845988352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

md1 : active raid6 sda2[0] sdc2[3] sdd2[2] sdb2[1]
1046528 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/4] [UUUU]

md0 : active raid1 sda1[0] sdd1[5] sdc1[6] sdb1[4]
4190208 blocks super 1.2 [4/4] [UUUU]

unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Sun Jul 19 11:29:12 2015
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 Oct 18 09:31:52 2016
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0

Name : 0e3462ae:0 (local to host 0e3462ae)
UUID : 6489314e:62984e45:393f9c86:fd1e14d6
Events : 106205

Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
4 8 17 1 active sync /dev/sdb1
6 8 33 2 active sync /dev/sdc1
5 8 49 3 active sync /dev/sdd1
/dev/md/1:
Version : 1.2
Creation Time : Fri Oct 14 18:41:03 2016
Raid Level : raid6
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 : Tue Oct 18 09:31:46 2016
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Name : 0e3462ae:1 (local to host 0e3462ae)
UUID : 37f9dc80:2c264e2f:5c4a85e7:8e1fc013
Events : 19

Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 50 2 active sync /dev/sdd2
3 8 34 3 active sync /dev/sdc2
/dev/md/data-0:
Version : 1.2
Creation Time : Sun Jul 19 11:29:13 2015
Raid Level : raid5
Array Size : 5845988352 (5575.17 GiB 5986.29 GB)
Used Dev Size : 1948662784 (1858.39 GiB 1995.43 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent

Update Time : Tue Oct 18 09:31:54 2016
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 64K

Name : 0e3462ae:data-0 (local to host 0e3462ae)
UUID : 02c0f892:0104f79b:8a172133:0596fcdd
Events : 387225

Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
4 8 19 1 active sync /dev/sdb3
6 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 Jul 21 18:00:29 2015
Raid Level : raid5
Array Size : 5860124736 (5588.65 GiB 6000.77 GB)
Used Dev Size : 1953374912 (1862.88 GiB 2000.26 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent

Update Time : Tue Oct 18 09:31:33 2016
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 64K

Name : 0e3462ae:data-1 (local to host 0e3462ae)
UUID : 36720040:47536d4d:2f17fa60:2ef8a702
Events : 24680

Number Major Minor RaidDevice State
0 8 20 0 active sync /dev/sdb4
1 8 4 1 active sync /dev/sda4
2 8 52 2 active sync /dev/sdd4
3 8 36 3 active sync /dev/sdc4

[mdgm-ntgr]

Odd. That should have expanded. Maybe try another reboot.

[iawa2k]

Ok. I will go for my (now 10th) reboot.

Edit: Nope. Still the same.

[iawa2k]

Pulling the drive and reinserting to let it sync a second time seems to have done the job!

Many thanks for your help!