JorgeB

Everything looks good with the array, some ATA errors with the Samsung SSD, you might want to try and replace that SATA cable.

Pool is completely full and using dual data profiles, you should have a system notification about that, free up some space then rebalance the pool to the intended profile.

Note that a Mellanox NIC won't work as eth0 with v6.10.2, it's a known issue and should be fixed soon.

Yes, I suspected the libvirt issues were unrelated, but have no idea what those are about, hopefully someone else will.

There are at leat a couple of other users running this workstation with vt-d enabled and no issues so far, mostly HP servers have been affected, also if you ran any previous v6.10 release for some time without issues it should also be safe to now run v6.10.2 with vt-d enabled and the NIC unblacklisted.

Looks like it, do you really need to virtualize Unraid?

Please post the diagnostics during a write to the server with write mode set to "reconstruct write"

Unlikely that it would be a device problem, you can swap with the other one to confirm, if there's a different m.2/PCIe slot you can use it might also help.

Yes.

Jun 6 11:44:38 MtX-Unraid emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/Vault2 Do you know what Vault2 is? It doesn't exist in any array/pool device.

Are you sure? Toshiba drives can have the same serial ending, but there are differences in the middle, or just post the diagnostics.

Check that power supply idle control is correctly set, if yes or if it doesn't help enable the syslog server and post that after a crash.

No, it's done in VMware.

Difficult to say for now, see how it goes in the future.

Good, now start a check and post new diags after it freezes, I assume only the check freezes, not the server?

Unlikely that would cause the server to crash or become unresponsive.

You can't remove devices from zfs raidz pools, you'd need to backup and re-create the pool.

Link detected: no No link on your NIC, also update to latest stable, you're running a test release.

Good, running the controller in IDE with those AMD chipsets is known to cause issues.

You should post the diagnostics while on v6.10.2.

You are virtualizing Unraid, that's not supported, though it might work, but if you really want to do that see if you can pass-through the SATA controller to Unraid instead of using the virtal VMware controller.

Did you reboot first? Like mentioned it was read-only.

First thing you need to fix is cache being completely full, because of that the filesystem went read only, reboot and see if you can manually move/delete some data before it goes read-only again.

This disk apparently not used is spamming the log with constant errors: Jun 5 21:44:29 sobnology emhttpd: WDC_WD30EFRX-68EUZN0_WD-WCC4N1SVT0RH (sdl) 512 5860533168 Disconnect it then please post new diags after a re-start.

With a Microserver G8 used with vt-d enabled it's most likely related, unless there was an unclean shutdown, you though you weren't affected but possible were, though very lightly, unclear for now why some users see severe issues after a couple of minutes use while others only minor or even no issues after a few days, as long as vt-d is now disabled you shouldn't see any more issues. Note that it's unclear for now if the NIC is the source of the problem, it has been found in all affected models so far but it could be just a coincidence, in fact the last case I've found might indicate that the NIC is not the problem, the only thing I know for sure for now is that there's an issue with the kernel and vt-d, and it affects mostly HP servers, not for example HP workstations, at least not so far, but there's also one Lenovo server, so it's not just HP.