Hi,

 

Im having this odd occurrence where my server slows down after about 9 hours of uptime.

First docker containers are unconnectable until after a few minutes I cannot load a page in the GUI.

I suspect its something to do with docker but am unsure. Ive tried scrubbing the docker file but get no errors.

 

Diagnostics attached (from just before unraid totally froze)

plex-diagnostics-20210520-1849.zip syslog-192.168.1.111.log

Don't see any errors logged, but load average according to top is crazy high, one thing you can try is starting the dockers one at a time then wait a few hours before starting the next one to see if you find a culprit.

Ok so after a week of no issues I thought this was sorted. Ive had no crashes since my last post.

 

However last night I started a parity check and have woken up this morning to a crashed server.

Ive had a quick look at the logs (im not very adept at this) and have seen : ata8.00: exception Emask 0x10 SAct 0xf000 SErr 0x90002 action 0xe frozen

I think ata8 is my first parity drive so im going to try and move it to a different SATA port and try a different cable.

 

But could this alone by causing crashes? Any other issues people can see?

 

Logs attached

 

Cheers

 

syslog-192.168.1.111.log

I can't see which drive it is just by the log but it was parity in the previous diags, so likley still is.

 

There are also more ATA errors:

May 24 22:08:18 Plex kernel: ata9.00: failed to read SCR 1 (Emask=0x40)
May 24 22:08:18 Plex kernel: ata9.01: failed to read SCR 1 (Emask=0x40)
May 24 22:08:18 Plex kernel: ata9.02: failed to read SCR 1 (Emask=0x40)

 

And these show you're using SATA port multipliers, those should really be avoided.

17 minutes ago, JorgeB said:

 

 

There are also more ATA errors:

May 24 22:08:18 Plex kernel: ata9.00: failed to read SCR 1 (Emask=0x40)
May 24 22:08:18 Plex kernel: ata9.01: failed to read SCR 1 (Emask=0x40)
May 24 22:08:18 Plex kernel: ata9.02: failed to read SCR 1 (Emask=0x40)

 

And these show you're using SATA port multipliers, those should really be avoided.

 

Thats odd, im using PCI to SATA adapters. Perhaps the manufacturer has cheaped out.

These Asmedia controllers are two port SATA controllers:

 

03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
    Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:1060]
    Kernel driver in use: ahci
    Kernel modules: ahci
04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
    Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:1060]
    Kernel driver in use: ahci
    Kernel modules: ahci
05:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
    Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:1060]
    Kernel driver in use: ahci
    Kernel modules: ahci

 

If they have more than two ports they have SATA port multipliers (or are connected to an external enclosure with a port multiplier).

Ah thanks for that.

 

Ill have to look into getting them replaced, I will probably look for SAS to SATA card.

Hopefully in the short term this isnt the cause of my issue.

You can check bellow for a list of recommended controllers:

 

 

Thanks for the post, its simple and to the point.

 

 

Turns out I already have a 6 port Asmedia ASM1166 card lying about.

Sadly im limited to 1 PCIe x16 slot and the other 5 are PCIe x1 so im probably going to have to get a  4 port: Asmedia ASM1064 to cover my usage