Hi,

 

I have come across a repeated notification on the console. I have chosen to report this as a defect as it has been reported twice on the General Support Forum over the last 2 months and has had no responses from the community. See here:

 

icedragonslair (reported issue on March 22, 2015, 11:05:33 AM ): http://lime-technology.com/forum/index.php?topic=38889.msg361827#msg361827

bob_iannucci (reported issue on February 12, 2015, 06:39:10 PM): http://lime-technology.com/forum/index.php?topic=38153.msg353392#msg353392

 

At the moment I am viewing this as an improper operation bug.

 

unRAID OS Version:

 

6.0-beta14b

 

Description:

 

Unexpected No Sensors Found Notification being received on the Console.

 

How to reproduce:

 

Using a system with the specifications I have noted in Other Information and using 6.0-beta14b: Open the console (either via BMI interface or a direct monitor connection) and load the Unraid GUI. Notification will appear when the page is loaded or reloaded.

 

Expected results:

 

Not to receive the notification.

 

Given I am not seeing any missing data in the GUI (with respect to sensor type data e.g.  temperature etc) I didn't expect this notification.

 

Actual results:

 

Repeated notifications on the console of "Make sure you loaded all the kernel drivers you need.  Try sensors-detect to find out what these are. No sensors found!"

 

Other information:

 

I did a bit of playing and it seems to be associated with the loading the GUI. When I load the Dashboard tab I get 2 messages and when I load others I seem to only get 1. I "assume" that the GUI is trying to get some sensor information that it can't get from my system BUT there also doesn't seem to be anything missing from any of the screens. So, whatever Unraid needs to get it seems to be getting just fine - which makes this notification more confusing.

 

This is happening on my new Backup Server which I have loaded v6.0-beta14b on. System Specs are:

 

ASRock C2550D4I Mini ITX Motherboard

Kingston 4GB (1x4GB), PC-12800 (1600MHz) ECC Unbuffered DDR3L, ValueRAM, CL11, 1.35V, Single Stick

Silverstone ST45SF-G 450W SFX Form Factor Power Supply - ST45SF-G

3 x Seagate 8TB Archive HDD, SATA III, 5900RPM, 128MB

 

Note I have encountered this message whether there is an Array configured or not, whether parity sync's or checks are in progress or not. It also occurred with NO additional Plugins. I have since loaded some additional plugins and there is no change.

 

I have also attached a syslog and here is a screen shot of this notification in my BMI console:

 

 

P.S. There are other users on the forum who pretty much have the exact same build as me. I am sure we could solicit their help to replicate. 

20150412_syslog.txt.zip

Have you tried the latest sensors-detect version? There is information about it here:

 

http://lime-technology.com/forum/index.php?topic=31172.msg344918#msg344918

 

Gary

Have you tried the latest sensors-detect version? There is information about it here:

 

http://lime-technology.com/forum/index.php?topic=31172.msg344918#msg344918

 

Gary

 

No I haven't tried it - thanks though! I am happy if its going to be fixed in a future release. I very rarely use the console (and the messages dont show up via telnet or in the GUI) so I don't think it will bother me.

 

Ill let the defect workflow just runs its course.

Ill let the defect workflow just runs its course.

 

I am not sure which Mod is monitoring this thread, but can someone either aknowledge this as a defect or push back. I think that with the information provided by Gary (Ghunter) in the post above this should be listed as a defect IMHO.

 

1. User creates defect report topic - COMPLETE

2. Admin/Moderator/Developer determines if this is a true defect and not a support issue.  If support issue, your topic will be moved to the appropriate support board - PENDING

3. If legitimate defect, your topic will be moved onto a Roadmap child-board for scheduling.

I have the same issue on my rig, the AsRock C216 WS. 

 

If I run the sensors-detect thingymabobber it finds the nct6775 chip. 

 

If I manually load the nct6775 driver with modprobe, everything works, fan speeds are displayed on the WebGUI. 

 

Upon reboot the drive isn't loaded again, despite sensors-detect saying it adjusted some file to do so.

 

 

I have the same issue on my rig, the AsRock C216 WS. 

 

If I run the sensors-detect thingymabobber it finds the nct6775 chip. 

 

If I manually load the nct6775 driver with modprobe, everything works, fan speeds are displayed on the WebGUI. 

 

Upon reboot the drive isn't loaded again, despite sensors-detect saying it adjusted some file to do so.

 

Interesting. Firstly another AsRockboard - but I am interest about your fan speed comment. As I note above "nothing seems to be missing from the gui" so I didn't even expect to see fan speeds. See below - nothing ...

 

 

Note to Mod / Admin / Developer: If as HellDriverUK points out, this driver can be loaded to stop the sensor error and provide the data to Unraid I'd be happy to help test so it can be included in an updated release.

This is the lm-sensors config I use.  The fans are not monitored by the sensor chip. They are only available through the BMC. So you can use the BMC webpage or ipmitool or freeipmi package. Also here is what I have in my go file

# Update Sensors
cp /boot/custom/etc/sensors.d/c2750.conf /etc/sensors.d
modprobe nct6775
modprobe ipmi_si
modprobe ipmi_devintf

I usually place files in a path similar to the actual system path under /boot/custom/

And the ipmitool for unRAID 6 is here

https://github.com/dmacias72/unRAID_6.0/releases/download/2015.03.22/ipmitool-1.8.13-x86_64-1_fs.tgz

c2750.txt

I am seeing this issue as well, b14b and b15 (asrock board as well).

 

System specs:

 

CPU - Intel Core i5-4440S

Motherboard - ASRock Z97 Extreme6

Desktop Memory - Crucial Ballistix Sport 8GB x 2

In most cases it's unnecessary to 'modprobe' device drivers because linux will automatically load them for h/w it finds.  However, for non-PNP (plug and play) h/w on legacy ISA buses, such as some of these sensor chips, you have to load the driver manually.  The way to do this has been documented above by dmacias.  Put this line at the start of your 'go' file:

 

modprobe nct6775

 

 

Had to add the jc42 driver manually for the Asus AM1M-A.