Unraid 6.9 crashes every few days and now docker service does not start.


Recommended Posts

1 hour ago, macmann said:

I want a stable reliable system.

Don't we all!

 

I think that you should focus on hardware. Unraid is a very stable operating system. If you are crashing every few days then there is (more than likely) something wrong with your hardware. I'd start with memtest86+ for a few days. This is never an easy problem to solve. If that passes, then try running with very few HDD (or, if possible, no HDD) for a few days and see if you are stable. There's usually something.

Link to comment
8 hours ago, scubanarc said:

Don't we all!

 

I think that you should focus on hardware. Unraid is a very stable operating system. If you are crashing every few days then there is (more than likely) something wrong with your hardware. I'd start with memtest86+ for a few days. This is never an easy problem to solve. If that passes, then try running with very few HDD (or, if possible, no HDD) for a few days and see if you are stable. There's usually something.

 

This particular setup was running on a Dell rack server.  It gave me the same issues there.  I decided to use a AMD Ryzen based system with ASUS board.  No luck 

Link to comment
8 hours ago, scubanarc said:

Don't we all!

 

I think that you should focus on hardware. Unraid is a very stable operating system. If you are crashing every few days then there is (more than likely) something wrong with your hardware. I'd start with memtest86+ for a few days. This is never an easy problem to solve. If that passes, then try running with very few HDD (or, if possible, no HDD) for a few days and see if you are stable. There's usually something.

See attached diagnostics. 

unraid-server-diagnostics-20210713-0805.zip

Link to comment
6 minutes ago, JorgeB said:

Docker image is corrupt

Probably because you filled it. Why have you given 55G to docker.img? Have you had problems filling it? 20G is usually much more than enough and making it larger won't fix anything, it will only make it take longer to fill.

 

The usual reason for filling docker.img is an application writing to a path that isn't mapped.

Link to comment
44 minutes ago, trurl said:

Probably because you filled it. Why have you given 55G to docker.img? Have you had problems filling it? 20G is usually much more than enough and making it larger won't fix anything, it will only make it take longer to fill.

 

The usual reason for filling docker.img is an application writing to a path that isn't mapped.

How do I find out which application it is?

Link to comment
13 hours ago, macmann said:

Docker image has been recreated and working now.  I have enabled syslog mirror to flash and will wait for the next crash and post here.  Thank you everyone for your help. 

System crashed a few hours ago and I had to perform a hard reboot.  How do i grab the crash data to upload?

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.