Hoopster

Steal away; especially when you are correct. @kaiguy Yes, that is what I followed but I ran the command to disable network bonding. Of course, with ipmitool already installed I did not have to go through all that install rigamarole and you can forget sudo. It also would not work for me directly on the affected server. I had to run it remotely from another Unraid server. ipmitool -I lanplus -H $target_ip -U $username -P $passwd {the raw command string}.

IPMI on my E3C246D4U looks just like yours; no network bond configuration under Network Settings. On my E3C246D2I it looks like this: However, I am fairly certain I had to run something on the command line to get that to show up. I'll dredge the depths of my memory (or Google) to see if I can come up with it. 😀

Yes, this is true. Too bad it can't work for everyone. 🙁

Your board is a bit different than the non-10G NIC version. It has both VGA and HDMI ports. The one I have only has VGA and that is tied to the BMC/IPMI. In this case, the iGPU is used only for video transcoding, it does not provide any video out capabilities. In your case, with an HDMI out, it must behave differently. I don't care about video out from the iGPU (only use it for hardware video transcoding) but you may. Unfortunately, I cannot give you any guidance on that as my board has no HDMI port.

You can test the iGPU/IPMI functionality with that BIOS to see if it already works and does not require the special BIOS like we needed for the E3C246D4U. Usually, the public BIOS provides that functionality. I have had two other ASRock Rack server boards that did require a special BIOS so we were surprised when that was required with the E3C246D4U.

Did you read this section in the 6.12.0 release notes (specifically the last paragraph)? Network Improvements We added a new section under Settings->Network Settings->Interface Extra, allowing users to define which interfaces the Unraid services use. By default, all standard interfaces with an IP address are included in the list of listening interfaces. The tunnels of the built-in WireGuard function of Unraid are automatically added or removed from the list when the Wireguard tunnels are activated or deactivated. The user may exclude these tunnels from the list of listening interfaces. To use the Tailscale or Zerotier interface, it is required to add the interface name or IP address of the communication to the list of included listening interfaces. Important: It is imperative that Tailscale or Zerotier container is running before the interface is added to the list.

In my case, I could not do it from a terminal session because Unraid 6.12.0 crashed during boot for me. I had to put the flash drive in another computer and manually edit i915.conf to add the options line. if you can get a terminal open in 6.12.0 just type this on the command line: echo "options i915 enable_dc=0" >> /boot/config/modprobe.d/i915.conf Attached is my i915.conf file with options i915 enable_dc=0 in it. If you are having trouble from the terminal, just drop this in /config/modprobe.d on your Unraid flash drive. i915.conf

Yes, that fixed my crashing problems with Unraid 6.12.0 and an i5-11600 CPU. The Linux kernel in Unraid 6.12.0 does not like 11th gen Intel CPUs with low power mode. That line turns off low-power mode on the CPU and solves a lot of instability/crashing issues. It is certainly worth a try to insert the option line in i915.conf and reboot.

It's more of a "works fine with some hardware and not with other hardware" thing. This one is very hard to pin down. For many. moving to ipvlan solves their call trace problem. Personally, the problem for me with macvlan call traces went away completely when I moved docker containers to a VLAN with their own IP addresses on that VLAN instead of using br0. It does not matter if I use macvlan or ipvlan for Docker since I created the VLAN.

Nothing special needed in the BIOS that is CPU related. If you want to use the iGPU you need to make sure primary graphics adapter is set to onboard and that intel multi-monitor is enabled. Other than that, just setting the Unraid USB flash as the boot disk and setting up IPMI the way you want it are the only necessary changes. There is really not much to it. Now, in the case of the E3C246D4U, we needed a special BIOS direct from ASRock Rack to enable the use of the iGPU for transcoding while still allowing IPMI/BMC video. I do not know if your version of the board with the 10G NICs also requires that. Other ASRock boards work just fine with the public BIOS.

The i915.conf file above completely blacklists the i915 driver so it does not even load. You'll get no iGPU that way and is just to test if that driver loading is the cause of a crash in Unraid 6.12.0. It was crashing 6.12.0 for me. Adding the line "options i915 enable_dc=0" (instead of blacklisting it) to i915.conf fixed those crashes as it turns off low power mode in the iGPU but still allows it to load and function.

What do you mean by detailed setup guide? Many of us in these forums have the E3C246D4U (version without the 10G NICs). Here is a somewhat lengthy forum thread detailing our experiences with the E3C246D4U.

I usually always read the release notes and failed to do so this time. With a big update like 6.12.0 there is likely to be a lot of useful info in the release notes. I had an issue after upgrading to 6.12.0 which was clearly spelled out in in Known Issues, but, this time I failed to read the release notes and got hit with a server crashing on boot. Easy fix if I had read the release notes. 🙁

Did you read the 6.12.0 release notes which explains what you need to do to get Tailscale to work with 6.12.0? The applicable section is called Network Improvements.

@Talisman2208 Attached is an i915.conf file with the i915 blacklist if you have trouble creating your own. Just put it in /config/modprobe.d on your Unraid flash drive.i915.conf

Likely it is crashing. It just does it in the middle of booting. On a different computer, manually create i915.conf (if it does not exist) in the config/modprode.d folder and add "blacklist i915" (without the quotes) to the file. This prevents the iGPU drivers from loading and will let you know that is the problem if the server then boots successfully.

Nope. Just copied files from "previous" folder to the root of the flash drive. It's like installing a new version of Unraid and leaves the config folder intact.

@grumpy When you upgrade within the GUI (Tools -->> Update OS) a folder named previous is created on the root of the flash drive. This contains the files associated with the previous version of Unraid that was installed on the flash drive. After my failed upgrade to 6.12.0 (would not boot at all), I just copied all of the files in the previous folder back to the root of the flash drive (overwriting everything) and I was back to 6.11.5.

As long as the lock icon on the right is locked (green), the wrench icon will not show up. When you unlock the icon (click on it and it turns red), the wrench icon (Content Management) then shows up in the dashboard.

So, because there may be an issue on some systems, Limetech should not be allowed to release a version of the OS that is stable on most systems and provides features some have been waiting for years to have? I actually blame myself more than Limetech because this issue I (and you, it appears) experienced is clearly documented in the release notes which I failed to read. Based on that, I would have known the solution before I experienced the problem and I could have decided if I wanted to upgrade to 6.12.0 as I had been warned. I usually read the release notes before performing any upgrade and forgot to do so this time. Known issues Crashes related to i915 driver We are aware that some 11th gen Intel Rocket Lake systems are experiencing crashes related to the i915 iGPU. If your Rocket Lake system crashes under Unraid 6.12.0, open a web terminal and type this, then reboot: echo "options i915 enable_dc=0" >> /boot/config/modprobe.d/i915.conf Setting this option may result in higher power use but it may resolve this issue for these GPUs.

If I reduce browser scaling to 90%, all three columns show up. That was not necessary with 6.11.5.

Yes. I failed to mention that. From the problematic laptop:

Same issue for me but only on one particular laptop. On two desktops on one other laptop, the GUI dashboard shows all three columns in 6.12.0. Lenovo laptop with 1920x1080 display. Only two columns in dashboard regardless of browser used. Reset does nothing. Clearing browser cache does nothing (except make me login to everything again). Three columns in 6.11.5 Lenovo laptop with 1920x1080 display. Three columns; all is well Desktop connected to 1920x1080 monitor. Three columns: all is well Desktop connected to 3840x2160 monitor. Three columns: all is well

@FlyingTexan This worked for me with the i5-11600 on one of my servers. I manually edited i915.conf in modprobe.d and added the options line. This is a Linux kernel issue with the version in 6.12.0 and the Rocket Lake (11th gen.) CPUs and low power mode. Not an Unraid problem per se and hopefully a future Linux kernel in Unraid will address the issue.

Yes, the server boots into 6.12.0 if I disable Intel Virtualization Technologies in the BIOS and with no i915.conf file in modprobe.d iGPU is still enabled as /dev/dri with the appropriate files exists and I am able to hardware transcode in Plex. This is also an acceptable short-term solution on this server as, for now, I do not intend to run any VMs on the server. @ich777 UPDATE: After a couple of more reboots, diabled Vt-d no longer solved the problem. The server was back to the prior no-boot behavior. After restoring the i915.conf file with the options line, it again boots successfully. That appears to be the only "permanent" solution.