Changes between Initial Version and Version 1 of Ticket #1215


Ignore:
Timestamp:
Jul 19, 2019, 2:44:30 PM (5 years ago)
Author:
Christian Franke
Comment:

Did it work with an older release on same machine?

Smartctl does not explicitly select a device, it simply accesses the pass-through I/O-control behind the specified device node. Are the major/minor device numbers correctly set for these nodes?

Please provide output of the following commands: 

ls -l /dev/nvme*
egrep ':|nvme' /proc/devices

./smartctl -d nvme,0x1 -a /dev/nvme0 | sed -n '1p;5,7p'

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1215

    • Property Keywords nvme linux added
    • Property Milestone → undecided

  • Ticket #1215 – Description

    initial v1  
    11In 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:
    22
     3{{{
    34# ls -l nvme-Samsung_SSD_970_EVO_2TB_S464NB0M200088N | cut -c40-
    45nvme-Samsung_SSD_970_EVO_2TB_S464NB0M200088N -> ../../nvme0n1
    … …  
    2728Serial Number:                      S464NB0M200088N
    2829Firmware Version:                   2B2QEXE7
     30}}}