Well, this is new reddit / freebsd ---------------------------------------------------------------------- oradba · 2022-11-11 21:24 Just installed FreeBSD 13.1 on a Thinkpad W530. Took defaults for zfs partitioning. Usually it goes right on and boots to the menu, but today, it boots to something else. When I type in the default path, it goes directly to the menu and all is well. Whyever doesn't it go the the default in the first place (and how can I configure it to do so?)? 'gpart show ada0' shows: => 40 1953525088 ada0 GPT (932G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 16777216 2 freebsd-swap [bootme] (8.0G) 16779264 1936744448 3 freebsd-zfs (924G) 1953523712 1416 - free - (708K)` so I thought "gpart set -a active -i 1 ada0s1" would do it. gpart doesn't like the device name, though. I've even tried "zpool set bootfs=zroot/ROOT/default zroot". I feel like I'm repeating steps the installer took, but clearly something is amiss. Oh - I've used this thumb drive to successfully install the OS elsewhere without this problem. This leads me to wonder if there is something in the BIOS that I need to change. Has anyone seen this problem before? What is the fix? TIA - ---------------------------------------------------------------------- grahamperrin · 2022-11-11 22:10 [efibootmgr\(8\)](https://www.freebsd.org/cgi/man.cgi?query=efibootmgr &sektion=8&manpath=FreeBSD) ---------------------------------------------------------------------- David_W_ · 2022-11-12 05:43 > Usually it goes right on and boots to the menu, but today, it boots to something else. Hard to know exactly what that "something else" is without some more description of it. > so I thought "gpart set -a active -i 1 ada0s1" would do it. gpart doesn't like the device name, though. I'm **not** saying this is your fix, but in GPT-land that'd be called `ada0p1`, not `ada0s1`, so that *is* why `gpart` didn't like your device name. ---------------------------------------------------------------------- oradba · 2022-11-12 20:21 Thanks - at least I now know that's not the problem. root@vatp1:~ # gpart set -a active -i 1 ada0p1 gpart: arg0 'ada0p1': Invalid argument ---------------------------------------------------------------------- oradba · 2022-11-12 20:24 root@vatp1:~ # efibootmgr -v efibootmgr: efi variables not supported on this system. root? kldload efirt? hmm. in the BIOS, I have to have UEFI set or POSt won't find the drive. ---------------------------------------------------------------------- oradba · 2022-11-13 05:55 I had it set to both. It finds the drive. I haven't gotten too far, I guess I'll wipe it, reset the BIOS settings to default, and try again. ---------------------------------------------------------------------- oradba · 2022-11-13 22:36 SOLVED, sort of. I reset the BIOS to the defaults, made sure it looked at UEFI first, and it now boots to the menu. Love that TCP stack speed. Going to tune a Linux box to see how close I can come to it.