@aryanrai said in Unable to boot: But why it boot without any issue even in efi mode after booting from another pc It depends on a number of things, the EFI implementation on that other system is different in some key way.

But does it show in the boot logs when booting the installer? Does it show an error against either drive or drive controller for example? Lets see the full boot log.

I had applied it about a week ago. Took me a while to work out that's also when the issues started. Once reverted, issues resolved. I'll add a note. Cheers

@stephenw10 hi, no I've been using the same (HPE MicroServer Gen 10 Plus) since 2020, I could not find my old activation token so I ordered a new one from your store today. I've sent my NDI to you via a a chat :)

Are you running Plus? Check System > Boot Environments. You probably have a bunch of old ZFS snaps you can remove to free space.

If it's in an unknown state I would also suggest reinstalling clean. But if it is able to reach the package servers you can try force reinstalling all the pkgs: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstall Steve

@ddepaolis You can upgrade directly to the latest version if it is offered. You can set the update branch to Previous Stable: https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html Per the upgrade guide it is recommended to uninstall packages, upgrade, and then reinstall packages. Otherwise the upgrade will also try to upgrade packages during the upgrade. Either way they do get upgraded to the latest version. Package settings are saved by default, though a few like pfBlockerNG have a checkbox to remove package settings when uninstalling.

@stephenw10 Thanks. Have opened a ticket now including config. The new Netgate 2100 has arrived :-)

@NSchwarzenberger had the same issu. https://forum.netgate.com/post/1063243 fixed it.

@DominikHoffmann Changing to ZFS wipes/repartitions the drive during the reinstall.

@stephenw10 Issue resolved. I deleted the ntop.conf. Thank you.

@unsichtbarre said in Please wait while the update system initializes: pfSense-repoc-static: invalid signature This was the solution: pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade pkg-static bootstrap -f pfSense-upgrade -d -c Found here: https://forum.netgate.com/topic/181308/version-2-5-2-upgrade-2-6-0-or-2-7-0/11

@_Adrian_ [image: 1694155654112-2ee19a44-6892-4003-b4f6-9ee36dfd21dc-image.png] You don't need the last four. If you're forwarding, double check DNS server 2 and 3, as these look like a black hole to me. 3 and 4 : ask what they do with your data. If doubt : ditch them all.

Send me your NDI in chat and I'll check it. Steve

Could be. There was an IPv6 issue at the servers a few days ago. I thought it had been fixed before you posted here but maybe not. It's fixed now. Steve

Hi @Gertjan I checked but unfortunately nothing works I tried the commands "boot /boot/kernel " , "boot /boot/kernel/kernel", "/boot/kernel " I can't read any file to check what could be the right boot command I m stuck at this boot prompt [image: 1693906050321-capture-d-%C3%A9cran-du-2023-09-05-11-27-14.png]

Scrap this - the following command worked for me: pkg-static upgrade -fy pkg

@MushyMiddle Did you follow the recommended practice of removing all installed packages and backing up your configuration before executing an upgrade?

@stephenw10 Thanks a million - fixed it!

@wgstarks Your issue doesn't exist anymore : you've updated to the latest version 23.05.1, so now pfSense knows where to look for updates for this version. If you see this here : [image: 1693557487536-6019a4c6-efd1-493f-b49a-5232a77c341c-image.png] you know you're good. You should see the 3 options : 23.09 23.01 23.05.1