JorgeB

Syslog in the diags starts over after every boot, enable the syslog server and post that if it happens again, but if I understand correctly the server did shutdown on its own after a quick button press? That you mean it wasn't completely crashed.

It's also logged in the syslog as a disk problem, though the UNC @ LBA 0 doesn't make much sense, I would run an extended test on the disk.

Memtest is only definitive if it finds errors, if you have multiple sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.

Please post the complete diagnostics.

Parity will not be accessed for any array reads, it will be access during a parity check or any array writes.

Don't really think so, controller is using the stock AHCI driver, I guess it could be a controller/board problem.

Server rebooting on its own, vs. crashing/hanging, is almost always a hardware problem, but it can be caused by different things, like PSU, RAM, board, etc.

It can start happening by just using a different Unraid release, or the same release with different hardware, several users had that issue come up after a change.

Yep.

Those should be OK, looks like result of macOS, but there is a problem with the flash drive: Apr 21 14:36:50 Tower emhttpd: Unregistered Flash device error (ENOFLASH4). There were similar reports before that were fixed by plying with the USB settings in the board BIOS, IIRC last one was fixed after enabling USB power delivery in S5 State, or something similar.

I would replace/swap the cables, if not done yet, but for now don't see a reason to suspect a device problem.

If you have multiple RAM sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.

Unfortunately there's nothing relevant logged, I do see some errors related to a CD/DVD drive, but those should not cause the server to crash, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Btrfs is detecting new data corruption, since memtest is only definitive if it finds errors, and since you have multiple sticks, fix the corrupt files and reset the stats and and try with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM.

Looks OK for now, no more ATA errors.