JorgeB

Done.

Then it looks like a board issue, is secure boot disabled? Also make sure you're using a USB 2.0 port.

Load average is still extremely high, >30.

Check filesystem on disk10.

Can you connect to a public share? And to the flash share if exported as public?

Please post the output of ls -la /mnt/user

Please post the diags, you might also have an AST GPU.

Do you see the Unraid boot menu or not even that?

Permissions are OK, please reboot in safe mode to see if there's any change.

Not as bad as it sounds, only 3 servers are always on, remaining ones are cold storage, they are on about once month or so for a few hours.

Server load is very high, and there's something writing to the array, stop services, if that doesn't help reboot and post new diags after parity check runs for a minute or so.

Delete and recreate the docker image, but if the image keeps growing without adding new containers there's likely a mapping problem in one or more.

Change it to no for now, this way and if it happens again, you'll know if the issue is related to array start.

Sep 24 14:47:05 ivpiter kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 ... Sep 24 14:47:05 ivpiter kernel: nvme nvme0: Removing after probe failure status: -19 NVMe device dropped offline, the below can sometimes help, also look for a BIOS update. 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 initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.

and the output of ls -la /mnt/user

Please post the diagnostics.

Please post the output of ls -la /mnt/user

Syslog starts over after every reboot, so everything normal so far, if it keeps crashing you can enable the syslog server to see if it catches something, though likely it won't if the problem is hardware related.

See if this helps: https://wiki.unraid.net/My_Servers#How_to_disable_SSL_for_local_access

Was the array started?

Issues with disk10, check/replace cables and post new diags.

It is, data drives are never touched, as long as parity is correctly assigned you're fine, and you can check "parity is already valid" before array start to avoid the parity sync, assuming it is valid, in doubt run a parity check after.

Looks like a USB problem, make sure the flash drive is using a USB 2.0 port if available.

Sleeping monitor should be OK, though I believe seep is not enabled in Unraid by default, so the dummy plug is probably the best solution, if it works.