In the beginning, I precleared an 8tb drive that I was replacing in my main server, so that I could put it in my secondary server, to replace a 2tb drive I was getting errors on. After preclearing was done I turned the secondary server off and replaced the drive, 2tb for 8tb. I changed slot 1 to the new drive and started the array. Then it asked to format the drive, and this is where I figured I did something wrong. I think I said format during parity rebuild, then I got spooked, so I stopped and tried parity rebuild again without formatting, which was also probably wrong. The rebuild finished and the "new" drive was still listed as unformated.
After that, I have put the old 2tb drive back in slot 1, and tried a new configuration, nothing had been written to the array but I was going to resync parity from the data drives just in case, better than losing 2tb. When trying that, it is showing disk 9 as unformated/no fs, disk 9 is 8tb, so if I had to choose, I'd lose 2tb. I double checked that the drive I removed was the "new" previously precleared drive from my main server. The serial from slot 8 is a different brand and the one I removed matches the serial from a spreadsheet I keep for my main array for locating drives.
Hopefully I'm still in a place where I can keep all my data, but after stumbling around I could really use some help on how to do that, please. Diagnostics are attached, for the boot it was generated from, I have tried new config and am getting that drive 9 is not formatted.
Extra stuff that might not matter: I think some of my confusion comes from the secondary server being encrypted, which my main one isn't, maybe replacing drives is different in this case. I was going to move SAS cards around, but the 16e card I bought for my new server started smoking when I started it up, so I couldn't use one of the 8i cards from that that I was going to put in my secondary server, but moving things around seems to have at least temporarily eased the errors.
tower-diagnostics-20191007-1806.zip