Adding another voice to this — I am having this issue on 13.0-U3.1 — and not only on NVMe disks.
Even on a SATA HDD (da5), I get an error similar to the following:
Not sure if it is related, but under Tasks > S.M.A.R.T Tests in the GUI, the disks menu is populated with only four devices (ada0, ada1, da0, and da1). I am able to initiate SMART tests for these four disks manually in Storage > Disks.
Even on a SATA HDD (da5), I get an error similar to the following:
Code:
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.0.identifier: {serial_lunid}Y6YGGNBD _5000cca2adc6abd4 is not valid. Please provide a valid disk identifier.
Not sure if it is related, but under Tasks > S.M.A.R.T Tests in the GUI, the disks menu is populated with only four devices (ada0, ada1, da0, and da1). I am able to initiate SMART tests for these four disks manually in Storage > Disks.