☰

Sata 포트는 1분마다 재설정됩니다. 케이블에 결함이 있습니까? 아니면 포트 멀티플라이어 카드(실리콘 이미지)입니까?

tag-icon • tag-icon ubuntu hard-drive sata
Sata 포트는 1분마다 재설정됩니다. 케이블에 결함이 있습니까? 아니면 포트 멀티플라이어 카드(실리콘 이미지)입니까?

내 우분투 서버에는아홉Silicon Image 기반의 "5-to-1 Sata 포트 멀티플라이어" 카드. syslog에 다음 메시지가 나타납니다. 이 메시지는 1분마다 반복됩니다. 제가 이해한 바로는 카드 중 하나에 몇 가지 문제가 있어 해당 카드에 대한 포트가 재설정되는 중입니다. 그리고 전체 프로세스를 재설정하는 데 약 4~5초가 소요됩니다.

누군가 이러한 오류로부터 무엇을 알아낼 수 있는지 말해 줄 수 있습니까? 카드를 교체해야 하나요? 아니면 케이블에 문제가 있는 걸까요? 케이블만 교체할 수도 있었지만 이 특정 서버 설계(맞춤 제작)에서는 케이블을 교체하는 데 많은 노력이 필요했습니다(카드 자체를 교체하는 것과 거의 동일함).

어떤 사람은 이 특정 카드에 연결된 하드 드라이브 중 하나가 원인일 수 있다고 말했습니다(회전하는 데 너무 오래 걸리는 등). 그게 사실인가요?

또한 smartctl이 카드의 모든 하드 드라이브에 많은 UDMA_CRC_Error_Count오류가 표시됩니다.

Sep 28 20:54:26 zapdb1 kernel: [56523.744913] ata15.00: failed to read SCR 1 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744921] ata15.00: failed to read SCR 0 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744924] ata15.01: failed to read SCR 1 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744929] ata15.01: failed to read SCR 0 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744932] ata15.02: failed to read SCR 1 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744936] ata15.02: failed to read SCR 0 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744939] ata15.03: failed to read SCR 1 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744943] ata15.03: failed to read SCR 0 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744946] ata15.04: failed to read SCR 1 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744950] ata15.04: failed to read SCR 0 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744953] ata15.05: failed to read SCR 1 (Emask=0x40)
Sep 28 20:54:26 zapdb1 kernel: [56523.744960] ata15.15: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 20:54:26 zapdb1 kernel: [56523.745009] ata15.15: irq_stat 0x00060002, PMP DMA CS errata
Sep 28 20:54:26 zapdb1 kernel: [56523.745040] ata15.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 20:54:26 zapdb1 kernel: [56523.745088] ata15.00: failed command: READ DMA EXT
Sep 28 20:54:26 zapdb1 kernel: [56523.745120] ata15.00: cmd 25/00:00:80:9e:91/00:04:52:00:00/e0 tag 1 dma 524288 in
Sep 28 20:54:26 zapdb1 kernel: [56523.745122]          res 86/15:06:06:00:00/00:00:c0:12:86/00 Emask 0x2 (HSM violation)
Sep 28 20:54:26 zapdb1 kernel: [56523.745212] ata15.00: status: { Busy }
Sep 28 20:54:26 zapdb1 kernel: [56523.745237] ata15.00: error: { IDNF ABRT }
Sep 28 20:54:26 zapdb1 kernel: [56523.745265] ata15.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 20:54:26 zapdb1 kernel: [56523.745311] ata15.01: irq_stat 0x00060002, device error via D2H FIS
Sep 28 20:54:26 zapdb1 kernel: [56523.745341] ata15.01: failed command: READ DMA EXT
Sep 28 20:54:26 zapdb1 kernel: [56523.745373] ata15.01: cmd 25/00:00:78:9e:91/00:04:52:00:00/e0 tag 2 dma 524288 in
Sep 28 20:54:26 zapdb1 kernel: [56523.745375]          res 51/84:61:17:a0:91/00:02:52:00:00/02 Emask 0x10 (ATA bus error)
Sep 28 20:54:26 zapdb1 kernel: [56523.745466] ata15.01: status: { DRDY ERR }
Sep 28 20:54:26 zapdb1 kernel: [56523.745492] ata15.01: error: { ICRC ABRT }
Sep 28 20:54:26 zapdb1 kernel: [56523.745519] ata15.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 20:54:26 zapdb1 kernel: [56523.745565] ata15.02: failed command: READ DMA EXT
Sep 28 20:54:26 zapdb1 kernel: [56523.745597] ata15.02: cmd 25/00:00:78:9e:91/00:04:52:00:00/e0 tag 0 dma 524288 in
Sep 28 20:54:26 zapdb1 kernel: [56523.745599]          res 86/15:06:06:00:00/00:00:00:01:86/00 Emask 0x2 (HSM violation)
Sep 28 20:54:26 zapdb1 kernel: [56523.745689] ata15.02: status: { Busy }
Sep 28 20:54:26 zapdb1 kernel: [56523.745714] ata15.02: error: { IDNF ABRT }
Sep 28 20:54:26 zapdb1 kernel: [56523.745741] ata15.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 20:54:26 zapdb1 kernel: [56523.745788] ata15.03: failed command: READ DMA EXT
Sep 28 20:54:26 zapdb1 kernel: [56523.745819] ata15.03: cmd 25/00:d8:98:9a:91/00:03:52:00:00/e0 tag 4 dma 503808 in
Sep 28 20:54:26 zapdb1 kernel: [56523.745821]          res 86/15:06:06:00:00/00:00:00:47:86/00 Emask 0x2 (HSM violation)
Sep 28 20:54:26 zapdb1 kernel: [56523.745911] ata15.03: status: { Busy }
Sep 28 20:54:26 zapdb1 kernel: [56523.745936] ata15.03: error: { IDNF ABRT }
Sep 28 20:54:26 zapdb1 kernel: [56523.745963] ata15.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 20:54:26 zapdb1 kernel: [56523.746010] ata15.04: failed command: READ DMA EXT
Sep 28 20:54:26 zapdb1 kernel: [56523.746041] ata15.04: cmd 25/00:d8:98:9a:91/00:03:52:00:00/e0 tag 3 dma 503808 in
Sep 28 20:54:26 zapdb1 kernel: [56523.746043]          res 86/15:06:06:00:00/00:00:80:37:86/00 Emask 0x2 (HSM violation)
Sep 28 20:54:26 zapdb1 kernel: [56523.746133] ata15.04: status: { Busy }
Sep 28 20:54:26 zapdb1 kernel: [56523.746158] ata15.04: error: { IDNF ABRT }
Sep 28 20:54:26 zapdb1 kernel: [56523.746185] ata15.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 28 20:54:26 zapdb1 kernel: [56523.746234] ata15.15: hard resetting link
Sep 28 20:54:26 zapdb1 kernel: [56523.746237] ata15: controller in dubious state, performing PORT_RST
Sep 28 20:54:29 zapdb1 kernel: [56525.973515] ata15.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
Sep 28 20:54:29 zapdb1 kernel: [56525.974240] ata15.00: hard resetting link
Sep 28 20:54:29 zapdb1 kernel: [56526.293478] ata15.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 28 20:54:29 zapdb1 kernel: [56526.293625] ata15.01: hard resetting link
Sep 28 20:54:29 zapdb1 kernel: [56526.613082] ata15.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 20:54:29 zapdb1 kernel: [56526.613131] ata15.02: hard resetting link
Sep 28 20:54:30 zapdb1 kernel: [56526.932262] ata15.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 20:54:30 zapdb1 kernel: [56526.932304] ata15.03: hard resetting link
Sep 28 20:54:30 zapdb1 kernel: [56527.252366] ata15.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 20:54:30 zapdb1 kernel: [56527.252417] ata15.04: hard resetting link
Sep 28 20:54:30 zapdb1 kernel: [56527.572270] ata15.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 20:54:30 zapdb1 kernel: [56527.572346] ata15.05: hard resetting link
Sep 28 20:54:31 zapdb1 kernel: [56527.891317] ata15.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320)
Sep 28 20:54:31 zapdb1 kernel: [56527.894471] ata15.00: configured for UDMA/33
Sep 28 20:54:31 zapdb1 kernel: [56527.897816] ata15.01: configured for UDMA/33
Sep 28 20:54:31 zapdb1 kernel: [56527.901165] ata15.02: configured for UDMA/33
Sep 28 20:54:31 zapdb1 kernel: [56527.904446] ata15.03: configured for UDMA/33
Sep 28 20:54:31 zapdb1 kernel: [56527.907628] ata15.04: configured for UDMA/33
Sep 28 20:54:31 zapdb1 kernel: [56527.908096] ata15: EH complete

답변1

나는 종종 이것이 전력 문제라는 것을 알았습니다. 드라이브에 공급되는 전원이 충분하지 않습니다.

관련 정보