6.5.2 - xsf drive with 128 read errors

graywolf

By graywolf
in General Support

Recommended Posts

graywolf Enthusiast

graywolf

Posted
Posted

Been so long and many versions ago since had an issue.

First time since been on xfs

Trying to find the troubleshooting link to determine what to do next.

 

Please help point me in the right direction 

May 20 04:40:01 Tower root: Fix Common Problems Version 2018.04.25
May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 Sense Key : 0x3 [current]
May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 ASC=0x11 ASCQ=0x0
May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 02 35 2f 28 00 00 04 00 00 00
May 20 04:43:06 Tower kernel: print_req_error: critical medium error, dev sde, sector 37039912
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039848
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039856
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039864
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039872
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039880
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039888
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039896
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039904
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039912
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039920
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039928
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039936
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039944
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039952
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039960
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039968
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039976
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039984
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039992
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040000
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040008
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040016
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040024
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040032
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040040
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040048
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040056
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040064
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040072
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040080
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040088
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040096
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040104
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040112
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040120
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040128
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040136
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040144
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040152
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040160
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040168
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040176
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040184
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040192
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040200
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040208
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040216
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040224
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040232
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040240
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040248
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040256
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040264
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040272
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040280
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040288
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040296
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040304
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040312
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040320
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040328
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040336
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040344
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040352
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040360
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040368
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040376
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040384
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040392
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040400
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040408
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040416
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040424
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040432
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040440
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040448
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040456
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040464
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040472
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040480
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040488
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040496
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040504
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040512
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040520
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040528
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040536
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040544
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040552
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040560
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040568
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040576
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040584
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040592
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040600
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040608
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040616
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040624
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040632
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040640
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040648
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040656
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040664
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040672
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040680
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040688
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040696
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040704
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040712
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040720
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040728
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040736
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040744
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040752
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040760
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040768
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040776
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040784
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040792
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040800
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040808
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040816
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040824
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040832
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040840
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040848
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040856
May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040864

 

Link to comment
John_M Experienced

John_M

Posted
Posted

On the face of it "critical medium error" seems to suggest that disk14 has failed but, looking at its SMART report, it seems ok. The SMART does indicate a recent issue but it's more consistent with a failure to communicate with the host. The output from your HBA is too cryptic for me to decipher but what I would do is shut down and check/replace the cable or move to a different backplane slot and run an extended SMART test.

Link to comment
graywolf Enthusiast

graywolf

Posted
  • Author
Posted
1 hour ago, John_M said:

On the face of it "critical medium error" seems to suggest that disk14 has failed but, looking at its SMART report, it seems ok. The SMART does indicate a recent issue but it's more consistent with a failure to communicate with the host. The output from your HBA is too cryptic for me to decipher but what I would do is shut down and check/replace the cable or move to a different backplane slot and run an extended SMART test.

 

Thanks John_M. 

Shut down

Checked cables 

Start up

Running extended SMART test

 

We'll see how it goes (fingers crossed)

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing