pappaq

Members
  • Content Count

    111
  • Joined

  • Last visited

Community Reputation

4 Neutral

1 Follower

About pappaq

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've disabled the plugin "HDDTemps" in the telegraf config. It would be awesome to get the functionality back up to monitor the HDD temps via grafana. But unti that I am happy that the HDDs stay spun down. I am tackling the issue in the next few days, if I find the time for it. Maybe you could explain the "post agrument" idea a little further? Thanks!
  2. This was not the case for me. I've restarted my dockers one by one and it looks like that "telegraf" is keeping the disks spun up. Trying to figure out now why though.
  3. I'm settling with RC2 right now. I hope it runs relatively smooth. I've got the next problem though. My HDDs are held spun up by somthing, I can't tell what. Does anyone can take a look at the diagnosis? Thanks. dringenet-ms-diagnostics-20210214-1551.zip
  4. Updated to RC2 and the behavior is gone. Going to test some more.
  5. Hey there, by investigating the high powerdraw of my system I stumbled upon a very bad quirk in my system. The system shows all disks as spun down but they are actually spun up! I can feel them vibrating or spinning back up, after I forced them to spin down. That is a HUGE difference of nearly 40W!!! Not to talk about the always running disks that should be spun down to enhance their lifespan. Here my diagnostics. dringenet-ms-diagnostics-20210214-1144.zip
  6. Very good idea! Thanks. Gonna try that out. I've ordered the CPU nevertheless. In case the sidegrade doesn't turn out as I hope it will, the CPU will propably sell for the very same price I've ordered it today. They are sold as salvaged parts from OEM systems. Does anyone have information about newer Ryzen generations and the powerstate handling under Unraid?
  7. Hey community, I'm in the process of upgrading/sidegrading my server. First off, I wanna get the powerdraw significantly lower. My current setup consists of: Ryzen 1700 @ 3000MHz Asus B450 ROG Strix F Gaming 32GB RAM @ 2400MHz 10x HDDs helium/Non-helium 4x SSDs 1x Dell H310 SAS controller 1x Intel Gigabit NIC 5x Noctua Fans 1x Nvidia GTX1070 for transcoding 34 Dockers and 2 Debian VMs running. The system draws around 100W in idle state. I've got several thoughts about getting the powerdraw lower:
  8. Hi, do you have information about the powerdraw of the system? I'm considering downgrading my Ryzen 1700 8 Core CPU to a more energy saving, newer CPU. Thanks!
  9. I've solved the docker issue for now. I changed the following setting: There was a second entry for br1 with no gateway etc. I've unchecked the entry and restarted the docker service. The dockers are resolving the addresses correctly now. I have no clue, why a docker with an IP in the 192.168.1.0/24 net would try to communicate via br1 and its not available gateway. It's a mystery to me. My problem from the first post isn't resolved yet. Maybe someone could help? Thanks a lot in advance!
  10. I've pinned the issue down to all the dockers with a static IP address and br0 as their network. They can't resolve any address. What am I missing? Do I have to configure the second NIC any different to not intervene with the traffic of br0 or sth like that? Has anyone an idea?
  11. Some docker, which are part of the network via br0 can't resolve DNS. I can't figure out what's wrong. Pleas help! dringenet-ms-diagnostics-20201027-1905.zip
  12. So my interface rules are set as follows: But after each reboot, unraid sets the default gateway to br1, like this: It should use 192.168.1.210 via br0! I can't delete the default route via GUI, so I do it after every reboot by hand via SSH. What am I doing wrong?
  13. Ok, do I have an option to see how far the reconstruction of the array is without the GUI?
  14. Here it is: [here was an upload]