Opened 6 months ago

Last modified 8 weeks ago

#1843 new enhancement

Request to modify Smart Attribute for SK hynix's SE5110 product

Reported by: ksj0312 Owned by:
Priority: minor Milestone: unscheduled
Component: drivedb Version:
Keywords: ssd Cc:

Description

Hi,

While using SK hynix's SE5110 product for Smartctl tool, we noticed that there is a difference between the SMART Attendant output from smartctl and the value we set.
I would like to ask you to modify drivenb.h so that we can see the correct SMART attribute through smartctl tool.

  • Smart output from smartctl

ID# ATTRIBUTE_NAME FLAG
1 Raw_Read_Error_Rate 0x000e
5 Retired_Block_Count 0x0033
9 Power_On_Hours 0x0032
12 Power_Cycle_Count 0x0032
13 Read_Soft_Error_Rate 0x002e
173 Max_Erase_Count 0x0032
174 Unexpected_Pwr_Loss_Cnt 0x0030
175 Program_Fail_Count 0x0032
179 Used_Rsrvd_Blk_Cnt_Tot 0x0033
181 Program_Fail_Count 0x0032
182 Erase_Fail_Count 0x0032
184 End-to-End_Error 0x0032
187 Reported_Uncorrect 0x0032
194 Temperature_Celsius 0x0002
195 ECC_on_the_Fly_Rate 0x001a
197 Current_Pending_Sector 0x0032
198 Offline_Uncorrectable 0x0010
199 UDMA_CRC_Error_Count 0x003e
202 Exception_Mode_Status 0x0033
203 Run_Out_Cancel 0x0033
231 SSD_Life_Left 0x0033
235 Lifetime_Writes_GiB 0x0032
241 Lifetime_NAND_Prg_GiB 0x0032
242 Lifetime_Reads_GiB 0x0032

  • SMART we set

ID Attribute Flags
1 Raw Read Error Rate 0x000e
5 Reallocated Block Count 0x0033
9 Power On Hours 0x0032
12 Power Cycle Count 0x0032
13 ECC Rate 0x002e
173 Per Block Max Erase Count 0x0032
174 Unexpected Power Loss Count 0x0030
175 Average Erase Count 0x0032
179 Used Reserved Block Count (SSD Total) 0x0033
181 Program Fail Count 0x0032
182 Erase Fail Count 0x0032
184 End-to-End Error Detection Count 0x0032
187 Reported Uncorrectable Errors 0x0032
194 Temperature 0x0002
195 Reported UECC 0x001a
197 Current Pending Sector Count 0x0032
198 Offline Scan Uncorrectable Sector Count 0x0010
199 Ultra DMA CRC Error Count 0x003e
202 Exception mode status (Read-only mode) 0x0033
203 Volatile Memory Backup Source Failure 0x0033
231 SSD Life Left 0x0033
235 Host Write In GB 0x0032
241 Nand Programs In GB 0x0032
242 Lifetime Reads From The Host in GB 0x0032

Attachments (2)

smartctl-skhynix-HFS480G3H2X069Ntxt.txt (12.4 KB ) - added by ksj0312 6 months ago.
smart we set.txt (6.2 KB ) - added by ksj0312 6 months ago.

Download all attachments as: .zip

Change History (10)

by ksj0312, 6 months ago

Attachment: smart we set.txt added

comment:1 by Christian Franke, 6 months ago

Milestone: undecided

Please provide a patch which clarifies the requested changes.

comment:2 by ksj0312, 6 months ago

I would like to ask you to change it so that it can be printed with the following attributes.

1 Raw_Read_Error_Rate
5 Retired_Block_Count ==> Reallocated Block Count
9 Power_On_Hours
12 Power_Cycle_Count
13 Read_Soft_Error_Rate ==> ECC Rate
173 Max_Erase_Count => Per Block Max Erase Count
174 Unexpected_Pwr_Loss_Cnt
175 Program_Fail_Count ==> Average Erase Count
179 Used_Rsrvd_Blk_Cnt_Tot
181 Program_Fail_Count
182 Erase_Fail_Count
184 End-to-End_Error
187 Reported_Uncorrect
194 Temperature_Celsius
195 ECC_on_the_Fly_Rate ==> Reported UECC
197 Current_Pending_Sector
198 Offline_Uncorrectable
199 UDMA_CRC_Error_Count
202 Exception_Mode_Status
203 Run_Out_Cancel ==> Volatile Memory Backup Source Failure
231 SSD_Life_Left
235 Lifetime_Writes_GiB ==> Host Write In GB
241 Lifetime_NAND_Prg_GiB ==> Nand Programs In GB
242 Lifetime_Reads_GiB ==> Lifetime Reads From The Host in GB

comment:3 by Christian Franke, 6 months ago

Which other SK hynix devices are affected by this change?

Model Family:     SK hynix SATA SSDs
Device Model:     HFS480G3H2X069N
Add. Product Id:  DELL(tm)
Firmware Version: DZ02

Is this Attribute set specific to this (Dell specific?) firmware?

comment:4 by ksj0312, 6 months ago

There are four model names for the device requesting a change as follows.
1) HFS480G3H2X069N
2) HFS960G3H2X069N
3) HFS1T9G3H2X069N
4) HFS3T8G3H2X069N

This attribute value is not for a specific Firmware (ex. Dell), but is applied to Firmware of our Generic SATAs.

comment:5 by ksj0312, 2 months ago

I wonder when this request will be applied to drivenb.h ...

comment:6 by Christian Franke, 2 months ago

Milestone: undecidedunscheduled

Please see the FAQ.

A tested(!) patch would ease integration.

comment:7 by ksj0312, 8 weeks ago

How do you make a patch??
Is it different from the two txt files I attached?

comment:8 by Christian Franke, 8 weeks ago

Yes, a patch is diff -u, svn diff or git diff output describing the changes suitable for the patch tool.

For an example see the Unified Diff output of the recent drivedb.h change r5625.

Note: See TracTickets for help on using tickets.