Wabs

@Spin-MasterThanks for thinking along. I belive I do have the correct BIOS settings. If you wouldn't mind, please have a look at my settings here: https://imgur.com/a/25ZBsGY Looks correct to me, right? I think my old PSU is the cause of the system not going beyond C3. I don't have any other PSU lying around right now. Will consider upgrading but hopefully a couple of brands introduce some new PSU's with 500W or less power with the ATX 3.0 spec. That should mean they are pretty efficient, also at 10W load. Not a lot of choice with ATX spec 2.53 or 3.0 right now. Not sure approx 100 euro is worth the investment (I have solar panels and am producing more power than I use in my house over a year).

Have a look at the list of hardware on Hardwareluxx: https://docs.google.com/spreadsheets/d/1LHvT2fRp7I6Hf18LcSzsNnjp10VI-odvwZpQZKv_NCI/edit#gid=0 you can see very efficient systems there and see what SSD's they have used. maybe that helps. No change in Ubuntu. I now think that it could be my PSU. Thats quite old. Bought it in 2014 and the model exisits since 2012. I also read a couple of posts online on other forums that cheap and old PSU's prevent lower c-states. I'll see if I can find an affordable PSU that has a low power usage at very low load. I know the Corsair 550 2021 version would be a nice bet.

Thanks for the reply @mgutt! I was trying to find info in the different PowerTOP tabs to find the reason why I wasn't going above C3. Makes sense to just disconnect hardware and see what happens. Will do so later this morning. Great tip to help me find the cause. Also thanks for explaining what and how the commands work. I did notice that both ethernet controllers have wake on LAN enabled, even after I run --auto-tune. I switched them manually in powertop. I'll try your command for that one too then. I'll do a search for lowering the power consumption for the dockers I'm running. If I find anything useful I'll link it here. /edit1: update to SSD firmware and BIOS made no noticable changes. still max C3 /edit2: pulled the SSD out, no change either, still max C3 /edit3: disconnected the hard drives, no change, still C3 I'm out of hardware to disconnect... I've only got RAM, a processor and the USB stick with unraid on it left. Can't figure out why it wont go beyond C state 3.

Hi all, and especially Mgutt, nice topic! Thanks for the write up! I've been doing my homework too and I'm trying to lower the power usage of my server. First the hardware which was sort of chosen for decent low power a couple years back (Dutch tech site Tweakers.net has a nice 'low energy server' topic that helped me choose this build. Not perfect but not a bad basis I believe): Processor: Intel Pentium Gold G5420 Motherboard: ASRock H370M-ITX/ac Memory: Crucial Ballistix Sport LT BLS16G4D240FSB (1x 16GB) SSD: Toshiba RC500 500GB Harddrives: 3x 10TB. 2x WDC_WD100EMAZ-00WJTA0_1EGLJKWZ 1x WDC_WD101EDBZ-11B1DA0_VCJDR1NP (all three shucked from a WD Elements desktop unit) Powersupply: Seasonic G-series 360 watt USB stick: Samsung FIT Plus 32GB Cooler: Scythe Big Shuriken 2 Rev. B Case: Fractal Design Node 304 HDD's spin down every 30 min Running completely headless unless I'm twaeking bios Running Plex, SABNZB, Radarr, Sonarr, Nextcloud, Pihole, Mariadb, SWAG, DuckDNS, unifi controller as dockers. All seem very low in cpu usage nearly all are at 0.01% Home Assistant as VM. I ran powertop --auto-tune and all tunables jump to good without any issue. Server now draws 18-20W when all the drives are idle. Aprox 35-40W when active. Measured with a Shelly plug S. C-state doesnt drop below C3, haven't fugured out why that is. Even with the array disabled, so not running anything at all for 30 min. C3 is all I get. Tips and Tweaks Power Saving CPU govenor set to Power Save All C-states enabled in the BIOS. Turbo Boost disabled. Lot of pictures and screenshots here: https://imgur.com/a/25ZBsGY My main goal is to see if I can get an even lower idle consumption Questions: Does any of the above info tell me (or you in this case) why I'm not getting a higher C-state than C3? If so, can I fix that? I'm guessing the SSD may be preventing it as I hardly have any other hardware. but how to prove that? I never edited the go-file before. From what I understand from your first post in this topic I should be able to disable more hardware (usb ports, PCI-e slot etc) with the list of commands you posted in the first post. How can I test them? Just in the console run: "for i in /sys/class/net/eth?; do ethtool -s $(basename $i) wol d; done" for example? see if it gives any errors and do all of them one by one. if all is fine add the complete list to the go file (just copy paste?)? I am also now doing the powertop --auto-tune by hand after every boot. that can go in the go-file too right? Any tips or tweaks to my dockers to prevent them from spinning up disks? it doesnt happen very often but a couple times a day. I expect Nextcloud does that and Plex checks the library or something. I hope all my info you need for some tips is there.... if not, let me know what else you need! Thanks for any tips or comments!

Thanks for the reply. Found the issue! The config file is seperated in to sections. Such as Items, player etc. I had changed the sub entries such as "teleportprevention = true" but I had missed the switch for the complete section "items". So after changing that line in the config to true and restarting the server it works. Again, thanks for your work, much appreciated!

@PeacefulDiscord & @ich777 Awesome! thanks for this! Started using your docker as a Valheim server about 4 days back. Playing with 2 friends. Good fun, thanks for the effort! Now we ran in to the issue that we can see each others map (fog of war is personal). This is an option to share in Valheim+ so started looking in to this. Found the update in docker and now we can enable it in our game. cool! What we did: Install the new docker and install the client window side files (from nexusmods). Changed the config file (valheim_plus.cfg i think its called) to enable the map visibility share and also disabled the teleport limit (with copper and tin). Put the config file in the server folde. Started server and logged in. Result = incompatible version... hmm ok. Copied the config file to all our client folders and tada! we can log in again! The mod seems to work as we have the black crow on our smelter saying hi, welcome to valheim plus bla bla donate here. However, the changes we made to the config don't have any affect. Still cant use portal with copper and cant see friends map. Looking at Nexusmods website and the description, the unix version of valheim plus states: Make sure to execute 'chmod u+x run_bepinex.sh' Make sure to run the run_bepinex.sh Is this something we still need to do? or do you run this in the docker start command? When I try to do this I get an error. Possibly I need to stop the server first? but how? I usually stop the docker container but then I close the docker, not just stop the server.... Any idea what we are doing wrong? How do we load the Valheim+ config file? Again, thanks for the help, cool docker to have and easy to setup and use!

Hi guys, I'm new to unraid (coming from windows 10). Im setting up sonarr and SABnzb. Watched a couple of videos and read 15+ threads about people having the same problem (such as this one, with an identical issue it looks like). sonarr sends downloads to SAB just fine. SAB downloads them en then the issue starts. Sonarr shows a bar at the episode that download is at 100% but doesn't process them. I cant get sonarr to see the completed downloads. In the log I see this error: Import failed, path does not exist or is not accessible by Sonarr: /config/Downloads/tvseriesfoldername It looks like sonarr is looking in the /config folder for completed downloads. However, I set my mapping to the following: Sonarr mapping: Container Path: /data -> /mnt/user/Data/Downloads/ Container Path: /media -> /mnt/user/Data/Series/ Container Path: /config -> /mnt/user/appdata/binhex-sonarr/ SABnzb mapping: Container Path: /data -> /mnt/user/Data/Downloads/ Container Path: /config -> /mnt/user/appdata/binhex-sabnzbd in SABnzb settings I have the following: Temporary Download Folder -> /data/INCOMPLETE Completed Download Folder -> /data the download folder mapping is identical (which was the issue in the post I linked with a similar problem), I don't get why it's giving the error. Should'nt Sonarr be looking in /data for the completed downloads and not in /config like the log is saying? the /media mapping in sonar works fine, why isn't it looking in /data? Any ideas? Argh... already found it. Sonarr settings > download client > at the bottom "remote path mappings" Didn't notice that and hadn't set it. What I set there: Host: x.x.x.x (ip of your unraid server, no port behind it) Remote path: /mnt/user/Data/Downloads/ (same as the /data mapping in sonarr) Local path: /data/ That solved my issues. Maybe my post will help others in the future.

Would just like to confirm that adding the SMB share in unassigned devices and mounting it indeed solved the issue. Copied over 3.1TB with an average speed of 100.7 MB/s. Thanks for the tip fka.

I'm experiencing nearly the exact same thing as the opening post. New to unRAID: new setup. -Intel Pentium Gold G5420 -ASRock H370M-ITX/ac -Fractal Design Node 304 -Samsung FIT Plus 32GB -2x WD Elements Desktop Storage 10TB (shuckt, WD 100EMAZ white disks) -Scythe Big Shuriken 2 Rev. B -Crucial Ballistix Sport LT BLS16G4D240FSB -Seasonic G-series 360 watt -Toshiba RC500 500GB Currently only 1 HDD attached. Precleared and filling it up before adding the second drive to startup parity. Cache drive is enabled but not on any of the shares (yet). I want to move over all my data directly before activating cache. Getting about 45MB/s right now when moving larger movie files (more than 1 GB per file) via a net connection in Krusader. My older server (i3 with 8gb ram and 4x4tb, all from 2014) running windows 10 filled up 1gbit LAN easily with any large files being transferred (100+ MB/s). I expect these speeds on the new setup too because I'm not using any parity yet. I just read fka's reply about 'remote SMB'. I haven't had the chance to test this yet (I'm at work right now). Could somebody explain why this could have an impact and what this setting actually changes? What actually happens when I then 'mount' this? Thanks for helping another noobie out!