How to grow the raid array size?

Hello

One of my 2x2TB drive failed. I run the device on raid (mirror). I took the opportunity and ended up replacing the HDs on my MBWE II (WhiteLight) with bigger HDs. It synced all the data already on the new HDs. It also recognize the new HD sizes (5TB each). Now, the problem is that it shows both drives in the raid array however it displays the old size (1,87 TB) instead of the new one (5TB)

What should I do ti fix this?

Thanks
Gilson

you would have to enable SSH on your unit. Then read carefully this from these websites to resize (grow/expand) your RAID 1 volume.

https://raid.wiki.kernel.org/index.php/Growing

Just to make sure I got this right. Since the GUI interface shows 2 drives of 5TB each the only thing I need to do is to resize the raid 1, correct?

It looks like I just need to run the following commands through ssh as root:

mdadm --grow /dev/md2 --size=max

e2fsck -f /dev/md2

resize2fs /dev/md2

e2fsck -f /dev/md2

Please confirm. Thanks

One last question: I have already synced all the data. I will not have lost my data after running those commands, will I? Thanks

The best thing to do, backup your data. Nothing is guarantee. You should not lose your data. But to make sure is to backup your data.

Awesome

I first ran the command:
~ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1]
md2 : active raid1 sda4[2] sdb4[3]
1950277343 blocks super 1.2 [2/2] [UU]

md1 : active raid1 sdb2[1] sda2[0]
256896 blocks [2/2] [UU]

md3 : active raid1 sdb3[1] sda3[0]
987904 blocks [2/2] [UU]

md0 : active raid1 sdb1[1] sda1[0]
1959872 blocks [2/2] [UU]

unused devices:

So, the next commands I should run are:
mdadm --grow /dev/md2 --size=max
e2fsck -f /dev/md2
resize2fs /dev/md2
e2fsck -f /dev/md2

Would you confirm?

Thanks

I also ran the following command, just to make sure you can help me with the right commands:
~ # fdisk -l
You must set cylinders.
You can do this from the extra functions menu.

Disk /dev/sda: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 1 0+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(267349, 89, 4)
You must set cylinders.
You can do this from the extra functions menu.

Disk /dev/sdb: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 1 0+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(267349, 89, 4)

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 121602 976762583 7 HPFS/NTFS

I ran the commands and this is what I got:

mdadm: component size of /dev/md2 has been set to 585566047K
~ # e2fsck -f /dev/md2
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/md2 is mounted.
Couldn’t find ext2 superblock, trying backup blocks…
e2fsck: while trying to open /dev/md2

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

e2fsck:
~ # resize2fs /dev/md2
resize2fs 1.41.4 (27-Jan-2009)
ext2fs_check_mount_point: Input/output error while determining whether /dev/md2 is mounted.
~ #
~ # e2fsck -f /dev/md2
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/md2 is mounted.
Couldn’t find ext2 superblock, trying backup blocks…
e2fsck: while trying to open /dev/md2

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

Now the divide shows a error in the raid. The status is failed to mount