Which lead me to apply the firmware upgrade of my Iomeaga IX2-200 (from around 2012) to 3.1. I'd also somehow managed to 'break' the 2nd disk. I seem to have broken the second disk so the array is only showing /dev/sda, but even with one disk the resize should work shouldn't it?įollowing the advice from Micheal I tried the lvresize and xfs_grow but no difference.

Realtime =none extsz=4096 blocks=0, rtextents=0īut the array size is unchanged: mdadm -D /dev/md1 Log =internal bsize=4096 blocks=32768, version=2 Increasing the Size values for Ident 2 and 3 below: įollowing the first answer suggestion I ran: I spotted a couple of config files with volume sizes, so I edited these: VG UUID EA3tJR-nVdm-0Dcf-YtBE-t1Qj-peHc-Sh0zXeįilesystem Size Used Avail Use% Mounted on VG UUID FB2tzp-8Gr2-6Dlj-9Dck-Tyc4-Gxx5-HHIsBD Now put disks back into the IX2 and reboot. This enables me to extend the partition (type Microsoft basic data 0700). The IX2 does not have gdisk installed, so I remove the disks, connect them to a Linux server as USB drives and run gdisk: Several hours later we have 2 4Tb disk in the IX2, but with only 1.8Tb showing as available. The IX2 again starts mirroring disk2 to disk1. Replace the first disk with another 4Tb drive, and restart. The IX2 automatically starts to resync / mirror disk1 (2Tb) to the new 4Tb disk.Īfter several hours, we see the seconds disk as 1.8Tb.

Remove the 2nd disk from the IX2, and replaced it with a 4Tb disk. So far this is the process I have followed: I am trying to upgrade this to 4Tb disks. I have a Iomega IX2-200 which came with 2Tb (1.8Tb usable) space.

Storcenter ix2 larger drives