Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

"355/113 -- Not the famous irrational number PI, but an incredible simulation!"


computers / alt.os.linux.mageia / No interaction between hddtemp and smart?

SubjectAuthor
* No interaction between hddtemp and smart?Markus Robert Kessler
`* Re: No interaction between hddtemp and smart?Markus Robert Kessler
 +* Re: No interaction between hddtemp and smart?Markus Robert Kessler
 |`* Re: No interaction between hddtemp and smart?Paul
 | `- Re: No interaction between hddtemp and smart?Markus Robert Kessler
 `* Re: No interaction between hddtemp and smart?David W. Hodgins
  `- Re: No interaction between hddtemp and smart?Markus Robert Kessler

1
No interaction between hddtemp and smart?

<tf4ius$3i39a$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5124&group=alt.os.linux.mageia#5124

 copy link   Newsgroups: alt.os.linux.mageia alt.os.linux.ubuntu
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: no_re...@dipl-ing-kessler.de (Markus Robert Kessler)
Newsgroups: alt.os.linux.mageia,alt.os.linux.ubuntu
Subject: No interaction between hddtemp and smart?
Date: Mon, 5 Sep 2022 10:27:40 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 46
Message-ID: <tf4ius$3i39a$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 5 Sep 2022 10:27:40 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="eebb4a051f861fde3f9f7b6afc6214b4";
logging-data="3738922"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+cKb+oby6alZwnixAv8Vlb"
User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a
git.gnome.org/pan2)
Cancel-Lock: sha1:ablzLN7IvYVJXA6PsN0Pb2N9YPM=
 by: Markus Robert Kessle - Mon, 5 Sep 2022 10:27 UTC

Hi everyone,

hope this is a known issue:

I am doing some testing with a Samsung EVO 870 drive. Since this one was
not in the smart database, so I made an update:

update-smart-drivedb

After that, I can see the temperature of the drive:

$ smartctl --all /dev/sdb | grep ^190
190 Airflow_Temperature_Cel 0x0032 072 045 000 Old_age
Always - 28

From what I have undestood, hddtemp is relying on the values received by
smart. So, I'd expect, that hddtemp now also works. If the drive is not
yet known to hddtemp, at least the field names should be displayable in
debug mode. But this seems not the case here:

$ hddtemp /dev/sdb
/dev/sdb: Samsung SSD 870 EVO 250G: S.M.A.R.T. not available

$ hddtemp --debug /dev/sdb

================= hddtemp 0.3-beta15 ==================
Model: Samsung SSD 870 EVO 250G

If one of the field value seems to match the temperature, be sure to read
the hddtemp man page before sending a report (section REPORT). Thanks.

Strange.

Any idea?

Thanks,
best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

Re: No interaction between hddtemp and smart?

<tf52cd$3jrhf$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5126&group=alt.os.linux.mageia#5126

 copy link   Newsgroups: alt.os.linux.mageia alt.os.linux.ubuntu
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: no_re...@dipl-ing-kessler.de (Markus Robert Kessler)
Newsgroups: alt.os.linux.mageia,alt.os.linux.ubuntu
Subject: Re: No interaction between hddtemp and smart?
Date: Mon, 5 Sep 2022 14:50:53 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 58
Message-ID: <tf52cd$3jrhf$1@dont-email.me>
References: <tf4ius$3i39a$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 5 Sep 2022 14:50:53 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="eebb4a051f861fde3f9f7b6afc6214b4";
logging-data="3796527"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18KpW+MALgihSQuarDYiNFh"
User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a
git.gnome.org/pan2)
Cancel-Lock: sha1:0M1HcoMZaFUtDbEM5iipFKWIV+o=
 by: Markus Robert Kessle - Mon, 5 Sep 2022 14:50 UTC

On Mon, 05 Sep 2022 10:27:40 +0000 Markus Robert Kessler wrote:

> Hi everyone,
>
> hope this is a known issue:
>
> I am doing some testing with a Samsung EVO 870 drive. Since this one was
> not in the smart database, so I made an update:
>
> update-smart-drivedb
>
> After that, I can see the temperature of the drive:
>
> $ smartctl --all /dev/sdb | grep ^190 190 Airflow_Temperature_Cel 0x0032
> 072 045 000 Old_age Always - 28
>
> From what I have undestood, hddtemp is relying on the values received by
> smart. So, I'd expect, that hddtemp now also works. If the drive is not
> yet known to hddtemp, at least the field names should be displayable in
> debug mode. But this seems not the case here:
>
> $ hddtemp /dev/sdb /dev/sdb: Samsung SSD 870 EVO 250G: S.M.A.R.T. not
> available
>
> $ hddtemp --debug /dev/sdb
>
> ================= hddtemp 0.3-beta15 ==================
> Model: Samsung SSD 870 EVO 250G
>
>
> If one of the field value seems to match the temperature, be sure to
> read the hddtemp man page before sending a report (section REPORT).
> Thanks.
>
>
> Strange.
>
> Any idea?
>
> Thanks,
> best regards,
>
> Markus

Forgot to mention:
The drive is connected via USB-to-SATA (2 different ones tested).

Well, the Smart-values are accessible, so hddtemp should be able to
extract and display the right one. No clue what's wrong here.

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

Re: No interaction between hddtemp and smart?

<tf59t2$3kljs$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5127&group=alt.os.linux.mageia#5127

 copy link   Newsgroups: alt.os.linux.mageia alt.os.linux.ubuntu
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: no_re...@dipl-ing-kessler.de (Markus Robert Kessler)
Newsgroups: alt.os.linux.mageia,alt.os.linux.ubuntu
Subject: Re: No interaction between hddtemp and smart?
Date: Mon, 5 Sep 2022 16:59:14 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 97
Message-ID: <tf59t2$3kljs$1@dont-email.me>
References: <tf4ius$3i39a$1@dont-email.me> <tf52cd$3jrhf$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 5 Sep 2022 16:59:14 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="eebb4a051f861fde3f9f7b6afc6214b4";
logging-data="3823228"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18FCZZZyjyZlBjWK5syWTPS"
User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a
git.gnome.org/pan2)
Cancel-Lock: sha1:exMqZt274WdzlAlJcCPE7HJLf38=
 by: Markus Robert Kessle - Mon, 5 Sep 2022 16:59 UTC

On Mon, 05 Sep 2022 14:50:53 +0000 Markus Robert Kessler wrote:

> On Mon, 05 Sep 2022 10:27:40 +0000 Markus Robert Kessler wrote:
>
>> Hi everyone,
>>
>> hope this is a known issue:
>>
>> I am doing some testing with a Samsung EVO 870 drive. Since this one
>> was not in the smart database, so I made an update:
>>
>> update-smart-drivedb
>>
>> After that, I can see the temperature of the drive:
>>
>> $ smartctl --all /dev/sdb | grep ^190 190 Airflow_Temperature_Cel
>> 0x0032
>> 072 045 000 Old_age Always - 28
>>
>> From what I have undestood, hddtemp is relying on the values received
>> by smart. So, I'd expect, that hddtemp now also works. If the drive is
>> not yet known to hddtemp, at least the field names should be
>> displayable in debug mode. But this seems not the case here:
>>
>> $ hddtemp /dev/sdb /dev/sdb: Samsung SSD 870 EVO 250G: S.M.A.R.T. not
>> available
>>
>> $ hddtemp --debug /dev/sdb
>>
>> ================= hddtemp 0.3-beta15 ==================
>> Model: Samsung SSD 870 EVO 250G
>>
>>
>> If one of the field value seems to match the temperature, be sure to
>> read the hddtemp man page before sending a report (section REPORT).
>> Thanks.
>>
>>
>> Strange.
>>
>> Any idea?
>>
>> Thanks,
>> best regards,
>>
>> Markus
>
> Forgot to mention:
> The drive is connected via USB-to-SATA (2 different ones tested).
>
> Well, the Smart-values are accessible, so hddtemp should be able to
> extract and display the right one. No clue what's wrong here.
>
> Best regards,
>
> Markus

Looks as if hddtemp does NOT use the values given by smartctl, but
instead it seems that hddtem is using own -- buggy -- routines.

So, as a workaround, for external drives I recommend using this sudo-
based script:

/bin/hddetemp (root:root, 0755):

######################################################################

#!/bin/bash

for DRIVE in /dev/sd[a-z] ; do

SMARTVALUES=`sudo /sbin/smartctl --all $DRIVE`

if [ "$?" != "0" ] ; then

echo "$DRIVE: ERROR"

else

MODEL_NAME=`echo "$SMARTVALUES" | grep '^Device Model:' |
sed -e 's/^Device Model: *//'`

AIRFLOW_TEMP=`echo "$SMARTVALUES" | grep
'Airflow_Temperature_Cel' | grep -o '[0-9]*$'`

echo "$DRIVE: $MODEL_NAME: $AIRFLOW_TEMP°C"

fi

done

######################################################################

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

Re: No interaction between hddtemp and smart?

<op.1r08vv0qa3w0dxdave@hodgins.homeip.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5128&group=alt.os.linux.mageia#5128

 copy link   Newsgroups: alt.os.linux.mageia alt.os.linux.ubuntu
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: dwhodg...@nomail.afraid.org (David W. Hodgins)
Newsgroups: alt.os.linux.mageia,alt.os.linux.ubuntu
Subject: Re: No interaction between hddtemp and smart?
Date: Mon, 05 Sep 2022 13:15:21 -0400
Organization: A noiseless patient Spider
Lines: 7
Message-ID: <op.1r08vv0qa3w0dxdave@hodgins.homeip.net>
References: <tf4ius$3i39a$1@dont-email.me> <tf52cd$3jrhf$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: 8bit
Injection-Info: reader01.eternal-september.org; posting-host="d728204fbf1ab5537d42cc60a06ec642";
logging-data="3827902"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/cXSLq6rmKElZkC+mwhgxbrqkraiQJa00="
User-Agent: Opera Mail/12.16 (Linux)
Cancel-Lock: sha1:Iex8XrcO/RrAIwt8MP7F5Z4cVqs=
 by: David W. Hodgins - Mon, 5 Sep 2022 17:15 UTC

On Mon, 05 Sep 2022 10:50:53 -0400, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
> Well, the Smart-values are accessible, so hddtemp should be able to
> extract and display the right one. No clue what's wrong here.

Did you restart hddtemp.service after updating the smart db?

Regards, Dave Hodgins

Re: No interaction between hddtemp and smart?

<tf5bqe$3kt7s$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5129&group=alt.os.linux.mageia#5129

 copy link   Newsgroups: alt.os.linux.mageia alt.os.linux.ubuntu
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mageia,alt.os.linux.ubuntu
Subject: Re: No interaction between hddtemp and smart?
Date: Mon, 5 Sep 2022 13:31:58 -0400
Organization: A noiseless patient Spider
Lines: 115
Message-ID: <tf5bqe$3kt7s$1@dont-email.me>
References: <tf4ius$3i39a$1@dont-email.me> <tf52cd$3jrhf$1@dont-email.me>
<tf59t2$3kljs$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 5 Sep 2022 17:31:58 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="557cecb031dc10d66ba393ea66a98e43";
logging-data="3831036"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18lAmry2hJ3WdZw2fDWXKH2v7frUZ+RLkc="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:IUNA56j1D4doiS12khkQHFyncd4=
Content-Language: en-US
In-Reply-To: <tf59t2$3kljs$1@dont-email.me>
 by: Paul - Mon, 5 Sep 2022 17:31 UTC

On 9/5/2022 12:59 PM, Markus Robert Kessler wrote:
> On Mon, 05 Sep 2022 14:50:53 +0000 Markus Robert Kessler wrote:
>
>> On Mon, 05 Sep 2022 10:27:40 +0000 Markus Robert Kessler wrote:
>>
>>> Hi everyone,
>>>
>>> hope this is a known issue:
>>>
>>> I am doing some testing with a Samsung EVO 870 drive. Since this one
>>> was not in the smart database, so I made an update:
>>>
>>> update-smart-drivedb
>>>
>>> After that, I can see the temperature of the drive:
>>>
>>> $ smartctl --all /dev/sdb | grep ^190 190 Airflow_Temperature_Cel
>>> 0x0032
>>> 072 045 000 Old_age Always - 28
>>>
>>> From what I have undestood, hddtemp is relying on the values received
>>> by smart. So, I'd expect, that hddtemp now also works. If the drive is
>>> not yet known to hddtemp, at least the field names should be
>>> displayable in debug mode. But this seems not the case here:
>>>
>>> $ hddtemp /dev/sdb /dev/sdb: Samsung SSD 870 EVO 250G: S.M.A.R.T. not
>>> available
>>>
>>> $ hddtemp --debug /dev/sdb
>>>
>>> ================= hddtemp 0.3-beta15 ==================
>>> Model: Samsung SSD 870 EVO 250G
>>>
>>>
>>> If one of the field value seems to match the temperature, be sure to
>>> read the hddtemp man page before sending a report (section REPORT).
>>> Thanks.
>>>
>>>
>>> Strange.
>>>
>>> Any idea?
>>>
>>> Thanks,
>>> best regards,
>>>
>>> Markus
>>
>> Forgot to mention:
>> The drive is connected via USB-to-SATA (2 different ones tested).
>>
>> Well, the Smart-values are accessible, so hddtemp should be able to
>> extract and display the right one. No clue what's wrong here.
>>
>> Best regards,
>>
>> Markus
>
> Looks as if hddtemp does NOT use the values given by smartctl, but
> instead it seems that hddtem is using own -- buggy -- routines.
>
> So, as a workaround, for external drives I recommend using this sudo-
> based script:
>
> /bin/hddetemp (root:root, 0755):
>
> ######################################################################
>
> #!/bin/bash
>
> for DRIVE in /dev/sd[a-z] ; do
>
> SMARTVALUES=`sudo /sbin/smartctl --all $DRIVE`
>
> if [ "$?" != "0" ] ; then
>
> echo "$DRIVE: ERROR"
>
> else
>
> MODEL_NAME=`echo "$SMARTVALUES" | grep '^Device Model:' |
> sed -e 's/^Device Model: *//'`
>
> AIRFLOW_TEMP=`echo "$SMARTVALUES" | grep
> 'Airflow_Temperature_Cel' | grep -o '[0-9]*$'`
>
> echo "$DRIVE: $MODEL_NAME: $AIRFLOW_TEMP°C"
>
> fi
>
> done
>
> ######################################################################

Does "hddtemp" need sudo ?

https://wiki.archlinux.org/title/Hddtemp

Usage

Hddtemp requires root privileges [formatted as persistent device path]

sudo hddtemp /dev/disk/by-id/wwn-0x60015ee0000b237f

Daemon

Running the daemon allows access to the temperature information via
TCP/IP as a regular user. This is useful for scripts and system monitors.

The daemon is controlled by hddtemp.service

"hddtemp S.M.A.R.T. not available" likely means /dev/sdb was not
accessible without root privilege.

Paul

Re: No interaction between hddtemp and smart?

<tf5c27$3kljs$2@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5130&group=alt.os.linux.mageia#5130

 copy link   Newsgroups: alt.os.linux.mageia alt.os.linux.ubuntu
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: no_re...@dipl-ing-kessler.de (Markus Robert Kessler)
Newsgroups: alt.os.linux.mageia,alt.os.linux.ubuntu
Subject: Re: No interaction between hddtemp and smart?
Date: Mon, 5 Sep 2022 17:36:07 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <tf5c27$3kljs$2@dont-email.me>
References: <tf4ius$3i39a$1@dont-email.me> <tf52cd$3jrhf$1@dont-email.me>
<op.1r08vv0qa3w0dxdave@hodgins.homeip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 5 Sep 2022 17:36:07 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="eebb4a051f861fde3f9f7b6afc6214b4";
logging-data="3823228"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1++H5ezBr4yBq3GN5spdW1+"
User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a
git.gnome.org/pan2)
Cancel-Lock: sha1:XLl29qKgHNS0zftt6iGFFTimKUw=
 by: Markus Robert Kessle - Mon, 5 Sep 2022 17:36 UTC

On Mon, 05 Sep 2022 13:15:21 -0400 David W. Hodgins wrote:

> On Mon, 05 Sep 2022 10:50:53 -0400, Markus Robert Kessler
> <no_reply@dipl-ing-kessler.de> wrote:
>> Well, the Smart-values are accessible, so hddtemp should be able to
>> extract and display the right one. No clue what's wrong here.
>
> Did you restart hddtemp.service after updating the smart db?
>
> Regards, Dave Hodgins

Hi Dave,

firstly, I invoked /sbin/smartctl directly without starting it as a
deamon. So, the values were up to date.

And, when running as "hddtemp -d" after machine restart the same occurs:

ncat localhost 7634 results in
|/dev/sdb|Samsung SSD 870 EVO 250G|NOS|*|

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

Re: No interaction between hddtemp and smart?

<tf5ccv$3kljs$3@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5131&group=alt.os.linux.mageia#5131

 copy link   Newsgroups: alt.os.linux.mageia alt.os.linux.ubuntu
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: no_re...@dipl-ing-kessler.de (Markus Robert Kessler)
Newsgroups: alt.os.linux.mageia,alt.os.linux.ubuntu
Subject: Re: No interaction between hddtemp and smart?
Date: Mon, 5 Sep 2022 17:41:51 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 115
Message-ID: <tf5ccv$3kljs$3@dont-email.me>
References: <tf4ius$3i39a$1@dont-email.me> <tf52cd$3jrhf$1@dont-email.me>
<tf59t2$3kljs$1@dont-email.me> <tf5bqe$3kt7s$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 5 Sep 2022 17:41:51 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="eebb4a051f861fde3f9f7b6afc6214b4";
logging-data="3823228"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/SQ8PeC7DKAZ3TKlfQo7Lt"
User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a
git.gnome.org/pan2)
Cancel-Lock: sha1:QTdTPtcVBHB5mmf0tZLkDXTg3a4=
 by: Markus Robert Kessle - Mon, 5 Sep 2022 17:41 UTC

On Mon, 05 Sep 2022 13:31:58 -0400 Paul wrote:

> On 9/5/2022 12:59 PM, Markus Robert Kessler wrote:
>> On Mon, 05 Sep 2022 14:50:53 +0000 Markus Robert Kessler wrote:
>>
>>> On Mon, 05 Sep 2022 10:27:40 +0000 Markus Robert Kessler wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> hope this is a known issue:
>>>>
>>>> I am doing some testing with a Samsung EVO 870 drive. Since this one
>>>> was not in the smart database, so I made an update:
>>>>
>>>> update-smart-drivedb
>>>>
>>>> After that, I can see the temperature of the drive:
>>>>
>>>> $ smartctl --all /dev/sdb | grep ^190 190 Airflow_Temperature_Cel
>>>> 0x0032
>>>> 072 045 000 Old_age Always - 28
>>>>
>>>> From what I have undestood, hddtemp is relying on the values
>>>> received
>>>> by smart. So, I'd expect, that hddtemp now also works. If the drive
>>>> is not yet known to hddtemp, at least the field names should be
>>>> displayable in debug mode. But this seems not the case here:
>>>>
>>>> $ hddtemp /dev/sdb /dev/sdb: Samsung SSD 870 EVO 250G: S.M.A.R.T. not
>>>> available
>>>>
>>>> $ hddtemp --debug /dev/sdb
>>>>
>>>> ================= hddtemp 0.3-beta15 ==================
>>>> Model: Samsung SSD 870 EVO 250G
>>>>
>>>>
>>>> If one of the field value seems to match the temperature, be sure to
>>>> read the hddtemp man page before sending a report (section REPORT).
>>>> Thanks.
>>>>
>>>>
>>>> Strange.
>>>>
>>>> Any idea?
>>>>
>>>> Thanks,
>>>> best regards,
>>>>
>>>> Markus
>>>
>>> Forgot to mention:
>>> The drive is connected via USB-to-SATA (2 different ones tested).
>>>
>>> Well, the Smart-values are accessible, so hddtemp should be able to
>>> extract and display the right one. No clue what's wrong here.
>>>
>>> Best regards,
>>>
>>> Markus
>>
>> Looks as if hddtemp does NOT use the values given by smartctl, but
>> instead it seems that hddtem is using own -- buggy -- routines.
>>
>> So, as a workaround, for external drives I recommend using this sudo-
>> based script:
>>
>> /bin/hddetemp (root:root, 0755):
>>
>> ######################################################################
>>
>> #!/bin/bash
>>
>> for DRIVE in /dev/sd[a-z] ; do
>>
>> SMARTVALUES=`sudo /sbin/smartctl --all $DRIVE`
>>
>> if [ "$?" != "0" ] ; then
>>
>> echo "$DRIVE: ERROR"
>>
>> else
>>
>> MODEL_NAME=`echo "$SMARTVALUES" | grep '^Device
>> Model:' |
>> sed -e 's/^Device Model: *//'`
>>
>> AIRFLOW_TEMP=`echo "$SMARTVALUES" | grep
>> 'Airflow_Temperature_Cel' | grep -o '[0-9]*$'`
>>
>> echo "$DRIVE: $MODEL_NAME: $AIRFLOW_TEMP°C"
>>
>> fi
>>
>> done
>>
>> ######################################################################
>
> Does "hddtemp" need sudo ?

Yes, and even worse: In most distros root is granted to hddtemp via
"policy kit", which is very infamous due to the evil bug recently.

But anyway, hddtemp works for internal drives and fails for external ones.

Thanks for asking!

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

1
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor