Custom Query (1552 matches)

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.

In the currently nightly, smartctl, when used on /dev/nvmeX rathern than /dev/nvmeXn1, selects the wrong device when two identical nvme modules are installed. Example:

# ls -l nvme-Samsung_SSD_970_EVO_2TB_S464NB0M200088N | cut -c40-
nvme-Samsung_SSD_970_EVO_2TB_S464NB0M200088N -> ../../nvme0n1
# ls -l nvme-Samsung_SSD_970_EVO_2TB_S464NB0M200161Y | cut -c40-
nvme-Samsung_SSD_970_EVO_2TB_S464NB0M200161Y -> ../../nvme1n1

# ./smartctl -a /dev/nvme0n1 | sed -n '1p;5,7p'
smartctl 7.1 2019-07-01 r4934 [x86_64-linux-4.18.0-24-generic] (local build)
Model Number:                       Samsung SSD 970 EVO 2TB
Serial Number:                      S464NB0M200088N
Firmware Version:                   2B2QEXE7
# ./smartctl -a /dev/nvme1n1 | sed -n '1p;5,7p'
smartctl 7.1 2019-07-01 r4934 [x86_64-linux-4.18.0-24-generic] (local build)
Model Number:                       Samsung SSD 970 EVO 2TB
Serial Number:                      S464NB0M200161Y
Firmware Version:                   2B2QEXE7

# ./smartctl -a /dev/nvme0 | sed -n '1p;5,7p'
smartctl 7.1 2019-07-01 r4934 [x86_64-linux-4.18.0-24-generic] (local build)
Model Number:                       Samsung SSD 970 EVO 2TB
Serial Number:                      S464NB0M200161Y
Firmware Version:                   2B2QEXE7
# ./smartctl -a /dev/nvme1 | sed -n '1p;5,7p'
smartctl 7.1 2019-07-01 r4934 [x86_64-linux-4.18.0-24-generic] (local build)
Model Number:                       Samsung SSD 970 EVO 2TB
Serial Number:                      S464NB0M200088N
Firmware Version:                   2B2QEXE7

On OpenBSD-current @powerpc smartctl 6.0 segfaults, here there are some info:

$ sudo smartctl -i /dev/wd0c smartctl 6.0 2012-10-10 r3643 [powerpc-unknown-openbsd5.2] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

Segmentation fault (core dumped)

Program received signal SIGSEGV, Segmentation fault. strcmp (s1=0xfffd5403 "ec2hour", s2=0x20436f6d <Address 0x20436f6d out of bounds>) at /usr/src/lib/libc/string/strcmp.c:47 47 while (*s1 == *s2++) Current language: auto; currently c (gdb) bt #0 strcmp (s1=0xfffd5403 "ec2hour", s2=0x20436f6d <Address 0x20436f6d out of bounds>) at /usr/src/lib/libc/string/strcmp.c:47 #1 0x0180bd54 in parse_attribute_def (opt=Variable "opt" is not available. ) at /usr/obj/ports/smartmontools-6.0/smartmontools-6.0/atacmds.cpp:213 #2 0x0181bf7c in parse_db_presets (presets=0x18588c4 "-v 9,seconds", defs=0xfffd5620, firmwarebugs=0xfffd7858, type=0x0)

at

/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #3 0x0181bf7c in parse_db_presets (presets=0xfffd7858 "", defs=0x0, firmwarebugs=0x0, type=0xfffd8269)

at

/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #4 0x0181bf7c in parse_db_presets (presets=0xffffffff <Address 0xffffffff out of bounds>, defs=0x30303800, firmwarebugs=0xf8c69177, type=0x1c00)

at

/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #5 0x0181bf7c in parse_db_presets (presets=0x0, defs=0x0, firmwarebugs=0x17, type=0xfffda354) at /usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #6 0x0181bf7c in parse_db_presets (presets=0x1890e1c "\001\210\r
", defs=0x5, firmwarebugs=0x24000022, type=0x18a0f30)

at

/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #7 0x0181bf7c in parse_db_presets (presets=0x20 <Address 0x20 out of bounds>, defs=0x1890e1c, firmwarebugs=0xfffda404, type=0xfffda3b0)

at

/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 #8 0x0181bf7c in parse_db_presets (presets=0x0, defs=0x20, firmwarebugs=0x1801eb0, type=0x1890e18)

at

/usr/obj/ports/smartmontools-6.0/smartmontools-6.0/knowndrives.cpp:221 Previous frame inner to this frame (corrupt stack?)