Jump to content

Network drops


Recommended Posts

May  1 19:40:30 Tower kernel: sky2 0000:06:00.0: error interrupt status=0x80000000
May  1 19:40:30 Tower kernel: sky2 0000:06:00.0: PCI hardware error (0x2010)

Looks like a NIC problem, I would try a different one, Intel preferred.

 

Also lots of ATA errors:

 

Apr 30 02:22:04 Tower kernel: ata5.00: exception Emask 0x10 SAct 0xf000 SErr 0x190002 action 0xe frozen
Apr 30 02:22:04 Tower kernel: ata5.00: irq_stat 0x80400000, PHY RDY changed
Apr 30 02:22:04 Tower kernel: ata5: SError: { RecovComm PHYRdyChg 10B8B Dispar }
Apr 30 02:22:04 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED
Apr 30 02:22:04 Tower kernel: ata5.00: cmd 60/20:60:c0:b5:6f/00:00:83:00:00/40 tag 12 ncq dma 16384 in
Apr 30 02:22:04 Tower kernel:         res 40/00:70:40:b6:6f/00:00:83:00:00/40 Emask 0x10 (ATA bus error)
Apr 30 02:22:04 Tower kernel: ata5.00: status: { DRDY }
Apr 30 02:22:04 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED

This is parity, could be a cable issue, could be the Marvell controller.

 

Apr 30 02:52:30 Tower kernel: ata8.01: status: { DRDY }
Apr 30 02:52:30 Tower kernel: ata8.01: failed command: WRITE FPDMA QUEUED
Apr 30 02:52:30 Tower kernel: ata8.01: cmd 61/20:70:20:9d:76/00:00:83:00:00/40 tag 14 ncq dma 16384 out
Apr 30 02:52:30 Tower kernel:         res 40/00:90:80:91:78/00:00:83:00:00/40 Emask 0x4 (timeout)
Apr 30 02:52:30 Tower kernel: ata8.01: status: { DRDY }
Apr 30 02:52:30 Tower kernel: ata8.01: failed command: WRITE FPDMA QUEUED
Apr 30 02:52:30 Tower kernel: ata8.01: cmd 61/20:78:e0:9d:76/00:00:83:00:00/40 tag 15 ncq dma 16384 out
Apr 30 02:52:30 Tower kernel:         res 40/00:90:80:91:78/00:00:83:00:00/40 Emask 0x4 (timeout)
Apr 30 02:52:30 Tower kernel: ata8.01: status: { DRDY }
Apr 30 02:52:30 Tower kernel: ata8.01: failed command: WRITE FPDMA QUEUED
Apr 30 02:52:30 Tower kernel: ata8.01: cmd 61/20:80:80:ab:76/00:00:83:00:00/40 tag 16 ncq dma 16384 out
Apr 30 02:52:30 Tower kernel:         res 40/00:90:80:91:78/00:00:83:00:00/40 Emask 0x4 (timeout)

This is disk2, same Marvell controller but with a SATA port multiplier, could also be a cable issue but Marvell controllers and port multipliers should not be used with Unraid.

 

Intel SATA controller is set to IDE mode and only has one disk connected, set it to AHCI and use those ports before any add-on controller.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...