Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Docker Containers Shutting Off, Error 403. Corrupted or Full Cache Drive.

Featured Replies

Hi,

 

I am having this issue with docker.

 

It started a couple months ago where my docker containers would all shut off and every time i tried to restart them i would get error 403. After a server restart, it would be fine for a random amount of days (Longest is 19 days, shortest is 3 days) and the issue would pop up.

 

Something I noticed is that the docker img file itself would be gone from the docker folder. This time though its still there which is confusing.

 

Recently, Fix Common Problems has been notifying me that the cache drive is either full or readonly and my docker img is either full or corrupted.

 

Checking the logs, I was getting btrfs errors so I assumed that the btrfs file system was corrupted so I ran the check file system for the cache but it did not give any errors (I had to run this after restarting the server because it would not let me stop the array, it said stopping but never did so).

 

Same problem showed up after a couple of days so I believe my btrfs file system is corrupted.

 

Should I reformat my cache drive and instead use xfs for the cache drive or is there something else wrong that I haven't found?

tower-diagnostics-20230103-0906.zip

  • Community Expert
Jan  2 23:16:02 Tower kernel: ata5: COMRESET failed (errno=-16)
Jan  2 23:16:02 Tower kernel: ata5: limiting SATA link speed to 3.0 Gbps
Jan  2 23:16:02 Tower kernel: ata5: hard resetting link
Jan  2 23:16:07 Tower kernel: ata5: COMRESET failed (errno=-16)
Jan  2 23:16:07 Tower kernel: ata5: reset failed, giving up
Jan  2 23:16:07 Tower kernel: ata5.00: disabled
Jan  2 23:16:07 Tower kernel: ata5: EH complete

 

Cache SSD dropped offline, check/replace cables.

  • 2 weeks later...
  • Author

Same problem today.

 

I checked and replugged all the cables almost a week ago.

 

I think the ssd might be bad because after a restart its starts to work again. Could also be the SATA port, the cable or psu.

 

I have new cables coming in and Ill update if it happens again.

 

I'm uploading the logs of when it happened.

tower-diagnostics-20230112-1841.zip

  • Community Expert

Dropped again, try the new cables.

  • 2 months later...
  • Author

Replaced Cables about 3 days ago when ssd dropped out again. Before that it did not drop out for a month.

 

It just dropped so I am guessing either bad ssd, sata port on mobo, or could be power supply. Ill try switching the sata port to see if it fixes it. 

 

Also, dont think this is related but for the month it worked fine, I had my Pi-Hole docker off. I turned it on about a week ago then ssd dropped 3 days ago. Gonna try turning it off to see if that helps.

 

Got new logs uploaded.

tower-diagnostics-20230318-2050.zip

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.