Jump to content

Parity check stuck at 100% will start again after reboot

Recommended Posts

The diagnostics show that your docker.img file is corrupt.  Since FCP is also warning about not being able to writ to the 'cache' pool that may also be corrupt.  At the very least the docker.img file will need to be deleted and then recreated followed by re-installing your docker containers with settings intact via Apps->Previous Apps.


I also notice that you have not set a Minimum Free Space value for the 'cache' pool.   You want this to be more than  the size of the largest file you expect to cache as BTRFS file systems tend to have problems if they get too full.

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.

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