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.

Help: Corrupt Docker Image or Bad SSD?

Featured Replies

I'll start off by saying that I'm relatively new to unRAID so apologies if I seem relatively unfamiliar with the system.

 

I installed Docker, and got my plex app, deluge app, and couch potato + sonarr installed.

 

I finally got everything configured and now, at random time intervals, several containers will just stop running and refuse to restart.

I got as much log information as I could, not really knowing which steps to start taking to correct the issue.

 

I've tried reseating a the SSD cache sata cable thinking that might be the issue but no luck there.

Some insight would be very much appreciated.

 

Thanks everyone. 

 

(sorry for the small log images, size limitation was hard to workaround)

initial_issue_started.PNG.c97321bc77f4acfe272e1ee7f6ad41dc.PNG

  • Author

Other log file attachment:

problem_new.jpg.232d024ebc929f56991c984138b6c867.jpg

  • Author

So even compressed, my diag file is 3MB. So I can't actually post it, any suggestions?

Probably because it's full of the error messages. 

 

Could reboot your server and look at the syslog, when you're sure you've captured the errors then collect the diagnostics.  Should make it smaller.

 

Or something like dropbox.

I can't speak for anyone else, but looking at the uncompressed size of your docker log it's well over 100MB in size!

 

Full of

 

time="2016-05-31T15:57:38.089467296-05:00" level=error msg="Failed to log msg \"runsv plexrequests: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.089525347-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.089581056-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.089665814-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.089737202-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.090002307-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.860677553-05:00" level=error msg="Failed to log msg \"runsv mongo: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.860965039-05:00" level=error msg="Failed to log msg \"runsv mongo: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:38.861220271-05:00" level=error msg="Failed to log msg \"runsv mongo: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.090136620-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to stat control/u: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.090265438-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to stat control/u: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.090342769-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.090399234-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.090655851-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.090781914-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.090975580-05:00" level=error msg="Failed to log msg \"runsv plexrequests: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.091293858-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.861399521-05:00" level=error msg="Failed to log msg \"runsv mongo: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.861684316-05:00" level=error msg="Failed to log msg \"runsv mongo: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:39.861970791-05:00" level=error msg="Failed to log msg \"runsv mongo: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.091339500-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to stat control/u: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.091419267-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.091575133-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.091760093-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to stat control/u: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.091842570-05:00" level=error msg="Failed to log msg \"runsv plexrequests: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.091953592-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.091996388-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.092164101-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.862302692-05:00" level=error msg="Failed to log msg \"runsv mongo: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.862570087-05:00" level=error msg="Failed to log msg \"runsv mongo: fatal: unable to start ./run: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:40.862835886-05:00" level=error msg="Failed to log msg \"runsv mongo: warning: unable to open supervise/pid.new: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:41.092322909-05:00" level=error msg="Failed to log msg \"runsv syslog-ng: warning: unable to stat control/u: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 
time="2016-05-31T15:57:41.092406379-05:00" level=error msg="Failed to log msg \"runsv plexrequests: warning: unable to stat control/u: input/output error\" for logger json-file: write /var/lib/docker/containers/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673/9f78c71897264fea87406bb0160220cf00305e5a1795fe1e1e7dfcd60b470673-json.log: read-only file system" 

 

Run this plugin and see what it flags up because something is jacked.

  • Author

Here's what's been found.

I think the read only file system is what's causing issues.

the SSD has 70GB free so it's definitely not full.

errors_found.PNG.62a199551ed4109ed8c32864796e322f.PNG

Your syslog filesystem is full.

Your docker imagefile is full.

  • Author

Well, I just installed it a few days ago.

Is there a way to expand the filesystem?

Assuming the docker image is mounted on the cache drive then it's not necessarily full because the cache drive is either full or corrupted and in read only mode.  That problem has to be fixed first before anything else.  (but after a reboot to clear out the log)

 

Sent from my LG-D852 using Tapatalk

 

Archived

This topic is now archived and is closed to further replies.

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.