Emask exception(s) causing hangups

[Foxilicious]

13 Jan 2018 - New comment has extra info

 

 

 

 

I'm not entirely sure if this has started occuring right after the latest update, my current version is 6.3.4.

The webGUI is slow, but usable, all my dockers appear to be working but are very slow as well.. Accessing shares doesn't always work either.

 

Is this a RAM issue? I've attached a screenshot showing my RAM usage, lots of it is cached, and barely any free.

Fix Common Problems found call traces (see attached image)

 

Any idea what's going on?

tower-diagnostics-20170521-1359.zip

Edited January 12, 2018 by Foxilicious
New title

[runraid]

What's your CPU usage look like? I had high CPU usage for several hours although nothing really interesting was happening on my machine. I found that once I restarted the Jackett container the CPU usage went back down to almost 0. Maybe try restarting containers one by one to see if any of them are consuming your CPU. 

[burtjr]

You have issues with ATA17 and 18

May 21 04:58:13 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 21 04:58:13 Tower kernel: ata17.00: failed command: WRITE DMA EXT
May 21 04:58:13 Tower kernel: ata17.00: cmd 35/00:58:88:cc:90/00:00:4f:00:00/e0 tag 6 dma 45056 out
May 21 04:58:13 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 21 04:58:13 Tower kernel: ata17.00: status: { DRDY }
May 21 04:58:13 Tower kernel: ata17: hard resetting link
May 21 04:58:13 Tower kernel: ata17: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May 21 04:58:13 Tower kernel: ata17.00: configured for UDMA/33
May 21 04:58:13 Tower kernel: ata17: EH complete

 

SAMSUNG drive HD204UIe

 

May 20 22:42:24 Tower kernel: ata18.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 20 22:42:24 Tower kernel: ata18.00: failed command: READ DMA EXT
May 20 22:42:24 Tower kernel: ata18.00: cmd 25/00:08:c8:d9:89/00:00:b1:00:00/e0 tag 30 dma 4096 in
May 20 22:42:24 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 20 22:42:24 Tower kernel: ata18.00: status: { DRDY }
May 20 22:42:24 Tower kernel: ata18: hard resetting link
May 20 22:42:24 Tower kernel: ata18: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 20 22:42:24 Tower kernel: ata18.00: configured for UDMA/133
May 20 22:42:24 Tower kernel: ata18: EH complete

 

 WD30EZRX-00SPEB0

 

You have a lot of downloading happening when these errors occurred and ATA:17 continues into a second log. I didn't see anything that stood out in the smart report for these 2 drives. I'll let someone chime in what the DRDY error is, but you could start by doing a clean shutdown and trying to reseat or replace your sata cables to those drives.

[JorgeB]

Looks more like a controller issue, can you post a link to your Asmedia controller since it's not the usual 2 port controller and identifies itself as a 12 ports controller (with 2 dummy ports).

[Foxilicious]

Apologies for the thread necro; up until now this issue hasn't bothered me much. But now that I am using my Unraid server more and more it's becoming too much of a nuisance..

 

@johnnie.black

This is the controller: http://www.delock.de/produkt/89384/pdf.html?sprache=en

which has the JMicron chipset; however it looks like an exact copy of: Ableconn PEX10-SAT which has ASMedia ASM1062 + 2x JMicron JMB575.

 

Since my post I have replaced the Samsung HD204UIe with a 4TB Red, thinking that one was the cause of the Emask errors.

 

I've been looking at replacements for the controller card, because I'm fairly sure that's the culprit; it's a cheap PoS...

 

Would the HP240 be a proper replacement?

 

 

Have also added a new diagnostics.

 

 

 

tower-diagnostics-20180112-2351.zip

Edited January 12, 2018 by Foxilicious
Forgot some words

[JorgeB]

That controller is no good, any SATA controller with port multipliers should be avoided.

 

Not sure what chipset the HP240 uses, nor if it's supported by unRAID, your best bet would be to gen an LSI controller, anything with a SAS2008/2308/3008 in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, etc and clones.

[Foxilicious]

22 minutes ago, johnnie.black said:

That controller is no good, any SATA controller with port multipliers should be avoided.

 

Not sure what chipset the HP240 uses, nor if it's supported by unRAID, your best bet would be to gen an LSI controller, anything with a SAS2008/2308/3008 in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, etc and clones.

 

Thought so.. thanks for the quick help!

[1812]

I run several h220's without issue... but most people tend to go for the LSI controllers.

[JorgeB]

I run several h220's without issue... but most people tend to go for the LSI controllers.

H220 is LSI 2308 based, I believe the H240 isn't LSI based.

[1812]

Just now, johnnie.black said:

4 minutes ago, 1812 said:

I run several h220's without issue... but most people tend to go for the LSI controllers.

H220 is LSI 2308 based, I believe the H240 isn't LSI based.

 

I feel like I kind of knew that somewhere in the back of my head, but regardless, we're not worthy!