Call Traces found on your server

[antihero412]

I cant figure out why i keep getting this error in fix common problems.  i woke up this morning and all my dockers showed offline.  i couldn't start them so i deleted the docker img and started fresh.  know when i create a new docker i get server error.   here is my diagnostic info.

 

Can someone please help 

docker.txt

libvirt.txt

syslog.1.txt

syslog.2.txt

syslog.last200.txt

syslog.txt

[trurl]

Please post the complete diagnostics zip so we get all the information we need in a single download.

 

Have you read the sections of the Docker FAQ that talks about docker image filling up?

 

https://lime-technology.com/forums/topic/57181-real-docker-faq/

 

[antihero412]

Here is all the files Zipped up.

logs.zip

[trurl]

I'm sorry. I meant go to Tools - Diagnostics and get the complete diagnostics zip. Those others may be useful too if they were generated by Fix Common Problems, but you should always start with the complete diagnostics zip.

[antihero412]

oh ok. this is straight from  tools diagnostics sorry about that

unraid-diagnostics-20180313-0927.rar

[trurl]

Tools - Diagnostics downloads a zip file for you to give us. Why have you attached a .rar?

 

 

[antihero412]

because i use Winrar and i opened the file and repacked it ill send the original

unraid-diagnostics-20180313-0927.zip

[trurl]

Your docker image is not currently full, but it is corrupt. And you have it set to 50G, which makes me think you are trying to solve this problem by making it very large. If you have things setup correctly it is unlikely you will even need 20G.

 

Have you looked at the FAQ I linked?

 

What dockers are you running?

[antihero412]

Ya. I did make it bigger because I thought maybe it was running out of space. The only thing that I know has happen was my cache got full when radarr and deluge was using it when downloading   When I woke up it showed that the cache had been filled up and it stopped all the dockers

 

[antihero412]

I’m running radarr, sonarr Deluge jacket Plex duplicate and krusader. 

[JorgeB]

Besides what trurl mentioned your syslog is filled with timeout errors on both cache device, check cables:

 

Mar 12 15:10:15 UnRaid kernel: ata1.00: status: { DRDY }
Mar 12 15:10:15 UnRaid kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Mar 12 15:10:15 UnRaid kernel: ata1.00: cmd 61/08:e8:80:08:04/00:00:00:00:00/40 tag 29 ncq dma 4096 out
Mar 12 15:10:15 UnRaid kernel:         res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 12 15:10:15 UnRaid kernel: ata1.00: status: { DRDY }
Mar 12 15:10:15 UnRaid kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Mar 12 15:10:15 UnRaid kernel: ata1.00: cmd 61/80:f0:c0:a6:a9/00:00:0a:00:00/40 tag 30 ncq dma 65536 out
Mar 12 15:10:15 UnRaid kernel:         res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 12 15:10:15 UnRaid kernel: ata1.00: status: { DRDY }
Mar 12 15:10:15 UnRaid kernel: ata1: hard resetting link
Mar 12 15:10:17 UnRaid kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 12 15:10:22 UnRaid kernel: ata1.00: qc timeout (cmd 0xec)
Mar 12 15:10:22 UnRaid kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Mar 12 15:10:22 UnRaid kernel: ata1.00: revalidation failed (errno=-5)
Mar 12 15:10:22 UnRaid kernel: ata1: hard resetting link
Mar 12 15:10:22 UnRaid kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 12 15:10:22 UnRaid kernel: ata1.00: configured for UDMA/133
Mar 12 15:10:22 UnRaid kernel: ata1: EH complete
Mar 12 15:18:30 UnRaid kernel: ata3.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
Mar 12 15:18:30 UnRaid kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Mar 12 15:18:30 UnRaid kernel: ata3.00: cmd 61/08:00:b8:01:05/00:00:03:00:00/40 tag 0 ncq dma 4096 out
Mar 12 15:18:30 UnRaid kernel:         res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 12 15:18:30 UnRaid kernel: ata3.00: status: { DRDY }
Mar 12 15:18:30 UnRaid kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Mar 12 15:18:30 UnRaid kernel: ata3.00: cmd 61/20:08:c0:01:05/00:00:03:00:00/40 tag 1 ncq dma 16384 out
Mar 12 15:18:30 UnRaid kernel:         res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 12 15:18:30 UnRaid kernel: ata3.00: status: { DRDY }
Mar 12 15:18:30 UnRaid kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Mar 12 15:18:30 UnRaid kernel: ata3.00: cmd 61/18:10:e0:01:05/00:00:03:00:00/40 tag 2 ncq dma 12288 out
Mar 12 15:18:30 UnRaid kernel:         res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 12 15:18:30 UnRaid kernel: ata3.00: status: { DRDY }

 

[trurl]

If you are filling up cache then you might want to reconsider how you are using it. I have most of my shares set to not use cache, since most of my writes are unattended downloads and backups and it doesn't matter if they are a little slower since I'm not waiting on them anyway.

[antihero412]

i think ill try setting the shares that are using radarr and sonarr and deluge to not use cache and see if that helps with me filling up my cache

[antihero412]

ill check the cables also thank you guys for your help.