After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778906 - Support NVME ssd devices better and read Model / Smart values
Support NVME ssd devices better and read Model / Smart values
Status: RESOLVED OBSOLETE
Product: gnome-disk-utility
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2017-02-19 12:29 UTC by boscowitch
Modified: 2018-05-24 10:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description boscowitch 2017-02-19 12:29:05 UTC
The version specified fails to show the "Model" field and disables SMART options in the menue. (only serialnumber is read correctly)

However it is possible to read those values as smartmontools can read all the infomation from Model to all the  SMART values. 

And it would be nice to show the most important value 

TBW/DUW (total bytes written or data units written) in the main UI
since it is the most important information together with temperature for a quick health estimate.

here is an example of the smartmonoutput for a samsung 950 nvme sdd:

sudo smartctl /dev/nvme0 -a
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.8-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 950 PRO 512GB
Serial Number:                      S2GMNXXXXXXXXXX
Firmware Version:                   1B0QBXX7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512.110.190.592 [512 GB]
Namespace 1 Utilization:            263.815.585.792 [263 GB]
Namespace 1 Formatted LBA Size:     512
Local Time is:                      Sun Feb 19 13:22:10 2017 CET
Firmware Updates (0x06):            3 Slots
Optional Admin Commands (0x0007):   Security Format Frmw_DL
Optional NVM Commands (0x001f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size:         32 Pages
...
...
...

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

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        56 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    21.504.679 [11,0 TB]
Data Units Written:                 6.064.597 [3,10 TB]
Host Read Commands:                 298.465.621
Host Write Commands:                139.265.204
Controller Busy Time:               1.501
Power Cycles:                       1.177
Power On Hours:                     4.569
Unsafe Shutdowns:                   160
Media and Data Integrity Errors:    0
Error Information Log Entries:      198

...
...


From this only the Serial Number is showed in the gnome-disks utility correctly

Model is shown as "—"


Btw THX for all your good work!
Comment 1 Stephen Panicho 2017-08-17 15:09:55 UTC
I can confirm that this bug also occurs for me exactly as described above. Using gnome-disks 3.24.1


sudo smartctl -a /dev/nvme0

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.12.6-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       INTEL SSDPEKKF256G7L
Serial Number:                      BTPY722304T5256D
Firmware Version:                   121P
PCI Vendor/Subsystem ID:            0x8086
IEEE OUI Identifier:                0x5cd2e4
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          256,060,514,304 [256 GB]
Namespace 1 Formatted LBA Size:     512
Local Time is:                      Thu Aug 17 10:54:02 2017 EDT
Firmware Updates (0x12):            1 Slot, no Reset required
Optional Admin Commands (0x0007):   Security Format Frmw_DL
Optional NVM Commands (0x001e):     Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size:         32 Pages
Warning  Comp. Temp. Threshold:     70 Celsius
Critical Comp. Temp. Threshold:     80 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.00W       -        -    0  0  0  0        5       5
 1 +     4.60W       -        -    1  1  1  1       30      30
 2 +     3.80W       -        -    2  2  2  2       30      30
 3 -   0.0700W       -        -    3  3  3  3    10000     300
 4 -   0.0050W       -        -    4  4  4  4     2000   10000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        26 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    1,282,460 [656 GB]
Data Units Written:                 107,266 [54.9 GB]
Host Read Commands:                 5,858,461
Host Write Commands:                938,522
Controller Busy Time:               29
Power Cycles:                       65
Power On Hours:                     10
Unsafe Shutdowns:                   56
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, max 64 entries)
No Errors Logged
Comment 2 Kai Lüke 2017-08-17 16:35:57 UTC
Hello,

thanks for the report. I think this issue needs to be forwarded to UDisks.
Can you please print the output of "udisksctl status" and
"udisksctl info -d INTEL_SSDPEKKF256G7L_BTPY722304T5256D" (if this fails then the relevant part of "udisksctl dump"). Then we can see if UDisks does not expose the properties Drive.Model and Ata.SmartEnabled/Supported: true.

Thanks,
Kai
Comment 3 Stephen Panicho 2017-08-17 19:20:52 UTC
Ooh, I think you're on to something.

$ udisksctl status
MODEL                     REVISION  SERIAL               DEVICE
--------------------------------------------------------------------------
-                                   BTPY722304T5256D     nvme0n1


I edited your second command so it specifies the correct drive:

$ udisksctl info -d BTPY722304T5256D
/org/freedesktop/UDisks2/drives/BTPY722304T5256D:
  org.freedesktop.UDisks2.Drive:
    CanPowerOff:                false
    Configuration:              {}
    ConnectionBus:              
    Ejectable:                  false
    Id:                         BTPY722304T5256D
    Media:                      
    MediaAvailable:             true
    MediaChangeDetected:        true
    MediaCompatibility:         
    MediaRemovable:             false
    Model:                      
    Optical:                    false
    OpticalBlank:               false
    OpticalNumAudioTracks:      0
    OpticalNumDataTracks:       0
    OpticalNumSessions:         0
    OpticalNumTracks:           0
    Removable:                  false
    Revision:                   
    RotationRate:               0
    Seat:                       seat0
    Serial:                     BTPY722304T5256D
    SiblingId:                  
    Size:                       256060514304
    SortKey:                    00coldplug/00fixed/nvme0n1
    TimeDetected:               1502993299595487
    TimeMediaDetected:          1502993299595487
    Vendor:                     
    WWN:                        eui.5cd2e41671a12af8
Comment 4 Stephen Panicho 2017-08-17 19:30:24 UTC
Additionally, this is the only entry under the /org/freedesktop/UDisks2/drives/ key. It has no org.freedesktop.UDisks2.Drive.Ata section.

Thanks for looking into this!

Stephen
Comment 5 Kai Lüke 2017-08-18 06:28:14 UTC
Good, I've reported it here:
https://github.com/storaged-project/udisks/issues/386

Let's see if it's not big or small issue.

Regards,
Kai
Comment 6 GNOME Infrastructure Team 2018-05-24 10:37:31 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/50.