This is fantastic, especially for me that manages hosts remotely and sometimes an update will cause it to hang during boot and then I need to either guide someone over the phone or drive out to a site and fix it manually. This will fix all that. Bravo Netgate, bravo!
First, love the background music to this. Secondly this is my most requested feature so thank you. Third, when boot verification fails and now we are back in the GUI, do we get a reason for the boot failure?
Hello! Thank you :) As long as it boots completely, it will validate the BE and rebooting after that would come back into the same BE. If you get stuck in interface mismatch, the watchdog would kick a reboot.
When doing system upgrade (when this feature will be released) - will pfSense create Boot environment automatically? Or user will need to manually create it prior to upgrade?
We now always create a boot environment and never upgrade the currently running boot environment (there is no opt-out). This approach provides more guarantees that if/when we do reboot into the upgraded boot environment that there is a high probability of the upgrade being successful and the system booting correctly. Barring that because we never touch the original boot environment, you can always rollback. If the upgrade fails we will automatically delete the cloned boot environment and the system remains in a functional state.
What about if sometimes on boot it doesn't detect your SFP interface card. So you have to reboot after rebooting to get the system to see the interface and boot properly?
Hello! A notice is posted upon rebooting into the working BE saying that [ ] BE failed boot verification and the system rebooted into [ ]. Failures are classified as a timeout occurred or software crashed. Any more detail would require inspection of the boot log. If it was a PHP error, you can see a crash report in the UI.
Super impressive. Well done, Christian. Netgate is so lucky to have you! We look forward to starting to use this new feature.
This is fantastic, especially for me that manages hosts remotely and sometimes an update will cause it to hang during boot and then I need to either guide someone over the phone or drive out to a site and fix it manually. This will fix all that. Bravo Netgate, bravo!
Thank you! :)
First, love the background music to this.
Secondly this is my most requested feature so thank you.
Third, when boot verification fails and now we are back in the GUI, do we get a reason for the boot failure?
Hello! Thank you :)
As long as it boots completely, it will validate the BE and rebooting after that would come back into the same BE. If you get stuck in interface mismatch, the watchdog would kick a reboot.
When doing system upgrade (when this feature will be released) - will pfSense create Boot environment automatically? Or user will need to manually create it prior to upgrade?
We now always create a boot environment and never upgrade the currently running boot environment (there is no opt-out). This approach provides more guarantees that if/when we do reboot into the upgraded boot environment that there is a high probability of the upgrade being successful and the system booting correctly. Barring that because we never touch the original boot environment, you can always rollback.
If the upgrade fails we will automatically delete the cloned boot environment and the system remains in a functional state.
Very nice 👍
Thank you! Cheers!
That is huge improvement.. good job 👏
Glad you think so!
Good day Christian. Will this feature trickle down to the CE edition?
Hello! Currently, we don't have plans to do so.
Nope, this is a plus only feature.
Very very Nice update...👍
Very impressive.
What about if sometimes on boot it doesn't detect your SFP interface card. So you have to reboot after rebooting to get the system to see the interface and boot properly?
Hello! A notice is posted upon rebooting into the working BE saying that [ ] BE failed boot verification and the system rebooted into [ ]. Failures are classified as a timeout occurred or software crashed. Any more detail would require inspection of the boot log. If it was a PHP error, you can see a crash report in the UI.
This is brilliant
I have a 2100 and it's not running ZFS. Will it "upgrade" my file system or is there more to it?
A reinstall is required to move from UFS to ZFS