stahlfuchs Posted November 1, 2021 Share Posted November 1, 2021 Hi all, I'm running Unraid 6.9.0-rc1 and I'm constantly struggling with BTRFS errors all the time. I was used to have it running for weeks on a row but during the summer something happened and now I get these errors. I stopped the docker via Settings - Docker, removed the docker.img and let it rebuild and did a clean restart but still getting these errors. Motherboard - TUF z390 pro gaming. Latest bios update Intel Core i5-9400T processor Running a mix of 8 and 14TB disks with a Samsung 970 EVO as cache. Here is the diagnostic file. I really hope someone can assist me with figuring out what is going on, I really love Unraid but this is starting to take its toll. Thank you all. dagon-diagnostics-20211101-1901.zip Quote Link to comment
trurl Posted November 1, 2021 Share Posted November 1, 2021 both cache and docker.img have corruption but not clear what caused it since they were already that way when you booted up. Maybe check connections and setup syslog server so we can see what happened next time. Quote Link to comment
stahlfuchs Posted November 1, 2021 Author Share Posted November 1, 2021 Thank you, I will try to set up a syslog server when I have the chance. Would this issue be resolved by getting a new cache drive and rebuild the dockers from scratch? Quote Link to comment
trurl Posted November 2, 2021 Share Posted November 2, 2021 1 hour ago, stahlfuchs said: Would this issue be resolved by getting a new cache drive and rebuild the dockers from scratch? No reason to think so. Have you ever filled cache or docker.img? Quote Link to comment
Squid Posted November 2, 2021 Share Posted November 2, 2021 Nov 1 18:58:31 DAGON kernel: BTRFS error (device nvme0n1p1): incorrect extent count for 3243245568; counted 1366, expected 1338 What you might consider doing is redoing the cache drive as XFS. BTRFS works fine for most people, but the most stable by far is using XFS, especially if you have no immediate plans to install a redundant cache pool in the near future. If the "docker image" keeps doing this for no real reason (ie: you've never filled it up), then something else that might help is switching to using a docker folder instead of a docker image. Quote Link to comment
stahlfuchs Posted November 2, 2021 Author Share Posted November 2, 2021 10 minutes ago, trurl said: No reason to think so. Have you ever filled cache or docker.img? A few days ago the log filled up and needed to restart. I was looking into it and then the BTRFS trouble started happening. Quote Link to comment
Recommended Posts
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.