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
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.