Custom Query (1564 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (415 - 417 of 1564)

Ticket Resolution Summary Owner Reporter
#293 invalid Incomplete support for fixed format sense data somebody maciej3
Description

File scsiata.cpp contains comments claiming that it supports fixed format response to SCSI request sense command (response code 0x70 and 0x71). Indeed, the implementation of sat_device::ata_pass_through() parses such responses correctly and returns true. However, it does not fill the descriptor buffer (adrp). Function smartcommandhandler() in atacmds.cpp calls sat_device::ata_pass_through() and fails if descriptor values are absent, specifically lba_high and lba_mid. It is not clear to me how this should be fixed:

  1. Use a different logic when fixed format is returned (instead of checking lba_high and lba_mid),
  2. Or, issue SCSI request sense command with the DESC bit set, which would force the descriptor format. As that may cause problems with older devices, perhaps a parameter should be introduced, settable in drivedb.h.

User-visible symptoms of this bug are:

  1. smartd refuses to monitor the affected drive, producing an error such as: "Device: /dev/sdd [SAT], not capable of SMART Health Status check"
  2. smartctl shows SMART info correctly, but with a complaint: "SMART STATUS RETURN: incomplete response, ATA output registers missing"

This problem was noticed with external USB drive: WD MyPassport 2TB (WDBY8L0020BBL), USB: 1058:0748

#318 invalid Spam somebody altas
#323 invalid Report for Western Digital Red drive doesn't make sense somebody aviram
Description

This is part of the 'smartctl -x /dev/sdf' output for a brand new WD Red 4TB drive that passed several self-tests:

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   100   253   051    -    0
  3 Spin_Up_Time            POS--K   100   253   021    -    0
  4 Start_Stop_Count        -O--CK   100   100   000    -    2
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   100   100   000    -    10
 10 Spin_Retry_Count        -O--CK   100   253   000    -    0
 11 Calibration_Retry_Count -O--CK   100   253   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    2
192 Power-Off_Retract_Count -O--CK   200   200   000    -    1
193 Load_Cycle_Count        -O--CK   200   200   000    -    2
194 Temperature_Celsius     -O---K   108   108   000    -    44
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--   100   253   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

It has pre-fail flags on 3 attributes that have 0 (zero) as raw values.

Why are those attributes marked as pre-fail ? Is this a bug on smartmontools or I am interpreting this in a wrong way ? Or should I configure drivedb.h correctly for this drive? Any tip on where to find WD documentation for these values?

Thank you

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.