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

Edited February 24Feb 24 by CrazyLordy

Ryzen with overclocked RAM like you have is known to corrupt data, and btrfs is detecting data corruption on the pool, so I recommend correcting that first and then running memtest:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

1 minute ago, JorgeB said:

Ryzen with overclocked RAM like you have is known to corrupt data, and btrfs is detecting data corruption on the pool, so I recommend correcting that first and then running memtest:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

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.

22 minutes ago, CrazyLordy said:

So memory is now running at ( Configured Memory Speed: 2133 MT/s )

Not according to the diags

Configured Memory Speed: 3000 MT/s

8 minutes ago, JorgeB said:

Not according to the diags

Configured Memory Speed: 3000 MT/s

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 ?

17 minutes ago, CrazyLordy said:

but i still see it says (ddr4-3000) does that mean that the change i did didnt stick ?

Possibly

You must never attempt to run any computer unless memory 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.

8 minutes ago, trurl said:

You must never attempt to run any computer unless memory 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.

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.

2 hours ago, CrazyLordy said:

the test is up in 81 errors now

No point in continuing memtest, even 1 error is too many

2 hours ago, trurl said:

unless memory is working perfectly

3 hours ago, CrazyLordy said:

it says (ddr4-3000)

Did you try to fix that again?

35 minutes ago, trurl said:

No point in continuing memtest, even 1 error is too many

Did you try to fix that again?

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

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.

The errors above should be harmless; you can ignore them.

2 minutes ago, JorgeB said:

The errors above should be harmless; you can ignore them.

okay, then i do that :) really apricate the help yet another time. 😁