M.2 nvme expansion bd

So today I was busy and I got the SMART information out of the device.
The first thing I messed up last time was the idproduct which was 2364 instead of 2362, which I corrected. The problem is that nvme support for ASM2362 was only added in smarmontools 7.3 and higher… Debian bullseye is still stuck on 7.2 which does not support it. So either you go bookworm or you can do some trickery - I manage to stay on bullseye. The steps I took to achieve it were the following:
I have openmediavault installed on a raspbian os.

prepare some dependencies

sudo apt-get install autoconf automake debhelper-compat libcap-ng-dev libselinux1-dev libsystemd-dev devscripts -y

remove the old smartmontools

sudo dpkg -r --force-depends smartmontools

get the newer version

dget https://deb.debian.org/debian/pool/main/s/smartmontools/smartmontools_7.3-1.dsc

create directory and exctract package into it

dpkg-source -x smartmontools_7.3-1.dsc

go to new directory

cd smartmontools-7.3/

build it

sudo dpkg-buildpackage -rfakeroot -b

go back

cd ..

add the built packages

sudo dpkg -i smartmontools_7.3-1_armhf.deb
sudo dpkg -i smartmontools-dbgsym_7.3-1_armhf.deb 

verify everything’s ok

sudo apt-get update && sudo apt-get upgrade
sudo smartctl -V

there should be nothing broken and you should see version 7.3
then to get the smart info do

sudo smartctl -a /dev/sda

for good measure devscripts can be removed, as it’s not needed

sudo apt-get remove devscripts

et voila

So to sum up if we want smart the official way I guess we need to wait until bookworm gets released… :frowning:
Anyway, now I am trying to get the openmediavault to work… I noticed that it is identifying my disk as sat and sudo smartctl -a /dev/sda -d sat will throw an error. There is a new type for asmedia - sudo smartctl -a /dev/sda -d sntasmedia which works for me. However, I cannot seem to yet figure out how to modify the openmedivault to use proper commands.

2 Likes