I recently had to rebuild my USB stick, that went ok, but I upgraded from 6.x to 7.3.1.

Now my server seems to be going to sleep or something, and the console(on the actual machine), the webgui and the shares all become unresponsive, the machine is still running( fans, LEDs etc. still on).

If its running a parity check, it stays awake during the parity check and everything works during the parity check. then sometime after the check finishes ( not immediately ) everything stops working.

cycling parity check is the only thing that keeps it useable, but that is not a long term solution =(.

Any help would be appreciated. Diagnostics below.

Ebein

ava-diagnostics-20260713-1246.zip

Make sure this has been taken care of, even if it wasn't an issue before: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Oh thanks, I am on 1st gen Ryzen(1800) and a 2nd gen MB(470).

Will see if it makes a difference.

Ebein

C-States where on AUTO, so I disabled them, also upgraded BIOS from F5(2019) to F66a(2026).

Also checked ram speed, is running with XMP off at 2133 for 2 sticks.

Hopefully this resolves some issues. Will report back asap.

Ebein

Still going to sleep/unresponsive. I dont know what else to change.

Ebein

new diagnostics after the BIOS update

ava-diagnostics-20260714-1029.zip

You can enable the syslog server and post that after the next crash, in case it's not a hardware crash.

Will do, thanks Jorge, looked at the syslog, and thiis was at the end.

Jul 14 10:29:01 AVA kernel: mdcmd (36): check correct
Jul 14 10:29:01 AVA kernel: md: recovery thread: check P ...
Jul 14 10:29:46 AVA root: Fix Common Problems Version 2026.05.16
Jul 14 10:29:49 AVA root: Fix Common Problems: Error: Machine Check Events detected on your server
Jul 14 10:29:49 AVA root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor.  Please use the edac_mce_amd module instead.
Jul 14 10:29:49 AVA root: CPU is unsupported
Jul 14 10:29:52 AVA kernel: r8169 0000:03:00.0: invalid VPD tag 0xff (size 0) at offset 0; assume missing optional EEPROM
Jul 14 10:29:52 AVA kernel: mpt3sas 0000:0a:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM
Jul 14 10:39:00 AVA root: Fix Common Problems Version 2026.05.16
Jul 14 10:39:02 AVA root: Fix Common Problems: Error: Machine Check Events detected on your server
Jul 14 10:39:02 AVA root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor.  Please use the edac_mce_amd module instead.
Jul 14 10:39:02 AVA root: CPU is unsupported

Edited July 14Jul 14 by Ebein
added logs

BEst to see the full syslog to see if the errors are just something harmless during boot or actual hardware issues.

full syslog.

ava-syslog-20260714-1635.zip

The current error logged is during boot, and should be harmless; we can see if the syslog server catches more until the next crash.

was that not the right syslog?

I just upgraded from 6.9 to 7.3.2 yesterday. I woke up to my server asleep and unresponsive, with the power button blinking (which I've never seen it do before). I pushed the button to power it back on and it was responsive within moments.

After some investigation, it appears that the Sleep (s3) plugin is a default part of Unraid now (?) and has a default sleep schedule. Maybe check out this plugin.

1 hour ago, Ebein said:

was that not the right syslog?

Is that after a crash?

42 minutes ago, barbarossa said:

it appears that the Sleep (s3) plugin is a default part of Unraid now (?)

It's not.

12 minutes ago, JorgeB said:

Is that after a crash?

every restart now is after it goes unresponsive, and I end up resetting it with the reset button on the front. It reboots I start the array up manually and it startts a parity check, parity runs for close to 24 hrs then within an hour of the parity stopping it becomese unresponsive again and i have to reset it.

But is that from the syslog server after a crash, or just the syslog after a reboot?

It freezes, machine is still running, at least powered on, all the lights and fans are going, but console with local monitor wont display anything, webgui wont respond and shares are not available. the diag is from after hitting the reset button. happy to try something else if you have suggestions.

8 hours ago, Ebein said:

happy to try something else if you have suggestions.

On 7/14/2026 at 4:33 PM, JorgeB said:

enable the syslog server and post that after the next crash

Guess im confused about the syslog server, I went and enabled it, is it added to the regular syslog or a separate file?

ava-syslog-20260716-1429.zip

18 minutes ago, Ebein said:

Guess im confused about the syslog server, I went and enabled it, is it added to the regular syslog or a separate file?

ava-syslog-20260716-1429.zip

It's a separate file saved to the share you selected, it will log everything up to the time you reboot so that way the record is not lost after a reboot.

38 minutes ago, Ebein said:

Guess im confused about the syslog server, I went and enabled it, is it added to the regular syslog or a separate file?

ava-syslog-20260716-1429.zip

It might be worth posting a screenshot of your syslog server settings so we can check that they are set correctly (many people get them wrong). It will also allow to tell you where its output is being written to (assuming you have correctly enabled the server).

You also have to set the Remote syslog server field. If logging to the same server, you can put localhost.

Ahh, Thanks!