firstTimer

Hi guys, did anyone try to connect any fan to the IPMI card itself? I just tried but this fan does not even start.. I also tried to connect a temperature sensor but the fan just doesn't even turn on... any idea?

Interesting topic and thanks for the contribution FYI, reaching C6 is usually the best compromise --> check this page out where this guy confirms that C6 to C8 difference is 1W only https://mattgadient.com/7-watts-idle-on-intel-12th-13th-gen-the-foundation-for-building-a-low-power-server-nas/ One question though for your second session of tests. (just to be the devil's advocate here) Did you remove the C-state limit of maximum C3 from the BIOS, right? There are some strange things here: As far as I know only HBA 9500 and 9600 support ASPM and 9400 can (with some issues though) Therefore with you HBA you should AT BEST reach C3 (disregarding if the slot is connected to PCH or CPU) So either powertop is bugged (presenting lower C-states than the device in reality is) OR motherboard is presenting some wrong values to powertop Following your tests though, it seems to me that, this "rush" (and time spent) to find the components with ASPM support to reach lower C-States does not really apply to every platform (I mean combination of CPU and Chipset)

@tdatta Can I ask you what you disabled to get the ASPEED 1150 get L1? I see it as disabled when using lspci command

macvlan, but I tried also with ipvlan and I have the same issue

@JorgeB I encounter this issue many times a day. I am setting up the internal services and external for my home and I am using a dual traefik configuration as proxy. The traefik I want to use for internal services has its own IP (coming from a VLAN) while the traefik used for external services is exposed on a bridge type of network. I started using docker-compose mostly because I can spin up things quickly but it happens (semi-randomly throughout the day that the Unraid UI becomes unreachable, and it happened also before with single docker container). The solution at the moment is to shut down the server, reboot, delete the docker.img and re-download everything. Can it maybe be something related to ipvlan or macvlan inside docker settings? As information, I have a dual NIC setup, where ETH0 is "reserved" for Unraid while ETH1 uses another VLAN and also binds another 2 VLANs

Can someone help me with this? I followed the thread above but with no success (in details this message here:) I did not understand where I should put the bind-interfaces parameter

Hi guys, do you think it is possible to connect the exisiting SlimSAS to a SAS expander card? I need to attach more devices but I would like to spare some watts of an HBA card, since most of the HDDs won't run at the same time (so bandwidth won't be an issue). Do you think it is possible?

My bad, I did not thought about deleting the dockerDisk... now it works perfectly, thank you for the support

Hi everyone, I don't understand why this happens but as soon as I activate the docker service inside Unraid ther WebGUI become unavaiable and my Unraid server becomes unreachable (even through SSH). When I restart the server through the IPMI card and I set the array to be started manually (hence docker service is turned off) then the server is reachable, until I start the array and docker service with it.

Oh nice, so at least the server with the 9600 is reaching a good result I would say (best would be C8 to C10) but with some many disks and so many variables that can influence this... it means you have a good result. Regarding the 9500, as you said, your server is quite busy so it is difficult to say if the lower C-states are not reached because of the high demand or because any component of the server could influence this result. I am kinda undecided whether to buy the 9500 or the 9600... both cost a good amount of money and calculating if those boards are more convenient in the long run because they could eventually lead the whole server to lower C-states is a hard problem to think about... My server doesn't go lower than C3 and it consumes 60W-70W at idle while similar builds consume 40ish watts with C8.

Could you please check with powertop if your cpu drops to lower c-states? I mean if the pckg state goes below C2 or C3

Thanks for your suggestion.... first I have to look into ubiquiti if it is even possible to set a different DNS Server for each VLAN

I don't like to open ports in router... I am just scared that if a bad actor tries to enter I wouldn't even notice... 1 pihole for each vlan, sounds a little complicated to set up but I know that there is teleport function/app. It is used to sync the settings between each pihole without doing it manually each time. What do you think? It means though that I have to add missing VLANs to eth1 page, right?

YES!!! Unraid is reachable from local address and HomeAssistant is running inside IoT VLAN and VMs are running in InternalServices VLAN so everything is working as expected. I wanted to route local services from IPs to domain names... do you have any suggestion? I mean let's say I have homeAssistant with IP 192.168.10.100 then I want to reach it at home.myhomelab.home Do you have any suggestion how to achieve something like this? I tried with Pihole but I can't see any device using pihole as local DNS server, I suspect that firewall rules that blocks VLAN to communicate with other VLANs is the problem... but even if I disable it, no devices is using pihole as DNS server

@Vr2Io Many many thanks for the help

Yes. I wanted to understand what container cause the issue of making the Unraid UI unreachable so I made those steps: Stopped all containers (with tailscale VPN activated on my laptop) otherwise I couldn't reach the Unraid UI Turned off tailscale and the Unraid UI became reachable again though domain Started each docker container one by one (I expected that one of the container made the Unraid UI unreachable) I started all the containers and Unraid UI is still reachable (basically no container caused the issue of make the Unraid UI unreachable) To double check, I restarted the Unraid and now everything is reachable without tailscale

@Vr2Io I still don't understand what happened... I went to docker page in Unraid and stopped all containers and I started the containers again, one by one. I even restarted the Unraid server and now I can access the domain locally without tailscale.

@Vr2Io After you suggestions I've managed to have homeAssistant running on IoT VLAN and pihole on InternalServices VLAN. Still, the only problem is that Unraid is unreachable when I turn docker service on

After the changes I've done in the previous message the gateway section was updated automatically

I tell you my setting on UDM: Port 7 is the cable for eth0 and has Unraid as Untagged VLAN (and block all the other VLAN) Port 8 is the cable for eth1 and has InternalServices as untagged VLAN and IoT (6) as tagged VLAN Changes i've made: eth0 --> as before, so it gets the untagged Unraid VLAN (30.X) eth1 --> It gets automatically an IP from InternalServices (20.X) untagged VLAN and it supports tagged IoT VLAN (60.X)

of course thanks ALOT for the help

Image 1: Eth0 is the Unraid VLAN network. Eth1 is InternalService VLAN and eth1.6 is the IoT VLAN Image 2: Config of eth0: so Unraid server is published on Unraid VLAN Image 3: Config of eth1: it is published on InternalServices VLAN but has also an access to IoT VLAN Image4: Are the current listening interfaces:

I tried to stop tailscale and I couldn't access the Unraid UI immediately ( I use tailscale as plugin). The only thing that makes the issue disappear is when I start the Unraid Server without docker service enabled, in that case I can reach the Unraid server without issues. So it seems to me that some docker container (or my docker configuration) is causing this issue. The only "weird" containers that use VLAN network instead of a bridge type of network are homeAssistant and pihole. I can confirm that if I turn off docker service then the unraid server is reachable locally (through domain, if I try with ip it get automatically redirected to domain)

I tried both to use the IP and domain locally ( only domain works when using tailscale) when I try to ping -n IpOfUnraid --> the packets are lost with timeout This is strange because the Wifi is connected by default to another VLAN (Daily) I tried to ping the gateway of the Unraid VLAN and it works! Mac Address of Unraid is not even shown

@Vr2Io Thanks for your help and explanations, it seems a little more stable the network now so now I still have 2 issues: Unraid isn't accessible though local IP once docker service starts VMs which should run on host1 (physical LAN2) network (even though I tried to refresh their generated mac) as soon as I start one of them, the Unraid UI just can't be reached anymore