Is NVM E still experimental in smarttools?

You have smart settings built into nvme-cli btw:

nvme smart-log <ctrl> --human-readable

What smart command are you running? I can (elevated) run:

sudo smartctl --all /dev/nvme0 and see the details...

On 21/07/2026 08:50, Óscar García Amor wrote:

  nvme0, nvme1 etc. are control devices
  nvme0n1 means nvme0 namespace id 1 and it's a block device

Thank you for your replies.

The problem I'm having with all this stems from how `smartctl` works.
When you run `smartctl --scan`, the device it finds is `/dev/nvme0`,
not `/dev/nvme0n1`:
```
# smartctl --scan
/dev/nvme0 -d nvme # /dev/nvme0, NVMe device
```

This causes it to then try to access `/dev/nvme0` to retrieve the
disk's S.M.A.R.T. data instead of `/dev/nvme0n1`, and of course, it
fails due to a lack of permissions. I could open an issue with the
`smartctl` developer, but first I'd like to make sure the problem isn't
actually related to how we set permissions at the Arch Linux level.

Greetings.


Reply via email to