Arubial

Ok I was able to find some 4 pin extensions, and I moved the other fans to headers 3 and 4, and all four fans are spinning down correctly. Thank you!

So do I need to move the other two fans to sensor 3 and 4? I don’t think the fan wires are long enough. I changed the threshold settings based on your reply but the last two fans stay at full speed.

I just discovered this plug-in this morning after migrating to a Supermicro X10DRU-i+ a couple months ago. I think I have everything configured properly, but only 2 of the fans are spinning down. I have 4 fans total, the stock ones from SuperMicro. My sensors report the last two fans are on FAN7 and FAN8, which is what I selected, but I cannot get them to spin down at all.

Thanks, I'm good to go now

I checked my settings, and they haven't changed. SMB is enabled, and I have it set to public like I always have. I don't really need security on this particular share. I also made sure the share option is enabled in the UD settings. What's going on?

Since upgrading to 6.10.3, I am unable to see my SMB shares with UD. I have rebooted the server and rebooted my Windows clients, but the share doesn't show up when I browse to my Unraid server. I can see the share if I SSH into the Unraid server, and the Docker containers can all see the share, but I can't access it via SMB. Diagnostics attached (the share is called "SSD") jarvis-diagnostics-20220616-0934.zip

Thank you, I was able to get it upgrade to 6.10.2 after creating tg3.conf

Can I put the tg3.conf file in place and then upgrade to 6.10.2 or does it need to be done after the upgrade? I'm still confused why the Intel NIC stops working during the Unraid boot sequence. It's like the OS is disabling it.

Also it looks like I was somehow able to get the rollback to work, but I don't know how. When I first tried it, it was still showing 6.10.2

I got it to boot correctly this time (it's using the Broadcom NIC). Diagnostics attached. jarvis-diagnostics-20220531-1008.zip

Thanks, I tried the tg3.conf file anyway and rebooted. The Intel NIC is still turning off during the Unraid boot-up sequence for some reason. It's my understanding those NICs aren't effected by the tg3 driver issue, correct?

Greetings, I have a Dell PowerEdge T320 with 2 Broadcom NICs, and I am not able to get any network activity after installing 6.10.2. The server boots fine and shows me the IP address, but I am not able to ping the server or out from it. I have read the announcement thread with the workaround to disable VT-D, but that didn't help. I disabled virtualization entirely and I still have the same issue. My server also has a 4 port Intel NIC that I was using to test pfSense, but I'm not doing that anymore. I moved the network cable to the Intel NIC and booted the server up. I confirmed the NIC had a link light during the boot-up sequence, but the LED turned off sometime during the Unraid boot. I can't even get the sever to boot up in GUI mode unless I do safe mode. But I still can't get any network activity with either the old NIC or the new one. I want to rollback the update, but when I downloaded my most recent backup using the "My Servers" section of the forum, it appeared to be the 6.10.2 version, not 6.10.1. What can I do?

Thanks, I tried that originally but it kept reverting back to the web version. You helped me fix it though, it was a caching issue.

I was able to do this and I'm receiving the 404 error whenever I try to browse to the admin section over the web. When I browse to it locally, it asks for the admin token like it should. When I put the admin token in, it reroutes back to the web and I get the 404 error again. So I have no way to login.