Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#1181 closed patch (fixed)

HFS(480|960|1T9|3T8)G3(2|E)FEH-7(4|A)10A SMART attributes

Reported by: xelama Owned by: Christian Franke
Priority: minor Milestone: Release 7.1
Component: drivedb Version: 7.0
Keywords: ssd Cc:


Attachments (1) (46.0 KB) - added by xelama 3 years ago.

Download all attachments as: .zip

Change History (9)

Changed 3 years ago by xelama

Attachment: added

comment:1 Changed 3 years ago by Christian Franke

Keywords: ssd added
Milestone: Release 7.1
Priority: majorminor
Type: taskpatch


comment:2 Changed 3 years ago by xelama

Could you please let me know due date as it's a bit urgent for our users.

comment:3 Changed 3 years ago by Christian Franke

Sorry, no due date as we do all this in unpaid spare time.

Note that it is possible to add a local database file which is automatically loaded if present. See -B option on smartctl man page or smartctl -h output for default path.

comment:4 Changed 3 years ago by xelama

Thank for the response and your time.
Will try to confirm whether this option works for our users or they have to wait for database update.
Thanks again.

comment:5 Changed 3 years ago by Christian Franke

Owner: set to Christian Franke
Status: newaccepted

comment:6 Changed 3 years ago by Christian Franke

Resolution: fixed
Status: acceptedclosed

comment:7 Changed 3 years ago by xelama

Could you please clarify why did you comment out necessary attributes for "HFS(480|960|1T9|3T8)G3(2|E)FEH-7(4|A)10A" drives?
It is completely new drives and SMART should not be mixed with previously added hynix drives.

Please note that full list of attributes should stay as:

"", "",
"-v 1,raw48,Read_Error_Rate "
"-v 5,raw48,Retired_Blk_Cnt "
"-v 9,raw48,Power_On_Hours "
"-v 12,raw48,Device_Power_Cycle_Cnt "
"-v 171,raw48,Program_Fail_Cnt "
"-v 172,raw48,Erase_Fail_Cnt "
"-v 174,raw48,Unexpected_Pwr_Loss_Cnt "
"-v 175,raw48,Program_Fail_Cnt "
"-v 176,raw48,Erase_Fail_Cnt "
"-v 177,raw48,Endurance_Limit_Met "
"-v 178,raw48,Used_Rsrvd_Blk_Cnt_Wrst "
"-v 179,raw48,Used_Rsrvd_Blk_Cnt_Tot "
"-v 180,raw48,E2E_Error_Det_Corr_Rate "
"-v 181,raw48,Program_Fail_Cnt "
"-v 182,raw48,Erase_Fail_Cnt "
"-v 183,raw48,SATA_Downshift_Cnt "
"-v 184,raw48,E2E_Error_Det_Corr_Cnt "
"-v 187,raw48,Reported_Uncorr_Error "
"-v 188,raw48,Command_Timeout_Cnt "
"-v 194,tempminmax,Temperature "
"-v 195,raw48,ECC_on_the_Fly_Rate "
"-v 199,raw48,Ultra_DMA_CRC_Error_Cnt "
"-v 201,raw48,Uncorr_Soft_Read_Err_Rt "
"-v 204,raw48,Soft_ECC_Correction_Rt "
"-v 231,raw48,SSD_Life_Left "
"-v 234,raw48,Lifetime_NAND_Prg_GB "
"-v 241,raw48,Lifetime_Writes_Host_GB "
"-v 242,raw48,Lifetime_Reads_Host_GB "
"-v 245,raw48,SSD_Life_Left "
"-v 250,raw48,Total_Number_Read_Retry "

Version 0, edited 3 years ago by xelama (next)

comment:8 Changed 3 years ago by Christian Franke

Yes, attributes not defined in an entry are taken from the "DEFAULT" entry. If -v settings for an SSD are equivalent to the default, I usually keep this setting as a comment in the new entry.

Note: See TracTickets for help on using tickets.