Re: Unable to get the temp for one disk in Stretch

2018-01-08 Thread Daniel Bareiro 
Hi, again.

On 08/01/18 10:28, Daniel Bareiro wrote:

>>> I recently updated my firewall from Jessie to Stretch and I realized
>>> that the check_lm_sensors plugin was apparently not working because it
>>> was not possible to get the temperature of one of the disks:
>>>
>>> # /usr/lib/nagios/plugins/check_lm_sensors --list
>>> LM_SENSORS UNKNOWN - Error while executing /usr/sbin/hddtemp -n /dev/sdb
>>>
>>> These are two disks which form several MD arrays.
>>>
>>> # /usr/sbin/hddtemp -n /dev/sda
>>> 44
>>>
>>> # /usr/sbin/hddtemp -n /dev/sdb
>>> WARNING: Drive /dev/sdb doesn't seem to have a temperature sensor.
>>> WARNING: This doesn't mean it hasn't got one.
>>> WARNING: If you are sure it has one, please contact me
>>> (hddt...@guzu.net).
>>> WARNING: See --help, --debug and --drivebase options.
>>> /dev/sdb: WDC WD5000AAKX-60U6AA0:  no sensor

>> It *might* be that the drive database doesn't recognise the drive (it'd
>> be odd for the database to forget about a drive, but accidents happen).
>>
>> Try running "sudo /usr/sbin/update-smart-drivedb" and check again.

> Thanks for your reply and your time.
> 
> It seems that this file is not available:
> 
> ---
> root@alderamin:~# /usr/sbin/update-smart-drivedb
> bash: /usr/sbin/update-smart-drivedb: No existe el fichero o el directorio
> ---
> 
> I looked for it in another path but I did not find it.
> 
> The strange thing is the man page does exist.
> 
> Can someone with Stretch please confirm?

I found this in the smartmontools package documentation:

--
root@alderamin:/usr/share/doc/smartmontools# zcat NEWS.Debian.gz
smartmontools (6.4+svn4214-1) unstable; urgency=medium

  Previous versions of the smartmontools package included a tool
  update-smart-drivedb which downloaded updated drive definitions
  from the smartmontools website and stored them at

  /var/lib/smartmontools/drivedb/drivedb.h

  This tool did not download the definitions in a secure manner and
  so the feature has been removed in this version.  Future drive DB
  updates will be propagated via normal Debian package updates,
  including backports.

  If you already have a drivedb.h file at that location, smartctl
  will continue to use it.

 -- Jonathan Dowland   Mon, 01 Feb 2016 21:19:47 +
(...)
--

The version available in Stretch for smartmontools is 6.5+svn4324-1.

So the update of the disk database would be done automatically when
installing the smartmontools package?

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: Unable to get the temp for one disk in Stretch

2018-01-08 Thread Daniel Bareiro 
Hi, Darac.

On 08/01/18 06:33, Darac Marjal wrote:

>> I recently updated my firewall from Jessie to Stretch and I realized
>> that the check_lm_sensors plugin was apparently not working because it
>> was not possible to get the temperature of one of the disks:
>>
>> # /usr/lib/nagios/plugins/check_lm_sensors --list
>> LM_SENSORS UNKNOWN - Error while executing /usr/sbin/hddtemp -n /dev/sdb
>>
>> These are two disks which form several MD arrays.
>>
>> # /usr/sbin/hddtemp -n /dev/sda
>> 44
>>
>> # /usr/sbin/hddtemp -n /dev/sdb
>> WARNING: Drive /dev/sdb doesn't seem to have a temperature sensor.
>> WARNING: This doesn't mean it hasn't got one.
>> WARNING: If you are sure it has one, please contact me
>> (hddt...@guzu.net).
>> WARNING: See --help, --debug and --drivebase options.
>> /dev/sdb: WDC WD5000AAKX-60U6AA0:  no sensor

> It *might* be that the drive database doesn't recognise the drive (it'd
> be odd for the database to forget about a drive, but accidents happen).
> 
> Try running "sudo /usr/sbin/update-smart-drivedb" and check again.

Thanks for your reply and your time.

It seems that this file is not available:

---
root@alderamin:~# /usr/sbin/update-smart-drivedb
bash: /usr/sbin/update-smart-drivedb: No existe el fichero o el directorio
---

I looked for it in another path but I did not find it.

The strange thing is the man page does exist.

Can someone with Stretch please confirm?


Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: Unable to get the temp for one disk in Stretch

2018-01-08 Thread Darac Marjal 

On Sun, Jan 07, 2018 at 03:08:48PM -0300, Daniel Bareiro wrote:

Hi all!

I recently updated my firewall from Jessie to Stretch and I realized
that the check_lm_sensors plugin was apparently not working because it
was not possible to get the temperature of one of the disks:

# /usr/lib/nagios/plugins/check_lm_sensors --list
LM_SENSORS UNKNOWN - Error while executing /usr/sbin/hddtemp -n /dev/sdb

These are two disks which form several MD arrays.

# /usr/sbin/hddtemp -n /dev/sda
44

# /usr/sbin/hddtemp -n /dev/sdb
WARNING: Drive /dev/sdb doesn't seem to have a temperature sensor.
WARNING: This doesn't mean it hasn't got one.
WARNING: If you are sure it has one, please contact me (hddt...@guzu.net).
WARNING: See --help, --debug and --drivebase options.
/dev/sdb: WDC WD5000AAKX-60U6AA0:  no sensor


It *might* be that the drive database doesn't recognise the drive (it'd 
be odd for the database to forget about a drive, but accidents happen).


Try running "sudo /usr/sbin/update-smart-drivedb" and check again.



In fact, not even smartctl is able to see the temperature:

# smartctl -a /dev/sda | grep Temperature_Celsius
194 Temperature_Celsius 0x0022   099   090   000Old_age   Always
 -   44

# smartctl -a /dev/sdb | grep Temperature_Celsius
#

It's weird because in Jessie I do not remember having this problem. I
can even find smartd entries in the syslog before doing the update:

# grep smart syslog
Jan  7 06:52:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 61
Jan  7 10:52:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 61 to 60
Jan  7 11:22:27 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 102 to 101
Jan  7 12:22:28 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 101 to 100
Jan  7 12:22:28 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 59
Jan  7 13:52:27 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 100 to 99
Jan  7 14:22:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 59 to 58

So I'm not sure where the problem may be. If it is in smartd (and
hddtemp is based on smartd) or maybe in some kernel module.

Any thoughts will be greatly appreciated.

Thanks in advance.


Kind regards,
Daniel






--
For more information, please reread.


signature.asc
Description: PGP signature

Unable to get the temp for one disk in Stretch

2018-01-07 Thread Daniel Bareiro 
Hi all!

I recently updated my firewall from Jessie to Stretch and I realized
that the check_lm_sensors plugin was apparently not working because it
was not possible to get the temperature of one of the disks:

# /usr/lib/nagios/plugins/check_lm_sensors --list
LM_SENSORS UNKNOWN - Error while executing /usr/sbin/hddtemp -n /dev/sdb

These are two disks which form several MD arrays.

# /usr/sbin/hddtemp -n /dev/sda
44

# /usr/sbin/hddtemp -n /dev/sdb
WARNING: Drive /dev/sdb doesn't seem to have a temperature sensor.
WARNING: This doesn't mean it hasn't got one.
WARNING: If you are sure it has one, please contact me (hddt...@guzu.net).
WARNING: See --help, --debug and --drivebase options.
/dev/sdb: WDC WD5000AAKX-60U6AA0:  no sensor

In fact, not even smartctl is able to see the temperature:

# smartctl -a /dev/sda | grep Temperature_Celsius
194 Temperature_Celsius 0x0022   099   090   000Old_age   Always
  -   44

# smartctl -a /dev/sdb | grep Temperature_Celsius
#

It's weird because in Jessie I do not remember having this problem. I
can even find smartd entries in the syslog before doing the update:

# grep smart syslog
Jan  7 06:52:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 61
Jan  7 10:52:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 61 to 60
Jan  7 11:22:27 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 102 to 101
Jan  7 12:22:28 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 101 to 100
Jan  7 12:22:28 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 59
Jan  7 13:52:27 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 100 to 99
Jan  7 14:22:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 59 to 58

So I'm not sure where the problem may be. If it is in smartd (and
hddtemp is based on smartd) or maybe in some kernel module.

Any thoughts will be greatly appreciated.

Thanks in advance.


Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature