HELP: repeated "No sensors found!" messages

hi all,

i’ve had unraid (version 5.0.5) up and running for more than a year without a hiccup, but recently i ran into an issue when i failed to properly power down my system when i added a new drive.  when i restarted, i began receiving

No sensors found!

Make sure you loaded all the kernel drivers you need.

Try sensors-detect to find out which these are.

over and over again, every few seconds.  the system operates just fine, but i am concerned about the lifespan of the usb memory stick i’m running on, as i see the writes adding up.

i properly powered the system down and ran fsck on the drive, and cleared the dirty bit.  i also received a notice that there were differences between the boot sector and its backup, but i’m not sure that is really an issue and have ignored it.  after the fsck completed, i am still getting those repeated messages.

i did run sensors-detect (output included at the end of this post) but there doesn’t seem to be any supported sensors found, which i am ok with if that is the case.  all i’d like to do is to stop the message from repeating. 

thinking i might have been missing a configuration file, i added an empty sensors.d file in /etc/sensors.d/, and i also copied a file i found sensors3.conf into /etc/sensors.d/, neither of which had any effect.

i’m not a complete novice at linux but i am also not super familiar with it.  i suspect i am missing something obvious, but i’m just not sure what that might be.

does anyone have any suggestions?

thanks!

-bob

# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)

# System: Dell Computer Corporation PowerEdge 830 [Not Specified]

# Board: Dell Computer Corporation 0HJ159

This program will help you determine which kernel modules you need

to load to use lm_sensors most effectively. It is generally safe

and recommended to accept the default answers to all questions,

unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.

Do you want to scan for them? This is totally safe. (YES/no): yes

Silicon Integrated Systems SIS5595...                      No

VIA VT82C686 Integrated Sensors...                          No

VIA VT8231 Integrated Sensors...                            No

AMD K8 thermal sensors...                                  No

AMD Family 10h thermal sensors...                          No

AMD Family 11h thermal sensors...                          No

AMD Family 12h and 14h thermal sensors...                  No

AMD Family 15h thermal sensors...                          No

AMD Family 15h power sensors...                            No

Intel digital thermal sensor...                            No

Intel AMB FB-DIMM thermal sensor...                        No

VIA C7 thermal sensor...                                    No

VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to

standard I/O ports to probe them. This is usually safe.

Do you want to scan for Super I/O sensors? (YES/no): yes

Probing for Super-I/O at 0x2e/0x2f

Trying family `National Semiconductor/ITE'...              Yes

Found `Nat. Semi. PC8374L Super IO Sensors'

    (but not activated)

Probing for Super-I/O at 0x4e/0x4f

Trying family `National Semiconductor/ITE'...              No

Trying family `SMSC'...                                    No

Trying family `VIA/Winbond/Nuvoton/Fintek'...              No

Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces

through which system health data may be retrieved, amongst other things.

We first try to get the information from SMBIOS. If we don't find it

there, we have to read from arbitrary I/O ports to probe for such

interfaces. This is normally safe. Do you want to scan for IPMI

interfaces? (YES/no): yes

Found `IPMI BMC KCS' at 0xca8...                            Success!

    (confidence 8, driver `to-be-written')

Some hardware monitoring chips are accessible through the ISA I/O ports.

We have to write to arbitrary I/O ports to probe them. This is usually

safe though. Yes, you do have ISA I/O ports even if you do not have any

ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes

Probing for `National Semiconductor LM78' at 0x290...      No

Probing for `National Semiconductor LM79' at 0x290...      No

Probing for `Winbond W83781D' at 0x290...                  No

Probing for `Winbond W83782D' at 0x290...                  No

Lastly, we can probe the I2C/SMBus adapters for connected hardware

monitoring devices. This is the most risky part, and while it works

reasonably well on most systems, it has been reported to cause trouble

on some systems.

Do you want to probe the I2C/SMBus adapters now? (YES/no): yes

Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

Module i2c-dev loaded successfully.

Now follows a summary of the probes I have just done.

Just press ENTER to continue:

Driver `to-be-written':

  * ISA bus, address 0xca8

    Chip `IPMI BMC KCS' (confidence:

Note: there is no driver for IPMI BMC KCS yet.

Check http://www.lm-sensors.org/wiki/Devices for updates.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK