Xaero

Members
  • Posts

    413
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Xaero

  1. So I have a new build running the latest Unraid 6.6.0 rc-4; and I'm having issues with the temperature plugin.
    The sensors correctly read inside the plugin like so:

     

    image.png.4e0cd6b5f4d7f521307739f450135954.png

     

    However after selecting desired sensors like this:

     

    image.png.c275ecfaa351072958cfdd58a037d11c.png

     


    And then hitting "Apply"
    The sensors all disappear like so:

     

     

    image.png.00bb02e7b8d7022e4ca58dab3f999faf.png

     

    Hitting "Rescan" and done have no effect, and all of the sensors on the dashboard also disappear (fan speeds)
    Running "sensors" in the terminal gives this output:

     

    		
    
    		sensors
    		Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced
    		Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
    		Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced
    		Error: File /etc/sensors.d/sensors.conf, line 12: Undeclared bus id referenced
    		sensors_init: Can't parse bus name		
    
    

    The content of that file looks like this after hitting Apply:

     

    		
    
    		# sensors
    		chip "nct7904-i2c-0-2e"
    		ignore "fan3"
    		chip "nct7904-i2c-0-2e"
    		ignore "fan4"
    		chip "nct7904-i2c-0-2e"
    		ignore "fan8"
    		chip "coretemp-isa-0000"
    		label "temp1" "CPU Temp"
    		chip "coretemp-isa-0001"
    		label "temp1" "MB Temp"
    		chip "nct7904-i2c-0-2e"
    		label "fan1" "Array Fan"		
    
    


    If I delete the file, and then run sensors this is the output I get:

     

     

    		
    
    		nct7904-i2c-0-2e
    		Adapter: SMBus I801 adapter at 0580
    		in1:          +1.04 V
    		in2:          +1.04 V
    		in3:          +1.48 V
    		in4:          +1.24 V
    		in5:          +1.23 V
    		in6:          +0.58 V
    		in7:          +1.84 V
    		in8:          +0.53 V
    		in9:          +1.78 V
    		in10:         +1.79 V
    		in11:         +1.21 V
    		in12:         +1.21 V
    		in13:         +1.21 V
    		in14:         +1.21 V
    		in15:         +3.31 V
    		in16:         +3.16 V
    		in20:         +3.32 V
    		fan1:        4591 RPM
    		fan2:        3026 RPM
    		fan3:           0 RPM
    		fan4:           0 RPM
    		fan5:        3006 RPM
    		fan6:        3033 RPM
    		fan8:           0 RPM
    		temp1:        +36.9°C
    		temp2:        +51.5°C
    		temp3:        +50.2°C		
    
    		coretemp-isa-0000
    		Adapter: ISA adapter
    		CPU Temp:     +52.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 0:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 1:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 2:       +46.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 3:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 4:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 5:       +43.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 8:       +45.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 9:       +47.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 10:      +45.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 11:      +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 12:      +45.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 13:      +46.0°C  (high = +83.0°C, crit = +93.0°C)		
    
    		coretemp-isa-0001
    		Adapter: ISA adapter
    		MB Temp:      +50.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 0:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 1:       +45.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 2:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 3:       +42.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 4:       +46.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 5:       +42.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 8:       +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 9:       +42.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 10:      +44.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 11:      +40.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 12:      +43.0°C  (high = +83.0°C, crit = +93.0°C)
    		Core 13:      +45.0°C  (high = +83.0°C, crit = +93.0°C)		
    
    


    If I comment out the lines in the config file "chip nct7904-i2c-0-2e" then it works. Not sure if this is a proper fix but its working for now. Hopefully the developer of this plugin can adopt a solution:

     

    		
    
    		# sensors
    		#chip "nct7904-i2c-0-2e"
    		ignore "fan3"
    		#chip "nct7904-i2c-0-2e"
    		ignore "fan4"
    		#chip "nct7904-i2c-0-2e"
    		ignore "fan8"
    		chip "coretemp-isa-0000"
    		label "temp1" "CPU Temp"
    		chip "coretemp-isa-0001"
    		label "temp1" "MB Temp"
    		#chip "nct7904-i2c-0-2e"
    		label "fan1" "Array Fan"		
    
    

  2. On 10/19/2018 at 1:10 PM, itimpi said:

    If you do not like the dark theme why not use the light one instead?

    That was the point of my post:
    To show the quoted user where the setting is on the interface. It's easier to show with a screengrab than it is to say "yeah at the bottom of the page on the left side of the footer look for the theme dropdown and click it, you can pick a light theme there."

  3. Anybody tried or gotten Pterodactyl.io dockers to work on unraid? I'd like to get that working as it seems like a better solution to me since I wish to run several game servers.

    I'm currently using MineOS for my minecraft server, and my other game servers are on my old NAS running ArchLinux. Everything is very manual and has no GUI there, which makes it difficult for me to allow other administrators access to start/stop functions etc. Pterodactyl seems like it would enable me to allow other people access to the bare essentials pretty easily. I'm trying to retire the old NAS, so I can eventually repopulate it with larger disks and renew it.

  4. How would one go about setting this up for TAP mode instead of TUN?
    I have tried every setting in TUN mode and cannot get hostname resolution and samba to perform correctly.

    For example I can type \\<unraid>\share and it does not work, but \\<ip>\share does. However in browsers where HTTP requests are made http://unraid/ works fine since they are going through the DNS.   I figure this is only possible via TAP mode?

  5. So I've got an ArchLinux guest, I've also tried Manjaro and Antergos. I've installed and started+enabled the spice-vdagentd service; video is set to QXL.
    If I set the builtin VNC Viewer to remote resize and resize the window or set fullscreen the display size never changes.
    What am I missing for this setup?
    I've read through the Archwiki page as well as what few posts I can find on the unraid website but nothing regarding this.

  6. I just purchased an unraid pro license, and I'm just a tad disappointed with the virtualization side of things. I love everything else, but I'm tempted to install Xen Server and then dump unraid inside that.
    There's an official SPICE HTML5 client, and a full generation of QEMU ahead of this now.
    NoVNC is "okay"
    VNC as a technology is "Okay"
    But for VMs I think SPICE, especially inside a web browser, is going to be far superior. Perhaps offer both options, but I cannot see the logical argument for being an entire generation behind on QEMU versions and using a dated technology like VNC for VMs.
    NoVNC's scaling doesn't seem to play nice with the QXL video driver so the fullscreen toggle and the "remote resize" options are completely useless.

    That said, I really think unraid should consider moving auxiliary components to a managed package system. Then we could update things like QEMU, the kernel, etc without waiting for unraid to bundle a new system.  Hopefully I don't end up regretting the purchase and having to migrate to a different technology in the end....

    • Upvote 1