Leaderboard

it does call that to get temps for disks that are spun up. In your disk settings what is the value of your poll attributes, mine is 1800 and spin down delay of 15mins.

A few tweaks to scripts and commands but I got it working, thanks.

That is done by the emhttp process which calls this script. Sounds like something else is spinning the drives up. I have a wrapper around the commands whilst in rc and was working on SAS spinup/down and fixes to smartctl. Below is part of my go file and attached are the two wrappers. hdparm and smartctl are moved and wrappers replace them and call the real command. You need to check it points to the correct real command in the wrapper. it should only be the real command in the smartctl wrapper you need to correct as it was using smartctl.r5131 on my system if you want to use them. mv /usr/sbin/smartctl /usr/sbin/smartctl.old cp /boot/extras/smartctl.wrapper /usr/sbin/smartctl chmod +x /usr/sbin/smartctl cp /usr/sbin/hdparm /usr/local/sbin/hdparm.real chmod +x /usr/local/sbin/hdparm.real cp /boot/extras/hdparm.wrapper /usr/sbin/hdparm chmod +x /usr/sbin/hdparm You will get output in syslog so you can see what is using the commands and args. Dec 20 13:47:39 Tower smartctl wrapper[17892]: caller is smartctl_type, grandpa is emhttpd, device /dev/sdb, args "-A /dev/sdb" Dec 20 13:47:59 Tower hdparm wrapper[18010]: caller is bash, grandpa is ttyd, device /dev/sdb, args "-C /dev/sdb" Wrapper and Smartctl.zip

Ah, was worth a shot. I only have a single drive in my second pool, so not sure if they makes a difference, it shouldnt. Sorry don't know what else to suggest. Maybe Limetech will find something. I dont use autofan, does that query the disks for temps?

If that uses rr272x_1x driver then, forgot to add to release notes, it does not build with Linux 5.10 kernel. I suggest you contact HighPoint and ask them to update their driver.

Hi @CS01-HS my second pool spins down, but didnt seem to when I first when from beta35 to rc1. But wasn't sure if was due to me setting spin down timer on test pool drive as I had disabled spin downs so my SAS drives would use timers. Now I have the timer set for the main pool I changed the second pool to use the default and now doesn't make any difference on the setting it spins down. Try changing the value on the pool and then change it back to see if that kicks it into life, but may have just been coincidence for me.

Spindown fixes are already coming with rc3, probably best to wait for that and retest.

This error is due to the absence of the 'nvme-cli' package in the container, and thus the 'nvme' command. You have to install the missing package through the "Post Arguments" parameter of the container (Edit/Advanced View). Here's the content of my "Post Argument" param for reference, properly working with nvme devices, to be adapted of course to your specific configuration if required : /bin/sh -c 'apt-get update && apt-get -y upgrade && apt-get -y install ipmitool && apt-get -y install smartmontools && apt-get -y install lm-sensors && apt-get -y install nvme-cli && telegraf' Edit the parameter according to your needs, the container will restart and you shouldn't have the error message in the log.

If you don't see device temperatures upon reboot, just click "spin up all" and everything should be fine until I can release -rc3.

Libvirt version: 6.5.0 QEMU version: 5.1.0