13 hours ago, Squid said:

 

OK, this is proving to be one pain in the a*s.

 

my dynamix.system.temp\drivers.conf has the following:

coretemp.nct6683

 

but for some reason the NCT6683 module is not loading as you can see from my sensors output below.

 

Sensors-detect:

 

Found `Nuvoton NCT6683D eSIO'                               Success!
    (address 0xa20, driver `nct6683')

 

Sensors:

 

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +26.0°C  (high = +99.0°C, crit = +115.0°C)
Core 0:       +24.0°C  (high = +99.0°C, crit = +115.0°C)
Core 1:       +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 2:       +26.0°C  (high = +99.0°C, crit = +115.0°C)
Core 3:       +23.0°C  (high = +99.0°C, crit = +115.0°C)
Core 4:       +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 5:       +23.0°C  (high = +99.0°C, crit = +115.0°C)
Core 6:       +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 7:       +24.0°C  (high = +99.0°C, crit = +115.0°C)
Core 8:       +24.0°C  (high = +99.0°C, crit = +115.0°C)
Core 9:       +24.0°C  (high = +99.0°C, crit = +115.0°C)

nvme-pci-0200
Adapter: PCI adapter
Composite:    +44.9°C  (low  = -60.1°C, high = +89.8°C)
                       (crit = +94.8°C)

nvme-pci-3e00
Adapter: PCI adapter
Composite:    +45.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +45.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)

 

Any idea why the sensor module isn't loading?

Linux peeps have managed to get it working by doing the following but there is no modules-load.d folder in UNRAID that I can see.

 

echo "options nct6683 force=1" >> /etc/modprobe.d/sensors.conf

modprobe nct6683

echo "nct6683" >> /etc/modules-load.d/modules.conf

 

33 minutes ago, mikeyosm said:

echo "options nct6683 force=1" >> /etc/modprobe.d/sensors.conf

modprobe nct6683

echo "nct6683" >> /etc/modules-load.d/modules.conf

 

Have tried just putting the modprobe command into your go file?

1 minute ago, PeterB said:

Have tried just putting the modprobe command into your go file?

I actually just tried running it manually and still same results.

On 1/3/2021 at 9:21 PM, itimpi said:

If you back it up first, it should be easy enough to test by seeing if you can successfully write the expected amount of data to the drive and then also read it back intact.   If it IS a fake one of those steps will fail.

Thanks, @itimpi. But I'm wondering about the logistics of this;

 

1. Back up the USB drive, having removed it while the array is (presumably) spun down but powered.

 

2. Leave the server alone while I…

 

3. Test the USB drive destructively with, say, F3 or some similar test.

 

4. Restore the original UnRAID data, reinsert the USB drive into the server.

 

Because of 2. the backup and subsequent restore would have to be outside the UnRAID server. Is this the sequence you had in mind? Have you tried this?

 

-- 

Chris

On 1/2/2021 at 2:30 AM, Marshalleq said:

I would always install trim on all SSD's.  I think it's highly worth and and have never had an issue.  I followed your link but it didn't make immediate sense to me what you mean.  Just install trim I reckon.

The question is: does RAISE replace TRIM? Unnecessarily running TRIM may not raise (ha!) any "issues" but you may be adding random wear to your SSD.

 

-- 

Chris

1 hour ago, bidmead said:

Thanks, @itimpi. But I'm wondering about the logistics of this;

 

1. Back up the USB drive, having removed it while the array is (presumably) spun down but powered.

 

2. Leave the server alone while I…

 

3. Test the USB drive destructively with, say, F3 or some similar test.

 

4. Restore the original UnRAID data, reinsert the USB drive into the server.

 

Because of 2. the backup and subsequent restore would have to be outside the UnRAID server. Is this the sequence you had in mind? Have you tried this?

 

-- 

Chris

Yes.

 

Depending on the test you run you may need to run the appropriate make_bootable command off the flash to make it bootable again if the test you use has destroyed that status.

2 hours ago, mikeyosm said:

OK, this is proving to be one pain in the a*s.

 

my dynamix.system.temp\drivers.conf has the following:

coretemp.nct6683

 

but for some reason the NCT6683 module is not loading as you can see from my sensors output below.

 

Sensors-detect:

 

Found `Nuvoton NCT6683D eSIO'                               Success!
    (address 0xa20, driver `nct6683')

 

Sensors:

 

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +26.0°C  (high = +99.0°C, crit = +115.0°C)
Core 0:       +24.0°C  (high = +99.0°C, crit = +115.0°C)
Core 1:       +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 2:       +26.0°C  (high = +99.0°C, crit = +115.0°C)
Core 3:       +23.0°C  (high = +99.0°C, crit = +115.0°C)
Core 4:       +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 5:       +23.0°C  (high = +99.0°C, crit = +115.0°C)
Core 6:       +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 7:       +24.0°C  (high = +99.0°C, crit = +115.0°C)
Core 8:       +24.0°C  (high = +99.0°C, crit = +115.0°C)
Core 9:       +24.0°C  (high = +99.0°C, crit = +115.0°C)

nvme-pci-0200
Adapter: PCI adapter
Composite:    +44.9°C  (low  = -60.1°C, high = +89.8°C)
                       (crit = +94.8°C)

nvme-pci-3e00
Adapter: PCI adapter
Composite:    +45.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +45.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)

 

Any idea why the sensor module isn't loading?

Linux peeps have managed to get it working by doing the following but there is no modules-load.d folder in UNRAID that I can see.

 

echo "options nct6683 force=1" >> /etc/modprobe.d/sensors.conf

modprobe nct6683

echo "nct6683" >> /etc/modules-load.d/modules.conf

 

I booted an Ubuntu distro and I get all the sensors info. How do I get the same sensors to show up in UNRAID?

I added the nct6683 module to modules.conf in Ubuntu but I can't see where I do this in UNRAID.

 

/etc/modules-load.d$ cat modules.conf

 

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
nct6683

 

sensors

 

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +28.0°C  (high = +99.0°C, crit = +115.0°C)
Core 0:        +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 1:        +26.0°C  (high = +99.0°C, crit = +115.0°C)
Core 2:        +27.0°C  (high = +99.0°C, crit = +115.0°C)
Core 3:        +26.0°C  (high = +99.0°C, crit = +115.0°C)
Core 4:        +27.0°C  (high = +99.0°C, crit = +115.0°C)
Core 5:        +24.0°C  (high = +99.0°C, crit = +115.0°C)
Core 6:        +27.0°C  (high = +99.0°C, crit = +115.0°C)
Core 7:        +25.0°C  (high = +99.0°C, crit = +115.0°C)
Core 8:        +26.0°C  (high = +99.0°C, crit = +115.0°C)
Core 9:        +26.0°C  (high = +99.0°C, crit = +115.0°C)

nct6683-isa-0a20
Adapter: ISA adapter
VIN0:          720.00 mV (min =  +0.00 V, max =  +0.00 V)
VIN1:            1.01 V  (min =  +0.00 V, max =  +0.00 V)
VIN2:          992.00 mV (min =  +0.00 V, max =  +0.00 V)
VIN3:            1.10 V  (min =  +0.00 V, max =  +0.00 V)
VIN7:            1.34 V  (min =  +0.00 V, max =  +0.00 V)
VIN14:         464.00 mV (min =  +0.00 V, max =  +0.00 V)
VIN15:           1.04 V  (min =  +0.00 V, max =  +0.00 V)
VIN16:           1.06 V  (min =  +0.00 V, max =  +0.00 V)
VSB:             3.49 V  (min =  +0.00 V, max =  +0.00 V)
fan1:           500 RPM  (min =    0 RPM)
fan2:           739 RPM  (min =    0 RPM)
fan3:          2013 RPM  (min =    0 RPM)
fan4:             0 RPM  (min =    0 RPM)
Thermistor 13:  +38.0°C  (low  =  +0.0°C)
                         (high =  +0.0°C, hyst =  +0.0°C)
                         (crit =  +0.0°C)  sensor = thermistor
PECI 0.0:       +27.5°C  (low  =  +0.0°C)
                         (high =  +0.0°C, hyst =  +0.0°C)
                         (crit =  +0.0°C)  sensor = Intel PECI
Thermistor 12:  +45.5°C  (low  =  +0.0°C)
                         (high =  +0.0°C, hyst =  +0.0°C)
                         (crit =  +0.0°C)  sensor = thermistor
intrusion0:    OK
beep_enable:   disabled

nvme-pci-0200
Adapter: PCI adapter
Composite:    +45.9°C  (low  = -60.1°C, high = +89.8°C)
                       (crit = +94.8°C)

37 minutes ago, itimpi said:

Yes.

 

Depending on the test you run you may need to run the appropriate make_bootable command off the flash to make it bootable again if the test you use has destroyed that status.

Thanks, @itimpi. I've realised subsequently that the official UnRAID USB backup downloads the output to the local machine running the WebGUI, so my remarks about backing up the USB outside the UnRAID NAS don't apply.

 

But there's a possible scenario that worries me. If this is a fake 2GB drive posing as a 16GB drive (as UnRAID seems to be suggesting) it's a possibility that the destructive test I run will make the drive unusable.

 

Whether it's 16GB or 2GB, it's working fine for now as a boot drive. My inclination would be to buy a second 16GB Cruzer Fit from the eBay SanDisk store (about £6), test that to guarantee it's a worthy understudy, and then run the destructive test on the working boot USB drive.

 

Or am I being overcautious here? Advice very welcome.

 

-- 

Chris

 

 

 

10 minutes ago, bidmead said:

Thanks, @itimpi. I've realised subsequently that the official UnRAID USB backup downloads the output to the local machine running the WebGUI, so my remarks about backing up the USB outside the UnRAID NAS don't apply.

 

But there's a possible scenario that worries me. If this is a fake 2GB drive posing as a 16GB drive (as UnRAID seems to be suggesting) it's a possibility that the destructive test I run will make the drive unusable.

 

Whether it's 16GB or 2GB, it's working fine for now as a boot drive. My inclination would be to buy a second 16GB Cruzer Fit from the eBay SanDisk store (about £6), test that to guarantee it's a worthy understudy, and then run the destructive test on the working boot USB drive.

 

Or am I being overcautious here? Advice very welcome.

 

-- 

Chris

 

 

 

I have no idea whether testing can make the drive unusable.

 

if you have to use a new USB then you will have to go through the process of transferring the licence to it (and blacklist the old one).   You can use the automated process once a year but if you have done a transfer more recently then you need to contact Limetech to do a manual transfer.

Thanks, @itimpi. I'm cool with the licence transfer process but think it's probably a good idea to have a physical backup USB drive ready. I've ordered another Cruzer. I'll report back here once that's all done.

 

-- 

Chris

16 hours ago, bidmead said:

The question is: does RAISE replace TRIM? Unnecessarily running TRIM may not raise (ha!) any "issues" but you may be adding random wear to your SSD.

 

-- 

Chris

What part of RAISE would you think replaces trim?  I can't see anything even slightly related in there. 

I was asking my question about RAISE and TRIM, @Marshalleq, from a position of ignorance. That's to say, I'm looking for an answer from someone who knows more than I do. You're asking me another question that seems to require the information I'm ignorant of.

 

Is there someone here who can help us both out? I've put this question to the SSD manufacturer and will follow up here if I get a response.

 

(Here's a useful gloss on how the SandForce controller and TRIM work, separately. There's no mention of RAISE here, but I'm assuming my cache OWC Mercury Extreme Pro, which uses a SandForce controller, also includes this DuraWrite feature. This may be an answer to my question but I don't understand SSD garbage collection well enough to be sure.)

 

-- 

Chris

may a question about the system fan plugin, after getting the fans to be recognized and adjustable question is

 

do i see this right that the automatic control is only triggered for hdd temps ?

 

my usecase is to control my fans due cpu temp but either i miss something ot its a hdd temp control base only ?

 

for any tipps, thanks ahead

With the Dynamix System Buttons plugin does the "Stop the Array" do the following.

Stop VMs properly

Stop Dockers properly

 

Or is it best to stop each docker and vm running before doing "Stop the array"?

 

All i did was install system temp plugin and fanspeed plugin, ran sensors-detect from command line, it reported coretemp and nct6775

So i ran modprobe coretemp and modprobe nct6775.

Been working ever since. Rebooted numerous times.

may a question about the system fan plugin, after getting the fans to be recognized and adjustable question is
 
do i see this right that the automatic control is only triggered for hdd temps ?
 
my usecase is to control my fans due cpu temp but either i miss something ot its a hdd temp control base only ?
 
for any tipps, thanks ahead

It is for fan speed control based on hdd temps only

may a question about the system fan plugin, after getting the fans to be recognized and adjustable question is
 
do i see this right that the automatic control is only triggered for hdd temps ?
 
my usecase is to control my fans due cpu temp but either i miss something ot its a hdd temp control base only ?
 
for any tipps, thanks ahead

Just use a fan splitter hub to connect all your fans to the cpu fan header and set you fan curve in the bios

@spl147 thanks for the info about hdd temps only, and they are already adjusted in bios, no need for a splitter here due i can adjust them all seperate anyway, would be just nice to take control while running without rebooting to bios etc etc.

I'm getting permission denied in autofan plugin.... Any ideas why? The plugin is detecting my sensor chip nct6683 OK.

 

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>43</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>46</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>49</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6683.2592/hwmon/hwmon3/fan2_input

 

Anyone with issues loading their sensor module and/or missing sensors for their motherboard, please read....

 

I have a Z490 Asrock ITX/TB3 board and have been battling for months trying to get the sensors to display in systemp plugin.

I have finally found a way to do it for the NCT6683 sensor chip.

 

I created a user script using the excellent plugin that contains the following at array startup-

 

modprobe -r nct6683

modprobe nct6683 force=1

 

The 1st line unloads the module.

The 2nd line loads the module using the 'force' option.

 

Now on every reboot of UNRAID i have full sensors from both coretemp and nct6683.

14 minutes ago, mikeyosm said:

Anyone with issues loading their sensor module and/or missing sensors for their motherboard, please read....

 

I have a Z490 Asrock ITX/TB3 board and have been battling for months trying to get the sensors to display in systemp plugin.

I have finally found a way to do it for the NCT6683 sensor chip.

 

I created a user script using the excellent plugin that contains the following at array startup-

 

modprobe -r nct6683

modprobe nct6683 force=1

 

The 1st line unloads the module.

The 2nd line loads the module using the 'force' option.

 

Now on every reboot of UNRAID i have full sensors from both coretemp and nct6683.

mikeyosm, I'm a bit new to unraid and all of this, would you mind going into more detail about how you created the user script and where? I understand the 2 lines in the script (roughly), but I don't know how to create the user script.

 

Thanks! 

8 minutes ago, Hkup859 said:

mikeyosm, I'm a bit new to unraid and all of this, would you mind going into more detail about how you created the user script and where? I understand the 2 lines in the script (roughly), but I don't know how to create the user script.

 

Thanks! 

I downloaded the plugin

 

then set up a script like this...

 

 

with the script contents

 

#!/bin/bash
modprobe -r nct6683
modprobe nct6683 force=1

9 minutes ago, mikeyosm said:

I downloaded the plugin

 

then set up a script like this...

 

 

with the script contents

 

#!/bin/bash
modprobe -r nct6683
modprobe nct6683 force=1

Assuming I did everything right, it didn't seem to work for me. Here's what I did:

 

1. Downloaded the plugin

2. Created modprobe script, but with nct6775 instead of nct6683 because that's what the dynamix system temp plugin detected for me.

3. Set the script to run at array startup

4. Stopped the array

5. Started the array.

 

When I went back to the dynamic system temp plugin it still didn't give me any sensors to choose from.

 

I guess my question(s) would be, do I need to use nct6683? Dynamix System Temp shows "k10temp nct6775" for me, do I need to do both in the script?

 

Like I said, I'm new to this, so I appreciate your help.

5 minutes ago, Hkup859 said:

Assuming I did everything right, it didn't seem to work for me. Here's what I did:

 

1. Downloaded the plugin

2. Created modprobe script, but with nct6775 instead of nct6683 because that's what the dynamix system temp plugin detected for me.

3. Set the script to run at array startup

4. Stopped the array

5. Started the array.

 

When I went back to the dynamic system temp plugin it still didn't give me any sensors to choose from.

 

I guess my question(s) would be, do I need to use nct6683? Dynamix System Temp shows "k10temp nct6775" for me, do I need to do both in the script?

 

Like I said, I'm new to this, so I appreciate your help.

please post modprobe nct6775, sensors-detect and sensors output

 

17 minutes ago, mikeyosm said:

please post modprobe nct6775, sensors-detect and sensors output

 

Here are the results from running those commands:
modprobe nct6775:

modprobe: ERROR: could not insert 'nct6775': No such device

 

sensors-detect:

# sensors-detect version 3.6.0
# System: Micro-Star International Co., Ltd. MS-7C35 [2.0]
# Board: Micro-Star International Co., Ltd. MEG X570 UNIFY (MS-7C35)
# Kernel: 4.19.107-Unraid x86_64
# Processor: AMD Ryzen 9 3950X 16-Core Processor (23/113/0)

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): y
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 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6797D Super IO Sensors'                   Success!
    (address 0xa20, driver `nct6775')

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): y
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

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): y
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): y
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x29
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM96080'...             No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Nuvoton NCT7802Y'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654'...                              No
Probing for `Maxim MAX6690'...                              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Maxim MAX6695/MAX6696'...                      No
Probing for `Texas Instruments TMP400'...                   No
Probing for `National Semiconductor LM95235'...             No
Probing for `National Semiconductor LM95245'...             No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC EMC1402'...                               No
Probing for `SMSC EMC1403'...                               No
Probing for `SMSC EMC1404'...                               No
Client found at address 0x4a
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3)
Do you want to scan it? (yes/NO/selectively): y


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `k10temp':
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

Driver `nct6775':
  * ISA bus, address 0xa20
    Chip `Nuvoton NCT6797D Super IO Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

Unloading i2c-dev... OK

sensors:

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.