This is your disk assignments from the original diagnostics you posted

Dec  8 11:08:21 WenteServer kernel: md: import disk0: (sde) MB2000GCWDA_Z1X2VG38 size: 1953514552 
Dec  8 11:08:21 WenteServer kernel: mdcmd (2): import 1 sdf 64 1953514552 0 MB2000GCWDA_S1X0F98D
Dec  8 11:08:21 WenteServer kernel: md: import disk1: (sdf) MB2000GCWDA_S1X0F98D size: 1953514552 
Dec  8 11:08:21 WenteServer kernel: mdcmd (3): import 2 sdd 64 1953514552 0 ST2000VM003-1CT164_W1H1ABSL
Dec  8 11:08:21 WenteServer kernel: md: import disk2: (sdd) ST2000VM003-1CT164_W1H1ABSL size: 1953514552 

This is your disk assignments on the last set of diagnostics

Dec  8 13:17:15 WenteServer kernel: mdcmd (1): import 0 sdd 64 1953514552 0 ST2000VM003-1CT164_W1H1ABSL
Dec  8 13:17:15 WenteServer kernel: md: import disk0: (sdd) ST2000VM003-1CT164_W1H1ABSL size: 1953514552 
Dec  8 13:17:15 WenteServer kernel: mdcmd (2): import 1 sde 64 1953514552 0 MB2000GCWDA_Z1X2VG38
Dec  8 13:17:15 WenteServer kernel: md: import disk1: (sde) MB2000GCWDA_Z1X2VG38 size: 1953514552 
Dec  8 13:17:15 WenteServer kernel: mdcmd (3): import 2 sdf 64 1953514552 0 MB2000GCWDA_S1X0F98D
Dec  8 13:17:15 WenteServer kernel: md: import disk2: (sdf) MB2000GCWDA_S1X0F98D size: 1953514552 

The important thing to take away here is that after

 

21 minutes ago, jwente said:

I created a new config

You assigned the drives incorrectly, and swapped around your original parity drive with the data drives.

 

This resulted in the "new" disk1 being unmountable and the parity rebuild (which your screenshot shows at the bottom as being in progress) trashing the data on what should have been disk1 (now the parity).

 

If the data that is now trashed was irreplaceable, then maybe something like UFS explorer would be able to recover it (if you immediately stop any parity rebuild from happening to prevent further corruption)  If it's replaceable, then just go ahead, format the drive, make a big note somewhere about the drive assignments so that this doesn't happen again.

(or, take a shot and assign the disks as per the original diagnostics and see what happens - another New Config will be required)

I am going to attempt to create a new config and assign the disk as they were originally. Not sure what to do after assigning the disk into the original order and starting the array. Thanks everyone for all the help. Sorry for being a noob. 

No need to apologize! We were all noobs at one point! In the future though, try to include all relevant info up front as it would have dramatically reduced the time it took to figure out what happened and how to get you back on track.

Sent from my Pixel 3 XL using Tapatalk

Assuming that after you reassign everything correctly, and the disk still comes up as unmountable then instead of hitting format, try running the File system checks https://wiki.unraid.net/Check_Disk_Filesystems against it.  *IF* it even runs, there will definitely be at least some data loss but maybe it won't be much.

1 hour ago, jonp said:

No need to apologize! We were all noobs at one point! In the future though, try to include all relevant info up front as it would have dramatically reduced the time it took to figure out what happened and how to get you back on track.

In future, if you aren't absolutely sure what to do, come to the forum before doing anything at all and wait for advice.

 

Probably a good chance you won't be able to recover all your data (if any), and the resulting lost+found files you get from filesystem repair can be difficult to work with since often the folders and filenames are lost.

 

It is probably simpler to just get your data from your backups.