I initiated a parity swap yesterday following this procedure: https://docs.unraid.net/legacy/FAQ/parity-swap-procedure/
I checked on the progress this morning and it was at 96% for the copy procedure, so I expected things to be done shortly there after and initiate the disk rebuild.
I just checked progress in the array again, and the array operation page is now back to where I started, saying I can initiate the copy again. According to the documentation, that COPY button should be a START button to start the array and initialize the data rebuild.
What's even more confusing, checking my server notifications, about the time I expected the copy function to complete, I have a notification saying the following:
"Disk 4, is being reconstructed and is available for normal operation"
Disk 4 is the old parity drive that is being turned into a data disk.
I can't see any indication that disk 4 is actually being reconstructed though, I have no ability to start the array, and the array devices page shows the new parity drive and new disk as new devices.
Did this somehow not complete successfully and I need to run the copy again? I don't see any indication of any failures and the notification message this morning makes me think it completed successfully, but now I don't know what state the array is in. I don't see anything in the logs out of the ordinary right now, the disks are spun down.
Log says the copy completed successfully, but below says slot 0 is wrong import.
Sep 24 12:29:29 Tower emhttpd: copy: disk4 to disk0 completed
Sep 24 12:29:55 Tower kernel: md: unRAID driver removed
Sep 24 12:29:55 Tower emhttpd: shcmd (39876): /sbin/modprobe md-mod super=/boot/config/super.dat
Sep 24 12:29:55 Tower kernel: md: unRAID driver 2.9.27 installed
Sep 24 12:29:55 Tower kernel: mdcmd (1): import 0 sdf 64 13672382412 0 WDC_WUH721414ALE6L1_Y6G3NGSC
Sep 24 12:29:55 Tower kernel: md: import disk0: (sdf) WDC_WUH721414ALE6L1_Y6G3NGSC size: 13672382412
Sep 24 12:29:55 Tower kernel: md: import_slot: 0 wrong
Sep 24 12:29:55 Tower kernel: mdcmd (2): import 1 sdd 64 7814026532 0 WDC_WD80EDAZ-11TA3A0_VGGYLR9G
Sep 24 12:29:55 Tower kernel: md: import disk1: (sdd) WDC_WD80EDAZ-11TA3A0_VGGYLR9G size: 7814026532
Sep 24 12:29:55 Tower kernel: mdcmd (3): import 2 sdc 64 7814026532 0 WDC_WD80EFAX-68LHPN0_7SGLHX6C
Sep 24 12:29:55 Tower kernel: md: import disk2: (sdc) WDC_WD80EFAX-68LHPN0_7SGLHX6C size: 7814026532
Sep 24 12:29:55 Tower kernel: mdcmd (4): import 3 sdh 64 3907018532 0 ST4000DM000-1F2168_Z304H4Z2
Sep 24 12:29:55 Tower kernel: md: import disk3: (sdh) ST4000DM000-1F2168_Z304H4Z2 size: 3907018532
Sep 24 12:30:05 Tower kernel: mdcmd (5): import 4 sdg 64 7814026532 0 WDC_WD80EFAX-68LHPN0_7SGLWD9C
Sep 24 12:30:05 Tower kernel: md: import disk4: (sdg) WDC_WD80EFAX-68LHPN0_7SGLWD9C size: 7814026532
Sep 24 12:30:05 Tower kernel: md: import_slot: 4 replaced
Also probably unrelated, but if you hover over the orange triangle on the array operation page, it says "Started, array unprotected" but on the dashboard I see all disks as offline.
Looking for next steps to help troubleshoot.
Array operation: https://imgur.com/id9jLUc
Array disks: https://imgur.com/hukGTbI