JorgeB

Still seeing some Nginx errors that could be caused by a plugin, my recommendation is the same

Unless I'm mistaken, that plugin is used when you try to update the server: Tools - Update OS.

Start by running memtest.

There appears to be a container constantly restating; see if you can find which one by looking at their uptimes, disable that container, reboot to clear the logs, then post new diags after array start

I meant a screenshot of the actual update page, when it's running the update.

Type unraid-api stop unraid-api restart Then try to sign in again.

There's a container set to 1GB max RAM that keeps going OOM, The container ID is: 5e01e8b65d09a6135c5876583f7bcd4f87d7ecbefc76dafde4d591b5b7f56515 That container includes these processes stash vips ffmpeg Increase the RAM limit to 2 or 4GB to see if that resolves the issue, then reboot to clear the logs and post new diags.

Diags only have a no-correcting check, reboot to clear the logs, run a correcting check, then another one (correct or non correct) right after and without rebooting.

There's no parity check on those diags, start a new one and post new diags if it crashes.

try this, on Main click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off Reboot and then see if it makes a difference; if it still drops post the diagnostics next time it happens.

See if it works after deleting the /previous folder on the flash drive.

Recommend creating a stock install with the tool and then restoring only the config folder from the backup

The USB tool cannot be used ot create an internal boot pool, boot from a flash drive, then use the wizard to create the internal boot pool

Please post a screenshot of the error you see, also the diagnostics.

It does, it suggests filesystem issues on disk9, check filesystem on that disk after rebooting You will also need to think about moving on from reiserfs, Unraid 7.3 no longer supports it.

This is the only option when using the data partition of a mirrored boot pool.

It's possible to mirror the boot partition; the remaining space can only be used as a single pool, either an 8GB mirror, or an 8GB+2TB volume without redundancy.

In that case, I would ignore the errors for now; they look to me like not actual errors but false positives.

Macvlan should no longer be an issue, since 6.12.11, but it's worth a try in case the problem is still related to Docker in general and that change helps.

Since no errors were found, reset the stats for the pool ,and keep monitoring; they could be old errors, but if new ones come up, there's still a problem

If the Connect icon is not showing, open a terminal window and copy/aspet unraid-api plugins install unraid-api-plugin-connect Then refresh the GUI and recheck

Again, that starter.sh process ran the server out of RAM, it was using around 58GB of RAM Out of memory: Killed process 733603 (start.sh) total-vm:61144552kB, anon-rss:61136512kB This process was running inside a Docker container with this long ID string. task_memcg=/docker/52668f00206d0cc53fecee251d6f428be8eeff903b6501bb172433553cf27258

That basically confirms to me there's an external issue with your LAN/internet.

Upload failed, please try again.And don't forget the screenshot.

Jun 9 20:52:57 NAS1 kernel: __vm_enough_memory: pid: 5571, comm: docker, bytes: 549760008192 not enough memory for the allocation A Docker container just tried to allocate 549,760,008,192 bytes of memory. That is 549 GB of RAM. Try recreating the Docker image in case something is corrupted, then restore your assp one by one https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file Then: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks If issues continue, it could also be bad RAM.