JorgeB

https://docs.unraid.net/unraid-os/manual/changing-the-flash-device#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments

That's normal until parity is synched.

If the server was configured to static IP delete/rename /config/network.cfg on the flash drive and reboot, it will return to default DHCP.

Try upgrading to v6.12 since it includes newer xfsprogs and try again, if it still fails post new diags after running xfs_repair.

All you disks are SMR, SMR disks tend to downgrade write performance after some GBs written, some models are worse than others.

Aug  8 00:07:53 DeKluis kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Aug  8 00:07:53 DeKluis kernel: ? _raw_spin_unlock+0x14/0x29 Aug  8 00:07:53 DeKluis kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]  
Wwitching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

For a single error I wouldn't do anything, if it keeps happening replace the SATA cable.

It should mount now, if it does look for a lost+found folder.

What was the device you used? If not the below try again:
 
btrfs rescue zero-log /dev/mapper/sdc1  
Then restart array

You can use the UD plugin to mount the existing data SSDs and copy the data to the array (assuming they are using a supported filesystem).

There was an issue with previous v6.12 releases that could cause that, as long as the next one is clean nothing you need to do.

Aug 13 13:37:42 PlexServer kernel: md: disk1 write error, sector=48934576 ... Aug 13 13:41:12 PlexServer kernel: md: disk0 read error, sector=2170387704  
There are errors with multiple apparently heathy disks, suggesting a power/connection problem, see if these two disks share something in common, like a power splitter or miniSAS cable.

Parity dropped offline and reconnected multiple times, this is usually a power/connection problem, for the MX500 this may help.

You can also do this:
https://forums.unraid.net/topic/143234-basic-too-many-attached-devices-to-activate/?do=findComment&comment=1292305
 

Aug 11 10:49:32 GALAXY kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Aug 11 10:49:32 GALAXY kernel: ? _raw_spin_unlock+0x14/0x29 Aug 11 10:49:32 GALAXY kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]  
Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

If stopping the array and refreshing the GUI doesn't work you will need to reboot.

It's failing to delete the missing device because sdi is failing, you will need to copy anything you can manually then create the new pool with the larger devices and restore the data.

Replace only the bz* files in the flash drive from the download zip.

Stock Unraid should never suspend.
 
See here about this, but this only affects v6.12.x:
https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues

Looks more like a power/connection problem, check/replace cables for disk6 and try again, also some issues with parity, so replace those also.

In the near future:
https://forums.unraid.net/topic/131857-soon™️-612-series/page/3/#comment-1213901
 

For now it can be done manually, v6.13 is expected to have GUI support for these:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=1256329
 

Your getting an unclean shutdown, start by adding 60 secs to the default timeout (Settings -> Disk Settings), if it doesn't help time how long it takes for the array to stop.

If possible try mapping the container to disk paths, or use exclusive shares.

Try connecting the monitor to the iGPU motherboard output, or blacklist the iGPU driver:
https://docs.unraid.net/unraid-os/release-notes/6.10.0#linux-kernel