rkotara Posted February 26 Share Posted February 26 (edited) TLDR: I've had Preclear fail on all 3 drives I just installed in my system using a Dell Perc H310 controller flash to IT mode. No smart errors, does that mean its the controller? I just installed a Dell H310 6Gbps SAS HBA (LSI 9211-8i) with IT MODE firmware. I added it to a free PCIe 16x slot and cabled up 3 refurb drives (which is why I want to preclear). I started Preclear on one, then seeing how long it would take (days), started the other two. All have failed since and that seems very unlikely. The failures all seem to be read errors and different points. There are no SMART issues from the data I can see. Breakout cables are new and all 3 drives failing seem to point to the controller. I guess its a bad controller? Any insight would be appreciated, thanks! preclear_disk_8DJGT6JH_21015.txt tower-diagnostics-20240226-1401.zip preclear_disk_9JH30AWT_27151.txt preclear_disk_8DJGT6JH_21015.txt Edited February 26 by rkotara Added Server Diags Quote Link to comment
dlandon Posted February 26 Share Posted February 26 Please post your full server diagnostics. Quote Link to comment
rkotara Posted February 26 Author Share Posted February 26 (edited) Thanks, just added that and the other preclear error logs. Edited February 26 by rkotara Quote Link to comment
Solution dlandon Posted February 26 Solution Share Posted February 26 You have disk errors: Feb 26 11:06:20 Tower kernel: scsi_io_completion_action: 812 callbacks suppressed Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2596 CDB: opcode=0x88 88 00 00 00 00 05 10 38 4a f0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: blk_print_req_error: 812 callbacks suppressed Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746961136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2597 CDB: opcode=0x88 88 00 00 00 00 05 10 38 4a f0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746961136 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: buffer_io_error: 401 callbacks suppressed Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370142, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2598 CDB: opcode=0x88 88 00 00 00 00 05 10 38 50 e0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746962656 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2599 CDB: opcode=0x88 88 00 00 00 00 05 10 38 50 e0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746962656 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370332, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2602 CDB: opcode=0x88 88 00 00 00 00 05 10 38 56 d0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746964176 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2603 CDB: opcode=0x88 88 00 00 00 00 05 10 38 56 d0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746964176 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370522, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2604 CDB: opcode=0x88 88 00 00 00 00 05 10 38 5c c0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746965696 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2605 CDB: opcode=0x88 88 00 00 00 00 05 10 38 5c c0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746965696 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370712, async page read Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2606 CDB: opcode=0x88 88 00 00 00 00 05 10 38 62 b0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746967216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 Sense Key : 0x2 [current] Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 ASC=0x4 ASCQ=0x0 Feb 26 11:06:20 Tower kernel: sd 7:0:2:0: [sdd] tag#2607 CDB: opcode=0x88 88 00 00 00 00 05 10 38 62 b0 00 00 00 08 00 00 Feb 26 11:06:20 Tower kernel: I/O error, dev sdd, sector 21746967216 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718370902, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371092, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371282, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371472, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371662, async page read Feb 26 11:06:20 Tower kernel: Buffer I/O error on dev sdd, logical block 2718371852, async page read Feb 26 11:06:22 Tower kernel: sd 7:0:2:0: Power-on or device reset occurred ### [PREVIOUS LINE REPEATED 1 TIMES] ### Feb 26 11:06:24 Tower kernel: sd 7:0:15:0: Power-on or device reset occurred Things to look at: Power supply. Cabling - power and/or data. If you're running three drives at once, I'd suspect a power supply issue. Quote Link to comment
rkotara Posted February 27 Author Share Posted February 27 Thanks for the diag on this. I do recall that I was not very confident of the Molex to Sata power connector but everything powered up fine. I'll swap things out until its stable, thanks!! Quote Link to comment
rkotara Posted March 1 Author Share Posted March 1 Replaced the sata power cable extension I had on hand (Monoprice 108794) with one from Cable Matters and all is well so far. No more drops on the drives after 24 hours of running preclear on all 3 drives so far. Will update if anything changes. 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.