Fatal Docker Image Error (Unraid 6.9.2)

[hazmatt]

I've have Unraid set up for about a week, and am running 3 Docker containers.  Everything was working fine, then this morning my containers were not working.  I went to the "Apps" tab and got this error:

 

So that's what I am doing.  I am completely new to Unraid, and I've followed instructions to set up the containers.  Everything seems correct, the array is still running, just Docker is having a problem.

hazmatt-diagnostics-20211027-1149.zip

[trurl]

Your docker.img is corrupt. Since it isn't full I suspect the problem is due to the bad connection you have with cache2.

[hazmatt]

Dang.  Could it be the other cache drive (sdb)?  It has a "UDMA CRC error count" error every once in a while.

 

How do I go about fixing the docker.img?

[trurl]

14 minutes ago, hazmatt said:

Could it be the other cache drive (sdb)?

Actually, it looks like both cache drives.

Oct 24 14:15:55 Hoid kernel: ata2.00: ATA-10: HDSTOR - HSAV25ST250AX, HS210906145529030, R0427ANR, max UDMA/133
Oct 24 14:15:55 Hoid kernel: ata3.00: ATA-10: HDSTOR - HSAV25ST250AX, HS21090614552908F, R0427ANR, max UDMA/133
Oct 24 14:27:16 Hoid kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Oct 24 14:27:16 Hoid kernel: ata3.00: cmd 61/40:d0:a0:35:61/00:00:00:00:00/40 tag 26 ncq dma 32768 out
Oct 24 14:27:16 Hoid kernel:         res 40/00:d4:a0:35:61/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
Oct 24 14:27:16 Hoid kernel: ata3.00: status: { DRDY }
Oct 24 14:27:16 Hoid kernel: ata3: hard resetting link
Oct 25 10:14:20 Hoid kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Oct 25 10:14:20 Hoid kernel: ata2.00: cmd 61/80:a8:80:cc:a2/00:00:06:00:00/40 tag 21 ncq dma 65536 out
Oct 25 10:14:20 Hoid kernel:         res 40/00:ac:80:cc:a2/00:00:06:00:00/40 Emask 0x10 (ATA bus error)
Oct 25 10:14:20 Hoid kernel: ata2.00: status: { DRDY }
Oct 25 10:14:20 Hoid kernel: ata2: hard resetting link

 

[trurl]

Fix the hardware problems first, then you will have to recreate docker.img and reinstall your dockers.

 

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F

 

https://wiki.unraid.net/Manual/Troubleshooting#Restoring_your_Docker_Applications

[hazmatt]

Okay, thanks!  I appreciate the help.

[thorium220]

I have had this same error today, I've attached my diags. I'm also in a similar position to OP being a complete newb; this server's been running for about 5 weeks now.

 

I'm assuming that @trurl's instructions to remediate the issue will work for me as well, but I think the source of my error is different.

 

I can track the approximate time of this error commencing to me completely filling my cache drive during some large transfers, but my ability to interpret the exact cause from the syslog just isn't up to scratch. This is a re-used SSD that used to be a boot drive before I refreshed my main rig.

tower-diagnostics-20211105-2007.zip