Custom Query (1365 matches)
Results (193 - 195 of 1365)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1294 | duplicate | Crucial MX500: bogus raw values in attribute 197 | ||
| Description |
Manjaro Linux, smartctl 7.1 (smartmontools 7.1-1) Since smartmontools has been updated from 7.0 to 7.1, I see the following error/warning about the Crucial MX500 SSD (Firmware version M3CR023) Warning This firmware returns bogus raw values in attribute 197 But this attribute, also checked in other utilities, doesn't report nothing of bad: 197,"Current Pending Sector Count","never","100","100","0","0","old age","-O--CK" As I dowgrade to smartctl 7.0, this warning disappear. |
|||
| #1306 | duplicate | DataError when trying to edit Wiki | ||
| Description |
I tried to add an entry to the list of supported USB devices and got the following error: DataError: (1406, "Data too long for column 'request' at row 1") Also on the error page there is a link to "Create a ticket". When I click that it tries to make a GET request to https://www.smartmontools.org/newticket with an extremely long URL containing all data of the Wiki page in question. |
|||
| #1311 | duplicate | Crucial MX500 firmware M3CR010 also returns bogus attribute 197 | ||
| 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 |
|||
