We've released interim 0.3.5.0 version some time ago, that is available for download. It hasn't been publicly announced because included various small improvements and bug fixes, and has been addressed to users, who faced these issues (support of vdev_id.conf file, display DRAID pools in UI, better support for NVMe S.M.A.R.T., support for pools with listsnapshots=on property, etc). We are still working on new Preview 4 (0.4.0.0) release with the new set of features and currently expect it on March 6.just checking in as I haven't seen any updates on the site, any news on a new release?
We use smartmontools to get the SMART data (the same package as in the article you mentioned). Poolsman mostly displays the data that it gets from this tool (the overall health state is also provided by this). Additionally we perform some minor transformations to make the data more friendly (e.g. calculate host reads/writes in bytes). You also can manually check any of the SMART attributes (including attributes from the article), provided by your drive and supported by smartmontools package.Regarding SMART and disks, how do you currently determine that a disk is healthy? Are you perhaps monitoring these? What SMART Hard Disk Errors Actually Tell Us
Thanks. It definitely makes sense to monitor these particular SMART attributes in parallel (and/or highlight them when they RAW values are greater than zero). We've added a research task for that into our backlog. Probably we will add some kind of such monitoring in one of our next releases (at least simple highlighting of these attributes should be easy to implement).Thank you. The reason I'm asking is because those specific SMART params seem to signal an impending drive failure without necessarily triggering SMART overall health alarms - backblaze have a massive statistic body of evidence on it. I think there's an opportunity here for SMART(er) drive health monitoring beyond simply echoing SMART values back to the user. Quoting the article:
View attachment 27864