Docker containers failed update and now are "stuck"


madpoet

Recommended Posts

Hello, I went to mass update a few Docker containers and it completely bombed out on them. Now none of them will start, and if I try force update they all give me "Error: open /var/lib/docker/tmp/GetImageBlob777644061: read-only file system". Different blob names obviously. Any ideas on how to recover? One of them is Plex so I REALLY don't want to have to recreate it. Thanks!

Link to comment

Cache device dropped offline:

Feb 17 11:21:47 Tower kernel: ata8: COMRESET failed (errno=-16)
Feb 17 11:21:47 Tower kernel: ata8: limiting SATA link speed to 3.0 Gbps
Feb 17 11:21:47 Tower kernel: ata8: hard resetting link
Feb 17 11:21:52 Tower kernel: ata8: COMRESET failed (errno=-16)
Feb 17 11:21:52 Tower kernel: ata8: reset failed, giving up
Feb 17 11:21:52 Tower kernel: ata8.00: disabled

 

You should never use the 4 Marvell ports on that board, first 4 white SATA ports, they are known to constantly drop drives.

Link to comment
1 hour ago, johnnie.black said:

4 Marvell ports on that board, first 4 white SATA ports,

Sorry, taking a second look I see that board doesn't have a Marvell controller onboard, many of those Asrock rack models have and I assumed that was one of them, so it's an addon controller you're using, you could replace that with a different one, an 8 port LSI HBA or a JMB585 if 4/5 ports are enough.

 

The 6 onboard SATA ports are from the Intel chipset and perfectly safe to use.

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.