#977 closed enhancement (fixed)
Please add Crucial MX500 to the database
| Reported by: | Cmdr_Zod | Owned by: | Christian Franke |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 7.0 |
| Component: | drivedb | Version: | 6.6 |
| Keywords: | Cc: | Holger Weiß |
Description
Please find attached the output of smartctl -q noserial -x /dev/sdX
According to press reviews, the MX500 uses Silicon Motion SM2258
Attachments (5)
Change History (18)
Changed 5 years ago by
| Attachment: | smartctl-CRUCIAL-MX500.txt added |
|---|
comment:1 Changed 5 years ago by
| Milestone: | → Release 6.7 |
|---|
comment:2 Changed 5 years ago by
comment:3 Changed 5 years ago by
Ticket #1024 (250GB) has been marked as a duplicate of this ticket.
comment:4 Changed 5 years ago by
Attached is a screenshot from Crucial's windows tool that shows some of the SMART ID mappings. From this thread in Crucial's support forums: https://forums.crucial.com/t5/Crucial-SSDs/MX500-SMART-parameters/m-p/184298/highlight/false#M55906
comment:5 Changed 5 years ago by
| Cc: | Holger Weiß added |
|---|
comment:6 Changed 5 years ago by
Please add for version 5.43 as well (sorry I'm not sure if this is done by default)
As it stands (on RHEL 6.9), smartmontools e-mails every few days (for both drives in a RAID mirrored array) with:
The following warning/error was logged by the smartd daemon:
Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
(or /dev/sdb)...but when I check manually, the "197 Current_Pending_Sector" shows zero maybe it returned to zero).
As noted by Ben B (I have the same issue):
https://listi.jpberlin.de/pipermail/smartmontools-database/2018-April/000176.html
"Note that one was originally displaying the warning about log count not
agreeing with the log buffer, and that both cause smartd to generate
occasional (every few day) warnings about "1 Currently unreadable (pending)
sectors" (which is what prompted me to dig in the first place). I suspect
the firmware isn't 100% correct."
In my RHEL 6.9 system, smartctl reports:
[sda] Warning: ATA error count 0 inconsistent with error log pointer 1
[sdb] Warning: ATA error count 0 inconsistent with error log pointer 2
Not sure how much of this is related to smartmontools and how much is Crucial firmware... Currently running M3CR020 firmware, will update to M3CR022 and see how things go.
Thanks, Antony.
Changed 5 years ago by
| Attachment: | smartctl-CT1000MX500SSD1.txt added |
|---|
Changed 5 years ago by
| Attachment: | smartctl_a_ct1000.sh added |
|---|
Decode new values for the Cruicial CT1000MX500SSD1, while waiting for the smartmon database to be updated
comment:7 Changed 5 years ago by
| Owner: | set to Christian Franke |
|---|---|
| Status: | new → accepted |
Changed 4 years ago by
comment:12 Changed 4 years ago by
I am afraid that this bug is not fixed. Even the latest firmware from Crucial (M3CR023) does not address the random reporting of a single unreadable sector.
comment:13 Changed 4 years ago by
I don't see any random reporting of a single unreadable sector in mx500.txt. BTW: If this only appears in the legacy SMART Error log, try smartctl -x -a ... to add legacy logs to the output.
Hiding a firmware bug would possibly require some clever heuristics or a new -F, --firmwarebug option. Feel free to propose this via a new ticket.
Don't reopen this ticket as it solely addresses the addition of MX500 to drive database.
Related: BX300, ticket #963.