JorgeB

https://docs.unraid.net/unraid-os/manual/users/reset-password/

https://forums.unraid.net/topic/113037-docker-advanced-view-reflect-memory-limit/?do=findComment&comment=1029211
 
No ATA errors so far.

Try recreating the docker image:
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Known issue, fixed for beta.2, but it's only visual, it will still create a stripe or mirror if you apply that before formatting.

Errors continue, if you replaced both cables it could be a bad disk, you can swap cables with a different disk to make sure, see where the problem follows.

The Sandisk should be the first option here:

 
Then save setting and reboot
 
 

Syslog rotated, and is missing the start of the problem, type reboot in the CLI then post new diags after array start.

Looks like there were some lost writes, likely to the underlying device.
 
If the vdisk is OK, you should be able to use a new libvirt image, then create a VM with the same settings and point to the existing vdisk.
 
Recommend keeping a backup of that file for the future.

There are errors in most disks, so Unraid cannot emulated them, reboot and post new diags after array start.

Yes.

If it's a refurb I do at least an extended SMART test or precelar to confirm it's good.

Add both pool devices to the pool and start the array, it should import the existing pool.

Those SQUASHFS errors usually mean a flash drive problem.

Not really, that looks more related to the hardware you running, possibly some incompatibility with the kernel/KVM, I would recommend retesting once 7.0.0-beta is out, which should be very soon, that one will use a much more recent kernel.
 

Look for the existing support thread, click on the container and then support.

SMART looks fine, so most likely power/connection issue, avoid splitters, especially if they are splitting one plug to more than 2 disks.
 

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.