pappaq
-
Posts
210 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by pappaq
-
-
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.
-
Updated to RC2 and the behavior is gone. Going to test some more.
-
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.
-
2 hours ago, Vr2Io said:
Depends on the setting, the core no. reduce in half, if also limit at low clock speed, does still have enough power to drive 34 docker and 2 VM ? If enable turbo/xfr, then it actually use same/more power then before. I suggest you disable half core to evaluate first.
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?
-
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:
- I've set the CPU clockspeed that low because under unraid the powerstates weren't managed right like 2 years ago and setting it lower was the only option to keep the CPU under control. Same with the RAM. I don't neet the speed of the RAM but from 3200MHz to 2400MHz were a decrease in powerdraw of 6W.
- Second I'm considering changing the CPU to a Ryzen 3 PRO 4350G. These CPUs should have a severly lower powerdraw.
What do you guys think?
Thanks for suggestions in advance!
cheers!
-
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!
-
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! -
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?
-
Some docker, which are part of the network via br0 can't resolve DNS. I can't figure out what's wrong. Pleas help!
-
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?
-
Thanks, works.
-
Ok, do I have an option to see how far the reconstruction of the array is without the GUI?
-
Here it is: [here was an upload]
-
Doesn't work via putty
-
Perhaps I did not express myself properly. I change the default route after each reboot as described above.
Gonna check the GUI later, if somebody answers my question regarding my "File not found." GUI problems!
-
Hello there,
I've got a problem with my default route in unRAID. After every reboot, the second NIC is used for the default route configuration. I have to change it after every reboot back to my first NIC. Is there a way around that?
Thanks in advance!
-
Hey there,
my server was running for many days without issues now, but now after swapping out a disk, to replace it with a bigger one, the GUI doesn't show. I've started the array with the encryption key and after I said start, the server shows this:
I had that problem before. Fixed it by rebooting. But I hope, that the new HDD is being rebuild and don't want to mess with that.
Does anyone have a fix?
Thanks in advance
-
1 hour ago, pappaq said:
Hey, I've tried the exact same procedure. It doesn't work. I'm always getting the following error message in the docker log:
I've created the database and user and checked the connection to my mariadb docker, that is already hosting like 3 databases.
I can't figure out what is wrong.
After a few re-installations it seems to run for now. Thanks anyway.
-
On 5/17/2020 at 5:10 AM, jevan23 said:
Thought I'd expand on this as it took some time for me to figure out what changes were needed in the shinobi container, and it might help out someone else:
Created a mariadb database as follows:
CREATE USER ‘shinobi’ IDENTIFIED by ‘password’;
CREATE DATABASE IF NOT EXISTS shinobi;
GRANT ALL PRIVILAGES ON shinobi.* TO ‘shinobi’ IDENTIFIED BY ‘password’;
now you can edit the shinobipro container and make the following changes based on the new mariadb database created above:
MYSQL_USER: shinobi
MYSQL_DATABASE: shinobi
MYSQL_HOST: IP address of unraid
maria db database location, change it to: /mnt/user/appdata/mariadb/databases/shinobi/
MYSQL_PASSWORD: password
Hey, I've tried the exact same procedure. It doesn't work. I'm always getting the following error message in the docker log:
I've created the database and user and checked the connection to my mariadb docker, that is already hosting like 3 databases.
I can't figure out what is wrong.
-
48 minutes ago, dlandon said:
Uninstall the preclear plugin. Post dagnostics if the same thing happens.
Still the same issue.
-
Hello there, I can't get an external HFS+ drive to mount. It only says format. And I've got UD+ installed. Do I miss something? The HDD comes right out of an old iMac from 2008. Thanks in advance!
-
Thanks so much saarg. Pretty standard rookie mistakes but I'm learning so much from guys like you. Thanks for the support!
It runs as expected!
-
2 hours ago, saarg said:
My guess is that you add it as root when you do a docker exec -it habridge bash?
You need to add the keys for the abc user. The home folder for abc is /config.
Ah that sound logical. In the deprecated habridge docker that was not the case. I've changed it and will try it out this evening. Thank you!
-
On 11/14/2019 at 10:35 PM, saarg said:
You mean the picture of the ssh command?
That is not a valid script. You haven't used the shebang. The script should start with #!/bin/bash
Ok, that was one dumb failure of me...in my other scripts I have #!/bin/bash at the beginning...
Now some more content to explain my last problem to get this working again:
I've got the following scripts to enable and disable my ambilight based on hyperion on my TV:
on.sh
#!/bin/bash ssh [email protected] "sudo systemctl start hyperion"which enables the ambilight.
off.sh
#!/bin/bash ssh [email protected] "sudo systemctl stop hyperion"which disables the ambilight.
These work from the commandline of the habridge docker. I've copied the SSL keys to the ambilight raspi and all works well. But with the below config the scripts are not executed properly. Does someone have a clue what I'm missing here?
Thanks in advance!
Disks spun up but show up as spun down!
in General Support
Posted
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.