JorgeB

Both are bound to vfio-pci: 04:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] (rev 05) Subsystem: Broadcom / LSI 9207-8e SAS2.1 HBA [1000:3040] Kernel driver in use: vfio-pci Kernel modules: mpt3sas 0c:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS3224 PCI-Express Fusion-MPT SAS-3 [1000:00c4] (rev 01) Subsystem: Broadcom / LSI SAS3224 PCI-Express Fusion-MPT SAS-3 [1000:3190] Kernel driver in use: vfio-pci Kernel modules: mpt3sas You need to unbind them before use.

Check the passed-through devices, the SATA controller is not being passed through as far as I can see, but it is/was that would also explain your issue, when the VM was started Unraid would lose connection with all the disks on that controller, it's this device: 0b:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901]

You didn't reboot, or posted old diags.

Yep, that works.

That screen still shows disk errors, if you did reboot post new diags.

I don't get an error, when I click on "Readings" the tab highlights but keeps displaying the tab that was open before.

Problem with the onboard SATA controller, quite common with some Ryzen boards, BIOS update might help or use an add-on controller. You need to reboot to see actual array status, there might be a disabled disk.

Yep, it does that.

You're getting an IP address same as before but from a different subnet: now 192.168.72.151 before 10.246.13.163 That suggests some issue with the network config, try simplifying the connection as much as possible to star, i.e., connect the server directly to the router, no vlan, no pfsense, then see if you can't access it like that, by name or IP.

"Readings" page is not opening for me since updating to v6.10.0-rc4/5, it's happening with multiple servers, so I assume it's a plugin issue?

Please use the existing docker support thread:

This, you don't even need the same order, just start the array without any pool device assigned so the config is "forgotten", then re-assign the original members only, not the new one, start the array and Unraid will import the existing pool, then add new device.

Ignore the above, didn't notice bonding is enable.

Formatting is never a part of rebuilding a disk, there's a popup warning about that, you need to check filesystem instead.

Please post the diagnostics.

No link on eth0: Link detected: no There is a link on eth2 Link detected: yes Unraid requires a working eth0 for managing/GUI access, you can either swap the cable there or boot with the GUI option and use the interface rules to make eth2 eth0.

Also note that you can always read those disks outside the server by booting with an Unraid trial key on any PC and add the disk you want to read to the array (without parity).

Same thing, you just need to add "mapper" before the device: mkfs.xfs -m crc=1,finobt=1 -s size=4096 -f /dev/mapper/md# Where # is the disk number, note that the array needs to be started in maintenance mode, can't format a mounted filesystem. No need for either. No, after. Parity remains in sync.

Yes, and if it asks for -L use it.

Yes, sorry, missed that part, current encryption implementation requires re-formatting the device.

https://wiki.unraid.net/Manual/Storage_Management#Removing_disks_from_a_multi-device_pool or https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480418

Please post the diagnostics.

Drive encryption has been available for a long time, since v6.4 IIRC.

Apr 28 23:49:57 ROLFOHIVE kernel: ata5: SATA link down (SStatus 0 SControl 300) Apr 28 23:49:57 ROLFOHIVE kernel: ata5.00: link offline, clearing class 1 to NONE Apr 28 23:49:57 ROLFOHIVE kernel: ata5: hard resetting link Apr 28 23:50:00 ROLFOHIVE kernel: ata5: SATA link down (SStatus 0 SControl 300) Apr 28 23:50:00 ROLFOHIVE kernel: ata5.00: link offline, clearing class 1 to NONE Apr 28 23:50:00 ROLFOHIVE kernel: ata5.00: disabled Cache device dropped offline, this is usually a power/connection problem, check/replace cables. Also a good idea to run memtest since some corruption was being detected.

IIRC LSI doesn't work with just a x1 link, spin down works normally with the Asmedia.