TelefraggerRick Posted May 24, 2022 Share Posted May 24, 2022 Server crashed a little while ago with a kernal panic. No idea why, checked iLO and it said it had a raid controller error. Rebooted and everything came back fine and worked fine for a few days. Since then all my dockers have become read only and I can't do anything with them. Tryed deleting the docker image, creating a new one and reinstalling all my applications but still same issue. There read only. None of them seem to be able to load there internal DBs or have issues reading config files, etc... I've search this topic a few times and found bunch of people with same issue but no one seems to have a definite resolution. I have attached my diagnostics file below. Wonder if anyone can help me with this? unraidserver-diagnostics-20220524-0925.zip Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 Please see here: https://forums.unraid.net/topic/123620-unraid-os-version-6100-available/?do=findComment&comment=1129618 Basically for now you need to disable Intel VT-d or go back to v6.9.2 Quote Link to comment
TelefraggerRick Posted May 24, 2022 Author Share Posted May 24, 2022 Just reverted back to 6.9.2 and looks like the docker images are still having issues with read only file system. Any other suggestions? Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 Docker image or a filesystem might still be corrupt, but at least it won't get worse now, please post new diags to see what's the best option. Quote Link to comment
TelefraggerRick Posted May 24, 2022 Author Share Posted May 24, 2022 Attached is the latest diagnostics. Its really weird because i can browse appdata fine with no issues and open files but docker cannot do anything with it. I have created a new docker image and added the files again but no change Still cant access it. unraidserver-diagnostics-20220524-1504.zip Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 Not seeing any filesystem issues logged, where are you seeing the read only error? Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 Also check filesystem on the cache device just to be sure there are no issues, run it without -n or nothing will be done if corruptions are found. Quote Link to comment
TelefraggerRick Posted May 24, 2022 Author Share Posted May 24, 2022 15 minutes ago, JorgeB said: Not seeing any filesystem issues logged, where are you seeing the read only error? My nginx docker says it has no users anymore and its own logs says it cant reach its internal DB, my unifi controller just hangs on migrating database because it says it cant read or write its database file, sonarr says it cant read or write its config file. Every single docker has stopped working with all similar issues Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 You did the format the cache before, did you restore the appdata from a backup? Quote Link to comment
TelefraggerRick Posted May 24, 2022 Author Share Posted May 24, 2022 trying to stock the array right now to get to maint. mode to run the check but its hanging on "retry unmounting user share(s)" and wont stop the array. Quote Link to comment
TelefraggerRick Posted May 24, 2022 Author Share Posted May 24, 2022 5 minutes ago, JorgeB said: You did the format the cache before, did you restore the appdata from a backup? I did format the cache and restored appdata from backup, i also tryed moving appdata to the array, but same issue with docker then as well. Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 Was the restore done before or after going back to v6.9? 5 minutes ago, TelefraggerRick said: mode to run the check but its hanging on "retry unmounting user share(s)" and wont stop the array. That means something is using that, also check no terminal windows open in a mounted folder. 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.