Custom Query (1566 matches)
Results (73 - 75 of 1566)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #486 | worksforme | smartctl tool is giving error ----- " Error Counter logging not supported Device does not support Self Test logging " while fetching the life of SSD. | ||
| Description |
Hi Team, The smartctl tool is giving some error while fetching the life of ssd ; the output is shared below. Can you please check and provide the solution asap as this info is needed and very critical for our environment. [root@ukna50sr-vf ~]# smartctl -a /dev/sda smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: LSI MR9261-8i Version: 2.90 Serial number: 00f329f7056cce821560f1e102b00506 Device type: disk Local Time is: Thu Nov 6 03:54:16 2014 UTC Device does not support SMART Error Counter logging not supported Device does not support Self Test logging Thanks & Regards, Dinesh Rathee M.No. ; +91-9650463332 |
|||
| #1220 | invalid | smartctl tests are not logged for SanDisk SDSSDA240G drive | ||
| 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. |
|||
| #1215 | invalid | smartctl selects the wrong NVMe device | ||
| Description |
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 |
|||
