I would like to say how much I appreciate how responsive Netgate has been during this development cycle: you guys are killing it!

@cmcdonald FWIW, everything seems to be working fine from a technical perspective.

@bmeeks Awesome, thank you for that explanation! It makes sense for it to cycle the interface like that then, I wanted to make 100% sure this was supposed to happen :)

@Lurick glad we finally found the root cause

[image: 1709812393342-5c7dad2d-5eb1-4686-b46f-7c56e80f6a77-immagine.png] I've just upgrade (again). PfSense reboot on 24.03b.20240306.0600 Is set "temporary BE" on 24.03b.20240307.0536 but is fully ignored

I suspect the repo settings were the culprit for all issues. Update: the repo change also solved the repeated boot verification prompts after each reboot. All is well! :)

Repo is correct now: [image: 1709655567118-09a74d0a-4e0c-4d16-92b2-50e5b36c3619-image.png]

@Diffuser0502 Weird, yah I reinstalled the wireguard package and now no issues myself.

@stephenw10 Yup, I was able to update just fine to 24.03b latest! Wasn't sure if it would prevent it or not but looks like no so that's good. All registered as well from what I can tell.

@stephenw10 Confirmed, NOW it does. ;-)

@stephenw10 said in Deleted boot environment space not reclaiming after upgrade: The BE snaps are difference files against whatever BE it was taken from. They will take up more space if the previous BE is very different. A BE generated by upgrading between daily snapshots should be quite small for example. Hi Stephen, This was resolved on last FRI's build when the package cache was cleared. I forgot to reply to my own thread!

Just to end this thread, this issue has been resolved for almost two weeks now. Thanks.

@cmcdonald sent you the full log as PM.

@High_bounce yep same cam timeout error here. I tried the other boot environments and get the same message

@High_bounce There's almost nothing to go on here, but my crystal ball asks if you're hitting the same issue as https://forum.netgate.com/topic/186431/php-error-after-updating-24-03-20240229 For future reference, if you're asking for help with a specific error it can be very helpful to actually post the error.

@DefenderLLC is this made to check the repository? There was issues with downgrading and the repository would have to re linked again. The linker file?

@w0w Mine would never boot any BE again after. I had to start from scratch and or use my backup SSD. It really messed it up for me.

Excellent. OK that explains why it showed Unknown. Just need to find out why that line went AWOL!

I can confirm that this is now fixed.