So I have been looking around the forum and can't find info on what I want to do.

 

I have 3 x 4TB drives.  None are failing. 

I need more storage so want to add an 8TB drive

I know the parity needs to be the largest so my thought was to make the new 8TB the parity and then the current 4TB parity a storage drive and then that gives me the option of adding 8TB drives as storage straight up in the future.

 

I have seen this wiki: http://lime-technology.com/wiki/index.php?title=UnRAID_Manual#Replace_a_failed_disk

 

The wiki looks to be specifically for a failed drive though.  Is this the same way I should do add the new larger parity drive in my case, not sure since it isn't failing?

https://lime-technology.com/wiki/index.php/The_parity_swap_procedure

Perfect.  Thanks!

Note that you could avoid the parity-swap procedure by doing this in two stages:

• Change the current 4TB disk to the new 8TB one and let unRAID rebuild it by reading all the data disks
  
• Once the 8TB drive is rebuild as the parity disks, simply assign the old 4TB parity disks as an additional data disk.
  

This would take longer, but many people feel more in control if they make only one change at a time.

If I read the OP correctly, there isn't going to be any data disk replacement, so parity-swap isn't appropriate.

 

And if you are just going to add the old parity as a new data disk, then you might as well  add it before resyncing the new parity.

 

So you could just New Config, assign new parity, assign all existing data drives, assign old parity as new data.

 

Then starting the array should begin parity build as well as format the old parity as a new data disk.

 

If you add the new data disk (old parity) after the resync then you would have to clear it, but if you add it before then it won't matter what is already on it since it will be formatted, and the new parity will be synced to include whatever other bits are already there (and not really part of the formatted filesystem).

If I read the OP correctly, there isn't going to be any data disk replacement, so parity-swap isn't appropriate.

 

I think you're right, misread.