-
(SOLVED) Docker daemon failed to start suddenly after appdata backup run
okay, then i do that :) really apricate the help yet another time. 😁
-
(SOLVED) Docker daemon failed to start suddenly after appdata backup run
So after now after starting up the array the docker service started fine. also seems like all dockers starts fine without any errors i can see. or errors in the syslog file other then the 2 i posted above that is.
-
(SOLVED) Docker daemon failed to start suddenly after appdata backup run
Yes i did. and it said 2133 in unraid and everywhere els so assume it was running at 2133. So i would assume does 2 sticks i had is faulty :(. luckily i had 1 extra 16GB stick "running at 2133" i have put in and also did a memtest and got a PASS on it. first failed memory i have ever had. So what's the safe best now to do ? format the cache drive and restore a appdata backup ? Or recommend do more tests ? only error i see now is root: error log : /var/log/graphql-api.log and mem kernel: pci 0000:02:00.2: bridge window [mem size 0x00700000]: failed to assign errors. but that maybe because i when from 32GB to 16GB ? also added another diagnosis file thor-diagnostics-20260224-1724.zip
-
(SOLVED) Docker daemon failed to start suddenly after appdata backup run
it have been working fine for many years now. and i always tout as the mb supported the memory expo it was all fine... the test is up in 81 errors now.
-
(SOLVED) Docker daemon failed to start suddenly after appdata backup run
i did it after infact right before you replied the first time. but running memtest now and not looking good :( . but i still see it says (ddr4-3000) does that mean that the change i did didnt stick ?
-
(SOLVED) Docker daemon failed to start suddenly after appdata backup run
So its still the same issue ? i did just now turn off the expo on my memory in the bios. and set it to auto in the asus bios ( AI tweaker settings ) So memory is now running at ( Configured Memory Speed: 2133 MT/s ) But i will also run a mem test and see. and come back when its done.
-
(SOLVED) Docker daemon failed to start suddenly after appdata backup run
Hi again. So suddenly during the night after my app data backup had run they didn't want to start again it seems. So when i also tried to manually start it i noticed rc.docker: Docker daemon... Failed. in the logs + some corrupted files on the cache drive it seems. also fix common problems saying my cache drive is write only Everything have been working fine since my last post on Friday. Only thing i have done since then is update my bios to latest version and got recommended to change docker from docker.img to docker directory. So i did that. Did some searching but got me just more confused. That it could be a normal btrfs corruption issue and that changing to xfs would minimize that. . or the docker.img change to docker directory. Also added the Diagnostics file. thor-diagnostics-20260224-0955.zip
-
(SOLVED) Power outage gave me Unmountable: wrong or no file system on the cache drive
Thank You guys. That's some great tips. i will give does a test. now that i can see my appdata content again after the command from JorgeB . is it safe to just reinstall the dockers ? Did check system docker / docker.img and it looks like this
-
(SOLVED) Power outage gave me Unmountable: wrong or no file system on the cache drive
i have tried to do so. but maybe i havnt done a good enough job ? i saw a doc file just now about etch container should atleast have 10-20 sec to do a clean shutdown or something ? after that command i could also see the appdata content . but still no dockers.
-
(SOLVED) Power outage gave me Unmountable: wrong or no file system on the cache drive
Here is the new diags after doing what you requested. thor-diagnostics-20260220-1401.zip
-
(SOLVED) Power outage gave me Unmountable: wrong or no file system on the cache drive
So we have had a few power outage and even with a UPS seems like i got a issue sadly. And noticed after i started unraid up again that docker containers started and suddenly stopped and was gone. and appdata was also gone. so took a restart and then when booted back up the cache drive was "Unmountable: wrong or no file system" So would love some assistance if this is fixable ? have added the diagnostics file. thor-diagnostics-20260220-1236.zip
-
Unable to write to cache SSD after unclean shutdown.
Okay was afraid off that. tnx . i will give that a try and see.
-
Unable to write to cache SSD after unclean shutdown.
My cache ssd wich is that nvme1n1. i assume thats there becouse i read someplace that i should also have it on array be the secondary place. So i turned it on. But then read another place that that was a bad idea so turned it back off agian after i had tried running the balance command. That was after this issue first started.
-
Unable to write to cache SSD after unclean shutdown.
So after a unclean shutdown that happen a week ago slowly after restarts seems this have happened more and more to now being totally unusable. Noticed docker wouldn't start today and saw this error in fix common problems plugin. i added syslog and diagnosis. edit: aim running Unraid 7.0.1 Is this because off my cache SSD have become corrupted and need to be re formatted and backup restored? or is there a better solution ? thor-diagnostics-20250318-1609.zip thor-syslog-20250318-1522.zip
-
Strange errors Buffer I/O error!
here is also the diagnostic/syslog from before the clean Unraid install. thor-syslog-20230412-2117.zip thor-diagnostics-20230412-2317.zip