Roman Bogorodskiy wrote: > Hi, > > I have a test box that's updated to -CURRENT usually once in a week or > two. This box boots using UEFI. After a regular update about two weeks > ago it started to panic on boot frequently (not UEFI related), but I > could not get a crash dump because my swap partition was too small. So I > moved data to the backup drive, repartitioned the main drive and boot > again. This went fine, so I decided to upgrade to fresh -CURRENT from > ~Jul 27th. Booting with the new kernel went fine, but after installworld > machine stopped booting, and on the screen I see: > > FreeBSD/amd64 EFI loader, ... > > .. > > BootOrder: .... > > And then it gets stuck and nothing happens. > > As I already have a fresh backup, I decided that it'd be easier to > just re-install and copy data back over (maybe I messed up with > repartitioning). So I've downloaded a fresh snapshot: > > FreeBSD-12.0-CURRENT-amd64-20180726-r336739-memstick.img > > And re-installed. In the installer I choose all the same settings that > were before: UEFI + GPT, default partition scheme it suggested (efi > followed by freebsd-ufs followed by freebsd-swap), just increased the > swap size. > > And the newly installed system won't boot just like a previous one: > > https://people.freebsd.org/~novel/misc/freebsd_efi_lookup.jpg > > Is there a way to recover this? Tried updating to get r336837 mentioned in another thread, and it still doesn't help. Current version is r336859. Partitioning schema looks this way: => 40 1953525088 ada0 GPT (932G) 40 409600 1 efi (200M) 409640 1803550720 2 freebsd-ufs (860G) 1803960360 148897792 3 freebsd-swap (71G) 1952858152 666976 - free - (326M) I can boot it when booting from memstick r336739 and setting vfs.root.mountfrom="ufs:ada0p2". Roman Bogorodskiy
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:17 UTC