daniel.boone

Started Parity 2 upgrade/rebuild is underway. Its taken a bit of time to juggle data around but its done. Once this completes I'll have dual parity of the same size. I had a mismatch previously which kept me from going beyond a certain size.

@trurl, Its exactly why I had to upgrade the 2nd parity disk. Parity build takes a long time so I anticipate the last of the current disk upgrades to happen next week. I've done so many disks swaps at this point that process doesn't worry me.

Quick recap..
Problem was dual parity drives of different sizes. Latest upgrade identified 2 xfs v4 disks. I was planning to fix my parity but the xfs disk support issue added a wrinkle I had not previously dealt with. I wasn't sure which approach was best for uptime while minimizing the disk wear. I anticipated multiple parity builds during this. I could have not been more wrong.

My solution..
I started by upgrading an array disk, non v4, to make room. Moved data off one of the v4 disk, reformatted, repeated process for for the 2nd xfs v4 disk. I was pleasantly surprised that formatting was quick and did not impact the parity. Once dust settled I proceeded to upgrade my smaller parity disk. That leaves one disk to upgrade after parity is recreated. Process took time but my array has been running the entire time minus the reboots/shutdowns I had to do during the disk upgrade process. Wish you all well. Thanks for reading. Consider this one done..

Appreciate the help, figured out webgui could be started with this command '/etc/rc.d/rc.nginx reload'. It came back with 'Nginx is not running' so I ran '/etc/rc.d/rc.nginx start'. Daemon started without issue. With that I got the webgui back and was able to correct the configuration. Rebuild is running once again. 
 
Thanks again, post marked solved.