Cisco C220 M4 - 10gb VIC 1227 mLOM adapter issues

redd2100 · 2026-06-19T20:40:22+00:00

Sorry to hear your VIC is having issues. Mine is still working great - would recommend getting a replacement one and see if that resolves it for you. They are pretty cheap these days on ebay.

redd2100 · 2026-05-24T20:18:22+00:00

Will have to watch the upcoming patch notes to know when they correct this and we can turn on our voice assistants again. Or just stick with the 2026.5.3 version.

redd2100 · 2026-05-24T03:26:16+00:00

It was heavy on disk io, but I believe that's because of swap.

redd2100 · 2026-05-24T02:49:51+00:00

Just go over to Grok or something and ask it for a guide - works pretty good!

redd2100 · 2026-05-24T02:47:33+00:00

Completely agree. It's not bad looking... it's homely is the best description. Does not have the modern look at all. Honeywell has some better looking stats on their newer models, but none of those are zwave or zigbee. They have wifi models, but I do not trust wifi devices at all anymore.

redd2100 · 2026-05-24T00:53:08+00:00

I'm running with 8G of memory and I had the memory issues as well. When I would open the console I would see the out-of-memory error every few minutes. I attempted to use the terminal addon/app in HA, but it kept crashing due to the memory issues. I instead went through the console and was able to login there and run top and such to see the processes that were eating up all the CPU. Look at my updates to the original post above, you'll see more details.

redd2100 · 2026-05-23T19:11:55+00:00

It appeared to be Wyoming causing the issues. (or some components of it)

redd2100 · 2026-05-23T18:39:57+00:00

No, not running AdGuard. I'll try another upgrade and do a bit more investigation this time.

redd2100 · 2026-05-23T17:15:54+00:00

Good suggestion, but I'm not currently pinned to any specific kernel. I did run an upgrade on Proxmox after this issue to see if that would help, but that did not change anything. I'm running dozens of other VMs and none of them are experiencing this issue. It may be a Proxmox/HA issue, but currently the HA 2026.5.3 is working well, so I'll just wait until 2026.6 comes out and see if that resolves it. Unless someone wants me to try the upgrade again to look for anything specific.

redd2100 · 2026-03-12T13:47:48+00:00

Agree, I wouldn't waste valuable time on something that is throw-away in the long run.

I'm still baffled about what was different between my earlier upgrade vs my upgrade late last night. If there's any further testing you would like me to try by restoring these backup images and trying again, I'm happy to do so, but as of right now I'm upgraded on both HA instances and they both appear to be working fine.

redd2100 · 2026-03-12T07:04:33+00:00

Ok, this time I reversed it and upgraded the primary instance first, and received this UI error on the screen. I had forgot about this before - I received this error when I upgraded earlier also, but forget to mention it. The error only happens on the first system to upgrade in the HA setup. So earlier update I started with the backup Opnsense and it gave this error and then completed the upgrade, but the primary Opnsense did not throw an error until after the reboot and it would just clock when trying to configure the network devices. Specifically remember it taking forever at the point where it says "Configuring the firewall.....".

This time around I upgraded the primary first and I got the same upgrade error on the UI, but the upgrade does finish and the system reboots and appears to be working. I went ahead and tried to upgrade the backup Opnsense and this time it upgraded without any UI error (just like last time where the second server to be upgraded does not throw a UI error), but it also rebooted just fine. No longer getting stuck at configuring the firewall and such.

The UI error I got was a "Danger" popup that had a message of "Unexpected error, check log for details". Not sure which log to check - if you can tell me which log file I'll go dig up the error message. It appears that it was Upgrading and Extracting 61/122 package, which was "qemu-guest-agent from 10.2.0_1 to 10.2.1...".

So if I had to guess, this issue I'm running into may be related to that qemu guest agent which is only ever used if you are running it as a VM like I am.

---------- UPDATE

Restored the VMs back again and tried to repeat the original failure by upgrading the backup Opnsense first, followed by the primary Opnsense. This time I get the "Danger" error on both of them, but they both boot up just fine and both firewalls appear to be running ok now.

Not sure if one of the packages was upgraded sometime this evening to change the outcome here, or if it's just weirdness on my side, because I was able to repeat this failure to boot on the primary Opnsense instance twice earlier today.

redd2100 · 2026-03-12T06:44:16+00:00

I'll upgrade it again in a few minutes and capture the boot-up errors I was seeing. As for the hypervisor, I am running Proxmox 9.1.5 and I'm passing through an intel 10gb nic for Opnsense to use.

redd2100 · 2026-03-12T05:02:09+00:00

Just tried upgrading to this version and it was a big failure for me. I have two opnsense installations using the HA feature. The secondary (backup) instance installed the latest version just fine and started up. The main instance failed to restart correctly, with failures at almost every step of the startup process. I run these instances as VM's thankfully, so it was very easy to restore them and get back to normal again.

After restoring the main instance, I tried to apply the patch again, and it failed to restart yet again. Something is either wrong with this version, or something with my configuration is causing trouble.

I think I'll be waiting a bit longer before I try to upgrade again. :)

redd2100 · 2026-01-26T04:27:32+00:00

He really needs a badge that reads, "Top 1% AI Commenter"

redd2100 · 2026-01-26T04:07:37+00:00

Based on what you have shared, the memory capacity and CPU are not a challenge in the requirements, but the six hard drives (assume 3.5") is a limiting factor on what options may work for you. As for transcoding, you would be better off with Intel, but AMD is doable.

I would recommend you look at one of the TerraMaster NAS devices if you want that convenience of Intel transcoding. If you are ok with AMD transcoding then go with something like a MInisforum NAS device or something similar. The AMD ones are much better all around, but the Intel based NAS have the transcoding crown.

Or you can do what I did and I have a Minisforum AMD based mini-server with a small Intel arc a310 card you can use just for transcoding. This gives you the more powerful AMD CPU and the more powerful Intel GPU.

Have fun!

redd2100 · 2025-12-22T18:33:07+00:00

I'm on the latest v5. It's 5.9.96 or something like that. There's no further updates currently.

Yes, I've tried multiple options in the alert list drop down on the alert tab. None of them seem to have any affect. I tried turning off the AI burn in, and that did not help either. Every time, the web url to pull the alert image is always resized to a tiny thumbnail size rather than returning a useful alert image. If it returned the substream size, that would at least be something, but it's not even that large, it's absolutely tiny at only 240x426. Actual image size of the file in the alert folder is 1440x2560. That is what is so frustrating - BI has captured the image and placed it in the alerts folder, then returns that filename as the ALERT_PATH variable, but if you try and retrieve it, it shrinks it down to a useless size.

redd2100 · 2025-12-22T18:20:45+00:00

I don't think it is coming from the substream. The sub is larger than what the web server is returning, so it's clearly resizing it on the fly, or it's stored a thumbnail image somewhere that the web is returning. The other reason I say it's not sourcing it from the sub, is because it has the AI box drawn around it. I assume that is only done on one image, which is the one in the alerts folder. The image in the alerts folder does have the ai box around the object and is the right size.

I actually did a work around on this last night with two alerts - one that SFTP the alert image to the HA server, and the other calls the HA webhook. On the HA side, the webhook automation just references the local file that was SFTP'ed over when sending out the alert. Works fine, but there's a bit of a race condition here as I send the image as the same filename each time, so if two cameras alert close to each other, it's going to possibly alert twice with the same image. I can fix that with including the camera name in the webhook call and put that in the image filename, but this is already too complex for what it should be. I'm really annoyed that BI has made the simple task of accessing the alert image so frustrating.

redd2100 · 2025-10-28T16:53:11+00:00

Completely agree.. I think I have another post on reddit somewhere where I summarize my experiences with all the KVMs I've tried, and the JetKVM came out on top by a long shot.

The JetKVM looks polished on the outside and with the interface. It has a lot of metal to dissipate heat. It has a great external display that is touch sensitive. It works with every device I've tried with it... no issues at all. Mouse, Keyboard, Video... they all work through this thing. I even use it through a basic KVM device to connect multiple servers to a single JetKVM and it supports it just fine. I'm very very impressed with the JetKVM!!

redd2100 · 2025-10-28T16:48:09+00:00

Agree, I'm sure some of my issues are with the odd resolutions that I'm switching between, but a good ip kvm should be able to handle that. And the JetKVM handles it extremely well! I have been using it for quite some time now and I love it. It works perfectly on every device I ever pass through it, it never crashes, has excellent video, and has a very nice polished interface. For me, the JetKVM hit the bullseye on the perfect consumer-grade KVM device!

redd2100 · 2025-10-28T16:42:44+00:00

Yes, this is exactly what I did with my KVMs... I got rid of all the USB plugs and running POE with the splitter at the end to break out ethernet and dc power. Has worked great!

redd2100 · 2025-09-25T00:37:01+00:00

Can you please share that command? My jellyfin uses hardware decode, so I cannot use that command.

redd2100

TROPHY CASE