ahsano0 Posted November 4, 2018 Share Posted November 4, 2018 So I faced this issue a few days ago, when unraid showed Parity disk as FAULTY. I removed it from the array, started the array without parity, stooped again and added Parity. It took some time to rebuild parity and everything was working fine until today it happened again. Seems like this time, I cannot do the same. Here's the log of my Parity disk, please let me know if I have to post some other logs/stats too. Please check attached image also. Quote Nov 4 13:19:55 Tower kernel: ata12: SATA max UDMA/133 abar m512@0xfbc00000 port 0xfbc00180 irq 55 Nov 4 13:19:55 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 4 13:19:55 Tower kernel: ata12.00: ATA-9: WDC WD4003FZEX-00Z4SA0, WD-WMC5D0DA17MU, 01.01A01, max UDMA/133 Nov 4 13:19:55 Tower kernel: ata12.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Nov 4 13:19:55 Tower kernel: ata12.00: configured for UDMA/133 Nov 4 13:19:55 Tower kernel: sd 12:0:0:0: [sdk] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Nov 4 13:19:55 Tower kernel: sd 12:0:0:0: [sdk] 4096-byte physical blocks Nov 4 13:19:55 Tower kernel: sd 12:0:0:0: [sdk] Write Protect is off Nov 4 13:19:55 Tower kernel: sd 12:0:0:0: [sdk] Mode Sense: 00 3a 00 00 Nov 4 13:19:55 Tower kernel: sd 12:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 4 13:19:55 Tower kernel: sdk: sdk1 Nov 4 13:19:55 Tower kernel: sd 12:0:0:0: [sdk] Attached SCSI disk Nov 4 13:19:58 Tower emhttp: WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0DA17MU (sdk) 3907018532 Nov 4 13:32:04 Tower kernel: ata12.00: exception Emask 0x10 SAct 0x0 SErr 0x800000 action 0x6 frozen Nov 4 13:32:04 Tower kernel: ata12.00: irq_stat 0x08000000, interface fatal error Nov 4 13:32:04 Tower kernel: ata12: SError: { LinkSeq } Nov 4 13:32:04 Tower kernel: ata12.00: failed command: CHECK POWER MODE Nov 4 13:32:04 Tower kernel: ata12.00: cmd e5/00:00:00:00:00/00:00:00:00:00/40 tag 13 Nov 4 13:32:04 Tower kernel: ata12.00: status: { DRDY } Nov 4 13:32:04 Tower kernel: ata12: hard resetting link Nov 4 13:32:14 Tower kernel: ata12: softreset failed (1st FIS failed) Nov 4 13:32:14 Tower kernel: ata12: hard resetting link Nov 4 13:32:24 Tower kernel: ata12: softreset failed (1st FIS failed) Nov 4 13:32:24 Tower kernel: ata12: hard resetting link Nov 4 13:32:59 Tower kernel: ata12: softreset failed (1st FIS failed) Nov 4 13:32:59 Tower kernel: ata12: limiting SATA link speed to 3.0 Gbps Nov 4 13:32:59 Tower kernel: ata12: hard resetting link Nov 4 13:32:59 Tower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 4 13:32:59 Tower kernel: ata12.00: configured for UDMA/133 Nov 4 13:32:59 Tower kernel: ata12: EH complete Nov 4 13:34:29 Tower emhttp: WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0DA17MU (sdk) 3907018532 Nov 4 13:34:31 Tower emhttp: WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0DA17MU (sdk) 3907018532 Nov 4 13:35:00 Tower emhttp: WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0DA17MU (sdk) 3907018532 Nov 4 13:35:00 Tower kernel: mdcmd (1): import 0 sdk 3907018532 0 WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0DA17MU Nov 4 13:35:00 Tower kernel: md: import disk0: (sdk) WDC_WD4003FZEX-00Z4SA0_WD-WMC5D0DA17MU size: 3907018532 Nov 4 13:35:10 Tower emhttp: shcmd (287): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Nov 4 13:35:10 Tower emhttp: shcmd (288): echo 128 > /sys/block/sdk/queue/nr_requests Nov 4 13:35:11 Tower kernel: ata12.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen Nov 4 13:35:11 Tower kernel: ata12.00: irq_stat 0x08000000, interface fatal error Nov 4 13:35:11 Tower kernel: ata12: SError: { Handshk } Nov 4 13:35:11 Tower kernel: ata12.00: failed command: WRITE DMA EXT Nov 4 13:35:11 Tower kernel: ata12.00: cmd 35/00:40:c8:98:e1/00:05:e8:00:00/e0 tag 21 dma 688128 out Nov 4 13:35:11 Tower kernel: ata12.00: status: { DRDY } Nov 4 13:35:11 Tower kernel: ata12: hard resetting link Nov 4 13:35:21 Tower kernel: ata12: softreset failed (1st FIS failed) Nov 4 13:35:21 Tower kernel: ata12: hard resetting link Nov 4 13:35:31 Tower kernel: ata12: softreset failed (1st FIS failed) Nov 4 13:35:31 Tower kernel: ata12: hard resetting link Nov 4 13:36:06 Tower kernel: ata12: softreset failed (1st FIS failed) Nov 4 13:36:06 Tower kernel: ata12: limiting SATA link speed to 1.5 Gbps Nov 4 13:36:06 Tower kernel: ata12: hard resetting link Nov 4 13:36:11 Tower kernel: ata12: softreset failed (1st FIS failed) Nov 4 13:36:11 Tower kernel: ata12: reset failed, giving up Nov 4 13:36:11 Tower kernel: ata12.00: disabled Nov 4 13:36:11 Tower kernel: ata12: EH complete Nov 4 13:36:11 Tower kernel: sd 12:0:0:0: [sdk] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:36:11 Tower kernel: sd 12:0:0:0: [sdk] tag#23 CDB: opcode=0x8a 8a 00 00 00 00 00 e8 e1 98 c8 00 00 05 40 00 00 Nov 4 13:36:11 Tower kernel: blk_update_request: I/O error, dev sdk, sector 3907098824 Nov 4 13:36:11 Tower kernel: sd 12:0:0:0: [sdk] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:36:11 Tower kernel: sd 12:0:0:0: [sdk] tag#24 CDB: opcode=0x8a 8a 00 00 00 00 00 e8 e1 9e 08 00 00 02 c8 00 00 Nov 4 13:36:11 Tower kernel: blk_update_request: I/O error, dev sdk, sector 3907100168 Nov 4 13:37:36 Tower kernel: sd 12:0:0:0: [sdk] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:37:36 Tower kernel: sd 12:0:0:0: [sdk] tag#27 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Nov 4 13:37:36 Tower kernel: sd 12:0:0:0: [sdk] tag#29 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:37:36 Tower kernel: sd 12:0:0:0: [sdk] tag#29 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 4 13:37:37 Tower kernel: sd 12:0:0:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:37:37 Tower kernel: sd 12:0:0:0: [sdk] tag#1 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Nov 4 13:37:37 Tower kernel: sd 12:0:0:0: [sdk] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:37:37 Tower kernel: sd 12:0:0:0: [sdk] tag#3 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#15 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#17 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#20 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:40:35 Tower kernel: sd 12:0:0:0: [sdk] tag#22 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 4 13:41:06 Tower emhttp: shcmd (436): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Nov 4 13:41:06 Tower emhttp: shcmd (437): echo 128 > /sys/block/sdk/queue/nr_requests Nov 4 13:41:06 Tower kernel: sd 12:0:0:0: [sdk] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:41:06 Tower kernel: sd 12:0:0:0: [sdk] tag#13 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Nov 4 13:41:06 Tower kernel: sd 12:0:0:0: [sdk] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:41:06 Tower kernel: sd 12:0:0:0: [sdk] tag#15 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 4 13:41:06 Tower emhttp: shcmd (454): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Nov 4 13:41:06 Tower emhttp: shcmd (455): echo 128 > /sys/block/sdk/queue/nr_requests Nov 4 13:42:22 Tower kernel: sd 12:0:0:0: [sdk] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 4 13:42:22 Tower kernel: sd 12:0:0:0: [sdk] tag#28 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e0 00 Link to comment
JorgeB Posted November 4, 2018 Share Posted November 4, 2018 Please post your diagnostics: Tools -> Diagnostics Link to comment
ahsano0 Posted November 4, 2018 Author Share Posted November 4, 2018 Here you are: tower-diagnostics-20181104-1433.zip Link to comment
JorgeB Posted November 4, 2018 Share Posted November 4, 2018 Diags are right after rebooting, but disk looks fine, replace cables and try again. Link to comment
ahsano0 Posted November 4, 2018 Author Share Posted November 4, 2018 Yea I rebooted and now it is working fine. Building parity again. But this sure isn't cable problem. Because last time it happened, I was using an HBA and now I've changed everything and all my drives are connected directly to the motherboard. I can tell you that parity drive runs on little higher temps as compared to the others, and I don't know which drives makes sound but I can hear the random read/write sound when something is running. Do you still think it is normal? I mean why is it happening again and again? And thanks alot for taking time to check the logs and reply back. Link to comment
JorgeB Posted November 4, 2018 Share Posted November 4, 2018 No, it's not normal, and if it continues to happen to the same disk even when used with a different controller and cables then it's likely a disk problem despite the healthy looking SMART. Link to comment
ahsano0 Posted November 4, 2018 Author Share Posted November 4, 2018 Alright, thanks a lot for you help sire. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.