Jump to content

Docker service has failed to start


Go to solution Solved by JorgeB,

Recommended Posts

  • Solution

These usually mean a bad flash drive:

 

May  6 23:50:27 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt
May  6 23:50:27 Tower kernel: SQUASHFS error: Failed to read block 0x29ae35c: -5
May  6 23:50:27 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt
May  6 23:50:27 Tower kernel: SQUASHFS error: Failed to read block 0x29ae35c: -5
May  6 23:50:27 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt
May  6 23:50:27 Tower kernel: SQUASHFS error: Failed to read block 0x29ae35c: -5

 

Link to comment

Thanks for the feedback Jorge, it is probably time to replace the flash drive if I remember correctly it's more than 8 years old.

This could also explain why the server is starting a new parity check after each reboot.

 

 

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