Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#618 closed enhancement (worksforme)

Add Crucial_CT960M500SSD1 to database

Reported by: Vincent Danjean Owned by:
Priority: minor Milestone: Release 6.4
Component: drivedb Version: 6.3
Keywords: Cc:

Description (last modified by Christian Franke)

Hi,
I've a disk that is not in the smart database:

Device Model:     Crucial_CT960M500SSD1
Serial Number:    14010960553B
LU WWN Device Id: 5 00a075 10960553b
Firmware Version: MU03
User Capacity:    960 197 124 096 bytes [960 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]

Looking for information, I found #326 and referenced commits 3925 and 3926 that suggests me that I should be just needed to add the reference of my disk in smartctl database, hence this bug report.
Here is the current report of smartctl (with smartmontools 6.3+svn4002 as in the Debian package):

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
5 Reallocated_Sector_Ct   0x0033   100   100   000    Pre-fail  Always       -       0
9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       14138
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       24
171 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
173 Unknown_Attribute       0x0032   094   094   000    Old_age   Always       -       204
174 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       8
180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   000   000   000    Pre-fail  Always       -       16523
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   061   050   000    Old_age   Always       -       39 (Min/Max 0/50)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       16
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
202 Unknown_SSD_Attribute   0x0031   094   094   000    Pre-fail  Offline      -       6
206 Unknown_SSD_Attribute   0x000e   100   100   000    Old_age   Always       -       0
210 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
246 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       14853124027
247 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       696996831
248 Unknown_Attribute       0x0032   100   100   ---    Old_age   Always       -       3912597374

The current drivedb.h does not seem to list my disk for now (I did not compile and test the last svn commit, I just looked at the sources) :
trunk/smartmontools/drivedb.h:
[...]

    "Crucial_CT(120|240|480)M500SSD[13]", // Marvell 88SS9187 BLD2, tested with Crucial_CT120M500SSD3/MU02,
    // Crucial_CT120M500SSD1/MU02, Crucial_CT240M500SSD1/MU03, Crucial_CT480M500SSD1/MU03

[...]

Regards,

Vincent

Change History (3)

comment:1 Changed 5 years ago by Christian Franke

Description: modified (diff)
Milestone: Release 6.5
Priority: majorminor
Summary: Attribute for SSDAdd Crucial_CT960M500SSD1 to database

comment:2 Changed 5 years ago by Christian Franke

Milestone: Release 6.5Release 6.4
Resolution: worksforme
Status: newclosed

This was already added in r4017 and included in smartmontools 6.4.

comment:3 Changed 5 years ago by Christian Franke

I did not compile and test the last svn commit, I just looked at the sources

Please note that there is no need to compile the last commit.

You could also update the drive database separately.

Note: See TracTickets for help on using tickets.