slimshizn Posted August 8, 2018 Share Posted August 8, 2018 Quote Aug 8 00:50:28 Tower kernel: ata1.00: READ LOG DMA EXT failed, trying PIOAug 8 00:50:28 Tower kernel: ata1.00: exception Emask 0x0 SAct 0xff8 SErr 0x0 action 0x0Aug 8 00:50:28 Tower kernel: ata1.00: irq_stat 0x40000008Aug 8 00:50:28 Tower kernel: ata1.00: failed command: READ FPDMA QUEUEDAug 8 00:50:28 Tower kernel: ata1.00: cmd 60/00:30:40:27:58/05:00:29:00:00/40 tag 6 ncq dma 655360 inAug 8 00:50:28 Tower kernel: res 41/04:30:40:27:58/00:00:29:00:00/40 Emask 0x401 (device error) <F>Aug 8 00:50:28 Tower kernel: ata1.00: status: { DRDY ERR }Aug 8 00:50:28 Tower kernel: ata1.00: error: { ABRT }Aug 8 00:50:28 Tower kernel: ata1.00: configured for UDMA/133Aug 8 00:50:28 Tower kernel: ata1: EH completeAug 8 03:17:35 Tower kernel: mdcmd (58): spindown 2Aug 8 03:17:38 Tower kernel: mdcmd (59): spindown 3Aug 8 03:18:14 Tower kernel: sd 2:0:5:0: attempting task abort! scmd(ffff880ad1240d48)Aug 8 03:18:14 Tower kernel: sd 2:0:5:0: [sdh] tag#1 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00Aug 8 03:18:14 Tower kernel: scsi target2:0:5: handle(0x000f), sas_address(0x50014380163731e1), phy(33)Aug 8 03:18:15 Tower kernel: sd 2:0:5:0: task abort: SUCCESS scmd(ffff880ad1240d48)Aug 8 04:15:33 Tower crond[2583]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null These logs showed up this morning, any idea on what to do here? sdh seems to be working fine and shows no issues in the attributes. Quote Link to comment
pwm Posted August 8, 2018 Share Posted August 8, 2018 Looks like a possible cable issue or power glitch where you got a transfer error between machine and disk. It decided to try a slow PIO transfer instead of the normal fast UDMA. Then it later reported to use UDMA/133 again. Keep an eye on this to see if it happens again. 1 Quote Link to comment
slimshizn Posted August 8, 2018 Author Share Posted August 8, 2018 I will, That being said I did open the tower to add something. Might have hit a cable just right. Thanks for the information. Quote Link to comment
slimshizn Posted August 10, 2018 Author Share Posted August 10, 2018 (edited) Looks like I just had another one, a bit different this time. Aug 10 17:38:54 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Aug 10 17:38:54 Tower kernel: ata2.00: failed command: SMART Aug 10 17:38:54 Tower kernel: ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in Aug 10 17:38:54 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 10 17:38:54 Tower kernel: ata2.00: status: { DRDY } Aug 10 17:38:54 Tower kernel: ata2: hard resetting link Aug 10 17:38:55 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 10 17:38:55 Tower kernel: ata2.00: configured for UDMA/133 Aug 10 17:38:55 Tower kernel: ata2: EH complete Edited August 10, 2018 by slimshizn Quote Link to comment
slimshizn Posted August 10, 2018 Author Share Posted August 10, 2018 I'm using a LSI 9211-8i SAS2 with the HP SAS Expander on the X9DRi-LN4F Quote Link to comment
bonienl Posted August 11, 2018 Share Posted August 11, 2018 These kind of messages appear when the communication between controller and disk isn't stable. Usually it is a bad SATA cable, or the cable isn't properly inserted, or it might be a bad port on the controller. Have you tried? 1. Re-insert the SATA cable(s) 2. Replace the SATA cable(s) 3. Move to a different controller port 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.