Posts by Ambro72

    I follow alexicon's instructions but this is the output:

    Of course I relunch commands to regenerate sensors conf... so there isn't the folder.

    What is acpi_enforce_resources=lax? I see in internet that may be dangerous for the hardware. Is it safe?



    I tried also to disable coretemp module and refresh sensors with /usr/share/openmediavault/mkconf/sensors but nothing changed in my sad graphics... ?(

    Have you new ideas?

    Thankyou for assistance.

    Sorry, but no graphs again....

    I don't have the folder you tell me....


    the attachment for sh -x /usr/share/openmediavault/mkconf/sensors


    • sensors.txt

      (9.86 kB, downloaded 186 times, last: )

    Thank you for your assistance!

    I made all thinks you write me. And I restart the system

    Now module it877 is loaded at bootup.

    # lsmod | grep it87
    it87 57344 0
    hwmon_vid 16384 1 it87

    I clear cache of my browser but in OMV Sensors panel I see only sad faces.
    I traied to deactivate CPU temperature and reactivate too, but with the same result. ;(


    And now, after omv-mkconf sensors, I tried to activate CPU Temperature in WEBGui and no errors when I click on apply! Wonderful!

    But in the monitor cpu page I see sad faces... ||

    Ok. Sorry.

    I uninstalled sensor plugin, I installed sensor plugin 3.0, I activated CPU temperature, I click "save", I click "Apply" and I have error again.

    Now I run the command and I attach the output.

    And this is the output when I run sensors :

    root@ServerOMV:~# sensors
    Adapter: ISA adapter
    Core 0: +31.0°C (high = +105.0°C, crit = +105.0°C)
    Core 1: +31.0°C (high = +105.0°C, crit = +105.0°C)


    • sensors.txt

      (9.79 kB, downloaded 168 times, last: )

    I am on Openmediavault 3.0.86 and kernel 4.9.0 stock

    When I click on "Apply" I have the error window. After I'm into a loop and only "restore" permit me to go out.

    I attach output of your command after having the error message.

    Thank you very much


    • sensors.txt

      (4.83 kB, downloaded 193 times, last: )

    I have good news!!!

    During last days I have remaked the USB pen more times but nothing changed.

    Today I have tried another new pen drive (same trademark, always 3.0) and all is good. System is always on-line and webgui is ok.

    Do you know if some kinds of pen drive don't work in openmediavault?
    Can I mark this thread as "solved" or it's better to investigate the reason of this?

    Now I start my openmediavault adventure! Thank you

    I am on a new Terramaster F2-220 and new openmediavault user
    I installed sensor plugin and after an error activating Temp CPU I tried to update to the latest version from github following your instruction.

    I have always the same error and I' m not able to "apply" changes.

    This is the error:

    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkconf sensors balls 2>&1' with exit code '2': # sensors-detect revision $Revision$ # Board: AMI Corporation Aptio CRB # Kernel: 4.9.0-0.bpo.3-amd64 x86_64 # Processor: Intel(R) Celeron(R) CPU J1800 @ 2.41GHz (6/55/8) Running in automatic mode, default answers to all questions are assumed. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Module cpuid loaded successfully. 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 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') 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): 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'... Yes Found `ITE IT8772E Super IO Sensors' Success! (address 0xa30, driver `it87') 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): 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): 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): Found unknown SMBus adapter 8086:0f12 at 0000:00:1f.3. Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f000 (i2c-0) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus ssc (i2c-1) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus vga (i2c-2) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus panel (i2c-3) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpc (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpb (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpd (i2c-6) Do you want to scan it? (yes/NO/selectively): Now follows a summary of the probes I have just done. Driver `it87': * ISA bus, address 0xa30 Chip `ITE IT8772E Super IO Sensors' (confidence: 9) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp modprobe it87 /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Unloading i2c-dev... OK Unloading cpuid... OK

    I need a hint, please.

    Thank you

    Sorry but I was busy.

    I tested over hating putting a big external fan to the cpu without case.

    The problem has appeared again. :(
    The matter is that the system is not shoutdown, the ping works again. But the system is not accessible.
    I'm thinking that the problem should be due at Virtual installation. Some kind of configuration in virtual machine that conflict with real hardware but I don't now what.
    Thankyou for your help and if you have same other idea I'm here :D

    Hello everybody.
    I'm from Italy and I use linux system since a lot of years (Archlinux)
    I am a new user of openmediavault. Weeks ago I tried it on virtualbox and I thought it's a vary good software for my future nas.

    I have bought a TERRAMASTER F2-220 but I want openmediavault instead of TOS.

    I installed openmediavault on USB key following this guide
    Installing OMV w/o keyboard and monitor using VirtualBox

    I' m able to boot Terramaster NAS with openmediavault but I have an issue.

    After 2-3 minutes from boot the control panel freezes and If I try to connect again by the browser I see the message: 403 Forbidden Nginx
    The same thing with Ssh connection: I'm able to connect to port 22 but afetr 2-3 minutes commands don't work and If I try to reconnect the message is: Connection reset by port 22.
    If I ping the NAS I have good answer (0% packet loss)

    The only way I have is switch off NAS by power botton.

    Someone has some idea about my problem?