#1220 closed defect (invalid)
smartctl tests are not logged for SanDisk SDSSDA240G drive
| Reported by: | Artem S. Tashkinov | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | smartctl | Version: | |
| Keywords: | ata | Cc: |
Description
It looks like smartctl tools cannot properly handle the SanDisk SDSSDA240G drive: whenever I try to run long/short/etc. tests, they are not stored in the SMART log. According to "Self-test execution status" they are indeed run.
SanDisk SSD Dashboard utility can run both short and long tests but no matter which test is run, short logs are always recorded:
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% 36 - # 2 Short offline Completed without error 00% 35 - # 3 Short offline Completed without error 00% 30 - # 4 Short offline Completed without error 00% 18 - # 5 Short offline Completed without error 00% 5 -
Also LifeTime is completely wrong. I've used this drive for at least 1000 hours.
SanDisk SSD Dashboard utility does not show logs at all.
I'm curious what's going on, whether it's special firmware which is not handled correctly or some issue with my drive.
Attachments (1)
Change History (6)
by , 6 years ago
| Attachment: | smartctl-x.log added |
|---|
comment:1 by , 6 years ago
| Component: | all → smartctl |
|---|---|
| Keywords: | ata added |
comment:2 by , 6 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
This is a (usually harmless) drive firmware bug.
comment:3 by , 6 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
This is a (usually harmless) drive firmware bug.
Do you keep a DB of buggy drives in smartctl? It would be great to have one, so that smartctl -a/-x could output something like:
"This drive has certain firmware bugs which prevents smartctl from working with it correctly, see PR1220".
Sorry for reopening this bug report - I just need this question to be answered and closed bug reports rarely draw any attention at all.
comment:4 by , 6 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
This is a (usually harmless) drive firmware bug.
Please don't reopen tickets to solely ask questions. Use smartmontools-support mailinglist instead.
comment:5 by , 6 years ago
Do you keep a DB of buggy drives in smartctl?
No. Too less unpaid open source spare time to add such minor features.
The self-test log contains a lot of other useless garbage (marked with
[...]):All (except Selective) Self-Test Logs are R/O, see
Log Directory. Smartctl does not store entries in the self-test log(s). Smartctl issues the ATA command to start the test. The drive firmware shall run the test then and shall store the result in the self-test log(s) after test completion.