Opened 22 months ago

Closed 21 months ago

Last modified 18 months ago

#1642 closed defect (fixed)

Swapped Bad_Blk_Ct_Erl/Lat values in drivedb for "Phison Driven SSDs"

Reported by: matjon Owned by:
Priority: minor Milestone: Release 7.4
Component: drivedb Version:
Keywords: ssd Cc:



The drivedb currently contains the following entry:

  { "Phison Driven SSDs", // see MKP_521_Phison_SMART_attribute.pdf
    "-v 170,raw24/raw24:z54z10,Bad_Blk_Ct_Erl/Lat " // Early bad block/Later bad block

I think that the early and late bad block count values are swapped (late in place of early, early in place of late) and the description should be changed to "Bad_Blk_Ct_Lat/Erl".

According to the documentation in the PDF:

“Bad Block Count (Early / Later)”
Counts the number of Bad blocks.

Raw Value Byte [1~0]: Early bad block count
Raw Value Byte [5~4]: Later bad block count

I have a drive that identifies itself as SSDPR-CX400-512-G2. It is not yet in the database (I will submit it shortly), but the SMART parameters are very likely the same as in SSDPR-CX400-512 (based on comparing with a vendor's tool). Since birth, it had "146" as the raw uninterpreted value of this attribute:

170 Unknown_Attribute       PO----   100   100   000    -    146

but when I modify the drivedb and add it to a regex for "Phison Driven SSDs", it is displayed as:

170 Bad_Blk_Ct_Erl/Lat      PO----   100   100   000    -    0/146

I think that the best way to fix this problem is to change the description to "Bad_Blk_Ct_Lat/Erl" to avoid confusion for people that have historical smartctl outputs stored somewhere.



Change History (7)

comment:1 by matjon, 22 months ago

The "Phison Driven OEM SSDs" entry in the database is a copy of the "Phison Driven SSDs" entry and is probably also affected.

comment:2 by Christian Franke, 22 months ago

Keywords: ssd added
Milestone: unscheduled

Sounds reasonable, thanks for the info.

Do you have any info what Early and Late actually mean here?

comment:3 by matjon, 22 months ago

Unfortunately, I don't have any secret knowledge about the meaning of these parameters. The vendor documentation ( ​ ) is already explicitly mentioned in the DriveDB and it does not explicitly describe them.

I have two additional drives that match the "Phison Driven SSDs" entry in the DriveDB. Both are Patriot Burst drives. One of them has Bad_Blk_Ct_Lat/Erl = 0/106 since around birth (using the "fixed" decoding), the other went from 0/33 to 1/33 some time ago.

So probably the usual meaning applies here:

Early bad blocks are blocks that are detected as bad at the factory. [...] Later bad blocks are blocks that have gone bad since the drive left the factory. [...] ( )

comment:4 by Alex Samorukov, 21 months ago

Resolution: fixed
Status: newclosed

Fixed in r5411, thank you

comment:5 by Christian Franke, 20 months ago

Merged in r5416.

comment:6 by Christian Franke, 20 months ago

Milestone: unscheduledRelease 7.4

comment:7 by Matthew Eaton, 18 months ago

Hi guys, first, thanks for fixing this. Second, I can confirm this statement to be accurate:
Early bad blocks are blocks that are detected as bad at the factory. [...] Later bad blocks are blocks that have gone bad since the drive left the factory.

Note: See TracTickets for help on using tickets.