JorgeB

Try installing the Nvidia driver plugin for the GUI mode to work, but note that you can access the GUI from another computer.

Known issue, v6.12.10 should be out soon with a fix.

You need to re-enable the disks first:
 
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
 
P.S. No need to do it in maintenance mode, or the array will be offline.
 
 

Check filesystem on the emulated disks 9 and 12, also post the complete diagnostics.

Those SSDs won't be able to maintain high sustained write speeds, also please note that trim is not supported for array devices, I would recommend creating a raidz zfs pool instead, it will perform much better, you can use an old flash drive to fulfill the current array device requirement.

failed to start daemon: write /var/lib/docker/volumes/metadata.db: no space left on device  
Try recreating the docker image:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Can you boot with a different flash drive with a stock install?

This looks more like a device problem, do you have other devices you could try width? Even a couple of non SMR HDDs would perform better than that.

Try deleting/renaming /config/vfio-pci.cfg on the flash drive.

You can use
blkdiscard /dev/sdX to do a full device trim, or
wipefs -a /dev/sdX just to delete the partitions

I don't see the S3 plugin installed, S3 sleep should not work on a stock install, do you remember changing anything to enable that? Also post new diags after a reboot, since they are incomplete.

If OK then convert the pool to raid1, once done you can remove the device and the pool will automatically be converted to single.

Nothing obvious in the logs, check to see if there's a write cache option in the BIOS, if yes set it to enabled, you can also run a test with the diskspeed docker to confirm disks are performing OK.

See if this helps:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

Did you confirm the disks are spinning up?

Diags confirm flash drive problems, you can first try to re-format it and/or using a different USB port, ideally USB 2.0, if the same replace it.

Unraid lost contact with multiple disks at the same time, suggesting a power/connection problem, you will need to reboot, by force if needed, that should get the disks back, and you can then check the damaged, possibly just one disabled disk.

Historical devices are from the UD plugin, and yes, you can delete them.

El disco parece estar fallando, puede ejecutar una prueba SMART extendida para confirmar, si falla debe reemplazarlo, el disco emulado se está montando, por lo que todos los datos deberían ser recuperables.

Use -L

The two logged parity checks have the same errors, at least the logged ones, reboot to clear the log, then run a correcting parity check, then a non correcting one, all without rebooting, if the second one finds new errors post new diags.

Update to v6.12.9 and you should see the correct device limit.

XFS is detecting metadata corruption:
 
Mar 27 14:09:02 Tower kernel: XFS (md1p1): Corruption warning: Metadata has LSN (1:23) ahead of current LSN (1:0). Please unmount and run xfs_repair (>= v4.3) to resolve. Mar 27 14:09:02 Tower kernel: XFS (md1p1): log mount/recovery failed: error -22  
Suggest trying with a different flash drive
 
 

Xfs can only be used in the array or single device pools, if you want the better performance that comes with striping disks, use a zfs pool instead.

Delete/rename /boot/config/network.cfg and reboot, that will revert the network settings to default DHCP, then post new diags after booting.