yyquest

Hi all Recently I noticed that that I was not able to update any docker image (in this case, it's FileZilla) on my Unraid box. After further investigations, it turns out that I am not able to install new docker as well. The error is similar to what is listed below. The system log is attached in case it provides some clues. Can someone suggest how I can fix this issue? Thanks very much in advance! IMAGE ID [a8b20fe26516]: Pulling fs layer. IMAGE ID [2b38ee75ca47]: Pulling fs layer. IMAGE ID [c705e2cfb7e4]: Pulling fs layer. IMAGE ID [99fc5de0159f]: Pulling fs layer. IMAGE ID [9be4eb2e172e]: Pulling fs layer. IMAGE ID [555ff972abc9]: Pulling fs layer. IMAGE ID [d8044fd0dc26]: Pulling fs layer. IMAGE ID [9c707b3cb6c4]: Pulling fs layer. IMAGE ID [ea96d2e5593d]: Pulling fs layer. IMAGE ID [bef6761818b2]: Pulling fs layer. IMAGE ID [0d966a25b1b2]: Pulling fs layer. IMAGE ID [4617d1abe01c]: Pulling fs layer. IMAGE ID [3c8e881516f5]: Pulling fs layer. IMAGE ID [d0dd78d3fd73]: Pulling fs layer. IMAGE ID [e8d6c4efaf3d]: Pulling fs layer. IMAGE ID [ecc455574ea9]: Pulling fs layer. IMAGE ID [ab133559bc58]: Pulling fs layer. TOTAL DATA PULLED: 3 MB Error: error pulling image configuration: download failed after attempts=6: unexpected EOF tower-diagnostics-20230630-2317.zip

Great, thanks for your helpful suggestions. By the way, this is not related to my original question, but is it recommended to use something like the Dynamix File Integrity plugin so, in case of problems, I have some ideas of which file may have been corrupted?

Hi, Reporting back after I changed the SATA cable. Actually just before I swapped out the SATA cable, the number of errors from (non-correcting) parity checks reached over 700 after a few more runs. The same number of errors remained after I changed the SATA cable, but (not sure if it was the change of cable or re-seating the cable that did the trick) after I ran correcting parity check once, my system has remained error free. I have run at least 5 non-correcting parity checks since swapping the cable. Does this mean I can rest easy that there are no other faults in my array? tower-diagnostics-20220814-1823.zip

I am able to run memtest using the image from memtest86.com I am able to run memtest now. Thanks!

Hi, I am able to start my Unraid server just fine but when I select the memtest option during Unraid bootup, there is a prompt that says memtest is loading but memtest is never started. I have already tried to boot in legacy mode (motherboard is J3455-ITX) with the same USB drive but it does not seem to make any difference. Any suggestions how I can actually run memtest? Thanks.

I see. Let me find a spare SATA cable first and try again. Thanks!

Sorry, forgot to add that my server is configured not to start array automatically after a shutdown. This means both the first and second parity checks were initiated manually. Both checks show identical number of errors (40). Should I run parity-check a third time?

Hi all, There was a power outage and my server was not cleanly shutdown. When the array was brought back online, the parity check showed 40 errors. I re-ran the checks and there were still 40 errors, option "write corrections to parity" checked. Any suggestions on how I can resolve these errors? The server has not been rebooted after the initial parity check. Attached is the diagnostics report. Thanks very much in advance! tower-diagnostics-20220803-2323.zip