Hkup859

Hi all, I've been running the storj docker app for almost a year and it has been largely great, but I've recently been having an issue where the container fails and restarts a lot. Like 4+ times a day. It usually restarts in 2's as well, such as at 2am then 2:10am, then it's fine for a few hours. I haven't really done any troubleshooting with crashing unraid docker containers and I'm having trouble finding where logs would be stored for the failed container(s). The log UI only shows the active container. Can someone point me to where useful logs would be? If it helps debug the issue, it also seems to happen every 2 to 4 weeks. I haven't had it restart in 2 weeks and now it's restarted 4 times.

For anyone interested, I got this to work by changing the USB Controller option from 2.0 to anything else. Hope that helps others in the future!

I've been playing around with setting up VMs, specifically Windows VMs. I use the unraid interface, assign my usb mouse and keyboard (separate usb devices) and no matter what I do, I can't get the mouse to work. The keyboard works out of the box when I assign it to the VM, but the mouse doesn't. I even bought new mice to try, so I've now tried 3 working mice and none of them work. I'm not trying to pass through an entire usb controller, though I tried that too just to see if it would work and it did not. I also tried using the "Libvirt Hotplug USB" app/plugin, which also didn't work. I also tried not passing through the keyboard, switching what usb port (and controller) the usb mouse and or keyboard was on, and those didn't work either. Does anyone have any ideas on how I can fix this issue? I'm new to unraid, but my understanding is it really shouldn't be this hard to pass a mouse into a vm. Thanks in advance!

I've been playing around with setting up VMs, specifically Windows VMs. I use the unraid interface, assign my usb mouse and keyboard (separate usb devices) and no matter what I do, I can't get the mouse to work. The keyboard works out of the box when I assign it to the VM, but the mouse doesn't. I even bought new mice to try, so I've now tried 3 working mice and none of them work. I'm not trying to pass through an entire usb controller, though I tried that too just to see if it would work and it did not. I also tried using the "Libvirt Hotplug USB" app/plugin, which also didn't work. I also tried not passing through the keyboard, switching what usb port (and controller) the usb mouse and or keyboard was on, and those didn't work either. Does anyone have any ideas on how I can fix this issue? I'm new to unraid, but my understanding is it really shouldn't be this hard to pass a mouse into a vm. Thanks in advance!

Perfect, thanks!

That did the trick! I now see a list of sensors in the dynamix system temp plug in. Thank you very much for your help! If you don't mind helping with one more thing. There's a lot of sensors here and I only understand what a few are. Which ones should I use for cpu and motherboard temperature monitoring? Thanks again for your help!

Version: 6.8.3 Pretty fresh install, just got it a few days ago.

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.

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.

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!

Thank you, I've added it to that plugin thread/topic.

I apologize if this is in the wrong thread, just let me know and I'll move it to general support or somewhere, but I am following the official wiki for setting up CPU temperature monitoring with the Dynamix System Temp plugin. I've installed NerdPack GUI, installed PERL, then installed and hit "DETECT" in Dynamix System Temp. It finds my driver as "k10temp nct6775", but the options for "Processor temperature" and "Motherboard temperature" are set to "not used" and do not show any other options. I've hit save, redetected, rescanned, and done all the research I could find. I even tried some alternatives to Dynamix, but I can't seem to get anything working. For more info, my motherboard is the MSI Meg X570 Unify and I have a Ryzen 3950X. Everything else is up and running, so far I'm loving Unraid and it's working great, I just can't get CPU temperature readings. I'm very new to Unraid (on trial day 3 now), I like it a lot, but am still unexperienced in it. If someone could please help me with the next troubleshooting steps or if anyone knows a solution to this issue, please let me know. Here is the link to the tutorial I am following: https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing Screenshot attached if it helps any.

I apologize if this is in the wrong thread, just let me know and I'll move it to general support or somewhere, but I am following the official wiki for setting up CPU temperature monitoring with the Dynamix System Temp plugin. I've installed NerdPack GUI, installed PERL, then installed and hit "DETECT" in Dynamix System Temp. It finds my driver as "k10temp nct6775", but the options for "Processor temperature" and "Motherboard temperature" are set to "not used" and do not show any other options. I've hit save, redetected, rescanned, and done all the research I could find. I even tried some alternatives to Dynamix, but I can't seem to get anything working. For more info, my motherboard is the MSI Meg X570 Unify and I have a Ryzen 3950X. Everything else is up and running, so far I'm loving Unraid and it's working great, I just can't get CPU temperature readings. I'm very new to Unraid (on trial day 3 now), I like it a lot, but am still unexperienced in it. If someone could please help me with the next troubleshooting steps or if anyone knows a solution to this issue, please let me know. Here is the link to the tutorial I am following: https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing Screenshot attached if it helps any.