Can't list SMART Test Results

R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
I have some HDs in my system and i have run several older smart tests on them on other operating systems some time ago.
But when i click on one HD to show me the SMART Test Results it says "No Data to display".

The same happens, after starting some new manual SMART Tests via the Webinterface of TrueNAS-12.0-U1.1


And there is one more problem with SMART on TrueNAS:

My SSD isn't recognized for SMART Tests.
From my Linux operating system, i know, that i had to specify a special device type for the smartctl command line tool to make it work on that SSD.
I can't remember if it was --device=nvme or --device=sat, but i know that it didn't work with auto detection.

The Webinterface of truenas also fails. I assume it tries to use auto detection which doesn't work.
The error message ist:
Code:
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
  File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1195, in _call
    return await methodobj(*prepared_call.args)
  File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 973, in nf
    return await f(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/smart.py", line 398, in manual_test
    verrors.check()
  File "/usr/local/lib/python3.8/site-packages/middlewared/service_exception.py", line 62, in check
    raise self
middlewared.service_exception.ValidationErrors: [EINVAL] disks.0.identifier: Test cannot be performed for {serial_lunid}XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX  disk. NVMe devices cannot be mapped yet.
[EINVAL] disks.0.identifier: Test cannot be performed for {serial_lunid}XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX. Unable to retrieve disk details.


The SSD Model is an INTEL SSDPEKKF256G8
 
sretalla

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Revan said:
But when i click on one HD to show me the SMART Test Results it says "No Data to display".
Click to expand...
That was a know bug and I can confirm was fixed today with 12.0-U2.
 
sretalla

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Revan said:
From my Linux operating system, i know, that i had to specify a special device type for the smartctl command line tool to make it work on that SSD.
I can't remember if it was --device=nvme or --device=sat, but i know that it didn't work with auto detection.
Click to expand...
I suggest you do a bit of testing at the command line and work it out again.

You can then add it in the options for that disk.
 
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
sretalla said:
I suggest you do a bit of testing at the command line and work it out again.

You can then add it in the options for that disk.
Click to expand...
Thanks a lot, i will try that.

When will 12.0-U2 be released?
 
Redcoat

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
sretalla

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
Thanks a lot. They should Update their Website. It still directs to U1.1.
But if you edit the url of the download link, you can download it.
 
sretalla

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Or just go to the update page on your server and search for updates...
 
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
sretalla said:
I suggest you do a bit of testing at the command line and work it out again.

You can then add it in the options for that disk.
Click to expand...

Ok, i did a little testing.

In Storage>Disks>Name the SSD device is called nvd0

So i did:
Code:
cd /dev
ls nv*
nvd0     nvd9p2    nvme0
nvd0p1   nvd0p3    vnme0ns1

then
Code:
smartctl -i /dev/nvd0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/nvd0: To monitor NVMe disks use /dev/nvme* device names
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

so i did:
Code:
smartctl -i /dev/nvme0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       INTEL SSDPEKKF256G8
Serial Number:                      XXXXXXXXXXXXXXXX
Firmware Version:                   005P
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:                      Wed Feb 10 16:04:30 2021 CET

Then i tried to run a test:
Code:
smartctl -t short /dev/nvme0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

NVMe device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

But no test time was given.
It seems like no test was run.
And running smartctl with option -a after waiting a little bit proves that there was no test run:
Code:
smartctl -a /dev/nvme0              
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       INTEL SSDPEKKF256G8
Serial Number:                      XXXXXXXXXXXXXXXX
Firmware Version:                   005P
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:                      Wed Feb 10 16:14:04 2021 CET
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
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     75 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        0       0
 1 +     4.60W       -        -    1  1  1  1        0       0
 2 +     3.80W       -        -    2  2  2  2        0       0
 3 -   0.0450W       -        -    3  3  3  3     2000    2000
 4 -   0.0040W       -        -    4  4  4  4     6000    8000

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)
Critical Warning:                   0x00
Temperature:                        26 Celsius
Available Spare:                    100%
Available Spare Threshold:          12%
Percentage Used:                    0%
Data Units Read:                    12,992 [6.65 GB]
Data Units Written:                 8,255 [4.22 GB]
Host Read Commands:                 285,806
Host Write Commands:                206,817
Controller Busy Time:               4
Power Cycles:                       138
Power On Hours:                     74
Unsafe Shutdowns:                   46
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 256 entries)
No Errors Logged

Same happens when trying to run a long test:
Code:
smartctl -t long -d nvme /dev/nvme0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

NVMe device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

smartctl --scan gives me:
Code:
smartctl --scan                     
/dev/ada0 -d atacam # /dev/ada0, ATA device
/dev/ada1 -d atacam # /dev/ada1, ATA device
/dev/ada2 -d atacam # /dev/ada2, ATA device
/dev/ada3 -d atacam # /dev/ada3, ATA device
/dev/ada4 -d atacam # /dev/ada4, ATA device
/dev/ada5 -d atacam # /dev/ada5, ATA device
/dev/ses0 -d atacam # /dev/ses0, ATA device
/dev/nvme0 -d nvme # /dev/nvme0, NVMe device


Any ideas?
 
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
And btw, i wonder what
Code:
smartctl --scan-open          
/dev/ada0 -d atacam # /dev/ada0, ATA device
/dev/ada1 -d atacam # /dev/ada1, ATA device
/dev/ada2 -d atacam # /dev/ada2, ATA device
/dev/ada3 -d atacam # /dev/ada3, ATA device
/dev/ada4 -d atacam # /dev/ada4, ATA device
/dev/ada5 -d atacam # /dev/ada5, ATA device
/dev/ses0 -d atacam # /dev/ses0, ATA device
/dev/nvme0 -d nvme # /dev/nvme0, NVMe device
root@elefant[/dev]# smartctl -i  /dev/ses0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: Input/output error

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.


/dev/ses0 is?
 
sretalla

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
C

CudIHavBn

Cadet
Joined
Apr 8, 2021
Messages
4
Awful to high jack a thread but its soo relevant. I have my OS installed on a 512 wd nvme. Overkill and a waste I now realize, but its up and running. I'm getting the same identifier error listed above. Will this cause any problems in system operation or performance?
 
C

CudIHavBn

Cadet
Joined
Apr 8, 2021
Messages
4
CudIHavBn said:
Awful to high jack a thread but its soo relevant. I have my OS installed on a 512 wd nvme. Overkill and a waste I now realize, but its up and running. I'm getting the same identifier error listed above. Will this cause any problems in system operation or performance?
Click to expand...
Not sure if this is the right term... On the console screen... VGA connected directly to the server... I get messages stating truenas.local savecore XXXX (varying 4 digit numbers) - - /dev/nvd0p3: Operation not permitted.
 
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
I upgraded my TrueNAS system to TrueNAS-12.0-U5 today, but when i do a manual smart test in the Web GUI i still get an error message, see below:

In the console i get at least a working and meaningful output, even if NVME disks are experimental in smartctl:
Code:
smartctl -t short -d nvme /dev/nvme0   
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

NVMe device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information



But the web gui still selects the wrong disk identifier when trying to do a manual test and gives an error message:
Code:
[EINVAL] disks.0.identifier: {serial_lunid}XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX is not valid. Please provide a valid disk identifier.

More info...
Error: Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 138, in call_method
    result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
  File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1205, in _call
    return await methodobj(*prepared_call.args)
  File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 973, in nf
    return await f(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/smart.py", line 402, in manual_test
    verrors.check()
  File "/usr/local/lib/python3.9/site-packages/middlewared/service_exception.py", line 62, in check
    raise self
middlewared.service_exception.ValidationErrors: [EINVAL] disks.0.identifier: {serial_lunid}XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX is not valid. Please provide a valid disk identifier.


In my opinion this is a bug. It should at least select the correct disk identifier and say something meaningful like smartctl doesn't support testing of NVME devices.
 
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
CudIHavBn said:
Awful to high jack a thread but its soo relevant. I have my OS installed on a 512 wd nvme. Overkill and a waste I now realize, but its up and running. I'm getting the same identifier error listed above. Will this cause any problems in system operation or performance?
Click to expand...
No, it does only mean that smartctl will not be able to do regular SMART tests on your nvme device.
The device will work, but you will not get any informations about SMART tests.

SMART tests are helpful to know if the drive will fail soon. It's some sort of pre-fail test. And if SMART tests fail it's time to replace the drive.
The problem with nvme devices is at the moment, that we are not able to run these SMART tests on them. :(
 
NugentS

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Doesn't seem to run on Optane's either
Code:
Error: Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 138, in call_method
    result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
  File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1205, in _call
    return await methodobj(*prepared_call.args)
  File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 973, in nf
    return await f(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/smart.py", line 402, in manual_test
    verrors.check()
  File "/usr/local/lib/python3.9/site-packages/middlewared/service_exception.py", line 62, in check
    raise self
middlewared.service_exception.ValidationErrors: [EINVAL] disks.0.identifier: {serial}PHMB742301HB280CGN is not valid. Please provide a valid disk identifier.

Given how important the Optane's are likley to be - this is a little concerning
 
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
T

TrumanHW

Contributor
Joined
Apr 17, 2018
Messages
197
NugentS said:
Doesn't seem to run on Optane's either
Code:
Error: Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 138, in call_method
    result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
  File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 1205, in _call
    return await methodobj(*prepared_call.args)
  File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 973, in nf
    return await f(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/smart.py", line 402, in manual_test
    verrors.check()
  File "/usr/local/lib/python3.9/site-packages/middlewared/service_exception.py", line 62, in check
    raise self
middlewared.service_exception.ValidationErrors: [EINVAL] disks.0.identifier: {serial}PHMB742301HB280CGN is not valid. Please provide a valid disk identifier.

Given how important the Optane's are likley to be - this is a little concerning
Click to expand...


Seriously. While I'm in no position to criticize people fixing things I don't understand, I think I'm still having this issue now.

RMS-200.png
 
R

Revan

Explorer
Joined
Mar 22, 2017
Messages
81
The bug still exists in TrueNAS-12.0-U8 when i click on Storage -> Disks and when i select my nvd0 device (mark the checkbox).
Then i can still run a manual test and this will result in the error message, i mentioned above.

It's only fixed for the right arrow button "expand/collpase row", there the manuel test doesn't show up for this device.
 
You must log in or register to reply here.

Similar threads

VivoAzzurro
Error when attempting manual SMART test
Replies
1
Views
1K
M103Tanker
M
S
Freenas - to - TrueNas Virtual machine failed to connect to libvirt
2
Replies
27
Views
11K
olly86
O
julian35152
VM remove error: "dataset does not exist" after data loss
Replies
3
Views
2K
julian35152
julian35152
L
Cannot create NFS share (sqlite3.OperationalError)
Replies
1
Views
1K
lpwevers
L
V
vm_create: This system does not support virtualization Error
Replies
12
Views
3K
headwhacker
H
Top