November 7, 20178 yr I'm getting a lot of errors in my log but I can't seem to trace these to a specific drive. Any help would be appreciated. This is the log during a parity rebuild on a new drive. Nov 7 19:36:15 NAS kernel: ata36.00: failed to read SCR 1 (Emask=0x40)Nov 7 19:36:15 NAS kernel: ata36.01: failed to read SCR 1 (Emask=0x40)Nov 7 19:36:15 NAS kernel: ata36.02: failed to read SCR 1 (Emask=0x40)Nov 7 19:36:15 NAS kernel: ata36.03: failed to read SCR 1 (Emask=0x40)Nov 7 19:36:15 NAS kernel: ata36.04: failed to read SCR 1 (Emask=0x40)Nov 7 19:36:15 NAS kernel: ata36.15: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozenNov 7 19:36:15 NAS kernel: ata36.15: irq_stat 0x08000000, interface fatal errorNov 7 19:36:15 NAS kernel: ata36.15: SError: { Handshk }Nov 7 19:36:15 NAS kernel: ata36.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozenNov 7 19:36:15 NAS kernel: ata36.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozenNov 7 19:36:15 NAS kernel: ata36.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozenNov 7 19:36:15 NAS kernel: ata36.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozenNov 7 19:36:15 NAS kernel: ata36.03: failed command: WRITE DMA EXTNov 7 19:36:15 NAS kernel: ata36.03: cmd 35/00:40:00:fc:d3/00:05:00:00:00/e0 tag 21 dma 688128 outNov 7 19:36:15 NAS kernel: res 50/00:00:ff:fb:d3/00:00:00:00:00/e0 Emask 0x100 (unknown error)Nov 7 19:36:15 NAS kernel: ata36.03: status: { DRDY }Nov 7 19:36:15 NAS kernel: ata36.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozenNov 7 19:36:15 NAS kernel: ata36.15: hard resetting linkNov 7 19:36:16 NAS kernel: ata36.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)Nov 7 19:36:16 NAS kernel: ata36.00: hard resetting linkNov 7 19:36:16 NAS kernel: ahci 0000:0b:00.0: FBS is disabledNov 7 19:36:16 NAS kernel: ahci 0000:0b:00.0: FBS is enabledNov 7 19:36:16 NAS kernel: ata36.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)Nov 7 19:36:16 NAS kernel: ata36.01: hard resetting linkNov 7 19:36:16 NAS kernel: ahci 0000:0b:00.0: FBS is disabledNov 7 19:36:17 NAS kernel: ahci 0000:0b:00.0: FBS is enabledNov 7 19:36:17 NAS kernel: ata36.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330)Nov 7 19:36:17 NAS kernel: ata36.02: hard resetting linkNov 7 19:36:17 NAS kernel: ata36.02: SATA link down (SStatus 0 SControl 330)Nov 7 19:36:17 NAS kernel: ata36.03: hard resetting linkNov 7 19:36:17 NAS kernel: ahci 0000:0b:00.0: FBS is disabledNov 7 19:36:17 NAS kernel: ahci 0000:0b:00.0: FBS is enabledNov 7 19:36:17 NAS kernel: ata36.03: SATA link up 1.5 Gbps (SStatus 113 SControl 310)Nov 7 19:36:17 NAS kernel: ata36.04: hard resetting linkNov 7 19:36:18 NAS kernel: ata36.04: SATA link down (SStatus 0 SControl 330)Nov 7 19:36:18 NAS kernel: ata36.00: configured for UDMA/133Nov 7 19:36:18 NAS kernel: ata36.01: configured for UDMA/133Nov 7 19:36:18 NAS kernel: ata36.03: configured for UDMA/133Nov 7 19:36:18 NAS kernel: ata36: EH complete nas-diagnostics-20171107-2049.zip Edited November 7, 20178 yr by Fpsware
November 7, 20178 yr Community Expert ATA36 is a port multiplier, those are not recommended: Nov 7 17:16:49 NAS kernel: ata36.15: Port Multiplier 1.2, 0x1b4b:0x9705 r160, 5 ports, feat 0x1/0x1f You have 3 disks connected to it, if possible use a different controller. Nov 7 17:16:49 NAS kernel: ata36.00: ATA-8: WDC WD2000F9YZ-09N20L1, WD-WMC1P0F4KVE0, 01.01A02, max UDMA/133 Nov 7 17:16:49 NAS kernel: ata36.01: ATA-9: ST2000DM001-1ER164, W4Z20P1E, CC45, max UDMA/133 Nov 7 17:17:02 NAS kernel: ata36.03: ATA-8: WDC WD10EALX-009BA0, WD-WCATR4937587, 15.01H15, max UDMA/133
November 7, 20178 yr Author Not sure what a port multiplayer is but .... UnRaid is running on an ESXi server. The SATA controller is passed through and all drives are connected to the same, single controller.
November 7, 20178 yr Community Expert Then the Marvell controller you're using has a bultin port multiplier, it's used to add more ports by allowing multiple devices on a single SATA port, I'd recommend using a different controller, preferably an LSI.
Archived
This topic is now archived and is closed to further replies.