Out of Memory and Call Trace Errors

[ok4ayl]

Hello Everyone 

 

So the last few days i have been getting out of Memory Errors and Call Traces found on my unraid Server. i am thinking it might have to do with Plex Docker but not positive on that. Attached is the system Diagnostics and a screen shot of the errors i am seeing. has any one seen this issue and if so how would you fix it?   i could see being out of memory if i only had a gig or two but i am running 32gigs with 8 Split out for a windows VM right now and the rest is available the rest of the system.  Let me know what you guys think and thank you for all your help. 

 

 
   

ratchet-diagnostics-20171230-0739.zip

[JorgeB]

This usually helps:

https://forums.lime-technology.com/topic/55910-out-of-memory-errors-detected-on-your-server-call-traces-found-on-your-server/?do=findComment&comment=546982

 

P.S.: You're also having some ATA errors, check cables:

 

Dec 29 20:58:31 Ratchet kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 29 20:58:31 Ratchet kernel: ata14.00: cmd a0/00:00:00:02:00/00:00:00:00:00/a0 tag 28 pio 16388 in
Dec 29 20:58:31 Ratchet kernel:         opcode=0x51 51 00 00 00 00 00 00 00 02 00res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Dec 29 20:58:31 Ratchet kernel: ata14.00: status: { DRDY }
Dec 29 20:58:31 Ratchet kernel: ata14: hard resetting link
Dec 29 20:58:31 Ratchet kernel: ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 29 20:58:31 Ratchet kernel: ata14.00: configured for UDMA/100
Dec 29 20:58:31 Ratchet kernel: ata14: EH complete

Dec 29 21:03:22 Ratchet kernel: ata9.00: exception Emask 0x10 SAct 0x7fffe00 SErr 0x400000 action 0x6 frozen
Dec 29 21:03:22 Ratchet kernel: ata9.00: irq_stat 0x08000000, interface fatal error
Dec 29 21:03:22 Ratchet kernel: ata9: SError: { Handshk }
Dec 29 21:03:22 Ratchet kernel: ata9.00: failed command: WRITE FPDMA QUEUED
Dec 29 21:03:22 Ratchet kernel: ata9.00: cmd 61/00:48:40:78:19/08:00:05:00:00/40 tag 9 ncq dma 1048576 ou
Dec 29 21:03:22 Ratchet kernel:         res 40/00:d4:40:00:1a/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
Dec 29 21:03:22 Ratchet kernel: ata9.00: status: { DRDY }
Dec 29 21:03:22 Ratchet kernel: ata9.00: failed command: WRITE FPDMA QUEUED
Dec 29 21:03:22 Ratchet kernel: ata9.00: cmd 61/00:50:40:80:19/08:00:05:00:00/40 tag 10 ncq dma 1048576 ou
Dec 29 21:03:22 Ratchet kernel:         res 40/00:d4:40:00:1a/00:00:05:00:00/40 Emask 0x10 (ATA bus error)

 

ATA9 is this one:

Dec 29 20:56:32 Ratchet kernel: ata9.00: ATA-8: WDC WD3000HLHX-01JJPV0,      WD-WX91EC1ANCS8, 04.05G04, max UDMA/133

 

ATA14 is a BD drive.

[ok4ayl]

So i Replaced the Cables on both the ata9 and ATA14 Drives.   Looking though the system logs looks like ATA9 might have been resloved.  but looks like ATA14 is still having issues.  ATA14 is a BD Drive i have setup on a Sata PCI-e Card. the PCI-E Card i think is bad since when i over the Cable to another port on the card the system doesnt see the drive. i am thinking i probably should look at replacing the card.   below is the newest log files after replacing the cables.    thank you for all your help.   

ratchet-diagnostics-20171230-1010.zip

[JorgeB]

It might be because it's a BD drive, or because of the controller it's in, if it's just a couple of ATA errors and you don't notice any issues ignore, the disk ones are much more important.