NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
User2024
Feb 13, 2024Aspirant
RN102 - RAID1 did not expand after adding disks
I have a problem with X-RAID volume expansion after disk replacement from 2x1TB to 2x4TB. X-RAID is full synchronized after disk upgrade (one by one) but still volume is 1TB size, even after NAS ...
Sandshark
Feb 13, 2024Sensei - Experienced User
You have confirmed XRAID is on?
You say the NAS is "fully synchronized". How may syncs did it do? It should have done one after the first disk replacement and two after the second, with the expansion occurring after the second.
Can you post the results of the SSH commands cat /proc/mdstat and lsblk?
User2024
Feb 13, 2024Aspirant
Yes, there were two synchronizations.
One sync. after the first disk replacement and second sync. after the second disk.
So, both synchronizations were successful, than restart and X-RAID is still 1TB size.
I will send the logs tomorrow.
- User2024Feb 13, 2024Aspirant
I forgot, X-RAID stats are green in volume management.
- SandsharkFeb 13, 2024Sensei - Experienced User
But there should have been three. One after the first drive was replaced and two after the second. The one sync for the first drive and first for the second drive re-sync the original volume. The second after the second drive re-syncs the additional space.
- User2024Feb 14, 2024Aspirant
cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid1 sda3[3] sdb3[2]
971910784 blocks super 1.2 [2/2] [UU]md1 : active raid1 sdb2[0] sda2[1]
523264 blocks super 1.2 [2/2] [UU]md0 : active raid1 sda1[3] sdb1[2]
4190208 blocks super 1.2 [2/2] [UU]lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 3.7T 0 disk
├─sda1 8:1 0 4G 0 part
│ └─md0 9:0 0 4G 0 raid1 /
├─sda2 8:2 0 512M 0 part
│ └─md1 9:1 0 511M 0 raid1 [SWAP]
└─sda3 8:3 0 3.6T 0 part
└─md127 9:127 0 926.9G 0 raid1 /data
sdb 8:16 0 3.7T 0 disk
├─sdb1 8:17 0 4G 0 part
│ └─md0 9:0 0 4G 0 raid1 /
├─sdb2 8:18 0 512M 0 part
│ └─md1 9:1 0 511M 0 raid1 [SWAP]
└─sdb3 8:19 0 927G 0 part
└─md127 9:127 0 926.9G 0 raid1 /data
mtdblock0 31:0 0 1.5M 1 disk
mtdblock1 31:1 0 512K 1 disk
mtdblock2 31:2 0 6M 1 disk
mtdblock3 31:3 0 4M 1 disk
mtdblock4 31:4 0 116M 1 disk- SandsharkFeb 14, 2024Sensei - Experienced User
User2024 wrote:sda 8:0 0 3.7T 0 disk
└─sda3 8:3 0 3.6T 0 partThat's bad. For some reason, the NAS created a 3.6TB partition on sda where it should have created a 927GB one like is on sdb. sda is normally drive 1 and sbd drive 2, but you'll need to check that. On the System/Performance page of the GUI, hover over the green dot for Drive 1 and Drive 2 and confirm that's the case.
The only way I can see around this is to remove sda (most likely Drive 1), zero it out with a PC (all you really need to do is remove all partitions), and then re-insert it. Note that you should do the removal and re-insertion with power on.
I recommend you insure your backup is up to date before you do so.
After you do that, while the re-sync is still happening, do the lsblk again and verify sda3 (which may be sdc3 at that point) is now 927G, like sdb3. If it is, then when that first sync completes, the NAS should create a 4th partition on both drives to form another RAID (which will have to sync) and then concatenate that RAID into your /data volume.
If it again creates a 3.6TB partition, I'm stumped as to why.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!