Unable to run Manual Smart tests from GUI

[richcr]

Hi all

I'm a new user. I recently installed TrueNAS Core (TrueNAS-12.0-U8) on an IBM X3250 M5, using an HBA card to connect to my Netapp DS4243 disk shelf. I have two SATA SSDs in the X3250 which are used as the boot-pool and 24x2TB drives in the shelf. All drives are seen and recognised in TrueNAS and I've setup my pool using 4 vdevs of 6 drives in RZ2 configuration.

When I go to Storage > Disks and select either of the boot-pool SSDs, I can successfully run a manual SMART test. However, if I select any of the drives in the shelf, I receive the following error:

---

Code:

ValidationErrors
[EINVAL] disks.0.identifier: {serial_lunid}YGH0R5XD _5000cca01c39ab38 is not valid. Please provide a valid disk identifier.


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 1213, in _call
    return await methodobj(*prepared_call.args)
  File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 975, in nf
    return await f(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/smart.py", line 403, 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}YGH0R5XD        _5000cca01c39ab38 is not valid. Please provide a valid disk identifier.

---

I can run the tests from CLI using smartctl -t short /dev/da0 and it works fine, just not from GUI?

I also tried to scheduled the tests to run using 'Tasks' but when checking the output of smartctl - a /dev/da0 etc, the tests do not appear to have run, so not sure if the above error is also preventing scheduled SMART tasks to be run? I ensured the SHORT and LONG tests were scheduled a few hours apart to avoid any scheduling conflict (SHORT @ 00:00, LONG @ 03:00)

I did a search before posting and found another user who posted the same issue previously, but there are no responses on their thread to suggest if it was ever resolved:

https://www.truenas.com/community/threads/error-when-attempting-manual-smart-test.93060/

Any help would be much appreciated.

Thanks,
Rich

 

[Hypopheralcus]

I want to once more raise that issue

I just installed 4 NVME SSD vie PCIE Bifurcation - and when I try to run a manual SMART test on either one or all of those 4, I get the error as described:

Error: Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/middlewared/main.py", line 139, 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 1235, in _call
return await methodobj(*prepared_call.args)
File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 975, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/smart.py", line 411, 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.1.identifier: {serial_lunid}S667NJ0T527685_36363730545276850025384a00000001 is not valid. Please provide a valid disk identifier.
[EINVAL] disks.2.identifier: {serial_lunid}S667NJ0T527696_36363730545276960025384a00000001 is not valid. Please provide a valid disk identifier.
[EINVAL] disks.3.identifier: {serial_lunid}S667NJ0T527693_36363730545276930025384a00000001 is not valid. Please provide a valid disk identifier.
[EINVAL] disks.4.identifier: {serial_lunid}S667NJ0T527692_36363730545276920025384a00000001 is not valid. Please provide a valid disk identifier.

A manual test with the other disks (i.e. SATADOM-Boot disks and SAS HDDs on a Backplane with expander controller) works perfectly fine.