Hard disk problem

[SSD]

Curious if my old trusty Hitachi 2T UD is starting to fail.

 

Here is the smart report

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   131   131   054    Pre-fail  Offline      -       108
  3 Spin_Up_Time            0x0007   115   115   024    Pre-fail  Always       -       624 (Average 629)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1370
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   121   121   020    Pre-fail  Offline      -       35
  9 Power_On_Hours          0x0012   093   093   000    Old_age   Always       -       53681
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       352
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       2339
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       2339
194 Temperature_Celsius     0x0002   240   240   000    Old_age   Always       -       25 (Min/Max 8/38)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

Taken after I say this in my syslog

 

Quote

Mar 12 17:22:28 merlin kernel: sd 10:0:3:0: [sdm] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Mar 12 17:22:28 merlin kernel: sd 10:0:3:0: [sdm] tag#0 CDB: opcode=0x28 28 00 82 52 40 27 00 00 08 00
Mar 12 17:22:28 merlin kernel: print_req_error: I/O error, dev sdm, sector 2186428455

 

Any thoughts?

[tdallen]

Maybe run a long test if you haven’t yet?

[JorgeB]

SMART looks perfect, and it's difficult to interpret the LSI errors codes, but looks more like a connection issue.

[Kode]

I'd agree with johnnie.black, SMART looks perfect.  I read somewhere that connection errors usually show up under 199, but that is empty as well.

[JorgeB]

11 minutes ago, Kode said:

I read somewhere that connection errors usually show up under 199

That's for CRC errors, timeout errors don't appear on SMART, I was referring to the error opcode=0x28 28 00 82 52 40 27 00 00 08 00

Edited March 13, 2018 by johnnie.black

[SSD]

I'll keep an eye on it and see if I get repeats. 

 

@Squid - not sure if this is a good candidate for a FCP warning.

[coolspot]

I'm seeing this exact same error, but different sector on a few of my drives:

 

Mar 12 17:22:28 merlin kernel: sd 10:0:3:0: [sdm] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
Mar 12 17:22:28 merlin kernel: sd 10:0:3:0: [sdm] tag#0 CDB: opcode=0x28 28 00 82 52 40 27 00 00 08 00
Mar 12 17:22:28 merlin kernel: print_req_error: I/O error, dev sdm, sector 2186428455

 

In my case:

 

[Sun Jun 23 13:05:35 2019] sd 1:0:28:0: [sdab] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
[Sun Jun 23 13:05:35 2019] sd 1:0:28:0: [sdab] tag#18 CDB: opcode=0x28 28 00 00 01 62 c0 00 02 00 00
[Sun Jun 23 13:05:35 2019] print_req_error: I/O error, dev sdab, sector 90816

I don't think it's a disk failure ... but rather something to do with SMART or controller communication with the drive. When I had the unassigned plugin installed I was seeing a lot more of these errors. 

 

I think it's more of a compatibility issue than hardware error. The error above is from a Crucial M500 running off a LSI 9207-8i on a BPN-SAS2-826EL2 backplane.

[Squid]

3 minutes ago, coolspot said:

but rather something to do with SMART or controller communication with the drive

You should post the full diagnostics before  you reboot to put the error(s) in context

 

3 minutes ago, coolspot said:

Crucial M500 running off a LSI 9207-8i

Just an FYI, but most HBA's do not properly (if at all) support TRIM on an attached SSD.  You're far better off connecting it directly to the motherboard

[coolspot]

3 hours ago, Squid said:

You should post the full diagnostics before  you reboot to put the error(s) in context

 

Just an FYI, but most HBA's do not properly (if at all) support TRIM on an attached SSD.  You're far better off connecting it directly to the motherboard

 

The LSI 9207 does detect the drive as a SATA-SSD, does that mean it supports TRIM?

 

If TRIM is not supported, can it be run manually via a schedule? Does that work or does it mean that even manual TRIM won't work on HBAs.

[JorgeB]

8 hours ago, coolspot said:

The LSI 9207 does detect the drive as a SATA-SSD, does that mean it supports TRIM?

It does but only with SSDs that support read zeros after trim, which the MX500 doesn't, so trim won't work, use the onboard SATA ports instead.