kaiguy

Worked like a charm! Thanks for the follow up and solution.

Hello! Just installed 2025.02.06.2108 and I see that the notification bell is showing notifications, there is an unread count of 27, but no notifications are displayed. Any way to clear this out? I tried all filter options, and in every case nothing is displayed. Thanks!

Upgraded to 7.0 stable from 6.12.14 without issue. Most tedious part was reinstalling all the docker containers after switching to overlay2. Might help others--when I deleted the existing docker folder, I didn't realize that would nuke my docker network. After a few reinstalls of containers I noticed they had no network assigned. Once I created the same docker network name, all the containers from that point on were assigned to the correct (previously-assigned) docker network. Really impressed how smooth this went overall! Great job, unraid team!

Just FYI... per William, BIOS 2.40 does support iGPU Multi-Monitor.

Looks like there's also a new 2.40 BIOS (I've been running the unreleased L2.35). My server seems to be so sensitive that I really don't want to take the jump to test out either of these updates.

This thread hasn't had much activity in a while, but I started getting frequent IPMI ECC errors for the past month. Curious if anyone else has run into this and has any suggestions. Sensor: DRAM ECC ErrorB2 Description: Correctable ECC - Asserted Pretty sure B2 indicates the memory slot (2nd from the top). I think I'll try swapping B1 and B2 and see if the IPMI error changes to B1. If not, this would be an indication that the B2 slot is going bad, right?

Hmm... this is a little odd. So I ended up successfully able to run the command locally on my unraid server (without specifying an IP address). I no longer see bond0 at all, but I also still don't have the bond configuration option. It's almost like the command just killed the bond without exposing that option. If I force refresh the network settings screen, it does end up showing the bond conf option before logging me out. When I log back in its not visible. What I do have is now the ability to choose enabling the LAN on eth0 or eth1 under Network IP settings, and also the ability to register eth0 and/or eth1 to the BMC. Maybe I'm just misunderstanding that I thought I would see 3 eth options (the 2 LAN and 1 IPMI LAN). Edit: Ok, I got the bonding configuration to show up. Required me to do a BMC cold reset in the settings. Ultimately, though, something is just not working for me. No matter what, I can't seem to get the board to utilize the IPMI port. Even with bonding disabled it's always attaching the IPMI mac address to either eth0 or eth1. I wonder if its related to this bug, but I'm not feeling confident or motivated enough to do anything about it. Oh well.

Thank you both, @Hoopster and @JimmyGerms. I tried the command locally on my server but as Hoopster experienced it didn't work for me. I don't have a secondary unraid server, so I am going to spin up a VM on a different machine, install ipmitool, and give it shot. I'll edit this post with my results.

Thanks, @JimmyGerms. I am on the same as well. I wonder if I need to plug a cable into LAN2 for the option to show up? Next step will probably be pulling power from the server to soft-reset the BMC. Weird.

Rehashing the IPMI bonding question earlier on this page... Although I have a network cable plugged into both the IPMI LAN and LAN1 (LAN2 is unused), I notice that my new Unifi switch is associating both MAC addresses with a single port. So I figured I'd just go and break the bonding, but I don't seem to have the "Network Bond Configuration" option in the GUI. I also didn't see anything in the BIOS. Any thoughts?

Been running the last few rc's without issue, and updated to stable tonight just fine. Thanks for all of the work that went into this huge release!

Working great so far. Thanks @Taddeusz! Supper happy I can now use ed25519 keys.

Thanks for the heads up, @Hoopster. I've never ran into that before, but I have had an intermittent issue where trying to login to the HTML5 IPMI gui would just keep going back to the login screen. The only way to correct it was to shut down and pull the power from the server, but I might try reflashing the BMC next time I encounter it.

Closing the loop. Since disabling turbo boost (once again), I have not encountered another CPU_CATERR crash, even with some pretty intensive CPU workloads.

Thanks for sharing this. Using your script (with the minor edit that @ICDeadPpl highlighted--it was erroring out for me as well without adding the backslash). What is your recommendation, @mgutt, for identifying what is making /var/docker/overlay2 writes? I'm getting pretty consistent writes still even after incorporating the script.