TerraMaster Forum

I have the F2-221 2-bay NAS
2x4TB RAID 1

I want to upgrade the drives to a larger size without losing anything. (2x6TB or 2x8TB)

How is the best way to do this without losing any data and system configuration?
Can I just unplug one of the 4TB drives and replace it with larger drive? Will it rebuild automatically?
If so, when it is finished then I replace the other 4TB so both drives will be the new larger size and wait for rebuild?

I'm using PLEX and I don't want to have to through setting that up again from scratch as I have a lot of custom media entries.

Thanks.

You can pull out one 4TB drive and insert the bigger drive at power on state, then click Edit at Storage pool and choose Repair the RAID. The rebuilding will begin. Do not turn off the device before the rebuilding completed.
You can repeat the process to replace the second 4TB drive.

Thank you.

Will the larger size be available after both drives have finished rebuild, or is there any further step?

I found some older threads that refer to problems with the newly rebuilt RAID not being recognized as bigger.

It should be expanded automatically after the rebuilding is finished.
If any abnormalities, we can help you with remote session.

TMSupport wrote: ↑16 Jul 2021, 11:11 It should be expanded automatically after the rebuilding is finished.
If any abnormalities, we can help you with remote session.

hi i have f2-220

i upragded 2x4tb to 2x6tb drives

i followed the instructions
1- replace one drive when system is online
2- start repair
3- repair finished replace other drive
4- repair finished
5- system shows 2x6tb good condition, but not volume size, it shows original volume size and it didnt increase automatically!
6- there is no option to increase (the volume section has minor adjustment to increase about 1tb extra but it doesnt work really!

see pics

Hi, It should be that some processes have not been stopped during the expansion. You can solve this problem by the following method: viewtopic.php?f=75&t=2342

[root@Terra ~]# mdadm --grow /dev/md0 --size=max
mdadm: component size of /dev/md0 unchanged at 5857097728K
[root@Terra ~]# umount /mnt/md0
umount: /mnt/md0: target is busy.
[root@Terra ~]# vgchange -an vg0
Volume group "vg0" not found


umount isnt working? coz next commands error

is it possible to do a remote session? thank you

What can you see by typing "vgs"?
[root@Terra ~]# vgs

TMRyan wrote: ↑30 Aug 2021, 21:57 What can you see by typing "vgs"?
[root@Terra ~]# vgs

[root@Terra ~]# vgs
[root@Terra ~]#