Jump to content

(SOLVED) unRAID crashes randomly, can't find cause


Go to solution Solved by JorgeB,

Recommended Posts

Hi there,

 

yesterday my unRAID crashed on me, while I was at work. I noticed because my DAV services gave an error on my phone. I thought nothing of it, things can happen, and rebooted the machine soon after. This morning, it crashed again, and now I'm curious.

It's also for no appereant reason, there was no load on the machine. I run some dockers (usually 8-9 are active, 17 are installed) and one Win 10 VM (which exclusively is there so I can TeamViewer on there to do things on remote). Only docker that usually pulls some heavier load is Plex, but no one was using it at the time.

 

Crash times were yesterday, 4th May around 16:00h and today, 5th May around 09:30h.

 

When I came home now, I tried to connect locally to see if it was accessible (could've been that just all Dockers and VMs acted up or whatever), no dice. I pinged it, you can see the result attached; 8 is the ending of the IP of unRAID, 43 from my desktop PC. I had a look into my router menu, there it was still listed as active connection (screenshot also attached)

 

I can't really see what happens, but I'm also not good with logs :( I attached the syslog (mirror to flash) and the diagnostic file which I just created after the reboot.

Anyone might know what to look for? I didn't do a memtest yet (because time), I use a desktop mainboard but have ECC memory (ECC is enabled in BIOS)

 

Best,

Rick

 

 

fritzbox_unraid.png

ping_unraid.png

syslog.zip lunas-diagnostics-20220505-1856.zip

Edited by CameraRick
Link to comment
  • CameraRick changed the title to (SOLVED) unRAID crashes randomly, can't find cause
  • 1 month later...
On 5/5/2022 at 5:12 PM, CameraRick said:

Hi there,

 

yesterday my unRAID crashed on me, while I was at work. I noticed because my DAV services gave an error on my phone. I thought nothing of it, things can happen, and rebooted the machine soon after. This morning, it crashed again, and now I'm curious.

It's also for no appereant reason, there was no load on the machine. I run some dockers (usually 8-9 are active, 17 are installed) and one Win 10 VM (which exclusively is there so I can TeamViewer on there to do things on remote). Only docker that usually pulls some heavier load is Plex, but no one was using it at the time.

 

Crash times were yesterday, 4th May around 16:00h and today, 5th May around 09:30h.

 

When I came home now, I tried to connect locally to see if it was accessible (could've been that just all Dockers and VMs acted up or whatever), no dice. I pinged it, you can see the result attached; 8 is the ending of the IP of unRAID, 43 from my desktop PC. I had a look into my router menu, there it was still listed as active connection (screenshot also attached)

 

I can't really see what happens, but I'm also not good with logs :( I attached the syslog (mirror to flash) and the diagnostic file which I just created after the reboot.

Anyone might know what to look for? I didn't do a memtest yet (because time), I use a desktop mainboard but have ECC memory (ECC is enabled in BIOS)

 

Best,

Rick

 

 

Hello,

 

Using an AMD Zen processor, CoreFreq is incompatible with any monitoring tool running in parallel.

 

CyrIng

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...