jonaharndt Posted December 15, 2021 Share Posted December 15, 2021 After completing the parity check this morning, my machine has been crashing randomly. The only errors I see in the log are: exception Emask 0x100 SAct 0x7c0 SErr 0x0 action 0x6 frozen Along with this, Dec 15 15:09:17 Badlands kernel: ata7: SATA max UDMA/133 abar m512@0xfb510000 port 0xfb510100 irq 36 Dec 15 15:09:17 Badlands kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 15 15:09:17 Badlands kernel: ata7.15: Port Multiplier 1.2, 0x1b21:0x1092 r0, 3 ports, feat 0x5/0xf Dec 15 15:09:17 Badlands kernel: ata7.00: hard resetting link Dec 15 15:09:17 Badlands kernel: ata7.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Dec 15 15:09:17 Badlands kernel: ata7.01: hard resetting link Dec 15 15:09:17 Badlands kernel: ata7.01: SATA link down (SStatus 0 SControl 330) Dec 15 15:09:17 Badlands kernel: ata7.02: hard resetting link Dec 15 15:09:17 Badlands kernel: ata7.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Dec 15 15:09:17 Badlands kernel: ata7.00: ATA-10: ST2000DM008-2FR102, ZFL0EB2C, 0001, max UDMA/133 Dec 15 15:09:17 Badlands kernel: ata7.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Dec 15 15:09:17 Badlands kernel: ata7.00: configured for UDMA/133 Dec 15 15:09:17 Badlands kernel: ata7.02: ATA-10: ST2000DM008-2FR102, ZFL0DM2J, 0001, max UDMA/133 Dec 15 15:09:17 Badlands kernel: ata7.02: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Dec 15 15:09:17 Badlands kernel: ata7.02: configured for UDMA/133 Dec 15 15:09:17 Badlands kernel: ata7: EH complete Dec 15 15:09:17 Badlands kernel: sd 7:2:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Dec 15 15:09:17 Badlands kernel: sd 7:2:0:0: [sdi] 4096-byte physical blocks Dec 15 15:09:17 Badlands kernel: sd 7:2:0:0: [sdi] Write Protect is off Dec 15 15:09:17 Badlands kernel: sd 7:2:0:0: [sdi] Mode Sense: 00 3a 00 00 Dec 15 15:09:17 Badlands kernel: sd 7:2:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 15 15:09:17 Badlands kernel: sdi: sdi1 Dec 15 15:09:17 Badlands kernel: sd 7:2:0:0: [sdi] Attached SCSI disk Dec 15 15:09:56 Badlands emhttpd: ST2000DM008-2FR102_ZFL0DM2J (sdi) 512 3907029168 Dec 15 15:09:56 Badlands kernel: mdcmd (8): import 7 sdi 64 1953514552 0 ST2000DM008-2FR102_ZFL0DM2J Dec 15 15:09:56 Badlands kernel: md: import disk7: (sdi) ST2000DM008-2FR102_ZFL0DM2J size: 1953514552 Dec 15 15:09:56 Badlands emhttpd: read SMART /dev/sdi Dec 15 15:10:01 Badlands emhttpd: shcmd (27): echo 128 > /sys/block/sdi/queue/nr_requests Which occurs in two drives that were installed in the system about two weeks ago. I have already tried swapping the cables for these drives, and I am still getting the warnings, but no Emask error. These drives are plugged in via a HBA card along with another drive, that has no warnings/errors. I am wondering if this sounds like drive issues (both the same western digital 2tb model) or something else. Any help would be greatly appreciated! Quote Link to comment
trurl Posted December 15, 2021 Share Posted December 15, 2021 Attach Diagnostics to your NEXT post in this thread. Also setup Syslog Server Quote Link to comment
Recommended Posts
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.