Fan Scripts for Supermicro Boards Using PID Logic 2020-08-20, previous one was missing a file

[wah00kid]

Could you post the output of sudo smartctl -a -n standby /dev/da3?
I don't know anything about SAS drives but could probably modify if I know how they respond.

root@freenas:~ # smartctl -a -n standby /dev/da3 smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.2-STABLE amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HITACHI Product: HUS72303CLAR3000 Revision: C442 Compliance: SPC-4 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Logical block size: 512 bytes Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000cca046212228 Serial number: YXGL6WKK Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Thu May 28 18:13:49 2020 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 45 C Drive Trip Temperature: 85 C Manufactured in week 03 of year 2014 Specified cycle count over device lifetime: 50000 Accumulated start-stop cycles: 49 Specified load-unload count over device lifetime: 600000 Accumulated load-unload cycles: 1346 Elements in grown defect list: 0 Vendor (Seagate) cache information Blocks sent to initiator = 15460576045786202112 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 0 2 0 2 70111 18833.679 0 write: 0 0 0 0 40940 13942.170 0 verify: 0 0 0 0 3727 0.000 0 Non-medium error count: 0 SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 31458 - [- - -] # 2 Background short Completed - 31338 - [- - -] # 3 Background short Completed - 31284 - [- - -] # 4 Background short Completed - 31164 - [- - -] # 5 Background short Completed - 31044 - [- - -] # 6 Background short Completed - 30807 - [- - -] # 7 Background short Completed - 30692 - [- - -] # 8 Background short Completed - 30572 - [- - -] # 9 Background short Completed - 30453 - [- - -] #10 Background short Completed - 30333 - [- - -] #11 Background short Completed - 30001 - [- - -] #12 Background short Completed - 30000 - [- - -] Long (extended) Self Test duration: 6 seconds [0.1 minutes] root@freenas:~ #

 

[Glorious1]

Could you try the attached and see if it works for both the SAS and SATA drives? Of course you'll have to lop off the '.txt' and make it executable chmod +x spincheck.sh.

 

[wah00kid]

Code:

root@freenas:/mnt/jailpool/scripts/fanscripts # ./spincheck-sas.sh
./spincheck-sas.sh: line 129: syntax error near unexpected token `done'
./spincheck-sas.sh: line 129: `   done <<< "$DEVLIST"'

Thanks for the quick effort.

This is what I am getting on that. It is right where you added the if and elif code ... or at the end of that little section

 

[Glorious1]

Sorry. My bash is rusty. Please try this.
Edit: 1st attachment was still wrong. Corrected:

 

[wah00kid]

Code:

root@freenas:/mnt/jailpool/scripts/fanscripts # ./spincheck-sasv2.sh
./spincheck-sasv2.sh: line 122: syntax error near unexpected token `then'
./spincheck-sasv2.sh: line 122: `         else [ cat /var/tempfile | grep "Transport protocol: SAS" ] ; then'

Still near that same spot in the code. Thanks again!

 

[Glorious1]

Too bad, I edited with a hopefully fixed attachment just before you replied. Please try it again.
Edit - wait, that's wrong too. Hold on

 

[Glorious1]

OK, I tested this one and it works for me, hopefully for SAS disks too. Let me know, if it's good I'll make the change in the spinpid scripts too and post a new version.

 

[wah00kid]

thanks so much for your work! truly glorious!

Code:

Friday, May 29
          da0  da1  da2  da3  ada1 ada3 Tmax Tmean  ERRc CPU  FAN1  FAN2  FAN3  FAN4  FANA Fan%0 Fan%1 MODE
09:51:15  *40  *43  *34  ./spincheck-sas-v3.sh: line 127: let: Tsum += Temperature:: syntax error in expression (error token is ":")
./spincheck-sas-v3.sh: line 131: printf: Temperature:: invalid number
*0   *34  *36  ./spincheck-sas-v3.sh: line 85: printf: Temperature:: invalid number
^0   31.17 -2.40  45   900   700  1400  1200  1800     0     0 Optimal^C

this one runs but produces the error on my da3, which is one of my sas drives

 

[wah00kid]

I added an echo $TEMP

Code:

 # Else assume SAS, their output is:
         #     Transport protocol: SAS (SPL-3) . . .
         #     Current Drive Temperature: 45 C
         else
                TEMP=$( cat /var/tempfile | grep "Drive Temperature" | awk '{print $3}')
         fi
         echo $TEMP
         let "Tsum += $TEMP"
         if [[ $TEMP > $Tmax ]]; then Tmax=$TEMP; fi;
         let "i += 1"

There to see what it is actually getting and here is what I got:

Code:

Friday, May 29
          da0  da1  da2  da3  ada1 ada3 Tmax Tmean  ERRc CPU  FAN1  FAN2  FAN3  FAN4  FANA Fan%0 Fan%1 MODE
09:56:37  40
*40  43
*43  34
*34  Temperature:
./spincheck-sas-v3.sh: line 128: let: Tsum += Temperature:: syntax error in expression (error token is ":")
./spincheck-sas-v3.sh: line 132: printf: Temperature:: invalid number
*0   34
*34  36
*36  ./spincheck-sas-v3.sh: line 85: printf: Temperature:: invalid number
^0   31.17 -2.40  44   900   700  1400  1200  1800     0     0 Optimal^C

so what the $TEMP is pulling is the string "Temperature:" it seems when it hits my da3

edit: .. i guess that is also apparent in the output from the original.. sorry trying to be helpful... something is off with the awk command i think....

 

[wah00kid]

Code:

 # Update temperatures each drive; spinners only
      if [ "$STATUS" == "*" ] ; then
         # Taking 10th space-delimited field for most SATA:
         if grep -Fq "Temperature_Celsius" /var/tempfile ; then
                TEMP=$( cat /var/tempfile | grep "Temperature_Celsius" | awk '{print $10}')
         # Else assume SAS, their output is:
         #     Transport protocol: SAS (SPL-3) . . .
         #     Current Drive Temperature: 45 C
         else
                TEMP=$( cat /var/tempfile | grep "Drive Temperature" | awk '{print $4}')
         fi
         let "Tsum += $TEMP"
         if [[ $TEMP > $Tmax ]]; then Tmax=$TEMP; fi;
         let "i += 1"
      fi
      printf "%s%-2d  " "$STATUS" $TEMP
   done <<< "$DEVLIST"
   manage_data  # manage data function
}

I think I got it changing the awk to 4:

Code:

Friday, May 29
          da0  da1  da2  da3  ada1 ada3 Tmax Tmean  ERRc CPU  FAN1  FAN2  FAN3  FAN4  FANA Fan%0 Fan%1 MODE
10:13:27  *40  *43  *34  *44  *34  *36  ^44  38.50  4.93  46   900   700  1400  1200  1800     0     0 Optimal
10:14:31  *40  *43  *34  *44  *34  *36  ^44  38.50  4.93  44   900   700  1400  1200  1800     0     0 Optimal

 

[Glorious1]

Good catch. I was stupidly assuming "Drive Temperature" was 1 field, but actually 2. On the SATA drives all the text fields are linked with underscore. I'll work on getting that change in the other scripts, but you can probably do it for yourself if you're in a hurry.

 

[wah00kid]

Good catch. I was stupidly assuming "Drive Temperature" was 1 field, but actually 2. On the SATA drives all the text fields are linked with underscore. I'll work on getting that change in the other scripts, but you can probably do it for yourself if you're in a hurry.

thanks so much glorious.

we have started to have some hot days.. supposed to hit 83 today and I had a temp warning yesterday so I wanted to run spincheck to see what it is like on a hot day and then I can configure my system.

i have spincheck-sas-v3.sh running in a tmux now.

again thanks so much for the support!

both of my sas drives are the same manufacturer so what you wrote works for me for both my sas drives because their smart output is identical... so i don't know enough about sas drives to know if different manufacturers would produce different smart output... something to think about if someone else with sas drives tries this and it doesn't work

 

[Glorious1]

both of my sas drives are the same manufacturer so what you wrote works for me for both my sas drives because their smart output is identical... so i don't know enough about sas drives to know if different manufacturers would produce different smart output... something to think about if someone else with sas drives tries this and it doesn't work

Just what I was thinking. More likely than not there are variations among manufacturers, but we can't deal with that until we see it.

 

[spacecabbie]

Hi and Hello

I get some issues with the script probably due to using a sas expander.

Code:

Key to drive status symbols:  * spinning;  _ standby;  ? unknown                              Version 2019-11-01

Monday, Jun 15
          ses0 da0  da1  da2  da3  da4  da5  da6  da7  da8  da9  da10 da11 da12 Tmax Tmean  ERRc CPU  FAN1  FAN2  FAN3  FAN4  FANA Fan%0 Fan%1 MODE
08:10:50  _0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")

Also tried adding to devicelist but i am not good with those kind of strings so i changed it.

Code:

DEVLIST="$(echo "$DEVLIST1"|sed '/KINGSTON/d;/ADATA/d;/SanDisk/d;/OCZ/d;/EXP/d;/INTEL/d;/TDKMedia/d;/SSD/d')"

info's:

Code:

camcontrol devlist
<Samsung SSD 840 EVO 500GB EXT0DB6Q>  at scbus6 target 0 lun 0 (pass0,ada0)
<Samsung SSD 840 EVO 500GB EXT0AB0Q>  at scbus7 target 0 lun 0 (pass1,ada1)
<AHCI SGPIO Enclosure 2.00 0001>   at scbus8 target 0 lun 0 (pass2,ses0)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 8 lun 0 (pass3,da0)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 9 lun 0 (pass4,da1)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 10 lun 0 (pass5,da2)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 11 lun 0 (pass6,da3)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 12 lun 0 (pass7,da4)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 13 lun 0 (pass8,da5)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 14 lun 0 (pass9,da6)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 15 lun 0 (pass10,da7)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 16 lun 0 (pass11,da8)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 17 lun 0 (pass12,da9)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 18 lun 0 (pass13,da10)
<HGST HUS724040ALS640 A1CD>        at scbus9 target 19 lun 0 (pass14,da11)
<HP HP SAS EXP Card 2.10>          at scbus9 target 20 lun 0 (pass15,ses1)

Any changes you would be so kind as to have a look ?

 

[Glorious1]

It looks like you correctly excluded your SSD. You may also need to exclude your Enclosure and your Card, assuming they are not spinning disks. Please try:

Code:

DEVLIST="$(echo "$DEVLIST1"|sed '/KINGSTON/d;/ADATA/d;/SanDisk/d;/OCZ/d;/EXP/d;/INTEL/d;/TDKMedia/d;/SSD/d;/Enclosure/d;/Card/d')"

 

[spacecabbie]

It looks like you correctly excluded your SSD. You may also need to exclude your Enclosure and your Card, assuming they are not spinning disks. Please try:

Code:

DEVLIST="$(echo "$DEVLIST1"|sed '/KINGSTON/d;/ADATA/d;/SanDisk/d;/OCZ/d;/EXP/d;/INTEL/d;/TDKMedia/d;/SSD/d;/Enclosure/d;/Card/d')"

Yup that solved the DEVLIST thanks ! But still got these errors:

Code:

How many whole minutes do you want between spin checks?
1

NOTE ABOUT DUTY CYCLE (Fan%0 and Fan%1):
Some boards apparently report incorrect duty cycle, and can
report duty cycle for zone 1 when that zone does not exist.

Key to drive status symbols:  * spinning;  _ standby;  ? unknown                              Version 2019-11-01

Monday, Jun 15
          da0  da1  da2  da3  da4  da5  da6  da7  da8  da9  da10 da11 da12 Tmax Tmean  ERRc CPU  FAN1  FAN2  FAN3  FAN4  FANA Fan%0 Fan%1 MODE
20:28:55  ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ?0   ^0    0.00-33.57  42  2400  2400  2400  2500  2300    20    65 HeavyIO
20:29:56  ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ./spincheck.sh: line 120: let: Tsum += : syntax error: operand expected (error token is "+= ")
*0   ?0   ^0    0.00-33.57  40  2400  2400  2500  2500  2300    20    65 HeavyIO^C

any idea's ?

 

[Glorious1]

Could you post output of smartctl -a /dev/da1?
Just need line(s) that show temperature.

 

[spacecabbie]

Could you post output of smartctl -a /dev/da1?
Just need line(s) that show temperature.

Ofcourse budy,

Code:

general/sh.scripts/fan_control]# smartctl -a /dev/da1
smartctl 7.0 2018-12-30 r4883 [FreeBSD 11.3-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUS724040ALS640
Revision:             A1CD
Compliance:           SPC-4
User Capacity:        4,000,787,030,016 bytes [4.00 TB]
Logical block size:   512 bytes
LU is resource provisioned, LBPRZ=0
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca0731c181c
Serial number:        PEGHEZ7X
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Mon Jun 15 23:28:48 2020 CEST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     64 C
Drive Trip Temperature:        85 C

Manufactured in week 19 of year 2015
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  70
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  2360
Elements in grown defect list: 0

Vendor (Seagate Cache) information
  Blocks sent to initiator = 4624399709765632

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:      58543        0         0     58543   21892754     128840.547           0
write:         0        0         0         0     479924      21488.477           0
verify: 14309607       35         0  14309642      37444     189650.763           0

Non-medium error count:        0

SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background long   Completed                   -      36                 - [-   -    -]
# 2  Background long   Completed                   -      10                 - [-   -    -]

Long (extended) Self-test duration: 37038 seconds [617.3 minutes]

 

[Glorious1]

@spacecabbie , thanks. Your drives use a different SMART output than most SATA drives. I'm working on updates to the scripts that deal with that, among other things. Please try the attached, just remove the .txt suffix first. It already has the fix for the device list that we did earlier.

By the way, I looked up the specs on those drives. Apparently, maximum operating temperature is 140 F = 60 C. That drive was 64 C when you did the smartctl command. Too hot!

If this works, and you run spintest.sh to characterize your fans, and adjust the fan limits as noted in the instructions, and you're ready to move on to spinpid2.sh to control the fans, I will send you the "beta" version of the script that should work with your drives.

 

[spacecabbie]

@spacecabbie , thanks. Your drives use a different SMART output than most SATA drives. I'm working on updates to the scripts that deal with that, among other things. Please try the attached, just remove the .txt suffix first. It already has the fix for the device list that we did earlier.

You're a star !

Code:

general/sh.scripts/fan_control]# ./spincheck.sh
How many whole minutes do you want between spin checks?
1

NOTE ABOUT DUTY CYCLE (Fan%0 and Fan%1):
Some boards apparently report incorrect duty cycle, and can
report duty cycle for zone 1 when that zone does not exist.

Key to drive status symbols:  * spinning;  _ standby;  ? unknown                              Version 2020-06-01

Tuesday, Jun 16
          da0  da1  da2  da3  da4  da5  da6  da7  da8  da9  da10 da11 da12 Tmax Tmean  ERRc CPU  FAN1  FAN2  FAN3  FAN4  FANA Fan%0 Fan%1 MODE
06:46:07  *32  *31  *31  *32  *31  *30  *32  *31  *31  *32  *31  *31  ?0   ^32  31.25 -2.32  37 12300 12300 12300 12300  3100   100   100 Full
06:47:09  *32  *32  *31  *33  *32  *30  *32  *31  *31  *32  *31  *32  ?0   ^33  31.58 -1.99  37 12300 12300 12300 12300  3100   100   100 Full
06:48:09  *33  *32  *32  *34  *32  *31  *33  *32  *32  *33  *32  *32  ?0   ^34  32.33 -1.24  42 12300 12300 12300 12300  3100   100   100 Full
06:49:10  *33  *32  *32  *34  *33  *31  *33  *32  *32  *33  *32  *32  ?0   ^34  32.42 -1.15  37 12300 12300 12300 12300  3100   100   100 Full
06:50:11  *33  *33  *32  *34  *33  *31  *34  *32  *32  *34  *32  *33  ?0   ^34  32.75 -0.82  37 12300 12200 12300 12300  3100   100   100 Full
06:51:12  *34  *33  *32  *35  *33  *31  *34  *33  *33  *34  *32  *33  ?0   ^35  33.08 -0.49  40 12300 12300 12300 12300  3200   100   100 Full
06:52:13  *35  *34  *32  *35  *33  *32  *34  *33  *32  *34  *33  *33  ?0   ^35  33.33 -0.24  49 12300 12200 12300 12300  3200   100   100 Full
06:53:19  *35  *34  *32  *35  *34  *32  *35  *33  *32  *35  *33  *33  ?0   ^35  33.58  0.01  47 12300 12300 12200 12300  3200   100   100 Full
06:54:24  *35  *34  *33  *35  *34  *32  *35  *34  *33  *35  *33  *34  ?0   ^35  33.92  0.35  49 12300 12300 12200 12300  3200   100   100 Full
06:55:27  *35  *34  *33  *36  *34  *32  *35  *34  *33  *35  *33  *34  ?0   ^36  34.00  0.43  50 12300 12300 12300 12300  3200   100   100 Full
06:56:28  *36  *34  *34  *36  *35  *33  *35  *34  *33  *36  *34  *34  ?0   ^36  34.50  0.93  61 12300 12300 12300 12300  3200   100   100 Full
06:57:31  *36  *35  *34  *36  *35  *33  *36  *35  *33  *36  *34  *34  ?0   ^36  34.75  1.18  52 12300 12300 12300 12300  3200   100   100 Full
06:58:37  *36  *35  *34  *37  *35  *33  *36  *35  *34  *36  *34  *34  ?0   ^37  34.92  1.35  43 12300 12300 12300 12200  3200   100   100 Full
06:59:38  *36  *35  *34  *37  *35  *33  *36  *35  *34  *36  *34  *35  ?0   ^37  35.00  1.43  41 12300 12300 12200 12300  3200   100   100 Full
07:00:39  *36  *35  *34  *37  *35  *33  *36  *35  *34  *37  *34  *35  ?0   ^37  35.08  1.51  56 12300 12300 12300 12300  3200   100   100 Full
07:01:42  *37  *35  *35  *37  *36  *34  *37  *35  *35  *37  *34  *35  ?0   ^37  35.58  2.01  42 12300 12300 12300 12300  3200   100   100 Full
07:02:43  *37  *35  *35  *38  *36  *34  *37  *35  *35  *37  *35  *35  ?0   ^38  35.75  2.18  43 12300 12300 12200 12200  3200   100   100 Full
07:03:44  *37  *35  *35  *38  *36  *34  *37  *35  *35  *37  *35  *35  ?0   ^38  35.75  2.18  43 12300 12300 12300 12300  3200   100   100 Full
07:04:44  *37  *36  *35  *38  *36  *34  *37  *36  *35  *37  *35  *35  ?0   ^38  35.92  2.35  42 12300 12300 12300 12300  3200   100   100 Full
07:05:45  *37  *36  *35  *38  *36  *34  *37  *36  *35  *37  *35  *35  ?0   ^38  35.92  2.35  46 12300 12300 12300 12300  3200   100   100 Full
07:06:50  *37  *36  *35  *38  *36  *34  *38  *36  *35  *37  *35  *36  ?0   ^38  36.08  2.51  44 12300 12300 12300 12300  3200   100   100 Full
07:07:51  *38  *36  *35  *39  *37  *34  *38  *36  *35  *38  *35  *36  ?0   ^39  36.42  2.85  51 12300 12300 12300 12200  3200   100   100 Full
07:08:52  *38  *36  *35  *38  *36  *34  *38  *36  *35  *38  *35  *36  ?0   ^38  36.25  2.68  42 12300 12300 12300 12300  3200   100   100 Full
07:09:52  *38  *36  *35  *38  *36  *34  *37  *36  *35  *37  *35  *36  ?0   ^38  36.08  2.51  43 12300 12300 12300 12300  3200   100   100 Full
07:10:53  *38  *36  *35  *38  *36  *34  *38  *36  *35  *38  *35  *35  ?0   ^38  36.17  2.60  51 12300 12300 12300 12300  3200   100   100 Full

Ps. any way we can convert the above into a nice little live graph ?

By the way, I looked up the specs on those drives. Apparently, maximum operating temperature is 140 F = 60 C. That drive was 64 C when you did the smartctl command. Too hot!

Aye hence the need for the script ;) but at that momment the fans where fubared and refused to go back to heavy io setting.

If this works, and you run spintest.sh to characterize your fans, and adjust the fan limits as noted in the instructions, and you're ready to move on to spinpid2.sh to control the fans, I will send you the "beta" version of the script that should work with your drives.

By all means do send can't wait to have some peace and silence again.