JorgeB

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.

Seems to be OK for now.

See if you can get the diagnostics, or at least the syslog, then type "reboot" in the CLI, if it doesn't start to reboot after 5 minutes, you may need to force it.

They shouldn't be, and there's nothing else there. If possible, try booting in safe mode and disable Docker and VM services; basically, use the server as a basic NAS, and see if it still crashes to rule out plugins or other apps.

That looks much better, multiple disks being written to in parallel with a decent speed. Keep an eye on reads from other disks that are not part of the resilver, and I mean high-speed reads, in the MB/s, not KB/s, because I don't 'think the whole pool is being scrubbed, at least it's not for me in a similar scenario. It's normal to "scan" the whole pool, but that should only be a metadata scan, not a full data scrub.

Scrub the pool and post the results from the GUI

That has SATA port multipliers and is not recommended; it doesn't mean it's the problem, but it should be replaced anyway https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/ Try connecting or swapping the disks that are not being detected to the onboard SATA controller.

If you can, I would try with a different model disk to confirm if that is the issue.

Again, no associated controller errors. This is looking more to me like a firmware/kernel issue with that disk; I see that it's a different model than the other ones.

Please attach the complete zip and a screenshot from Main.

Multiple disks are not being initialized correctly, can you post a link to the Asmedia controller you are using? It appears to have port multipliers, which are a known problem.

Shares are correct, so it's mostly what Itimpi mentioned.

That should not make any difference, main issue I would try would be to replace the power cable for the SATA drive, to see if it helps with the noises.

You can use it again, TPM is not permanently blacklisted, unlike flash drives.

It should be fine to go directly to 7.3.1, read the release notes for 7.3.0 and 7.3.1, and always goof to create a flash drive backup just in case.