#1311 closed defect (duplicate)
Crucial MX500 firmware M3CR010 also returns bogus attribute 197
| Reported by: | sersorrel | Owned by: | Christian Franke |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 7.2 |
| Component: | drivedb | Version: | |
| Keywords: | ssd | Cc: |
Description
#1227 prompted attribute 197 to be ignored for some Crucial MX500 drives, but not mine, despite mine exhibiting the same broken behaviour of an oscillating pending sector count.
The model number of my drive is CT1000MX500SSD1, and it has firmware M3CR010. Currently the drivedb only ignores the attribute for firmwares matching M3CR02[0-3].
Change History (6)
comment:1 Changed 4 years ago by
| Milestone: | → Release 7.2 |
|---|
comment:2 Changed 4 years ago by
| Owner: | set to Christian Franke |
|---|---|
| Status: | new → accepted |
comment:4 Changed 3 years ago by
| Milestone: | Release 7.2 |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
| Type: | enhancement → defect |
Reopen because new info is available, see ticket #1227.
comment:5 Changed 3 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | reopened → closed |
See ticket #1227.
Note: See
TracTickets for help on using
tickets.
Firmware regex should be changed to
M3CR0([01][0-9]|2[0-3])to match all versions <= M3CR023.