JorgeB

Already posted above: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

Definitely, I didn't notice you had dual parity, that's the way to go.

Call trace on the log is NIC related, and usually not a problem.

The you'd need to get another disk of the same size since parity was also 5TB, alternatively you could clone the old parity to the new 6TB disk with dd then use that one for disk1.

It might be possible to recover, if the array disks are using xfs (or reiser), but you need a disk of the same size of the missing disk to configure the array, disk doesn't need to be healthy but it needs to be detected.

LSI 9300-8i which uses the same chip (SAS3008) works fine, so it would be something specif to this controller/model.

Yes, you can mount without starting the array with the UD plugin, or in any other Linux distro, either case you just mount one of the devices and the other one will mount together.

Like mentioned you need to delete BTRS.key from the flash drive, that's a pirated key and needs to be removed, after that reboot, if you still have issues please post the diagnostics: Tools -> Diagnostics

See if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

This SATA controller is being passed through to the Win10 VM: 49:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) DeviceName: X570/590 SATA1 Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci So when the VM starts Unraid loses access to it and all the connected disks.

We need more info, is this a new assignment and did you attempt to format? If yes and if it failed please post diags. If you prefer I can also move this to the Chinese subforum.

Do you have a backup of the flash drive? It doesn't, there's a GUI option to manually backup, there's also the myservers plugin that auto backups to the cloud.

Number of reads in the GUI is mostly meaningless, it can vary widely from the dist to disk with the same number of reads, e.g., right after a parity check, unless you're seeing actual unexplained disk activity you can ignore that.

That is not the persistent mirrored syslog.

Data on disk4 can look OK but should still be mostly corrupt, unless the previous diags don't show the old story.

Now it's working correctly, if it stops working I'd need to see the diags showing the problem, before rebooting.

That's from the docker folder plugin, pleas use the existing support thread.

Disk3 dropped offline 1 minute after you started rebuilding disk4, so the rebuilt disk4 will be mostly corrupt, if system notifications are enable you'd be notified about the read errors, syslog cuts off due to log spam, if if you were rebuilding on top of the old disk, all data on that disk will be gone, and likely there will be be filesystem corruption preventing user shares from working, reboot and post new diags after array start.

Either way is plug and play.

Yes, now is OK, other one will need to be formatted before use.

2nd device wasn't added to the pool, try again, stop array, unassign sdi, start array, stop array, re-assign sdi, start array and post new diags.

There's a RAM problem: Jul 14 05:53:52 Tower kernel: mce: [Hardware Error]: Machine check events logged Jul 14 05:53:52 Tower kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR Jul 14 05:53:52 Tower kernel: EDAC sbridge MC0: CPU 0: Machine Check Event: 0 Bank 7: 8c00004000010092 Jul 14 05:53:52 Tower kernel: EDAC sbridge MC0: TSC 26fa9a273d20a Jul 14 05:53:52 Tower kernel: EDAC sbridge MC0: ADDR 11da50f40 Jul 14 05:53:52 Tower kernel: EDAC sbridge MC0: MISC 4405c1a86 Jul 14 05:53:52 Tower kernel: EDAC sbridge MC0: PROCESSOR 0:306e4 TIME 1626263632 SOCKET 0 APIC 2 Check the board's system/ipmi event log, it should have more info on the affected DIMM, then remove or replace and see if the errors go away.

Balanced finished now, just didn't delete the missing device since it wasn't done automatically at array start, type this: btrfs device delete missing /mnt/cache Then post new diags to confirm it's done.

Don't see any issues before the checksum error, but if it keeps getting corrupt you might have a hardware issue, if it's an option try recreating the image on a different device.

Please post the diagnostics: Tools -> Diagnostics