ses0 device visible in SMART widget

Started by ksx4system, August 02, 2023, 03:43:59 PM

Previous topic - Next topic
Hello,

I've just upgraded my router from 23.1.11_1 to 23.7 release. Everything seems to work fine but I see a non-existent device named ses0 within SMART widget on dashboard. How do I remove it? This device is not visible in SMART menu, just ada0 (SSD system drive, the only storage available for this machine).

Thanks in advance for any help.
HP ProDesk 600 G1 SFF (OPNsense latest stable)
i3 4160 / 8GB RAM / 60GB SLC SSD / Intel and Broadcom 1GbE NICs

have a nice day :)

August 02, 2023, 03:48:39 PM #1 Last Edit: August 02, 2023, 04:02:07 PM by franco
https://github.com/opnsense/plugins/issues/3513

If we have enough complaints I will switch back to the old behaviour. This is how "smartctl" sees devices and thinks this is a disk for one reason or another.


Cheers,
Franco

Quote from: franco on August 02, 2023, 03:48:39 PM
This is how "smartctl" sees devices and things

I assume this could be safely ignored then (eg. only aesthetic issue). Thanks for rapid reply and have a great day :)
HP ProDesk 600 G1 SFF (OPNsense latest stable)
i3 4160 / 8GB RAM / 60GB SLC SSD / Intel and Broadcom 1GbE NICs

have a nice day :)

Yes but.. what is the exact metric for ignoring something that is not a disk after all? ;)

The old script also had to dance around the nmve driver madness.


Cheers,
Franco

Quote from: franco on August 02, 2023, 04:03:51 PM
Yes but.. what is the exact metric for ignoring something that is not a disk after all? ;)

The ses0 device probably can't fail (it's not a real disk) so it can be ignored.
HP ProDesk 600 G1 SFF (OPNsense latest stable)
i3 4160 / 8GB RAM / 60GB SLC SSD / Intel and Broadcom 1GbE NICs

have a nice day :)

Quote from: franco on August 02, 2023, 04:03:51 PM
Yes but.. what is the exact metric for ignoring something that is not a disk after all? ;)
The old script also had to dance around the nmve driver madness.

nvd* disk devices are going to be replaced by nda* and integrated into the CAM subsystem. I do not know from the top of my head in which FreeBSD release this is going to be the default.

One can set the loader tunable hw.nvme.use_nvd to 0 to force the new behaviour on FreeBSD 13.

Warning: if you installed with UFS, changing this after the fact might render your installation unable to boot. ZFS users should be fine.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Thanks for the insight. Well, not with our UFS install using labels properly, but we should be careful here indeed.

My best guess here is just revert that change than, I don't feel like scripting around smartctl which could go stale at any point in time as well or needs more maintenance.

Ok?


Cheers,
Franco

I was all for it. But I have no system on which the sysctl method would not work. This is my TrueNAS CORE (FreeBSD 13), the box with the most disks plus different types, too:
root@freenas[~]# sysctl -n kern.disks
ada5 ada4 ada3 ada2 ada1 ada0 nda2 nda1 nda0


I just checked, you still need to use /dev/nvme* for smartctl, even with the nda* devices enabled, so special treatment still necessary.  :-\ At least on 13.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)