JorgeB

Both NVMe devices are bound to vfio-pci, you need to unbind them.

Diags posted only show a problem with the docker image, it should be recreated, they don't have the ATA error on the second post.

Parity2 didn't finish synching, and both parity and disk2 are disable, so no way for Unraid to emulate disk2, disk2 look fine so doing a new config should fix it, also if it happens again don't forget to save diags before rebooting or we can't see what happened.

Multiple drive issues usually suggest a connection or power problem, check those first.

https://wiki.unraid.net/Upgrading_to_UnRAID_v6

Both good options.

Cache filesystem is corrupt, best bet is to backup and re-format, some data recovery options here if needed.

There's Midnight Commander (mc in the console).

Try rebooting.

Copy super.dat from the config folder.

Cache pool is corrupt and needs to be re-formatted, before it was showing checksum errors (data corruption), that suggests a hardware problem, usually RAM related, and since you're running the RAM above the max supported speed it's the most likely culprit.

Just re-assign them all and start the array, there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device.

You need to run a filesystem check, but if it's happening on multiple drives without an apparent reason it suggests a hardware problem, start by running memtest.

Those old PCI-X controllers have known issues with some newer devices, use another controller for the SSD if possible.

Not a network guy but there's something misconfigured: Nov 7 20:02:53 media-1 kernel: br0: received packet on bond0 with own address as source address (addr:d4:ae:52:7d:0f:65, vlan:0 ) Also a network related crash after that.

If it happens again setup the syslog server and then post that log, but you need update to latest Unraid first..

Power down, check/swap connections and power back up, if the drive is still missing it's likely dead, if not check SMART.

Nothing out of the ordinary on the logs, most likely a hardware issue, you can try running in safe more without any docker and VMs, if it still crash like that it pretty much confirms it's a hardware problem.

Best (and only option) is to run reiserfsck.

Shfs crashed during the mover, can't say what causing the crash though: Nov 14 03:40:01 Tower kernel: shfs[10471]: segfault at 0 ip 0000000000403bd6 sp 000014e19166d930 error 4 in shfs[403000+c000] Nov 14 03:40:01 Tower kernel: Code: 89 7d f8 48 89 75 f0 eb 1d 48 8b 55 f0 48 8d 42 01 48 89 45 f0 48 8b 45 f8 48 8d 48 01 48 89 4d f8 0f b6 12 88 10 48 8b 45 f0 <0f> b6 00 84 c0 74 0b 48 8b 45 f0 0f b6 00 3c 2f 75 cd 48 8b 45 f8 Nov 14 03:40:02 Tower crond[1676]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null You thing you can do is to avoid having docker manipulating files (like unpacking or moving) when the mover runs.

There's a btrfs crash, can't see if it's comming from the docker image or the pool itself, you can try re-formatting the pool and re-create the docker image, that should fix it.

They are using this controller: 06:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02) Subsystem: ASRock Incorporation Motherboard [1849:0612] Kernel driver in use: ahci Kernel modules: ahci Try this one instead: 01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller [1022:43b6] (rev 02) Subsystem: ASMedia Technology Inc. Device [1b21:1062] Kernel driver in use: ahci Kernel modules: ahci

Parity is not a backup, for 6 data drives single parity is enough for most cases, though a second parity disk is a small price to pay for the added redundancy, but you still need to have backups of anything irreplaceable.

Yes. Array is saved when you press the start button. Don't check. parity won't be valid with a missing disk, it will be synced after array start. Yes, after it's synced. Yes, but I would run another check to confirm.

Probably yes. If it's not parity it can be one of the data disks, but if you just do a standard rebuild it will likely corrupt data, unless by luck it is a disk and it's the first one you pick, so I would make a new array without one of the data disks and test, if no more issues it was that disk, if still errors repeat the process without a different data disk until hopefully you find the culprit.