Custom Query (1386 matches)
Results (145 - 147 of 1386)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1750 | invalid | Samsung SSD 970 EVO Plus 250GB | ||
Description |
Hi, Please see attached test report for my nvme SSD. I have checked the online drivedb and don't see any mention of 970 EVO, so I am hoping this drive can be added. I have updated the drivedb locally, but am not able to access the smart data and tests via the "disks" utility in Fedora 37 for this drive, and I don't see an entry in the journal for this drive saying "found in smartd database" as I do for other drives (see below). Thanks, MrG smartd[23992]: Device: /dev/sdc [SAT], opened smartd[23992]: Device: /dev/sdc [SAT], WDC WD3200AAKS-00SBA0, S/N:WD-WMAPZ0463624, WWN:5-0014ee-0aabb2a43, FW:12.01B01, 320 GB smartd[23992]: Device: /dev/sdc [SAT], **found in smartd database** 7.3/5533: Western Digital Caviar Blue (SATA) smartd[23992]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list. ... smartd[23992]: Device: /dev/nvme0, opened smartd[23992]: Device: /dev/nvme0, Samsung SSD 970 EVO Plus 250GB, S/N:S4EUNX0R533480T, FW:2B2QEXM7, 250 GB smartd[23992]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list. smartd[23992]: Monitoring 4 ATA/SATA, 0 SCSI/SAS and 1 NVMe devices |
|||
#1706 | fixed | Submitting a new model of ssd not found in the database (INTENSO/V0609A0) | ||
#947 | wontfix | Windows 10 To Go: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1117 | ||
Description |
Hi; Running smartmontools 6.6 r4594 under Windows 10, I receive the following error when I try to access my Samsung 960 Pro 512 GB NVMe drive: smartctl -a /dev/sdf smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-1709] (sf-6.6-1) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Read NVMe Identify Controller failed: IOCTL_STORAGE_QUERY_PROPERTY(NVMe) failed, Error=1117 I was under the impression from the 6.6 release notes that the built-in Windows NVMe 10 driver (stornvme.sys) would work. Am I missing something? Do I need to add an additional driver or use a different command line option? Getting SMART from the other (SATA attached) drives seems to work o.k. Thanks. |