Hi!

I got a notification from "Fix Common Problems" today that one disk had read errors. I looked in the Unraid GUI and disk7 did indeed have a few of them, 74 to be exact. I checked syslog and it looks like they happened in two "batches", once on April 1 (so while the monthly parity check was running) and once earlier today.

The parity check that ran when the first batch of errors happened reported zero parity errors, the extended SMART test that I ran before making this post had nothing to complain about either, and looking at the SMART attributes both before and after the extended test there isn't really anything that seems "off" to me.

I'm leaning towards it being due to some cable issue, but figured I'd post here as well to make sure I'm not missing anything obvious and/or if there are other possible causes. I've attached the diagnostics.zip, please let me know if there's anything else that could be useful.

Any help is appreciated. Thanks in advance!

 

blockbuster-diagnostics-20250406-2223.zip

3 minutes ago, jyggen said:

due to some cable issue

Probably.

 

Apr  6 14:46:43 blockbuster root: Fix Common Problems: Error: Docker image file is getting full (currently 95 % used)

Looks like you "fixed" this problem by changing to a docker folder. Probably that is only hiding the actual problem.

https://docs.unraid.net/unraid-os/troubleshooting/docker/

16 minutes ago, trurl said:

Apr  6 14:46:43 blockbuster root: Fix Common Problems: Error: Docker image file is getting full (currently 95 % used)

Looks like you "fixed" this problem by changing to a docker folder. Probably that is only hiding the actual problem.

https://docs.unraid.net/unraid-os/troubleshooting/docker/

I've had it as a folder for a good while. It's stored on one of the my cache drives though (and set to never move to the array), so I'm pretty certain that error is/was related to the cache drive filling up. At least it went away after the mover ran. Is there any benefit to using docker.img vs. using a folder?

Thanks for the reply!

Edited April 6, 20251 yr by jyggen

7 minutes ago, jyggen said:

any benefit to using docker.img vs. using a folder

Easier to see if you are filling it up. docker.img (or folder) should have little written to it, except when you add a new container. Usage should not be growing. It is supposed to just have the downloaded executables for the applications. The working storage for the applications are mapped to appdata, and other storage that needs to be read/written is to a container volume mapped to a host volume.

 

Maybe nothing is wrong with what you have. The link I gave has some suggestions for what to pay special attention to when specifying paths.