OMV6 GUI and S.M.A.R.T. Storage pane details - No NVMe Vendor Displayed?

Konsti · Jun 25th 2023

Hello everyone, I am on latest OMV 6 version (6.4.5-1 Shaitan) and in Home > Storage > S.M.A.R.T. > Devices there is no vendor appearing for my NVMe disk.

The disk is a boot disk, correctly identified and mounted as /dev/nvme0 but for some reason, there's no vendor displayed. Is this a problem with the SMART data for my NVMe disk or a minor bug of how OMV6 parses data?

Code

$ sudo smartctl -x /dev/nvme0

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.1.0-0.deb11.7-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       WD Blue SN570 1TB
Serial Number:                      <REMOVED>
Firmware Version:                   234110WD
PCI Vendor/Subsystem ID:            0x15b7
IEEE OUI Identifier:                0x001b44
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            001b44 8b4a63565b
Local Time is:                      Sun Jun 25 16:17:22 2023 CEST
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     80 Celsius
Critical Comp. Temp. Threshold:     85 Celsius
Namespace 1 Features (0x02):        NA_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     4.20W    3.70W       -    0  0  0  0        0       0
1 +     2.70W    2.30W       -    0  0  0  0        0       0
2 +     1.90W    1.80W       -    0  0  0  0        0       0
3 -   0.0250W       -        -    3  3  3  3     3900   11000
4 -   0.0050W       -        -    4  4  4  4     5000   44000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         2
1 -    4096       0         1

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        37 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    400,086 [204 GB]
Data Units Written:                 262,618 [134 GB]
Host Read Commands:                 2,539,307
Host Write Commands:                1,092,300
Controller Busy Time:               23
Power Cycles:                       9
Power On Hours:                     190
Unsafe Shutdowns:                   0
Media and Data Integrity Errors:    0
Error Information Log Entries:      1
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged

Display More

Moreover, when I select to view the Details window of a highlighted drive, there's a bad hyperlink (?) on the breadcrumb path (right above the SMART details pane of the drive) if I accidentally click on "Details" again: I get a Guru Meditation error (black screen, red message) saying Software Failure etc. and I need to reload the OMV6 pages.

The Home > Storage > S.M.A.R.T. > Devices > Details link points to the "same" drive but not sure if the URL is constructed in a wrong way, causing the error:

Code

http://192.168.1.199/#/storage/smart/devices/details/dev/disk/by-id/nvme-WD_Blue_SN570_1TB_231832802976

The Devices URL works, thankfully. It points to http://192.168.1.199/#/storage/smart/devices

Thanks for your feedback!

votdev · Jun 25th 2023

The data displayed in the devices table is fetched from sysfs. This is by intention to not confuse users because the same is done on the Storage | Devices page. The data is extracted from sysfs, so ff the kernel does not get the "correct" data from the device, then the UI can not display it as well.

votdev · Jun 25th 2023

Quote from Konsti

Moreover, when I select to view the Details window of a highlighted drive, there's a bad hyperlink (?) on the breadcrumb path (right above the SMART details pane of the drive) if I accidentally click on "Details" again: I get a Guru Meditation error (black screen, red message) saying Software Failure etc. and I need to reload the OMV6 pages.

I think you should clear your browser cache to fix the issue.

Quote from Konsti
The Home > Storage > S.M.A.R.T. > Devices > Details link points to the "same" drive but not sure if the URL is constructed in a wrong way, causing the error:
Code
http://192.168.1.199/#/storage/smart/devices/details/dev/disk/by-id/nvme-WD_Blue_SN570_1TB_231832802976
The Devices URL works, thankfully. It points to http://192.168.1.199/#/storage/smart/devices

Thanks for your feedback!

This URL looks correctly encoded like this for me: http://omv6box.local/#/storage/smart/devices/details/%2Fdev%2Fdisk%2Fby-id%2Fscsi-0QEMU_QEMU_HARDDISK_drive-ua-disk-volume-0

Konsti · Jun 25th 2023

Hi votdev thanks for your reply.

What would be a command that I can run to provide the output of sysfs so that OMV developers can see if there's something that could be missing or omitted? Unless this is not working like that and I cannot provide feedback on my WD SN570 NVMe?

With regard to the bug of the breadcrumb path (i.e. right above the SMART details pane of the drive) it happens all the time, browser cache cleared. Both on Safari and Firefox... If you click on Details you will see. It's on 2 different OMV6 installation (latest version) and different browsers...

Again, to reproduce: Go to Home > Storage > S.M.A.R.T. > Devices then highlight a drive. Click on the TRIANGLE to show SMART Details. Then click on the white URL of the path right above the drive list... You will see. Clicking on it will cause the error. P.S. I am not talking about the URL you see on the address bar but the hyperlink in "Details".

danilovesky · Jun 25th 2023

I can confirm that after following the above sequence of steps and clicking on "Details" link (see screenshot) I get an error "Software Failure. Press left mouse button to continue. The required page was not found."

votdev · Jun 25th 2023

The UI bug will be fixed in openmediavault 6.4.6, see https://github.com/openmediava…447e6709c150aef017be287da.

votdev · Jun 25th 2023

Quote from Konsti

What would be a command that I can run to provide the output of sysfs so that OMV developers can see if there's something that could be missing or omitted? Unless this is not working like that and I cannot provide feedback on my WD SN570 NVMe?

You will find the info at /sys/block/<DEVICENAME>/device/vendor.

Konsti · Jun 25th 2023

Thanks votdev for confirming the UI bug of the hyperlink.

Regarding my NVMe there is a confusing result.

In /sys/block/ I find the following entries:

Code

lrwxrwxrwx  1 root root 0 Jun 25 15:54 nvme0n1 -> ../devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx  1 root root 0 Jun 25 15:54 sda -> ../devices/pci0000:00/0000:00:12.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx  1 root root 0 Jun 25 15:54 sdb -> ../devices/pci0000:00/0000:00:12.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx  1 root root 0 Jun 25 15:54 sdc -> ../devices/pci0000:00/0000:00:13.3/0000:04:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sdc
lrwxrwxrwx  1 root root 0 Jun 25 15:54 sdd -> ../devices/pci0000:00/0000:00:13.3/0000:04:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdd

Path /sys/block/nvme0n1/device/ has no vendor file. Only model file ("WD Blue SN570 1TB")

Code

$ cd /sys/block/nvme0n1/device/

-r--r--r--  1 root root 4096 Jun 25 22:54 address
-r--r--r--  1 root root 4096 Jun 25 22:54 cntlid
-r--r--r--  1 root root 4096 Jun 25 22:54 cntrltype
-r--r--r--  1 root root 4096 Jun 25 22:54 dctype
-r--r--r--  1 root root 4096 Jun 25 22:54 dev
lrwxrwxrwx  1 root root    0 Jun 25 22:54 device -> ../../../0000:01:00.0
-r--r--r--  1 root root 4096 Jun 25 15:54 firmware_rev
drwxr-xr-x  3 root root    0 Jun 25 15:54 hwmon1
-r--r--r--  1 root root 4096 Jun 25 22:54 kato
-r--r--r--  1 root root 4096 Jun 25 15:54 model
drwxr-xr-x  3 root root    0 Jun 25 15:54 ng0n1
-r--r--r--  1 root root 4096 Jun 25 22:54 numa_node
drwxr-xr-x 13 root root    0 Jun 25 15:54 nvme0n1
drwxr-xr-x  2 root root    0 Jun 25 22:54 power
-r--r--r--  1 root root 4096 Jun 25 22:54 queue_count
--w-------  1 root root 4096 Jun 25 22:54 rescan_controller
--w-------  1 root root 4096 Jun 25 22:54 reset_controller
-r--r--r--  1 root root 4096 Jun 25 15:54 serial
-r--r--r--  1 root root 4096 Jun 25 22:54 sqsize
-r--r--r--  1 root root 4096 Jun 25 22:54 state
-r--r--r--  1 root root 4096 Jun 25 22:54 subsysnqn
lrwxrwxrwx  1 root root    0 Jun 25 15:54 subsystem -> ../../../../../../class/nvme
-r--r--r--  1 root root 4096 Jun 25 22:54 transport
-rw-r--r--  1 root root 4096 Jun 25 15:54 uevent

Display More

I then followed the actual real path, there is a vendor in the device folder (but no model):

Code

$ cd /sys/devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0/device/

-r--r--r-- 1 root root  4096 Jun 25 15:54 aer_dev_correctable
-r--r--r-- 1 root root  4096 Jun 25 15:54 aer_dev_fatal
-r--r--r-- 1 root root  4096 Jun 25 15:54 aer_dev_nonfatal
-r--r--r-- 1 root root  4096 Jun 25 15:54 ari_enabled
-rw-r--r-- 1 root root  4096 Jun 25 15:54 broken_parity_status
-r--r--r-- 1 root root  4096 Jun 25 15:54 class
-rw-r--r-- 1 root root  4096 Jun 25 15:54 config
-r--r--r-- 1 root root  4096 Jun 25 15:54 consistent_dma_mask_bits
-r--r--r-- 1 root root  4096 Jun 25 15:54 current_link_speed
-r--r--r-- 1 root root  4096 Jun 25 15:54 current_link_width
-rw-r--r-- 1 root root  4096 Jun 25 15:54 d3cold_allowed
-r--r--r-- 1 root root  4096 Jun 25 15:54 device
-r--r--r-- 1 root root  4096 Jun 25 15:54 dma_mask_bits
lrwxrwxrwx 1 root root     0 Jun 25 15:54 driver -> ../../../../bus/pci/drivers/nvme
-rw-r--r-- 1 root root  4096 Jun 25 15:54 driver_override
-rw-r--r-- 1 root root  4096 Jun 25 15:54 enable
lrwxrwxrwx 1 root root     0 Jun 25 15:54 firmware_node -> ../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3a/device:3b
lrwxrwxrwx 1 root root     0 Jun 25 15:54 iommu -> ../../../virtual/iommu/dmar1
lrwxrwxrwx 1 root root     0 Jun 25 15:54 iommu_group -> ../../../../kernel/iommu_groups/10
-r--r--r-- 1 root root  4096 Jun 25 15:54 irq
drwxr-xr-x 2 root root     0 Jun 25 15:54 link
-r--r--r-- 1 root root  4096 Jun 25 15:54 local_cpulist
-r--r--r-- 1 root root  4096 Jun 25 15:54 local_cpus
-r--r--r-- 1 root root  4096 Jun 25 15:54 max_link_speed
-r--r--r-- 1 root root  4096 Jun 25 15:54 max_link_width
-r--r--r-- 1 root root  4096 Jun 25 15:54 modalias
-rw-r--r-- 1 root root  4096 Jun 25 15:54 msi_bus
drwxr-xr-x 2 root root     0 Jun 25 15:54 msi_irqs
-rw-r--r-- 1 root root  4096 Jun 25 15:54 numa_node
drwxr-xr-x 3 root root     0 Jun 25 15:54 nvme
-r--r--r-- 1 root root  4096 Jun 25 15:54 pools
drwxr-xr-x 2 root root     0 Jun 25 15:54 power
-r--r--r-- 1 root root  4096 Jun 25 15:54 power_state
--w--w---- 1 root root  4096 Jun 25 15:54 remove
--w------- 1 root root  4096 Jun 25 15:54 rescan
--w------- 1 root root  4096 Jun 25 15:54 reset
-rw-r--r-- 1 root root  4096 Jun 25 15:54 reset_method
-r--r--r-- 1 root root  4096 Jun 25 15:54 resource
-rw------- 1 root root 16384 Jun 25 15:54 resource0
-rw------- 1 root root   256 Jun 25 15:54 resource4
-r--r--r-- 1 root root  4096 Jun 25 15:54 revision
lrwxrwxrwx 1 root root     0 Jun 25 15:54 subsystem -> ../../../../bus/pci
-r--r--r-- 1 root root  4096 Jun 25 15:54 subsystem_device
-r--r--r-- 1 root root  4096 Jun 25 22:55 subsystem_vendor
-rw-r--r-- 1 root root  4096 Jun 25 15:54 uevent
-r--r--r-- 1 root root  4096 Jun 25 15:54 vendor

Display More

...there is a vendor file, with contents "0x15b7"

N.B. The path /sys/devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/ only contains nvme0 so I am forced to go inside nvme0 folder that has the same contents as /sys/block/nvme0n1/device/ above (first list) but if you cd device you end up in the list here that has vendor...

Makes sense?

Path /sys/block/nvme0n1/device/ has same contents as

/sys/devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0/

...and no vendor, only model files.

But /sys/devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0/device/ does have a vendor file, no model (go figure).

Thanks and good night

Konsti · Jul 10th 2023

Hi votdev hope you are well. Any comment on my report above? The path you indicate for my NVMe doesn't seem to be the right one, to get the vendor... Thanks.

votdev · Jul 10th 2023

Whar is the output of udevadm info --query=property --name=/dev/nvme0

BTW, my NVMe does not have a vendor as well, only model. So it seems this information can not be queried via UDEV or sysfs. Seems i can not do anything here because i will not call any other userland app to fetch that info because this action is too expensive and accumulates the more devices are plugged into the system.

Konsti · Jul 10th 2023

Hi votdev here's the output of this command:

Code

$ udevadm info --query=property --name=/dev/nvme0

DEVPATH=/devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0
DEVNAME=/dev/nvme0
NVME_TRTYPE=pcie
MAJOR=248
MINOR=0
SUBSYSTEM=nvme
root@ASRock-NAS:~#

But if I add the correct device name nvme0n1 we get other stuff (perhaps expected):

Code

$ udevadm info --query=property --name=/dev/nvme0n1

DEVPATH=/devices/pci0000:00/0000:00:13.0/0000:01:00.0/nvme/nvme0/nvme0n1
DEVNAME=/dev/nvme0n1
DEVTYPE=disk
DISKSEQ=5
MAJOR=259
MINOR=0
SUBSYSTEM=block
USEC_INITIALIZED=3151668
ID_SERIAL_SHORT=231832802976
ID_WWN=eui.e8238fa6bf530001001b448b4a63565b
ID_MODEL=WD Blue SN570 1TB
ID_REVISION=234110WD
ID_SERIAL=WD Blue SN570 1TB_231832802976
ID_PATH=pci-0000:01:00.0-nvme-1
ID_PATH_TAG=pci-0000_01_00_0-nvme-1
ID_PART_TABLE_UUID=e6efb323-aca3-41ae-b3fc-51c0c6d10240
ID_PART_TABLE_TYPE=gpt
DEVLINKS=/dev/disk/by-id/nvme-WD_Blue_SN570_1TB_231832802976 /dev/disk/by-path/pci-0000:01:00.0-nvme-1 /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b448b4a63565b
TAGS=:systemd:
CURRENT_TAGS=:systemd:

Display More

Thanks for your help.

FYI this is the output of the lsblk -fp command:

Code

NAME             FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINT
/dev/nvme0n1                                                                                 
├─/dev/nvme0n1p1 vfat   FAT32            53C2-4CD6                                           
├─/dev/nvme0n1p2 ext4   1.0   System     82876742-7862-4142-b549-0beadf739779   50.5G    11% /
├─/dev/nvme0n1p3 swap   1                6c9bc92d-5371-4865-921e-0518ba5c6025                [SWAP]
└─/dev/nvme0n1p4 ext4   1.0   Data       f53e761d-e8bc-4c16-a839-37acf0fa2921  717.5G    11% /srv/dev-disk-by-uuid-f53e761d-e8bc-4c16-a839-37acf0fa2921

Konsti · Aug 2nd 2023

Hi votdev does the above provide you an insight on the Manufacturer display issue for my NVMe boot drive?

For your information, my board is an Intel J5040 CPU (by ASRock) and has 4xSATA ports, but the NVMe is a (WD) SATA one connected on a PCIe adapter. Could this be a reason why we have this difference between /dev/nvme0 and /dev/nvme0n1 devices, perhaps? (sorry, I am not a connoisseur of such Linux deep kernel knowledge...).

Hi ryecoaaron or macom any comments based on your global experience?

Many thanks to all ! (and hope you're relaxing to some beach far away )

votdev · Aug 2nd 2023

https://utcc.utoronto.ca/~cks/…log/linux/NVMeDeviceNames might help to understand the naming of NVMe device names.

Konsti · Nov 5th 2023

Hello votdev I'd like to inform you that I was pleasantly surprised to discover that the latest OMV6 versions (I updated to 6.9.6-2) has improved the display of the NVMe vendor column for NVMe's, so my next question is where does one find/define the ID of the vendor (in my case it shows 0x15b7) and how can we improve this? Here are my screenshots, thank you in advance!

Reference: https://admin.pci-ids.ucw.cz/read/PC/15b7

P.S. Reminder, My ASRock J5040-ITX board has 2+2 SATA ports and I boot from a PCIe-NVMe adapter (WD Blue SN570) to maximize capacity.

OMV6 GUI and S.M.A.R.T. Storage pane details - No NVMe Vendor Displayed?

Participate now!

Tags