howiser1 Posted June 16, 2020 Posted June 16, 2020 Disk 1 logged read disk errors and is now disabled. Here's the snippet from the logs. If you need a full Diag I'm happy to post. I did a Short SMART - and it came back: -- Completed without error -- Going to kick off an extended SMART overnight. No SMART errors or issues prior to this. Jun 15 07:41:57 Tower kernel: mdcmd (99): spindown 2 Jun 15 07:41:59 Tower kernel: mdcmd (100): spindown 5 Jun 15 07:42:04 Tower kernel: mdcmd (101): spindown 0 Jun 15 07:42:05 Tower kernel: mdcmd (102): spindown 6 Jun 15 10:48:30 Tower kernel: mdcmd (103): spindown 2 Jun 15 10:50:04 Tower kernel: mdcmd (104): spindown 1 Jun 15 10:50:05 Tower kernel: mdcmd (105): spindown 4 Jun 15 10:50:17 Tower kernel: mdcmd (106): spindown 0 Jun 15 10:50:18 Tower kernel: mdcmd (107): spindown 3 Jun 15 15:34:25 Tower kernel: mdcmd (108): spindown 3 Jun 15 20:06:33 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9878 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9878 Sense Key : 0x2 [current] Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9878 ASC=0x4 ASCQ=0x0 Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9878 CDB: opcode=0x88 88 00 00 00 00 01 1e 13 cf 50 00 00 00 40 00 00 Jun 15 20:06:33 Tower kernel: print_req_error: I/O error, dev sde, sector 4799582032 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799581968 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799581976 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799581984 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799581992 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799582000 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799582008 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799582016 Jun 15 20:06:33 Tower kernel: md: disk1 read error, sector=4799582024 Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9120 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9120 Sense Key : 0x2 [current] Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9120 ASC=0x4 ASCQ=0x0 Jun 15 20:06:33 Tower kernel: sd 1:0:0:0: [sde] tag#9120 CDB: opcode=0x8a 8a 00 00 00 00 01 1e 13 cf 50 00 00 00 40 00 00 Jun 15 20:06:33 Tower kernel: print_req_error: I/O error, dev sde, sector 4799582032 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799581968 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799581976 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799581984 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799581992 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799582000 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799582008 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799582016 Jun 15 20:06:33 Tower kernel: md: disk1 write error, sector=4799582024 Jun 15 20:07:01 Tower sSMTP[21923]: Creating SSL connection to host Jun 15 20:07:01 Tower sSMTP[21923]: SSL connection using TLS_AES_256_GCM_SHA384 Jun 15 20:07:04 Tower sSMTP[21923]: Sent mail for XXXXXXXXXXXXXXXXX (221 2.0.0 closing connection p44sm14351530qta.12 - gsmtp) uid=0 username=root outbytes=812 Jun 15 20:09:27 Tower kernel: sd 1:0:0:0: Power-on or device reset occurred Jun 15 21:09:27 Tower kernel: mdcmd (109): set md_write_method 1 Quote
trurl Posted June 16, 2020 Posted June 16, 2020 41 minutes ago, howiser1 said: full Diag Please save us the trouble of asking Quote
howiser1 Posted June 16, 2020 Author Posted June 16, 2020 Full Diag attached. Also the extended SMART passed with no issues. diagnostics-20200616-0722.zip Quote
JorgeB Posted June 16, 2020 Posted June 16, 2020 Disk looks fine, recommend replacing/swapping both cables to rule them out, then rebuild on top. Quote
howiser1 Posted June 16, 2020 Author Posted June 16, 2020 Thanks -- it's a break out cable from a LSI HBA controller. So not as simple as a single SATA cable replacement. Not sure what you mean by both cables? I'll re-seat all cables and then rebuild. If the issue comes back - I'll replace that entire breakout cable. Thanks again for your prompt review! Quote
JorgeB Posted June 16, 2020 Posted June 16, 2020 22 minutes ago, howiser1 said: So not as simple as a single SATA cable replacement. You can still swap with another disk. 22 minutes ago, howiser1 said: Not sure what you mean by both cables? SATA + Power cable Quote
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.