NVMe probe finds incorrect drive "error" state and suggests replacing the drive

[kode54]

The current release of smartmontools, 7.4.0, as of this post, has a misfeature with certain NVMe drives. Those drives do not support querying the self-test logs from the namespace devices (nvme#n1, etc), but only the root or broadcast device. (nvme#)

In fact, one of my drives, a Samsung 980 Pro, not only spits out an error for that command, it logs the erroneous command in its error log forever more.

The latest snapshot of 7.5.0 fixes this by sending the commands to the correct place, not sure if it's specific to these drives, though.

Unfortunately, that has already resulted in a mess of hardware probes in the hardware database all reporting errors for these affected drives.