June 8Jun 8 I had a drive fail last week as I was adding new drives with the intent of repurposing an existing drive as parity. Ended up doing a new config and getting parity working. Had to reinstall most of my Docker containers due to data loss. Parity built over the weekend (~26 hour runtime). Today I woke up today to a hard hang where I had to force power off. Now permissions are broke, all my containers are failing with errors about corrupt files, and the server in general is slow and sluggish.I know it's not a lot to go off and nothing immediately stands out as a smoking gun in my logs, but hopefully someone more knowledgeable than me can take a look at my diagnostics and see if there's anything. illmatic-diagnostics-20260608-1009.zip
June 8Jun 8 Community Expert Don't see obvious issues, but any particular reason you are using NTFS for the dockercache pool? NTFS support is limited with Linux; recommend backing up and recreating that pool with a Linux filesystem.
June 8Jun 8 Author 1 hour ago, JorgeB said:Don't see obvious issues, but any particular reason you are using NTFS for the dockercache pool? NTFS support is limited with Linux; recommend backing up and recreating that pool with a Linux filesystem.Oh that's super weird. I did set it to use xfs when I noticed that a week ago. I must not have fully applied my changes and formatted.
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.