JorgeB

Device is not part of the pool, despite of what the GUI shows, try this, stop array, unassign cache3, start array, stop array, re-assign cache3, start array, post new diags.

Auto parity check after an unclean shutdown is always non correcting.

Delete /config/vfio-pci.cfg on the flash drive.

This is usually the result of bad RAM, you're running Ryzen with overclocked RAM, it has been known to corrupt data even when the RAM is OK.

You can't direct replace to smaller devices. You can do that, when done the cache reset procedure is the same as the one posted in the link above. P.S.: metadata profile is DUP, you should change to RAID1.

Disk looks OK, most likely a power/connection problem, replace cables to rule those out and rebuild on top.

https://forums.unraid.net/topic/115767-solved-unraid-v692-upgrading-cache-pool-drive/?do=findComment&comment=1052576

Yes, it's in the link I posted above.

Then it looks like a xfs_repair issue and if that's the case not much we can do, please post new diags after array start (in normal mode).

Pool device replacement is broken on v6.9+ If you're comfortable using the console you can do it manually.

You need forward breakout cables, sometimes called SFF-8087 host to SATA target.

I if understood correctly you need 3 extra ports, if yes I would go with an Asmedia 1164.

It's normal with WD SMR disks before they were used, reads come from the controller, since it knows the disk is all zeros it doesn't read it, it's also pointless to do a pre-read, post-read will be normal.

These errors suggest device sdc dropped offline in the past, you should run a correcting scrub and make sure all errors were corrected, also see here for better pool monitoring.

Nope.

That can help, and they should be off if you don't need it, it's this issue:

Nope.

To expand, there would be some times when writes would go to both SSDs, others were it would go to one SSD and the HDD, it would alternate every new chunk, and when the HDD is used it would always be limited by the HDD speed.

Any vdisk that doesn't discard freed space will keep growing.

Yes. No.

You can do the parity swap, one of the first steps is to disable the disk you want to replace, since it's not yet disabled, after you do that you can remove that disk and connect the new parity.

There are still macvlan call traces, also the server is constantly running out of RAM.

In the first screenshot there's still plenty of space, but if the free space keeps getting lower without writing new files it's usually lack of discard on vdisks, see here for Windows VMs: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606

Disk dropped offline so there's no SMART report, check replace cables and post new diags.

SMART for parity is showing some issues, but current problem look more power/connection related, power down the server, check/replace cables on parity and then try this, but note that it will only work if parity is still valid: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk1 -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk -If the emulated disk mounts and contents look correct stop the array -Re-assign disk1 to rebuild and start array to begin. Keep old disk1 intact for now in case it's needed.