JorgeB

Posted diags have VM service disable and no attempts to start it, we need to see the error when trying to start it.

Ryzen based CPUs on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/

Docker image could have been the issue, I did see a couple of btrs crashes earlier but no specific filesystem was mentioned, still recommend running RAM at non overclock speeds, especially with Ryzen, there have been previous cases here of instability and even data corruption.

There are some out of memory errors and a fuse errors a few minutes after that, that would be when /mnt/user stopped working, so it could be related, fix the out of memory errors first and see if it helps, if not post new diags.

What is exactly the current problem? If the server fails to boot sometimes it's likely this known issue:

Possibly a share with an invalid name? Jan 25 16:24:59 Tower24TB emhttpd: error: put_config_idx, 613: Invalid argument (22): fopen: /boot/config/shares/?.cfg

Did you already replace any of the SATA cables?

You should post on the preclear plugin support thread.

Some examples here: https://forums.lime-technology.com/topic/59589-solved-v635-advice-please-on-shares-settings/?do=findComment&comment=584558

That is always going to be slow.

If they are SSDs it's most commonly a cable issue, unless they are M.2 devices, but without diags can't say much more.

Likely the same issue posted 4 posts above.

Changed Priority to Other

This looks likely a general support issue, and most likely a hardware problem since different applications are crashing/segfaulting: Jan 25 01:26:06 Alexandria kernel: traps: diskload[2804] general protection ip:44bd57 sp:7ffca8fba090 error:0 in bash[424000+b4000] Jan 25 01:27:56 Alexandria kernel: traps: shfs[5215] general protection ip:1468584d450c sp:14685567d950 error:0 in libc-2.30.so[1468583e5000+16b000] Jan 25 01:28:01 Alexandria kernel: traps: monitor[27445] trap stack segment ip:64e0bd sp:7ffe5e5f5160 error:0 in php[433000+2b4000] Jan 25 01:28:01 Alexandria crond[1653]: exit status 135 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null Jan 25 01:28:01 Alexandria sSMTP[27458]: Creating SSL connection to host Jan 25 01:28:01 Alexandria sSMTP[27458]: SSL connection using TLS_AES_256_GCM_SHA384 Jan 25 01:28:01 Alexandria sSMTP[27458]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials d26sm3571777lfa.44 - gsmtp) Jan 25 01:29:01 Alexandria kernel: monitor[27464]: segfault at 1000eebbc8 ip 000000000066970c sp 00007ffd05f12250 error 4 in php[433000+2b4000] Jan 25 01:29:01 Alexandria kernel: Code: 55 48 89 f5 53 48 8b 46 08 48 89 fb 48 85 c0 74 65 0b 43 0c 4c 8b 63 10 48 98 41 8b 1c 84 83 fb ff 74 7b 48 c1 e3 05 4c 01 e3 <48> 3b 6b 18 75 36 48 89 d8 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b Try running in safe mode to rule out any plugins issues, but like mentioned looks more like a hardware problem, because this doesn't look like an Unraid bug I'm going to downgrade the report for now, it can be changed again later if it turns it is one.

There will be a few sync errors due to mounting the disks read/write without parity.

It does work out of the box with Unraid, but if you can't get the server to boot...likely it's interfering with the boot order.

Prefer moves from array to cache, you want cache="yes".

9207-8i is a very good option and compatible with Unraid, though thee could always be some compatibility issue with your particular board or a problem with the HBA itself. If the disk was unmountable there would be corruption, since it mounted correctly should be fine, but yes, you need to be careful before rebuilding on top, sometimes when this happens, when you know the disk wasn't the problem, it's better to do new config and re-sync/check parity instead or rebuilding the disk on top of the old one.

The crash on boot is likely this issue, you just need to try again, reportedly power cycling increases the chances of success, instead of a warm reboot. As for the HBA, no errors so far, so everything looks good for now.

Some models are plug'n play since they are IT mode only, e.g. 9207-8i, 9300-8i

You metadata is raid5, not raid1 like you said you did, I recommend using raid1 for metadata, it's much safer.

Please post the diagnostics: Tools -> Diagnostics

The HBA were those 3 drives are connected is constantly re-initializing, power down, make sure it's well seated, you can also try a different PCIe slot if available, then power back on, if no more errors all disks should mount correctly (disk8 might not if the file system on the emulated disk got corrupted), in any case post new diags after doing that.

Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append" nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.