February 10, 20251 yr I've been having issues with my docker containers not restarting properly after Appdata Backup has run. I attempted to update to 7.0.0 from 6.12.14 a few weeks ago and the containers gave an execution error and wouldn't start. I rolled back to 6.12.14 (currently running) and rebuilt the containers. I've since also had to rebuild my VMS. I've followed all the docs and forum posts I could find, including below, to attempt to resolve the issue but it still continues to present itself: https://docs.unraid.net/#Re-Create_the_Docker_image_file https://docs.unraid.net/#Re-Installing_Docker_Applications I've also cleaned and formatted my cache drive. A restart does seem to bring them back but only for a couple days. I've attached a before reboot diagnostic and a fresh reboot diagnostic. I'm at my end with this and can't seem to figure it out. Please help! lovenest-diagnostics-20250210-1605_after.zip lovenest-diagnostics-20250210-1556_before.zip
February 11, 20251 yr Community Expert Previous diags had already rotated, but they show issues with the docker image, delete and recreate and if it still happens post new diags right after.
February 13, 20251 yr Author It happened again, not sure if I got to the diagnostics in time. lovenest-diagnostics-20250213-1212.zip
February 13, 20251 yr Community Expert Diags rotated again, reboot and post new ones after array start.
February 13, 20251 yr Author I have not run a memtest recently. I can do that this weekend at some point. Here are the new diags from a reboot about 45 mins ago. lovenest-diagnostics-20250213-1244.zip
February 13, 20251 yr Community Expert I was looking for btrfs csum errors on cache, but it appears system share also has files on disk3. So does that mean docker.img is on disk3 and has btrfs csum corruption due to bad RAM?
February 13, 20251 yr Community Expert 26 minutes ago, kal-el681 said: I have not run a memtest recently. I can do that this weekend at some point. You should not even attempt to run any computer unless RAM is working perfectly. Everything goes through RAM. The OS and other executable code, your data. Everything. The CPU can't do anything with anything until it is loaded into RAM.
February 13, 20251 yr Community Expert Are you sure the docker image was recreated a couple of days ago? Doesn't look like it was, based on the trans ID.
February 13, 20251 yr Author 35 minutes ago, trurl said: You should not even attempt to run any computer unless RAM is working perfectly. Everything goes through RAM. The OS and other executable code, your data. Everything. The CPU can't do anything with anything until it is loaded into RAM. I did a memtest when I upgraded the RAM about a year ago and have made no hardware changes since. 39 minutes ago, trurl said: I was looking for btrfs csum errors on cache, but it appears system share also has files on disk3. So does that mean docker.img is on disk3 and has btrfs csum corruption due to bad RAM? When I formatted the cache, I copied everything from that drive to the array and then back after. The system files are also set as cache->array for mover and backup. Is this incorrect? 3 minutes ago, JorgeB said: Are you sure the docker image was recreated a couple of days ago? Doesn't look like it was, based on the trans ID. It may have been a week ago but I did rebuild it following the steps for the docs.
February 13, 20251 yr Community Expert Probably wouldn't hurt to start with another memtest. Would definitely hurt if you continue to run with bad RAM. If memtest passes then continue with this next part. 2 hours ago, kal-el681 said: system files are also set as cache->array for mover and backup Don't know what you mean by "backup". Mover doesn't do backups, and any backup you might do of these shares should be to some subfolder of another share. And you don't want mover moving these to the array. Ideally, appdata, domains, system shares would have all files on cache or other pool with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open. Nothing can move open files, so after setting those shares to be moved to cache, you also have to Disable Docker and VM Manager in Settings. You can see how much of each disk or pool is used by each share by clicking Compute... for the share on the User Shares page. Mover won't overwrite files, so if something is on the array and on cache, you will have to clean that up yourself. After you get things moved where they need to be On 2/10/2025 at 3:33 PM, kal-el681 said: https://docs.unraid.net/#Re-Create_the_Docker_image_file https://docs.unraid.net/#Re-Installing_Docker_Applications
February 14, 20251 yr Community Expert 13 hours ago, kal-el681 said: It may have been a week ago This was just a few days ago: On 2/11/2025 at 7:44 AM, JorgeB said: they show issues with the docker image, delete and recreate So the image was already bad.
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.