Post B6KHDggrE67bknJHU0 by gumnos@bsd.cafe
 (DIR) More posts by gumnos@bsd.cafe
 (DIR) Post #B6JvtnHEvfDNLy04ZM by mwl@io.mwl.io
       0 likes, 0 repeats
       
       One of the few #sysadmin things that worries me any more is updating boot code after a zpool upgrade. #FreeBSD I'm sure it'll be fine, but if I disappear forever you know what happened.
       
 (DIR) Post #B6Jw2P9vy4fF9wgmJs by seanwbruno@infosec.exchange
       0 likes, 0 repeats
       
       @mwl it has never caused me drama, but there is a bit of “clench” when I issue that reboot to test.
       
 (DIR) Post #B6Jw7UGCQhqMQb2jJo by jeanmimi@mamot.fr
       0 likes, 0 repeats
       
       @mwl if you bootstrap, you will fly
       
 (DIR) Post #B6JwQgUBCS6TqYjhK4 by peteorrall@bsd.cafe
       0 likes, 0 repeats
       
       @mwl Good luck!
       
 (DIR) Post #B6Jx1ykmFB87DYHbBA by mwl@io.mwl.io
       0 likes, 0 repeats
       
       dammit
       
 (DIR) Post #B6JxNogKN45sLqcAE4 by raven@fedi.raventhemaker.com
       0 likes, 0 repeats
       
       @mwl breathe...
       
 (DIR) Post #B6JydMiMDiXyCSXfuK by djfiander@code4lib.social
       0 likes, 0 repeats
       
       @mwl I always forget that, then freak out when the next boot fails
       
 (DIR) Post #B6JzOTiM0p9RWK0PwG by djb@social.shirow.net
       0 likes, 0 repeats
       
       @mwl I should have checked the errata. The 5.0 had a problem with iLO devices and wouldn’t boot. So yes, it’s the only time I’ve borked a FreeBSD upgrade
       
 (DIR) Post #B6KHDggrE67bknJHU0 by gumnos@bsd.cafe
       0 likes, 0 repeats
       
       @mwl At least it's recoverable if/when you screw it up.  Annoying to recover.  But recoverable.#AskMeHowIKnow  😖
       
 (DIR) Post #B6KIff94fD2h1bPZsu by mwl@io.mwl.io
       0 likes, 0 repeats
       
       Fried my boot loader trying to update it.#FreeBSD has decades of archives on boot loader updating, which means that searches are full of noise. "gpart bootcode" is not a thing today. Possibly complicated further because this was installed as 14.0 and upgraded to 15.0.Reboot and got "missing boot loader"Start over by hand:gpart add -t efi -s 100M nda0newfs_msdosfs -F 32 -c 1 /dev/nda0p1attach to /mntmkdir -p /mnt/EFI/BOOTcp /boot/gptboot.efi /mnt/EFI/BOOT/BOOTX64.efiReboot and again: "missing boot loader"Anyone know the current incantation?
       
 (DIR) Post #B6KKlisZtTKoFdiGjg by encthenet@flyovercountry.social
       0 likes, 0 repeats
       
       @mwlHmm, looks like loader.efi(8) doesn't contain much help.I think you have to set an efi var because FreeBSD puts its loader in a non-standard location.  I'll dry to dig up more info since I remember having to deal with this a few years ago.#FreeBSD
       
 (DIR) Post #B6KLGaA6M31UBxcm8m by csgordon@discuss.systems
       0 likes, 0 repeats
       
       @mwl maybe your machine needs a kick with efibootmgr?https://man.freebsd.org/cgi/man.cgi?query=efibootmgr&apropos=0&sektion=8&manpath=FreeBSD%2B15.0-RELEASE&format=htmlI mean, it *shouldn't* need you to run efibootmgr yourself if you're putting it in the standard location on an EFI partition, but I have had to do this a couple times on machines with flaky firmware
       
 (DIR) Post #B6KME8300r40N4hEeG by overeducatedredneck@bitbang.social
       0 likes, 0 repeats
       
       @mwl It's surprising that you'd have to create a new EFI partition.  If you were using EFI boot blocks previously, that FS should already be in place somewhere.  I'd be surprised at that getting stomped by an upgrade.To check if @encthenet is onto it being a firmware config problem, you can try pulling up the boot menu, it's usually F12 (IIRC).  If you can figure out what nda0 is according to the firmware, select that.  Otherwise, there might be clues in there to where your EFI partition is.
       
 (DIR) Post #B6KME8M8rgNNKReWUC by mwl@io.mwl.io
       0 likes, 0 repeats
       
       @overeducatedredneck @encthenet Recreating was probably a mistake, tbh. But I can remove and recreate it, once I know what goes there..
       
 (DIR) Post #B6KNAt1tUZmosbCICW by encthenet@flyovercountry.social
       0 likes, 0 repeats
       
       @putney @mwl Check out:https://wiki.freebsd.org/UEFIThat talks about using FAT16 instead of FAT32, and also using loader.efi.
       
 (DIR) Post #B6KNAtFMgUYtYNV3CK by mwl@io.mwl.io
       0 likes, 0 repeats
       
       @encthenet @putney ty!
       
 (DIR) Post #B6KNb6apgaHSTX2dlY by encthenet@flyovercountry.social
       0 likes, 0 repeats
       
       @mwl @putney Yeah, I'm annoyed that the old boot man page has gone away, and other manpages like loader.efi doesn't contain this info.  I thought I had some fixes in my tree, but can't find them.  I'll try to dig them up later.
       
 (DIR) Post #B6KPQ4Oxh2RIOxM3f6 by mwl@io.mwl.io
       0 likes, 0 repeats
       
       Deleting the old boot partition was a mistake.Ate lunch. Walked around the block. Went back and deleted the new boot partition I had made. Cracked open my book on FreeBSD storage. Made myself read it (eight years ago that dude knew things, but not so much today). Followed the instructions therein. Restored boot.No idea how it broke before, but I'm gonna go beat my head against a wall for a bit just to relax.
       
 (DIR) Post #B6KZ4juBhagmIGQaxs by agreeable_landfall@mastodon.social
       0 likes, 0 repeats
       
       @mwl Or at least hit the dojo, so the pain is contributing to growth.  ;)
       
 (DIR) Post #B6MikRFcjhn0VLKhKi by ewon_c@social.linux.pizza
       0 likes, 0 repeats
       
       @mwl Oh my, sounds painful. Good luck and Godspeed.