Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

unmenu overtemp_shutdown.sh triggering when temperatures are normal

Featured Replies

Hi folks,

 

I've been running unraid v4.7 for a long time now. My box has been 100% stable. Recently it has been getting close to full so i've been trying to preclear a couple disks so that i can add them to the array. However, i'm running into an issue with a package i installed via unmenu which is supposed to shutdown the unraid server when the temperature of a drive exceeds a certain value (in my case 55 degrees celsius). It supposed to send a warning email when it gets to a warning threshold (50 degrees), and then send another if it reaches the max temp (55) and then initiate a shutdown. I've never had heat problems with my server... and none of my drives ever exceed 40 degrees, even when they're in use. I've got 2 wd green drives (1.5tb and 2tb) that i was running a preclear on simultaneously. In two different attempts to run these preclears, i've received an email from this overtemp script that it was killing processes due to temperature. I didn't even get the warning email. Here are the contents of the overtemp shutdown email:

 

/bin/sh: line 1:  3686 Killed                  /usr/local/sbin/overtemp_shutdown.sh >/dev/null 2>&1

 

Unfortunately im unable to verify if the temps did exceed the values as the syslog is gone after reboot, but i can't see how this would have happened. I've been monitoring the drive temperatures throughout the preclear operation and have not seen the temps go above 32-35 degrees... plus there is the fact that the warning email was never sent. It seems like this overtemp shutdown script is having some kind of issue.

 

Has anyone else had this problem before ? or any other problems related to this overtemp_shutdown script ? Any recommendations on what i should do ? Im thinking of just disabling this package but i kind of like to have something in place to monitor temps... but the way it's working now doesn't make sense to me. Maybe there are alternatives for monitoring temperature ?

 

Appreciate any help you can give. Thanx.

 

-Dave

 

Hi folks,

 

I've been running unraid v4.7 for a long time now. My box has been 100% stable. Recently it has been getting close to full so i've been trying to preclear a couple disks so that i can add them to the array. However, i'm running into an issue with a package i installed via unmenu which is supposed to shutdown the unraid server when the temperature of a drive exceeds a certain value (in my case 55 degrees celsius). It supposed to send a warning email when it gets to a warning threshold (50 degrees), and then send another if it reaches the max temp (55) and then initiate a shutdown. I've never had heat problems with my server... and none of my drives ever exceed 40 degrees, even when they're in use. I've got 2 wd green drives (1.5tb and 2tb) that i was running a preclear on simultaneously. In two different attempts to run these preclears, i've received an email from this overtemp script that it was killing processes due to temperature. I didn't even get the warning email. Here are the contents of the overtemp shutdown email:

 

/bin/sh: line 1:  3686 Killed                  /usr/local/sbin/overtemp_shutdown.sh >/dev/null 2>&1

 

Unfortunately im unable to verify if the temps did exceed the values as the syslog is gone after reboot, but i can't see how this would have happened. I've been monitoring the drive temperatures throughout the preclear operation and have not seen the temps go above 32-35 degrees... plus there is the fact that the warning email was never sent. It seems like this overtemp shutdown script is having some kind of issue.

 

Has anyone else had this problem before ? or any other problems related to this overtemp_shutdown script ? Any recommendations on what i should do ? Im thinking of just disabling this package but i kind of like to have something in place to monitor temps... but the way it's working now doesn't make sense to me. Maybe there are alternatives for monitoring temperature ?

 

Appreciate any help you can give. Thanx.

 

-Dave

It says the process was killed... odds are you ran out of "low" memory while clearing the drives.  Unless you used the -r -w and -b options to preclear, it is really easy to run out of memory.

 

The overtemp script does NOT kill anything unless you tell it to shut down the array in the event of a overtemp.  It sleeps in between its check of the temperature.  Because of this is is a likely choice of the kernel out-of-memory process killer when memory is exhausted and the kernel is looking to free what it can by killing the processes idle the longest.

 

There is a possibility, depending n your disk controller chipset, that the smartctl command used to read the disks might fail because of the "-d ata" option.

 

You can try it (see what the temperature is that is returned)  by trying this

for i in /dev/sd?; do smartctl -d ata -A $i | grep -i temperature | sed 1q | awk -v d=$i '{ print d, $10 }'; done

vs this

for i in /dev/sd?; do smartctl  -A $i | grep -i temperature | sed 1q | awk -v d=$i '{ print d, $10 }'; done

Joe L.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.