@fireix I understand when I was still in the field I was one time in a data center for over 18 hours straight working on this huge Cisco equipment that has a special service contact. We had to keep swapping drives and devices back and forth to get configuration and data off for the new drives it was a nightmare call and the parts were no longer made so they sent new stuff that required new cards to work. I felt like a zombie after I left. But it was accessible and running had iOS running and when I started it was completely dead and no parts could be ordered for it in the system, Our team had our hands full with it but we got it going. By the time I left all the needed was an activation code adapted and added to it for all the features it was using again.

Right. The FreeBSD base changed from 12 to 14 between pfSense 2.6 and 2.7. Older versions of both ESXi and the VM version within it do not support FreeBSD 14 so be sure both are new enough.

@stephenw10 thank you, sir.

What does pciconf -lv show? None of that is especially new. I'd expect all of it to be supported. Steve

No worries.

@stephenw10 Yes, it's resolved - attributed to Devine Intervention.

@stephenw10 no more random drops. Thanks!

@dam034 Thank you for sharing VGA Dummy. And then i owned that...It helped my mini PC work well which doesn't need a plug-in monitor when booting up Everybody can seek a lots dummy on the internet with the lowest price (About 1$) Another dummy type: HDMI Dummy (I am using it. Work well) DP Dummy ...etc...

I had tried a bunch of things from the troubleshooting guide but had missed the package re-install. Looks like that did it. I'm on 2.7.2 now. https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html?_gl=11qha9n4_gcl_auMTAzODQxMzcxNi4xNzE5NDU3Nzc2_gaOTM4NDE4ODkuMTcxOTQ1Nzc3Ng.._ga_TM99KBGXCB*MTcxOTQ1Nzc3NS4xLjEuMTcxOTQ1OTUxMi4xNi4wLjA.#forced-pkg-reinstall

@brianjg said in Unable to upgrade due to HTTPS scanning (NOT USING A PROXY): env SSL_CERT_DIR=/etc/ssl/certs/ curl -v https://www.pfsense.org Yet that works there? And using the system env (which appears to be the same!) doesn't?

This is resolved. A hardware update caused an NDI change.

It definitely isn't and wasn't CE because there has never been an arm64 CE build. You should just be able to select the aarch64 memstick image for 1100 like: https://shop.netgate.com/products/netgate-installer?variant=41345658454131

https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html

Hmm, well I have no explanation for that. Glad it worked out though.

Either will work. Or both! We usually prefer a forum post first just so we can triage issues that have already been solved or are actually some other cause.

The legacy recovery image? How exactly is the upgrade failing? Just to be clear it should upgrade with no problems. I tested numerous times in different configurations on the 1100.

@stephenw10 I am grateful for every answer. My pfSense runs in KVM, so backup and restore are very fast.

Yes we could probably improve the wording there. It depends on how that sees the error. It is actually an improvement already. Previously it always reported 'latest version' even if it couldn't actually check.

Yes just open a support ticket and request it: https://www.netgate.com/tac-support-request

@User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?: @User6buinf43 said in Cannot boot after successful 2.7.2 install - EFI partition problem?: Is there a way to try this hw.mfi.mrsas_enable="1" option with the pfSense installer? I was able to set this option by choosing "3. Escape to loader prompt" and using these commands: set hw.mfi.mrsas_enable="1" boot The drives then showed up as da0 and da1 with the manufacturer/model displayed instead of just mfisyspd. Installation worked and it boots! Still trying to find a way to get a boot log from the installer. So looks like this is FreeBSD installer not properly recognizing some hardware RAID controllers and loading MFI driver instead MRSAS. Recently I have similar problem when CE (probable the Plus also) version, when installer not see VDRIVE at all if it was ZFS formatted. And installer able to see, choose and successfully installing pfSense on it and working w/o any issues ONLY WHEN RE-INITILIZE TGE SAME VDRIVE ON RAID CONTROLLER’S LEVEL (from it’s BIOS menu). I wrote bug to pfSense bugzilla, but still no solution from pfSense DevTeam. (May be because this is mostly problem on FreeBSD side, not on pfSense. And the second - this issue not affect exactly pfSense’s hardware, , only users with bare metal DIY servers, so not have higher priority to resolving…).