NVMe SMART status reading failure (wrong drive name)

    • OMV 4.x
    • NVMe SMART status reading failure (wrong drive name)

      I'm having a small issue with my new OS drive, which is a Corsair MP510 NVMe drive. OMV is unable to fetch the SMART data in the webGUI most likely because the data is trying to be fetched with the drive name "nvme0n1". The SMART data can be read just fine if I try to read it in the shell with the command "smartctl -x /dev/nvme0"

      Here is the error message that I get in the webGUI:
      "Read NVMe SMART/Health Information failed: NVMe Status 0x2002"

      I get the exact same error message if I try to read the SMART data with the command "smartctl -x /dev/nvme0n1". So I know what the problem is but I'm not sure how to fix it so that it works in the GUI ?(
    • I'm wondering about the device naming. I did some research and i think a NVMe device has to be accessed via nvme<controller>n<namespace>. Can you please try

      Shell-Script

      1. # smartctl -x -d nvme /dev/nvme0n1
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Thanks to VMware Player i was able to create a NVMe device. With that i can't reproduce your problem.

      Shell-Script

      1. root@vmpc01:~# cat /proc/partitions
      2. major minor #blocks name
      3. 259 0 1048576 nvme0n1
      4. 11 0 477184 sr0
      5. 8 0 20971520 sda
      6. 8 1 19921920 sda1
      7. 8 2 1 sda2
      8. 8 5 1046528 sda5
      9. 8 16 1048576 sdb
      10. 8 17 1047535 sdb1
      11. root@vmpc01:~# smartctl -x /dev/nvme0n1
      12. smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.18.0-0.bpo.3-amd64] (local build)
      13. Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
      14. === START OF INFORMATION SECTION ===
      15. Model Number: VMware Virtual NVMe Disk
      16. Serial Number: VMWare NVME-0000
      17. Firmware Version: 1.0
      18. PCI Vendor/Subsystem ID: 0x15ad
      19. IEEE OUI Identifier: 0x565000
      20. Controller ID: 0
      21. Number of Namespaces: 1
      22. Namespace 1 Size/Capacity: 1.073.741.824 [1,07 GB]
      23. Namespace 1 Formatted LBA Size: 512
      24. Local Time is: Fri Sep 6 16:37:34 2019 CEST
      25. Firmware Updates (0x03): 1 Slot, Slot 1 R/O
      26. Maximum Data Transfer Size: 256 Pages
      27. Supported Power States
      28. St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
      29. 0 + 0.00W - - 0 0 0 0 0 0
      30. Supported LBA Sizes (NSID 0x1)
      31. Id Fmt Data Metadt Rel_Perf
      32. 0 + 512 0 0
      33. === START OF SMART DATA SECTION ===
      34. SMART overall-health self-assessment test result: PASSED
      35. SMART/Health Information (NVMe Log 0x02, NSID 0x1)
      36. Critical Warning: 0x00
      37. Temperature: 11759 Celsius
      38. Available Spare: 1%
      39. Available Spare Threshold: 100%
      40. Percentage Used: 0%
      41. Data Units Read: ~110680464442257309696
      42. Data Units Written: ~92233720368547758080
      43. Host Read Commands: ~110680464442257309696000
      44. Host Write Commands: ~92233720368547758080000
      45. Controller Busy Time: ~92233720368547758080
      46. Power Cycles: ~184467440737095516160
      47. Power On Hours: ~1106804644422573096960
      48. Unsafe Shutdowns: 0
      49. Media and Data Integrity Errors: 0
      50. Error Information Log Entries: 0
      51. Error Information (NVMe Log 0x01, max 4 entries)
      52. No Errors Logged
      Display All
      What smartmontools version are you using?

      Shell-Script

      1. $ dpkg -l | grep smartmontools
      2. $ smartctl -V
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • From the manual page of smartctl:

      Source Code

      1. Use the forms "/dev/nvme[0-9]" (broadcast namespace) or "/dev/nvme[0-9]n[1-9]" (specific namespace 1-9) for NVMe devices.

      So i do not see anything wrong in handling NVMe devices in OMV.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • votdev wrote:

      I'm wondering about the device naming. I did some research and i think a NVMe device has to be accessed via nvme<controller>n<namespace>. Can you please try

      Shell-Script

      1. # smartctl -x -d nvme /dev/nvme0n1

      Hi, here is the output of that command:

      Source Code

      1. smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.19.0-0.bpo.5-amd64] (local build)
      2. Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
      3. === START OF INFORMATION SECTION ===
      4. Model Number: Force MP510
      5. Serial Number: 19318206000127700490
      6. Firmware Version: ECFM12.2
      7. PCI Vendor/Subsystem ID: 0x1987
      8. IEEE OUI Identifier: 0x6479a7
      9. Total NVM Capacity: 480,103,981,056 [480 GB]
      10. Unallocated NVM Capacity: 0
      11. Controller ID: 1
      12. Number of Namespaces: 1
      13. Namespace 1 Size/Capacity: 480,103,981,056 [480 GB]
      14. Namespace 1 Formatted LBA Size: 512
      15. Local Time is: Sat Sep 7 14:01:40 2019 EEST
      16. Firmware Updates (0x12): 1 Slot, no Reset required
      17. Optional Admin Commands (0x0007): Security Format Frmw_DL
      18. Optional NVM Commands (0x0054): DS_Mngmt Sav/Sel_Feat *Other*
      19. Maximum Data Transfer Size: 512 Pages
      20. Warning Comp. Temp. Threshold: 70 Celsius
      21. Critical Comp. Temp. Threshold: 90 Celsius
      22. Supported Power States
      23. St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
      24. 0 + 8.12W - - 0 0 0 0 0 0
      25. 1 + 6.40W - - 1 1 1 1 0 0
      26. 2 + 5.54W - - 2 2 2 2 0 0
      27. 3 - 0.0490W - - 3 3 3 3 2000 2000
      28. 4 - 0.0018W - - 4 4 4 4 25000 25000
      29. Supported LBA Sizes (NSID 0x1)
      30. Id Fmt Data Metadt Rel_Perf
      31. 0 + 512 0 2
      32. 1 - 4096 0 1
      33. === START OF SMART DATA SECTION ===
      34. Read NVMe SMART/Health Information failed: NVMe Status 0x2002
      Display All
    • Here is "dpkg -l | grep smartmontools":

      Shell-Script

      1. ii smartmontools 6.5+svn4324-1 amd64 control and monitor storage systems using S.M.A.R.T.

      And "smartctl -V"


      Shell-Script

      1. smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.19.0-0.bpo.5-amd64] (local build)
      2. Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
      3. smartctl comes with ABSOLUTELY NO WARRANTY. This is free
      4. software, and you are welcome to redistribute it under
      5. the terms of the GNU General Public License; either
      6. version 2, or (at your option) any later version.
      7. See http://www.gnu.org for further details.
      8. smartmontools release 6.6 dated 2016-05-07 at 11:17:46 UTC
      9. smartmontools SVN rev 4324 dated 2016-05-31 at 20:45:50
      10. smartmontools build host: x86_64-pc-linux-gnu
      11. smartmontools build with: C++98, GCC 5.4.0 20160609
      12. smartmontools configure arguments: '--prefix=/usr' '--build=x86_64-linux-gnu' '--host=x86_64-linux-gnu' '--sysconfdir=/etc' '--mandir=/usr/share/man' '--with-initscriptdir=no' '--docdir=/usr/share/doc/smartmontools' '--with-savestates=/var/lib/smartmontools/smartd.' '--with-attributelog=/var/lib/smartmontools/attrlog.' '--with-exampledir=/usr/share/doc/smartmontools/examples/' '--with-drivedbdir=/var/lib/smartmontools/drivedb' '--with-systemdsystemunitdir=/lib/systemd/system' '--with-smartdscriptdir=/usr/share/smartmontools' '--with-smartdplugindir=/etc/smartmontools/smartd_warning.d' '--with-systemdenvfile=/etc/default/smartmontools' '--with-selinux' 'build_alias=x86_64-linux-gnu' 'host_alias=x86_64-linux-gnu' 'CXXFLAGS=-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -fsigned-char -Wall -O2' 'LDFLAGS=-fPIE -pie -Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2' 'CFLAGS=-g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -fsigned-char -Wall -O2'
      Display All

      The post was edited 1 time, last by jackster ().

    • jackster wrote:

      I'm having a small issue with my new OS drive, which is a Corsair MP510 NVMe drive. OMV is unable to fetch the SMART data in the webGUI most likely because the data is trying to be fetched with the drive name "nvme0n1". The SMART data can be read just fine if I try to read it in the shell with the command "smartctl -x /dev/nvme0"

      Here is the error message that I get in the webGUI:
      "Read NVMe SMART/Health Information failed: NVMe Status 0x2002"

      I get the exact same error message if I try to read the SMART data with the command "smartctl -x /dev/nvme0n1". So I know what the problem is but I'm not sure how to fix it so that it works in the GUI ?(
      I'm having the exact same issue. Did you ever find a solution?
    • Fuelrod wrote:

      jackster wrote:

      I'm having a small issue with my new OS drive, which is a Corsair MP510 NVMe drive. OMV is unable to fetch the SMART data in the webGUI most likely because the data is trying to be fetched with the drive name "nvme0n1". The SMART data can be read just fine if I try to read it in the shell with the command "smartctl -x /dev/nvme0"

      Here is the error message that I get in the webGUI:
      "Read NVMe SMART/Health Information failed: NVMe Status 0x2002"

      I get the exact same error message if I try to read the SMART data with the command "smartctl -x /dev/nvme0n1". So I know what the problem is but I'm not sure how to fix it so that it works in the GUI ?(
      I'm having the exact same issue. Did you ever find a solution?
      Apparently it's a known issue which is fixed in Debian 10 so it'll work normally with OMV5 and therefore I haven't bothered doing anything about it: github.com/openmediavault/openmediavault/issues/437