Opened 8 months ago

Closed 6 months ago

#1320 closed enhancement (fixed)

Device not in database: CORSAIR FORCE LX SSD

Reported by: Mathias Owned by: Christian Franke
Priority: minor Milestone: Release 7.2
Component: drivedb Version:
Keywords: ssd Cc:

Description

My SSD is not in the smartmontools database.
smartctl-X report is attached.

Attachments (1)

smartctl-CORSAIR-FORCE_LX_SSD.txt (7.5 KB) - added by Mathias 8 months ago.
smartctl -x report of a CORSAIR FORCE LX SSD drive

Download all attachments as: .zip

Change History (7)

Changed 8 months ago by Mathias

smartctl -x report of a CORSAIR FORCE LX SSD drive

comment:1 Changed 7 months ago by Christian Franke

Keywords: ssd added
Milestone: Release 7.2

Could be added to existing entry Silicon Motion based SSDs.

comment:2 Changed 7 months ago by Mathias

Is there a way I could add the disk temporarily to some loca file?
There is a file /etc/smart_drivedb.h on openSUSE which right now is empty...
What would I put in there?

what really puzzles me though is the weird selftest log, must be a data format thing:

kumiko:~ # smartctl -l selftest /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.12.14-lp151.28.44-default] (SUSE RPM)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%       143         -
# 2  Offline             Completed without error       00%         1         -
# 3  Vendor (0x6d)       Fatal or unknown error        30%        34         569662208
# 4  Vendor (0xff)       Self-test routine in progress 150%     18704         -
# 5  Offline             Completed without error       00%         0         -
# 6  Reserved (0x21)     Completed without error       00%         0         -
# 7  Offline             Completed without error       00%         1         -
# 8  Vendor (0x6d)       Fatal or unknown error        30%        34         569665024
# 9  Vendor (0xff)       Self-test routine in progress 150%     18704         -
#10  Offline             Completed without error       00%         0         -
#11  Reserved (0x21)     Completed without error       00%         0         -
#12  Offline             Completed without error       00%         1         -
#13  Vendor (0x6d)       Fatal or unknown error        30%        34         569667072
#14  Vendor (0xff)       Self-test routine in progress 150%     18704         -
#15  Offline             Completed without error       00%         0         -
#16  Reserved (0x21)     Completed without error       00%         0         -
#17  Offline             Completed without error       00%         1         -
#18  Vendor (0x6e)       Fatal or unknown error        30%        34         569667840
#19  Vendor (0xff)       Self-test routine in progress 150%     18704         -
#20  Short offline       Completed without error       00%       139         -
#21  Abort offline test  Aborted by host               90%       139         -

I mean, ONE hour of lifetime? That SSD is about 6 years old... and it seems to repeat the same four entries over and over, too.

comment:3 Changed 7 months ago by Christian Franke

Copy the Silicon Motion based SSDs entry from ..../smartmontools/drivedb.h to /etc/smart_drivedb.h and add a pattern line to the long regex string, for example:

   { "Silicon Motion based SSDs",
     ...
     "CIS 2S M305 (16|32|64|128|256)GB|" // Ceroz M305, tested with CIS 2S M305 64GB/P0316B
+    "CORSAIR FORCE LX SSD|"
     "CT(120|250|500|1000)BX100SSD1|" // Crucial BX100, tested with CT250BX100SSD1/MU02,
     ...
   }

comment:4 Changed 7 months ago by Christian Franke

what really puzzles me though is the weird selftest log, must be a data format thing: ...

This is likely another case of a SSD firmware returning garbage in the self-test log data. This is unrelated to the drive database entry. For further diagnostics, feel free to create a separate ticket.

comment:5 Changed 6 months ago by Christian Franke

Owner: set to Christian Franke
Status: newaccepted

comment:6 Changed 6 months ago by Christian Franke

Resolution: fixed
Status: acceptedclosed
Note: See TracTickets for help on using tickets.