<![CDATA[Boot Environment and old version]]>Boot Environments - Amazing. Already been helpful in debugging OpenVPN config.

However - I note that there is an Environment created of the old PF install - its created when updating. When I chose that and rebooted, the system did not come back, and there were a ton of errors in the console about config problems.

I expected it might be able to boot into the old image - and not get back, because it was an old image. But I didn't expect it to fail like this.

]]>https://forum.netgate.com/topic/172480/boot-environment-and-old-versionRSS for NodeSun, 19 Jul 2026 05:53:02 GMTFri, 27 May 2022 16:57:23 GMT60<![CDATA[Reply to Boot Environment and old version on Fri, 27 May 2022 21:34:55 GMT]]>@stephenw10
If there is a way to make it actually boot and run - that would be better!

]]>https://forum.netgate.com/post/1044190https://forum.netgate.com/post/1044190Fri, 27 May 2022 21:34:55 GMT<![CDATA[Reply to Boot Environment and old version on Fri, 27 May 2022 21:14:22 GMT]]>I agree. In 22.05 there will be an option to not create a BE at upgrade.

]]>https://forum.netgate.com/post/1044189https://forum.netgate.com/post/1044189Fri, 27 May 2022 21:14:22 GMT<![CDATA[Reply to Boot Environment and old version on Fri, 27 May 2022 20:58:20 GMT]]>@stephenw10
The Environment was the 22.01 release version. If restarting into it will break the system, better to not create it at all, IMHO.

]]>https://forum.netgate.com/post/1044186https://forum.netgate.com/post/1044186Fri, 27 May 2022 20:58:20 GMT<![CDATA[Reply to Boot Environment and old version on Fri, 27 May 2022 20:11:20 GMT]]>Like a 22.01 snap?

Changes in the filesystem layout can make going backwards a problem like that.

Going forward you should be OK as we don't expect to see layout changes between, for example, 22.05 and 22.09.

Steve

]]>https://forum.netgate.com/post/1044175https://forum.netgate.com/post/1044175Fri, 27 May 2022 20:11:20 GMT