Jump to content

Docker 403 Errors


Go to solution Solved by JorgeB,

Recommended Posts

5 minutes ago, Wheels said:

Anything I can look out for that could have caused that to happen?

Running memstest is always good to rule out any obvious RAM issues, but no indication for now that bad RAM was the problem.

 

5 minutes ago, Wheels said:

Where could I find the best practice for the backup and restore for the cache pool?

Pool is still mounted read only, you should be able to copy anything important to the array, you can use you favorite tool, like Midnight Commander or the Dynamix file manager, then re-format and restore

 

Link to comment

Thank you both for your help.   I was able to move the data, recreate the pool and then move back.  I also created a new docker image and everything seems to be working as expected.  Not looking forward to 64GB or RAM memtest again but I want to be sure.

 

Thank you for the help!

  • Like 1
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...