@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…).

What exactly do you mean by options 1 and 2? If for some reason your system cannot work with the current Net Installer you can ask for the legacy installer. If it's using a PPPoE WAN for example. If it was an upgrade from CE though that wasn't available. You would have to reinstall CE 2.7.2 and upgrade to Plus again. Steve

@sabersoul1217 yeah just open a ticket with TAC..

@HLPPC said in asked for login and password, however after entering login: admin unable to type pasword: Does Intel RDrand matter at all? No, not really. And OpenSSL no longer supports hardware engines like that anyway.

OK so it seems like whatever is running DHCP for those VMs is not passing any DNS servers. That is presumably some Hyper-V setting.

Try running: pfSense-repoc first. If that doesn't work try resaving the update branch in System > Update Settings.

@stephenw10 Which means that valid USB boot drive with the good firmware etc doesn't auto boot except if the admin interrupts the boot process from the console, and types in the command 'run usbrecovery' .... So, I was wrong. Some manual manipulations are needed then. https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html is clear about it.

@iantmarshall Don’t worry, I got caught in Captcha hell last weekend and couldn’t’ even download the thing, and ended up giving up in disgust and finally managing to track down a direct link to the images to do it manually. It is ridiculous. If someone can’t manage to download an image and create their own USB stick I don’t think they’re the market for pfSense quite frankly.

It appears to be choking on this function: /* override php memory limit */ $php_memory_limit = config_get_path('system/php_memory_limit', 0); if (($php_memory_limit >= 128) && ($php_memory_limit <= get_php_max_memory())) { ini_set("memory_limit", config_get_path('system/php_memory_limit') . "M"); } Do you have a custom php memory size set in System > Advanced > Misc?

Great result!

I finished the upgrade. I had to use the dropdown box and go from 2.7.0 to 2.7.1. After that update completed I went to 2.7.2, It would not allow an update from 2.7.0 to 2.7.2. After the update to 2.7.1 the admin screen still said I was on the current release. Otherwise it went smoothly and quickly. The processor in the Hunsn (passmark about 2400) made it fly relative to my older slower pcs from the past. Thanks.

Opened a bug to track it: https://redmine.pfsense.org/issues/15533 Feel free to add comments.

If you download the Net Installer from the store you should currently get: pfSense-plus-installer-24.02-BETA2-aarch64-20240312-0600 That will install 24.03-release.

Yes I would probably just reinstall 24.03 clean. However you may be able to upgrade from there by setting the ranch back to 22.05 and then force reinstalling the key packages: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

@provels You didn’t get sent through the store?

@stephenw10 thank you, helped me today on one of the customers 2100 box.

Just renumber the LAN for the install to any unused subnet. Or even just unassign the LAN. You only need the WAN interface to access the pkg servers.

@stephenw10 perfect, thank you :)