TRAID and expanding drives
TRAID and expanding drives
I have a 5 bay NAS right now, with 5 4TB drives in TRAID. Looks like TRAID is flexible, if I buy a bigger drive, say one every month to spread out cost, TRAID will adjust and expand, is that correct? So over the course of 6 months I could put replace one 4TB drive with an 8TB drive once a month and it will roll with it and expand? Is that right?
Re: TRAID and expanding drives
The first 8TB will not show any expansion of available space. This only occurs with the second and later. The expansion of the first drive is (essentially) expanding the parity drive in preparation for further expansion.
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
Re: TRAID and expanding drives
But after the second 8TB it should expand and not have to redo the raid with any driver that are larger? Is there anything that needs to be done or will TRAID just see it and run with it and auto expand the raid?
Re: TRAID and expanding drives
You will have to update the array from control panel. There are proper guides on here.
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
Re: TRAID and expanding drives
Hello,
Does TRAID automatically handle the parity expansion when the first larger drive is added, or is there a way to optimize this process for smoother upgrades?
Does TRAID automatically handle the parity expansion when the first larger drive is added, or is there a way to optimize this process for smoother upgrades?
I'm a software developer working on amazing technology.


