JorgeB

Yes, but as mentioned you need to do a new config (Tools - New Config)

Floor for the TV share s set to about 1TB, you can lower that.

Unassign both pool devices, start array, stop array, this will reset the pool config, re-assign both pool devices, start array, existing pool should be normally imported, but if it doesn't mount post the diagnostics.

The NVMe device is bound to vfio-pci, unbind it, and also check that Asmedia controller, in case it's also bound by mistake:
 
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]     Subsystem: Samsung Electronics Co Ltd SSD 970 EVO/PRO [144d:a801]     Kernel driver in use: vfio-pci     Kernel modules: nvme 03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller [1b21:0612] (rev 02)     Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:1060]     Kernel driver in use: vfio-pci     Kernel modules: ahci  

It should use the lower starting sector if you manually create the partition first, to do that, unassing parity, type:
 
sgdisk -o -a 8 -n 1:32K:0 /dev/sdX  
Replace X with correct letter, reassign the device as parity and see if it's now accepted.

SMART looks OK, since the emulated disk is mounting, and assuming contents look correct you can rebuild on top, but recommend replacing cables before doing it, to rule that out:
 
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Jun 21 19:30:10 RR-Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Jun 21 19:30:10 RR-Tower kernel: SQUASHFS error: Failed to read block 0x256f0a4: -5 Jun 21 19:30:10 RR-Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Jun 21 19:30:10 RR-Tower kernel: SQUASHFS error: Failed to read block 0x256f0a4: -5 Jun 21 19:30:10 RR-Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Jun 21 19:30:10 RR-Tower kernel: SQUASHFS error: Failed to read block 0x256f0a4: -5  
These indicate mean a flash drive problem, you can try recreating it first, if the issues remain replace it.

It's not, in fact there's not even an attempt to start it, same for docker, suggesting this is a config issue, I would recommend recreating the flash drive from scratch.
 
How did you create the fresh 7.0.0-beta install since there's no zip?

If it's an existing Unraid pool you can easily import it, just add a new pool, assign all devices from that pool, and start the array.

Depends on the amount of installed containers and the size of the image, but as long as it doesn't keep growing it's not a problem for now.

Try booting in safe mode to rule out any plugin issues.

Constant call traces, start by running memtest, if nothing is found, and because memtest is only definitive if it finds errors, try running the server with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM, if issues persist, another thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

For that you need to configure the 10GbE NIC using a different subnet:
 
 

I'm not seeing any i/o errors in the diags, there is a filesystem issue with disk2, check filesystem on that disk, run it without -n.

Check filesystem on that disk, run it without -n

You can upgrade the pool one device at a time, it will remain online during the process.
 
 
This is normal if you are using the default high water allocation method, once disk1 is over half full it will start writing to disk2.

If you still see the freeze issue and it started happening after the hardware change, it suggests the problem may be hardware related, but you can try redoing the flash drive, backup the current one first and then redo it and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if the freeze issue is gone you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit, if it's still there it's most likely hardware related.

Make sure you reset the stats and keep monitoring for more errors, if there are more, there's still an issue:
 
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
 
 

Try reconnecting the device, or using a different M.2 slot to see if it comes back.

Yes, but only if you do the parity sync in maintenance mode.

Try using a different flash drive with a stock install, no key needed, that will confirm if it's a board problem or not.

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Ig this is not an option it may be linked to a different account, you should contact support with all the details.

You are using USB disks, besides not being generally recommended for other reasons, some USB bridges have issues with spin down, recommend using SATA.

Uninstall the plugin and enable turbo write manually in Disk Settings.
 
Do this test again with large files but using Windows explorer, and post a screenshot of the transfer speed graph.
 
Disk to disk transfer will always be slow, and turbo write cannot help for this.