Hi All,

 

I'm currently running glances in a docker container to export system/disk stats to influxdb, and then graphing that data via grafana.

 

That all works great (after some frustrating setup)... the one thing I'm missing now is pulling hard disk temp stats in. Glances provides support for this if you have the hddtemp python library install, and is supposed to just work out of the box with it once it's installed.

 

I've seen some setup guides around for non-unraid systems:

http://www.cyberciti.biz/tips/howto-monitor-hard-drive-temperature.html

 

Has anyone installed hddtemp on unraid? Should I dockerize it? Will the setup link I posted above actually work on unraid without causing system issues?

 

Here's what happens when I try to install hddtemp on the host:

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... no
checking for gcc... no
checking for cc... no
checking for cc... no
checking for cl... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

I need to install a 'C' compiler somehow...

 

Thanks!

Any linux (or docker?) gurus out there that have an idea?

Well the fact that we can access hdd temps in Unraid, makes me think it should be possible.

 

Sent from my LG-H815 using Tapatalk

 

 

I'm sure it's possible. I think unraid taps into the temperatures directly via SMART stats.However, I will need to specifically use the hddtemp lib because that is a dependency of the glances app for obtaining temp info.

Ok, so I've made a docker container for hddtemp -> https://hub.docker.com/r/drewster727/hddtemp-docker/

 

I'm running this command to install it:

docker run -d --name="hddtemp-docker" -e HDDTEMP_ARGS="-q --listen localhost --port 7634 /mnt/*" --net="host" --pid host -e TZ="America/Chicago" -v "/var/run/docker.sock":"/var/run/docker.sock":rw -v "/mnt":"/mnt":ro drewster727/hddtemp-docker

 

It installs successfully, then I get into the docker UI in Unraid. It tells me it exited X seconds ago. I click on that to get the logs for that container... nothing.

 

Here's my dockerfile:

#
# hddtemp Dockerfile
#

# Pull base image.
FROM ubuntu

# Install hddtemp
RUN apt-get update && apt-get -y install build-essential hddtemp

# Define working directory.
WORKDIR /hddtemp

# Define default command.
# example = -d --listen localhost --port 7634 /dev/s*
CMD hddtemp $HDDTEMP_ARGS

 

Anyone have any idea what's up?

more info from the logs...

 

docker logs hddtemp-docker
ERROR: /mnt/user0: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/user: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk9: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk8: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk7: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk6: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk5: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk4: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk3: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk2: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk15: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk14: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk13: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk12: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk11: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk10: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/disk1: can't determine bus type (or this bus type is unknown)
ERROR: /mnt/cache: can't determine bus type (or this bus type is unknown)

 

then I realized I mapped /mnt, changed it to /dev and now the logs say:

/dev/sda: open: Operation not permitted
/dev/sda1: open: Operation not permitted
/dev/sdb: open: Operation not permitted
/dev/sdb1: open: Operation not permitted
/dev/sdc: open: Operation not permitted
/dev/sdc1: open: Operation not permitted
/dev/sdd: open: Operation not permitted
/dev/sdd1: open: Operation not permitted
/dev/sde: open: Operation not permitted
/dev/sde1: open: Operation not permitted
/dev/sdf: open: Operation not permitted
/dev/sdf1: open: Operation not permitted
/dev/sdg: open: Operation not permitted
/dev/sdg1: open: Operation not permitted
/dev/sdh: open: Operation not permitted
/dev/sdh1: open: Operation not permitted
/dev/sdi: open: Operation not permitted
/dev/sdi1: open: Operation not permitted
/dev/sdj: open: Operation not permitted
/dev/sdj1: open: Operation not permitted
/dev/sdk: open: Operation not permitted
/dev/sdk1: open: Operation not permitted
/dev/sdl: open: Operation not permitted
/dev/sdl1: open: Operation not permitted
/dev/sdm: open: Operation not permitted
/dev/sdm1: open: Operation not permitted
/dev/sdn: open: Operation not permitted
/dev/sdn1: open: Operation not permitted
/dev/sdo: open: Operation not permitted
/dev/sdo1: open: Operation not permitted
/dev/sdp: open: Operation not permitted
/dev/sdp1: open: Operation not permitted
/dev/sdq: open: Operation not permitted
/dev/sdq1: open: Operation not permitted
/dev/sdr: open: Operation not permitted
/dev/sdr1: open: Operation not permitted
/dev/sds: open: Operation not permitted
/dev/sds1: open: Operation not permitted
/dev/sg0: open: Operation not permitted
/dev/sg1: open: Operation not permitted
/dev/sg10: open: Operation not permitted
/dev/sg11: open: Operation not permitted
/dev/sg12: open: Operation not permitted
/dev/sg13: open: Operation not permitted
/dev/sg14: open: Operation not permitted
/dev/sg15: open: Operation not permitted
/dev/sg16: open: Operation not permitted
/dev/sg17: open: Operation not permitted
/dev/sg18: open: Operation not permitted
/dev/sg2: open: Operation not permitted
/dev/sg3: open: Operation not permitted
/dev/sg4: open: Operation not permitted
/dev/sg5: open: Operation not permitted
/dev/sg6: open: Operation not permitted
/dev/sg7: open: Operation not permitted
/dev/sg8: open: Operation not permitted
/dev/sg9: open: Operation not permitted

 

so, I *think* I am to the point where hddtemp is working, but it doesn't have access to the disk info (or the SMART attributes?)

 

got it working... needed --privileged=true

 

influxdb has the colums now, but no data in the fields... LOL just can't win

got it working... needed --privileged=true

 

influxdb has the colums now, but no data in the fields... LOL just can't win

Here's a link to a pre compiled version. http://packages.slackonly.com/pub/packages/14.1-x86_64/system/hddtemp/hddtemp-0.3beta15-x86_64-1_slack.txz

I ended up creating my own docker container to get things working:

https://hub.docker.com/r/drewster727/hddtemp-docker/