PSteward

My issue is that sometimes the fans don't get detected properly on boot, I've had them show 0 rpm and also show as DC instead of PWM. The fix for this seems be shutting down and then starting back up OR if that didn't work shut down and pull out and put power back then boot up. Being that once I have a successful boot it runs fine, it's the first thing I check once I reboot (I also don't reboot often, maybe once every few months). For the sensors.conf , it gets populated by the System Temp plugin, when you check that did it detect and try to load up your fans? You need to run it first and save (which breaks the sensors.conf file), then edit the file and save (you'll need to do it after rebooting too as it gets re-written). Mine finally works and I can see those RPMS in the dashboard and bottom of my browser.

For the unit itself I recommend going big, brand name, check that it fit in your case, and plugs are on the correct side (they vary). I also went with 80+ Platinum but you can do whatever. As for the cables you likely won't find it all in one box and need to find good 3rd party for the molex adapters, just ensuring that anything you connect to the power supply itself is compatible (pin outs are important), otherwise just molex breakouts should be fine if good quality (even though we wish we could avoid, it's impossible!).

I bought the Corsair HX Series, HX1200 for my 24 bay server as I was getting issues when all my drives were spun at once. Haven't had an issue since! The sata backplane was molex powered so dealing with that requires caution, definitely balance it and use good quality cables (OEM + splitters only where required).

My System Temp plugin has been broken for some time, finally I understand where it's getting the information from and why it was blank. Basically if your lists are all blank but worked before it's likely because your sensors.conf has an error. Run # sensors If there is no errors, it's something else, if there is errors, vi into /etc/sensors.d/sensors.conf and check for a line like: chip "nzxtsmart2-hid-#-#" It could be corsair or some other fan type you tried to enable on the plugin. Remove the hid-#-# part so it's like this: chip "nzxtsmart2-*" Change all that are like that, and save! Now it should work (works for me at least)! Link to known issue: https://github.com/lm-sensors/lm-sensors/issues/369

Also as an update today I found if you use Dynamix System Temp and scan add the fans from the NZXT to add in it will BREAK the sensors.conf file (not related to my docker). Steps to fix (and then you can show fan RPM on your dash!): Go to terminal (in Unraid) # vi /etc/sensors.d/sensors.conf change any line with chip "nzxtsmart2-hid-#-#" TO chip "nzxtsmart2-*" Press ESC and then :x # sensors Should output properly, not with an error. Now it will fix the Dynamic System Temp.

Seems like it isn't seeing the device. Did you check under USB (in Unraid) to see if it's there?

Updated to add a check for the liquidctl initialize, and fixed it so it doesn't set speed if already correct, plus additional checks for zero RPM. Just update your docker.

Hey Greg, Never noticed! I put that in because I noticed sometimes when I rebooted or started the server not all fans would work (showing 0 RPM) - honestly it doesn't really fix that issue though. It is REALLY important to check the logs at reboot to ensure that all fans are reporting more than 0 RPM and if not shutdown - then start again (reboot doesn't always resolve). I never had the issue once all fans are running but only on the occasional startup or reboot (I may do that every few months, so definitely important to verify). I'll review the coding and see if I can make some improvements based on how its been working of late - in addition at one point I'd like to extract the data into a plugin and show it on the interface (% + Speed).

Recently I have been having on-going issues where Unraid will hang/freeze. This causes all services to freeze (GUI direct on server, SSH, web interface, dockers) and unfortunately even with a syslog server there is nothing posting to the log when the freeze happens. I am assuming it's a hardware issue (CPU temps get up around 85c when I have a specific docker running and a VM at the same time), but not sure about that 100% (I am going to change my cooler / thermal paste this week however). My question is - if Unraid is hung up on a specific docker or VM, is it possible to have it force close that (is there a script that can still run?) and recover from the freeze up? I can still ping my server, and ssh TRIES to get in but just sits there, same with the GUI - I can type the username! I really wonder if there is a script that recover this type of issue. Thanks, --Phil

Same issue here with the sub-containers.

Yep that was it, Q24-27 are on point. I used localhost to access the qbitorrent hosting the VPN for this docker and then added the ports for my external qbittorrent (on a different machine). Thanks!

Next time I'm on that server I will! FYI it's not that it doesn't Auto Mount (can't mount what's not online...) - it shows "Remote Server is OFFLINE" until I push it to search for servers, then they all reconnect.

Hello! I tried using this container as a network for another however it appears the it blocks the LAN network (can ping items but not get to them). For example I put Lidarr to use the container as it's network (which works) but now Lidarr cannot access the local clients. I tried "curl http://LAN_address:port" and it times out - is this normal? Thanks!

Quick question: SMB Shares never reconnect after a reboot, but if I go to "Add Remote SMB" then click on the "windows logo" then "Next" then press "Search For Servers" - they all reconnect! What is it doing when it searches? I would like to add a user script to run after boot to reconnect the SMB drives since UD doesn't appear to be doing it at the moment. Thanks!

Hello! Server just completely froze up, couldn't even SSH or control it on my KVM (though it did have video output showing the login screen). It did respond to pings but all dockers, shares, ssh, emhttp were gone and I was forced to restart. Diag attached. Any ideas of the cause? Version: 6.12.3 Thanks, --Phil homeserver-diagnostics-20230824-1248.zip