XPost: alt.os.linux.mageia   
   From: no_reply@dipl-ing-kessler.de   
      
   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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)