Re: new drivedb.h incompatible?

----------------------------------------
> Subject: Re: [smartmontools-support] new drivedb.h incompatible?
> To: [email protected]
> CC: [email protected]
> From: [email protected]
> Date: Sat, 30 Apr 2016 13:39:57 +0200
>
> Reinoud Koornstra wrote:
>> I did build smartmontools from the scv repository.
>> I configured it like this:
>>
>> ./configure --prefix=/usr --with-savestates=yes --with-attributelog=yes --with-drivedbdir=yes --with-update-smart-drivedb=yes -with-nvme-devicescan=yes
>
> If --prefix=/usr is used instead of its default (/usr/local), it is
> recommended to set --sysconfdir=/etc and --localstatedir=/var. Otherwise
> nonstandard directories /usr/etc and /usr/var are used. This is not
> needed for the other directories. /usr/sbin and
> /usr/share/{doc,man,smartmontools} are correctly set by --prefix=/usr.
>
> Here a fixed version of above, unneeded --with options are removed:
>
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
> --with-savestates --with-attributelog --with-nvme-devicescan

Thanks, I did notice the /usr/var stuff indeed.
Ok I did rebuild and am running it now:

May  2 19:59:01 router-dev smartd[14825]: smartd 6.5 2016-04-27 r4312 [x86_64-linux-4.4.5] (local build) 
May  2 19:59:01 router-dev smartd[14825]: Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org 
May  2 19:59:01 router-dev smartd[14825]: Opened configuration file /usr/etc/smartd.conf 
May  2 19:59:01 router-dev smartd[14825]: Drive: DEVICESCAN, implied '-a' Directive on line 23 of file /usr/etc/smartd.conf 
May  2 19:59:01 router-dev smartd[14825]: Configuration file /usr/etc/smartd.conf was parsed, found DEVICESCAN, scanning devices 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sda, type changed from 'scsi' to 'sat' 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sda [SAT], opened 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sda [SAT], WDC WD1003FZEX-00MK2A0, S/N:WD-WCC3F7RCJLS4, WWN:5-0014ee-20cf9eac4, FW:01.01A01, 1.00 TB 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sda [SAT], found in smartd database: Western Digital Black 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list. 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sdb, type changed from 'scsi' to 'sat' 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sdb [SAT], opened 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sdb [SAT], Crucial_CT250MX200SSD1, S/N:154711194417, WWN:5-00a075-111194417, FW:MU03, 250 GB 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sdb [SAT], found in smartd database: Crucial/Micron MX100/MX200/M5x0/M600 Client SSDs 
May  2 19:59:01 router-dev smartd[14825]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list. 
May  2 19:59:01 router-dev smartd[14825]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices

>
>
>> This is the result:
>>
>> ...
>> Apr 29 02:25:01 router-dev smartd[9442]: Device: /dev/sdb [SAT], Crucial_CT250MX200SSD1, S/N:154711194417, WWN:5-00a075-111194417, FW:MU03, 250 GB
>> Apr 29 02:25:01 router-dev smartd[9442]: Device: /dev/sdb [SAT], found in smartd database: Crucial/Micron MX100/MX200/M5x0/M600 Client SSDs
>> Apr 29 02:25:01 router-dev smartd[9442]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
>> Apr 29 02:25:01 router-dev smartd[9442]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
>> ...
>>
>> The SSD is now recognized nicely. :)
>
> Thanks for testing. :)
>
>
>> Previous temperatures showed very high, that might not be correct, but I'll follow up if I see it again.
>
> You might want to enable temperature tracking in smartd.conf. See '-W
> DIFF[,INFO[,CRIT]]' on smartd.conf man page.

Ok, I'll add this to the boot params.

In the mean time I noticed this:

May  2 15:46:17 router-dev smartd[12364]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 120 to 119 
May  2 15:46:17 router-dev smartd[12364]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 74 to 73

Likely these aren't the real temperatures?
Otherwise these looks critical to me and reduces the lifetime of these disks.
Should I interpret these temperatures differently?

>
> Thanks,
> Christian

Thanks,
Reinoud.
>
 		 	   		  
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z