I'm about to upgrade my parity drive, so I'm getting everything set. Looking at some SMART reports, the only disk I have any reason to worry about shows the following:

  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    5
  3 Spin_Up_Time            POS--K   185   175   021    -    7733
  4 Start_Stop_Count        -O--CK   100   100   000    -    857
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   100   253   000    -    0
  9 Power_On_Hours          -O--CK   075   075   000    -    18930
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   253   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    39
192 Power-Off_Retract_Count -O--CK   200   200   000    -    30
193 Load_Cycle_Count        -O--CK   197   197   000    -    11446
194 Temperature_Celsius     -O---K   128   102   000    -    24
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    1

 

Checking back a few logs, 1 and 200 are stable in that neither has gone up. If that's the case, should I just keep monitoring (and still feel comfortable upgrading parity, assuming I stop array, make a backup of config, and keep the old parity drive set in case something happens), or should I get that disk replaced first?

 

Thanks!

Edited November 25, 20187 yr by Idaho121

If both attributes are stable and there are no recent read errors (UNC @ LBA on the bottom of the SMART report), I say monitor for now.

Would it be in this section?

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            1  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            2  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4       160495  Vendor specific

No, you could just post the full SMART report.