My unraid is regularly crashing overnight. System completely hangs - black screen, cannot ping it, full lockup. I have only just started using unraid so this has never worked properly. 

 

I have enabled syslog mirroring to flash and captured the logs - please see attached diagnostics.zip. It seems to have stopped at  04:08:50 whilst mover is running but I cant see anything in the logs to help identify why. Mover is the only thing scheduled to run at that time AFAIK and I have run mover manually this morning and it completed successfully. I am using the Mover Tuning plugin. 

 

I need to observe some more to see if the crash only occurs when mover is running, but am hoping someone can have a look and see if there is anything helpful in the diagnostics and to help with suggestions how to troubleshoot this.

stragstore-diagnostics-20240605-0837.zip

Edited June 5, 20242 yr by Stragen001

There's a Samba crash at 1:15AM any idea what would be using SMB at that time?

17 minutes ago, JorgeB said:

There's a Samba crash at 1:15AM any idea what would be using SMB at that time?

 

Thanks for taking a look JorgeB,

The only thing connected via SMB is my desktop computer. I use Veeam to back it up to my array and it did fail last night at that time with the error below. However, there are log entries after this which make me think the array was up and working until the last log entry at 04:08?

 

05/06/2024 01:14:33 :: Error: Shared memory connection was closed. Failed to upload disk. Skipped arguments: [EmulatedDiskSpec>]; Agent failed to process method {DataTransfer.SyncDisk} 
 

50 minutes ago, Stragen001 said:

make me think the array was up and working until the last log entry at 04:08?

Correct, but that's the only relevant error I see, 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.

On 6/5/2024 at 11:49 AM, JorgeB said:

Correct, but that's the only relevant error I see, 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.

Thanks JorgeB for pointing me in the right direction. Still crashed with all dockers/plugins/etc turned off and getting more frequent, so started eliminating hardware one by one. Turns out it was a faulty DIMM. Even though it passed 3 x passes with Memtest. Joy. 

Edited June 8, 20242 yr by Stragen001