Unable to update 15.0-RELEASE-p6

D

drhowarddrfine

Unlike Scottro's other thread, I am not using pkgbase.

I've happily upgraded through p6 but, as of yesterday, I noticed my upgrades to p7 and p8 did not go through even though the upgrades claim to be successful.
Code: 
BE                                Active Mountpoint Space Created
15.0-RELEASE-p5_2026-04-23_101031 -      -          584M  2026-04-23 10:10
15.0-RELEASE-p6_2026-05-11_192459 -      -          95.7M 2026-05-11 19:24
15.0-RELEASE-p6_2026-05-15_074730 -      -          95.6M 2026-05-15 07:47
15.0-RELEASE-p6_2026-05-15_195917 NR     /          7.20G 2026-05-15 19:59
I thought for sure that, at one time, this showed a p7 upgrade but I could be wrong.

Unfortunately, I'm packing and leaving on vacation in a couple of hours and will be gone for a week but perhaps someone has a solution for now or later.
 
BE snapshot with freebsd-update(8) is made before the patches are applied. So if you updated from p6 to p8 the snapshots will show p6.

drhowarddrfine said:
15.0-RELEASE-p6_2026-05-15_195917 NR / 7.20G 2026-05-15 19:59
Click to expand...
Your currently running BE (NR), I suspect you reverted at some point. The name of your currently active BE doesn't change, ever. Rename this back to default because it's just confusing you.

Code: 
             Display all boot environments.  The Active field indicates
             whether the boot environment is active now (N); active on reboot
             (R); is used on next boot once (T); or combination of (NRT).
 
I think I need different drugs. I just ran freebsd-update again and now i get p8 in freebsd-version. Haven't a clue what I was doing wrong but, as I said, I guess I need a drug update.
 
drhowarddrfine said:
I think I need different drugs. I just ran freebsd-update again and now i get p8 in freebsd-version. Haven't a clue what I was doing wrong but, as I said, I guess I need a drug update.
Click to expand...
Don't worry too much. If you think about it, the biggest mystery in software is how it is possible that millions of lines of code written by hundreds or thousands of different people add to a functioning system. Enjoy your vacation.
 
drhowarddrfine said:
Haven't a clue what I was doing wrong
Click to expand...
I suspect you installed the update previously, then reverted to the BE from before the update (which is why the 15.0-RELEASE-p6_2026-05-15_195917 BE is currently active). This effectively reverted the update.

When you use freebsd-update(8) and have it create a BE automatically, you do NOT need to switch BEs. Only revert the BE if you run into trouble after installing the update.

Just rename that currently active BE back to default (you appear to have removed it at some point; it doesn't show up in your bectl list).
 
You must log in or register to reply here.
Back
Top