Bug 279829 - Unable to automatically boot after upgrading to 14.1-RELEASE
Summary: Unable to automatically boot after upgrading to 14.1-RELEASE
Status: Closed Not A Bug
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 14.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2024-06-18 10:45 UTC by Albert Valbuena
Modified: 2024-06-26 13:43 UTC (History)
3 users (show)

See Also:


Attachments
core-lua-68-error-booting-14.1-release (923.06 KB, image/png)
2024-06-18 10:45 UTC, Albert Valbuena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Albert Valbuena 2024-06-18 10:45:03 UTC
Created attachment 251535 [details]
core-lua-68-error-booting-14.1-release

Unable to automatically boot after upgrading to 14.1-RELEASE. There are two cases, one coming from 13.3-RELEASE and the other (mine) coming from 14.0-RELEASE-p6.

For reference this thread contains the error in the very first post, picture included (attached here as well). 

https://forums.freebsd.org/threads/problem-upgrading-from-13-3-release-to-14-1-release-lua-error-upon-booting-kernel.93737/

Both boxes booted after physically inputting 'boot' or 'autoboot', but they did not execute the whole boot process without manual intervention.
Comment 1 Kyle Evans freebsd_committer freebsd_triage 2024-06-18 14:54:23 UTC
(In reply to Albert Valbuena from comment #0)

You need to update loader.efi on your EFI System Partition, this was a thing added many versions ago.  There will probably be two copies of loader.efi, one in \EFI\FreeBSD and one in \EFI\Boot, and both should be kept up to date if they're both FreeBSD just in case.
Comment 2 Albert Valbuena 2024-06-19 14:03:22 UTC
(In reply to Kyle Evans from comment #1)

The device has become bricked after attempting an overdue BIOS upgrade (non related to FreeBSD). Since it does not equip a backup copy, it's now a paperweight. I can't test further with an EFI equipped system at this time.
Comment 3 Kyle Evans freebsd_committer freebsd_triage 2024-06-19 14:27:55 UTC
(In reply to Albert Valbuena from comment #2)

Oof, sorry to hear that. =( I'm going to NOT A BUG this, but feel free to comment back if you or anyone else discovers there's still an issue here.
Comment 4 Albert Valbuena 2024-06-26 13:43:50 UTC
(In reply to Kyle Evans from comment #3)

Thanks.

PS: Rebuilt the whole thing on a new box with modern EFI, first reusing the same exact drive without a hassle. Reinstalled just for the sake of starting fresh on a new box.