|
From: Alexander S. <ash...@gm...> - 2017-05-11 11:43:49
|
Hi Orsiris, Thanks for testing it, I'm glad you like it. The NVME drive seems to be treated like an SCSI drive by smartctl (that is, the output is somewhat free-form, unlike (S)ATA drives, where the output is "standardized"). Unfortunately, GSmartControl doesn't support such drives (yet), so it doesn't make much sense to detect them. Thanks, Alexander On Thu, 11 May 2017 11:54:04 +0200 Orsiris de Jong wrote: > Hello Alexander, > > > > Congratulations for the new version of your tool, really looks > steamlined :) > > I just ran it on my Win10 x64 with an nvme and an ssd disk. > > > > The NVME disk is detected, but output is limited: > > smartctl 6.5 2016-05-07 r4318 [i686-w64-mingw32-win10(64)] (sf-6.5-1) > > Copyright (C) 2002-16, Bruce Allen, Christian Franke, > www.smartmontools.org > > > > === START OF INFORMATION SECTION === > Vendor: NVMe > Product: Samsung SSD 950 > Revision: 2B0Q > Compliance: SPC-4 > LU is resource provisioned, LBPRZ=1 > Rotation Rate: Solid State Device > Logical Unit id: YYYYYYYYYYYYYYYYYYYYY 2B0Q > Serial number: XXXXXXXXXXXXXXXXXXX > Device type: disk > Local Time is: Thu May 11 11:34:15 2017 PM > SMART support is: Available - device has SMART capability. > SMART support is: Disabled > Temperature Warning: Disabled or Not Supported > > === START OF READ SMART DATA SECTION === > Request Sense failed, [Input/output error] > Current Drive Temperature: 51 C > Drive Trip Temperature: 80 C > > Error Counter logging not supported > > > [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S > on'] Device does not support Self Test logging > > ------------------------------ > Doing the same with smartctl -a /dev/nvme0 > C:\Program Files\smartmontools\bin>smartctl -a /dev/nvme0 > smartctl 6.5 2016-05-07 r4318 [x86_64-w64-mingw32-win10] (sf-6.5-1) > Copyright (C) 2002-16, Bruce Allen, Christian Franke, > www.smartmontools.org > > === START OF INFORMATION SECTION === > Model Number: Samsung SSD 950 PRO 256GB > Serial Number: XXXXXXXXXXXXXXXXXXX > Firmware Version: 2B0QBXX7 > PCI Vendor/Subsystem ID: 0x144d > IEEE OUI Identifier: 0x002538 > Controller ID: 1 > Number of Namespaces: 1 > Namespace 1 Size/Capacity: 256 060 514 304 [256 GB] > Namespace 1 Utilization: 153 960 095 744 [153 GB] > Namespace 1 Formatted LBA Size: 512 > Local Time is: Thu May 11 11:35:11 2017 PM > 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 > > Supported Power States > St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat > 0 + 6.50W - - 0 0 0 0 5 5 > 1 + 5.80W - - 1 1 1 1 30 30 > 2 + 3.60W - - 2 2 2 2 100 100 > 3 - 0.0700W - - 3 3 3 3 500 5000 > 4 - 0.0050W - - 4 4 4 4 2000 22000 > > 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: 51 Celsius > Available Spare: 100% > Available Spare Threshold: 10% > Percentage Used: 0% > Data Units Read: 8 802 764 [4,50 TB] > Data Units Written: 8 100 637 [4,14 TB] > Host Read Commands: 163 470 567 > Host Write Commands: 207 549 906 > Controller Busy Time: 879 > Power Cycles: 1 846 > Power On Hours: 3 551 > Unsafe Shutdowns: 210 > Media and Data Integrity Errors: 0 > Error Information Log Entries: 97 > > Error Information (NVMe Log 0x01, max 64 entries) > Num ErrCount SQId CmdId Status PELoc LBA NSID VS > 0 97 0 0x001d 0x4004 0x000 0 0 - > 1 96 0 0x001c 0x4004 0x000 0 0 - > 2 95 0 0x001d 0x4004 0x000 0 0 - > 3 94 0 0x001c 0x4004 0x000 0 0 - > 4 93 0 0x001d 0x4004 0x000 0 0 - > 5 92 0 0x001c 0x4004 0x000 0 0 - > 6 91 0 0x001f 0x4004 0x000 0 0 - > 7 90 0 0x001e 0x4004 0x000 0 0 - > 8 89 0 0x001f 0x4004 0x000 0 0 - > 9 88 0 0x001e 0x4004 0x000 0 0 - > 10 87 0 0x001d 0x4004 0x000 0 0 - > 11 86 0 0x001c 0x4004 0x000 0 0 - > 12 85 0 0x001d 0x4004 0x000 0 0 - > 13 84 0 0x001c 0x4004 0x000 0 0 - > 14 83 0 0x001d 0x4004 0x000 0 0 - > 15 82 0 0x001c 0x4004 0x000 0 0 - > ... (48 entries not shown) > I've seen that smartctl --scan can't really find nvme devices as of > v6.5. > > Is there a chance to run a pseudo code loop like > > > > for i in {0..15}; do > > smartctl -a /dev/nvme$i > > if [$! == 0]; then device_exists+=$i; fi > > done > > > > This would allow to detect those devices and get nvme output. > > > > Btw, the berlios.de link didn't work for me, had to go to sourceforge. > > > > Best regards, > > > > Orsiris de Jong > > oz...@ne... - http://www.netpower.fr <http://www.netpower.fr> > > Tel: 06 75 40 48 41 |