JorgeB

I don't know that model, complete diags would give more info.

That suggest an incompatibility problem with the board, not much you can probably do, try enabling/disabling opt ROM boot support (or similar option) in the BIOS, also try booting UEFI if booting CSM, or vice-versa, other than try a different model, board or NIC.

That's fine for 3rd gen with a full load, look for a bios update, unfortunately other than that don't have many suggestions, a future Unraid release with a newer kernel might also help.

Ryzen and Linux not the best choice, though it does work OK for some, there are NMIs logged, but no idea what is causing them, make sure RAM is not over the to max officially supported speed for your config, can't see that without the full diags.

It's still the parity check plugin pausing the check. Yes.

Set the filesystem to xfs and it should work, if not you can do it using the console: https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS

Diags are after rebooting and not much help, if it keeps happening try this and post that syslog after a crash.

Delete/rename network.cfg and network-rules.cfg (if it exists) and reboot.

Yeah, resilvering is what zfs uses when rebuilding/repairing a disk, why I assumed he meant rebuilding. I love astronomy, I wish I had better conditions in my home for that, I did get a telescope some years ago, but basically only looked at the moon and a couple of planets, still worth it seeing Jupiter's moons and Saturn's rings.

One thing I forgot to ask before, leave the HBA disconnected from the backplane, boot Unraid and post new diags, this way we can see if the HBA is able to initialize correctly if not connected to the backplane.

Format is done after the device is part of the array, so parity can be updated. Default Unraid xfs format is: mkfs.xfs -m crc=1,finobt=1 -f /dev/mdX where X is the disk #, since I don't use xfs for a long time not current on the options, but probably crc=0 would get rid of the extra space, google "mkfs.xfs man page" for the options. Format will likely not work on a mounted filesystem, you'd need to manually unmount, probably easier for you to do this: -stop array -click on the disk you want to format and change it to a different filesystem -start array, that disk won't mount -type the correct mkfs command for the disk on the console (all data on that disk will be deleted) -stop array, change its fs back to xfs/auto -start array, if you used the correct format options it will now use less space.

Issue appears to start after some Macvlan call traces, those are usually related to dockers with a custom IP address, and in some some might end up locking up the server, more info here:

It's not using all the RAM, large part is cached, look here. As for the CPU usage, looks normal on the diags, if it wasn't at 100% then try to grab new ones when the CPU is at 100%.

It doesn't need to be, but it's better if it is.

Not really Your are mentioning both Windows and DOS, you just use one or another, try DOS first since if it works it's faster (assuming you know the basics of DOS, like changing dir etc, if not this will be difficult to explain for me, you might need to use google: Create a DOS flash drive with rufus unzip the correct firmware package to the flash drive leave only the HBA you're updating this time, remove the other one navigate to correct folder where you extracted the firmware and the sas2flsh utility, then type sas2flsh -o -f 2118it.bin replace 2118it.bin with correct firmware name

You only formatted the cache now... That is done by running the mover, but shares need to be correctly configured, see here for more info (or turn the GUI help on).

Then I suspect some HBA issue, still worth to try the beta, if the normal update isn't working you install it manually, download the zip: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta25-x86_64.zip Then extract it and copy all the bz* files to the flash drive overwriting existing ones, then reboot.

Should work fine, but note that you can only connect one or two minSAS cables, since it's an expander backplane.

It should work correctly with any Supermicro backplane, what model backplane do you have?

If cache is now mounted please post new diags.

Should work as long as you pass trough the HBA to the VM, but it wouldn't be available for Unriad, so you couldn't start the array. Not sure X8 boards already had UEFI support, I know X9 have, if they don't it's easy to do it with DOS.

Download the Package_P20_IT_Firmware_BIOS_for_MSDOS_Windows for the correct models you have, then the easiest way to update is with Windows, by either installing the HBA on a Windows desktop or installing Windows on the server on a spare SSD or something, then just follow the instructions but basically is opening a command prompt windows and typing from where the package folder was unzipped: sas2flash -o -f blahblah.bin You can also boot form a dos flash drive an the update is the same, just using the DOS executable, though it only work wit older boards, newer ones will require the UEFI utility, sas2flsh -o - f blahblah.bin P.S. since you have two HBAs you'd need to specify the correct number, or just remove the other one and do it one at a time. I'm sure it's also possible to do it on Linux, but likely more complicated.

It's easier to update with a DOS boot flash or even Windows, you can download the latest firmware from Broadcom's support site, those HBAs will be under legacy, then HBA.

But you also need to fix these.