Hello,
I got the same problems since I installed OMV5 as replacement for OMV4.
On my system, the noted devices are LV partitions with present LVM snapshots.
Given this LV partition with two present snapshots
~# lvs | grep home
export_home ldd owi-aos--- 128,00g
export_home_2110100610_w1 ldd swi-aos--- 32,00g export_home 17,83
export_home_2110150611_d1 ldd swi-aos--- 8,00g export_home 4,89
the following devices exist on the system. Some of them are the snapshots, some others kind of snapshot "helper" devices:
/dev/mapper# ls -l | grep home
lrwxrwxrwx 1 root root 7 Okt 15 06:11 ldd-export_home -> ../dm-2
lrwxrwxrwx 1 root root 7 Okt 15 06:11 ldd-export_home_2110100610_w1 -> ../dm-4
lrwxrwxrwx 1 root root 7 Okt 15 06:11 ldd-export_home_2110100610_w1-cow -> ../dm-3
lrwxrwxrwx 1 root root 8 Okt 15 06:11 ldd-export_home_2110150611_d1 -> ../dm-26
lrwxrwxrwx 1 root root 8 Okt 15 06:11 ldd-export_home_2110150611_d1-cow -> ../dm-25
lrwxrwxrwx 1 root root 7 Okt 15 06:11 ldd-export_home-real -> ../dm-1
and the OMV webGUI fails when clicking S.M.A.R.T. with noticing arbitrarily one of these devices like f.i.
which happens to be the representation of /dev/mapper/ldd-export_home-real.
The workflow in the webGUI stops then. S.M.A.R.T. configuration doesn't work.
It seems that the function doesn't distinct hard, lv, snapshot and "helper" devices.
As a surprise, the problem exists since OMV5 only.
I didn't exist in my former OMV4 installation, where I could successfully configure and run S.M.A.R.T. checks on my hard disks with the same presence of snapshots as here.
Best regards
Robert