USB disks dropping off-line
Que Twilight Zone theme. For your consideration: This started in December when I was running 11.2-STABLE. Starting in December, when I try to backup my laptop to a USB drive, it periodically dropped off-line (disconnected) and immediately reconnected. This was originally using rsync. It seemed fairly random and, eventually I got a successful backup. After I upgraded to 12.0, it was much worse and I could no longer get a clean rsync. I assumed that the drive was failing and swapped it for an identical one, re-partitioned, and used dd to copy each partition. The same thing happened, but I noticed that it seemed to happen when the system was a bit active. I then shutdown X and tried with nothing else running. It ran for a few minutes until I did a sync from a different login while the dd was running. Boom. Disk disconnected again. I finally got an almost complete backup of /usr. I had about 1-2 GB lest when it happened again. I suspect that some background operation (periodic sync?) triggered it again. Any suggestions? Here is my system info: Lenovo T520 now running FreeBSD 12.0-STABLE r342788 and GENERIC config except SCHED_4BSD. System is completely stable except for the USB disk dropping off-line. Disk is a 2TB WD My Passport. It is a USB 3.0 drive,but plugged intoa 2.0 port. (The T520 has no 3.0 capability. Has anyone seen anything like this? Any ideas? I am REALLY nervous running without a backup. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Boot from one drive and load FreeBSD from another
On Fri, Jan 11, 2019 at 3:09 PM Walter Parker wrote: > Hi, > > I'd like to boot FreeBSD 12 on a system where the OS is installed to a ZFS > pool that can't be booted by the OS. > > This is a pre-UEFI machine. It has a pair of SAS drives and 3 PCIe slots. > What I'd like to do is put the boot loader on the SAS drive and then have > FreeBSD load from a ZFS mirror created using 2 nvme SSD drives on PCIe to > M.2 adapter cards. The BIOS is old enough that it will not boot from a PCIe > card. > > If I create a FreeBSD-boot partition on the SAS drive and a FreeBSD-zfs > partition on the ZFS mirror, will the boot partition loader automatically > find the ZFS pool? If not, is there anything special I can do to force a > boot? > So on older BIOS machines, there's a two stage boot process. The first stage loads gptboot off a dedicated partition (which is type FreeBSD-boot, iirc). This stage then finds the 'root' filesystem, and loads /boot/loader from that. Newer /boot/loader should have the right fallback logic to fall back to a ZFS pool properly. However, there's a catch that will trip you up: the devices with the zpool have to be presented as BIOS devices. It sounds like in your case they are not. This means you'll have to do the next best thing: You'll need a small FreeBSD UFS partition and need to pivot to the ZFS root. I've not done this, so it may be a bit of a pita, but it looks to be documented in reboot(8) and init(8). Second, if I want to do this on a second machine that does have UEFI, can I > do the same thing? This time, I think would I would do is put a UEFI boot > partition on the SAS drive and have it find the FreeBSD-zfs partition on > the ZFS mirror. > Yes. You could do that. If the RAID controller the drives are on has UEFI support, then it will be automatic. Otherwise, you'll need to fall back to the method described above. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Fri, Jan 11, 2019 at 03:47:45PM -0700, Warner Losh wrote: > On Fri, Jan 11, 2019 at 3:22 PM Gary Palmer wrote: > > > On Fri, Jan 11, 2019 at 01:18:35PM -0600, Kyle Evans wrote: > > > On Fri, Jan 11, 2019 at 1:15 PM Jonathan Chen wrote: > > > > > > > > On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote: > > > > [...] > > > > > The UEFI man page has a good explanation of which files are involved > > in booting: > > > > > > > https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports > > > > > > > > > > I mounted the ESP and copied /boot/boot1.efi to > > /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much > > smaller than what I had before (according to the timestamp from November), > > but using that, booting seems to be restored. > > > > > > > > > > # grep efi /etc/fstab > > > > > /dev/ada0p2 /boot/efi msdos rw,noauto 0 > >0 > > > > > # mount /boot/efi > > > > > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI > > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > > > > > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 > > /boot/efi/EFI/BOOT/BOOTX64.EFI* > > > > > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 > > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* > > > > > > > > While the uefi(8) man page suggests that boot1.efi should be used, > > > > loader.efi can also substituted. I believe the release images use > > > > loader.efi instead of boot1.efi, as it's slightly more efficient. > > > > > > > > > > Indeed, boot1.efi is a hack that's going to get kicked out of the tree > > > in due time. > > > > Can I request a clarification in the man page? At least in 11.2 the > > uefi(8) man page state > > > > -- QUOTE -- > >2. boot1.efi reads boot configuration from /boot.config or > > /boot/config. Unlike other first-stage boot loaders, > > boot1.efi passes the configuration to the next stage boot > > loader and does not itself act on the contents of the file. > > -- QUOTE -- > > > > It's not 100% clear, although implied by the fact that the next step > > looks for freebsd-ufs or freebsd-zfs partitions, that the boot.config is > > loaded from the ESP (at least I'm guessing that's where it's loaded > > from). Could the location of where boot.config is loaded from be > > clarified please? > > > > In 11.2, boot1.efi was used to load the next stage of the boot process > (which was /boot/loader.efi off either a UFS or ZFS filesystem based on a > number of heuristics). The boot.config was loaded from the same filesystem > loader.efi was loaded from, and not the ESP. Hi Warner, OK, how does boot1.efi know where to look for boot.config? Are steps 2 and 3 reversed in the man page? Thanks, Gary ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Fri, Jan 11, 2019 at 3:22 PM Gary Palmer wrote: > On Fri, Jan 11, 2019 at 01:18:35PM -0600, Kyle Evans wrote: > > On Fri, Jan 11, 2019 at 1:15 PM Jonathan Chen wrote: > > > > > > On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote: > > > [...] > > > > The UEFI man page has a good explanation of which files are involved > in booting: > > > > > https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports > > > > > > > > I mounted the ESP and copied /boot/boot1.efi to > /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much > smaller than what I had before (according to the timestamp from November), > but using that, booting seems to be restored. > > > > > > > > # grep efi /etc/fstab > > > > /dev/ada0p2 /boot/efi msdos rw,noauto 0 >0 > > > > # mount /boot/efi > > > > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > > > > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 > /boot/efi/EFI/BOOT/BOOTX64.EFI* > > > > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* > > > > > > While the uefi(8) man page suggests that boot1.efi should be used, > > > loader.efi can also substituted. I believe the release images use > > > loader.efi instead of boot1.efi, as it's slightly more efficient. > > > > > > > Indeed, boot1.efi is a hack that's going to get kicked out of the tree > > in due time. > > Can I request a clarification in the man page? At least in 11.2 the > uefi(8) man page state > > -- QUOTE -- >2. boot1.efi reads boot configuration from /boot.config or > /boot/config. Unlike other first-stage boot loaders, > boot1.efi passes the configuration to the next stage boot > loader and does not itself act on the contents of the file. > -- QUOTE -- > > It's not 100% clear, although implied by the fact that the next step > looks for freebsd-ufs or freebsd-zfs partitions, that the boot.config is > loaded from the ESP (at least I'm guessing that's where it's loaded > from). Could the location of where boot.config is loaded from be > clarified please? > In 11.2, boot1.efi was used to load the next stage of the boot process (which was /boot/loader.efi off either a UFS or ZFS filesystem based on a number of heuristics). The boot.config was loaded from the same filesystem loader.efi was loaded from, and not the ESP. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Fri, Jan 11, 2019 at 01:18:35PM -0600, Kyle Evans wrote: > On Fri, Jan 11, 2019 at 1:15 PM Jonathan Chen wrote: > > > > On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote: > > [...] > > > The UEFI man page has a good explanation of which files are involved in > > > booting: > > > https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports > > > > > > I mounted the ESP and copied /boot/boot1.efi to > > > /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much > > > smaller than what I had before (according to the timestamp from > > > November), but using that, booting seems to be restored. > > > > > > # grep efi /etc/fstab > > > /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 > > > # mount /boot/efi > > > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > > > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 > > > /boot/efi/EFI/BOOT/BOOTX64.EFI* > > > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 > > > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* > > > > While the uefi(8) man page suggests that boot1.efi should be used, > > loader.efi can also substituted. I believe the release images use > > loader.efi instead of boot1.efi, as it's slightly more efficient. > > > > Indeed, boot1.efi is a hack that's going to get kicked out of the tree > in due time. Can I request a clarification in the man page? At least in 11.2 the uefi(8) man page state -- QUOTE -- 2. boot1.efi reads boot configuration from /boot.config or /boot/config. Unlike other first-stage boot loaders, boot1.efi passes the configuration to the next stage boot loader and does not itself act on the contents of the file. -- QUOTE -- It's not 100% clear, although implied by the fact that the next step looks for freebsd-ufs or freebsd-zfs partitions, that the boot.config is loaded from the ESP (at least I'm guessing that's where it's loaded from). Could the location of where boot.config is loaded from be clarified please? Thanks, Gary ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Boot from one drive and load FreeBSD from another
Hi, I'd like to boot FreeBSD 12 on a system where the OS is installed to a ZFS pool that can't be booted by the OS. This is a pre-UEFI machine. It has a pair of SAS drives and 3 PCIe slots. What I'd like to do is put the boot loader on the SAS drive and then have FreeBSD load from a ZFS mirror created using 2 nvme SSD drives on PCIe to M.2 adapter cards. The BIOS is old enough that it will not boot from a PCIe card. If I create a FreeBSD-boot partition on the SAS drive and a FreeBSD-zfs partition on the ZFS mirror, will the boot partition loader automatically find the ZFS pool? If not, is there anything special I can do to force a boot? Second, if I want to do this on a second machine that does have UEFI, can I do the same thing? This time, I think would I would do is put a UEFI boot partition on the SAS drive and have it find the FreeBSD-zfs partition on the ZFS mirror. Thank you, Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Fri, Jan 11, 2019 at 12:19 PM Warner Losh wrote: > > > On Fri, Jan 11, 2019 at 12:17 PM Jonathan Chen wrote: > >> On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote: >> [...] >> > The UEFI man page has a good explanation of which files are involved in >> booting: >> > >> https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports >> > >> > I mounted the ESP and copied /boot/boot1.efi to >> /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much >> smaller than what I had before (according to the timestamp from November), >> but using that, booting seems to be restored. >> > >> > # grep efi /etc/fstab >> > /dev/ada0p2 /boot/efi msdos rw,noauto 0 >> 0 >> > # mount /boot/efi >> > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI >> /boot/efi/EFI/BOOT/bak/BOOTX64.EFI >> > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 >> /boot/efi/EFI/BOOT/BOOTX64.EFI* >> > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 >> /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* >> >> While the uefi(8) man page suggests that boot1.efi should be used, >> loader.efi can also substituted. I believe the release images use >> loader.efi instead of boot1.efi, as it's slightly more efficient. >> > > We should change that... boot1.efi has transitioned to 'legacy > applications only' and we should recommend loader.efi only. > I hit send too soon, -current already has removed boot1.efi... Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Fri, Jan 11, 2019 at 12:17 PM Jonathan Chen wrote: > On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote: > [...] > > The UEFI man page has a good explanation of which files are involved in > booting: > > > https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports > > > > I mounted the ESP and copied /boot/boot1.efi to > /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much > smaller than what I had before (according to the timestamp from November), > but using that, booting seems to be restored. > > > > # grep efi /etc/fstab > > /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 > > # mount /boot/efi > > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 > /boot/efi/EFI/BOOT/BOOTX64.EFI* > > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* > > While the uefi(8) man page suggests that boot1.efi should be used, > loader.efi can also substituted. I believe the release images use > loader.efi instead of boot1.efi, as it's slightly more efficient. > We should change that... boot1.efi has transitioned to 'legacy applications only' and we should recommend loader.efi only. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Fri, Jan 11, 2019 at 1:15 PM Jonathan Chen wrote: > > On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote: > [...] > > The UEFI man page has a good explanation of which files are involved in > > booting: > > https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports > > > > I mounted the ESP and copied /boot/boot1.efi to > > /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much > > smaller than what I had before (according to the timestamp from November), > > but using that, booting seems to be restored. > > > > # grep efi /etc/fstab > > /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 > > # mount /boot/efi > > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 > > /boot/efi/EFI/BOOT/BOOTX64.EFI* > > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 > > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* > > While the uefi(8) man page suggests that boot1.efi should be used, > loader.efi can also substituted. I believe the release images use > loader.efi instead of boot1.efi, as it's slightly more efficient. > Indeed, boot1.efi is a hack that's going to get kicked out of the tree in due time. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Sat, 12 Jan 2019 at 07:55, Stefan Bethke wrote: [...] > The UEFI man page has a good explanation of which files are involved in > booting: > https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports > > I mounted the ESP and copied /boot/boot1.efi to > /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much > smaller than what I had before (according to the timestamp from November), > but using that, booting seems to be restored. > > # grep efi /etc/fstab > /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 > # mount /boot/efi > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 /boot/efi/EFI/BOOT/BOOTX64.EFI* > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* While the uefi(8) man page suggests that boot1.efi should be used, loader.efi can also substituted. I believe the release images use loader.efi instead of boot1.efi, as it's slightly more efficient. Cheers. -- Jonathan Chen ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
> Am 11.01.2019 um 19:35 schrieb Stefan Bethke : > > > >> Am 11.01.2019 um 15:04 schrieb Kyle Evans : >> >> On Fri, Jan 11, 2019 at 5:05 AM Stefan Bethke wrote: >>> >>> The loader stumbles over this error and then drops to the prompt: >>> efi-autoresizecons not found >>> >>> module_path is then not set, and loader can’t load the kernel. Typing in >>> everything by hand will boot the system OK. >>> >>> I just did a regular make installworld installkernel (previous install was >>> from mid-december). Do I need to update the boot blocks or the EFI >>> partition? >>> >> >> Hi, >> >> Interesting; this is generally an indicator that your loader >> (/boot/loader.efi in 12.0 EFI-land) is out-of-date with respect to >> scripts. For that I'd go ahead and double-check that /boot/loader.efi >> was actually updated *and* update the contents of the ESP -- that >> particular change was paired with another one that stopped doing any >> resizing in boot1. > > I thought as much. Is there a succinct step-by-step to install/update > everything involved in the UEFI boot process? The Handbook appears to have > very little on UEFI booting… The UEFI man page has a good explanation of which files are involved in booting: https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports I mounted the ESP and copied /boot/boot1.efi to /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much smaller than what I had before (according to the timestamp from November), but using that, booting seems to be restored. # grep efi /etc/fstab /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 # mount /boot/efi # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 /boot/efi/EFI/BOOT/BOOTX64.EFI* -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* Thanks, Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
> Am 11.01.2019 um 15:04 schrieb Kyle Evans : > > On Fri, Jan 11, 2019 at 5:05 AM Stefan Bethke wrote: >> >> The loader stumbles over this error and then drops to the prompt: >> efi-autoresizecons not found >> >> module_path is then not set, and loader can’t load the kernel. Typing in >> everything by hand will boot the system OK. >> >> I just did a regular make installworld installkernel (previous install was >> from mid-december). Do I need to update the boot blocks or the EFI partition? >> > > Hi, > > Interesting; this is generally an indicator that your loader > (/boot/loader.efi in 12.0 EFI-land) is out-of-date with respect to > scripts. For that I'd go ahead and double-check that /boot/loader.efi > was actually updated *and* update the contents of the ESP -- that > particular change was paired with another one that stopped doing any > resizing in boot1. I thought as much. Is there a succinct step-by-step to install/update everything involved in the UEFI boot process? The Handbook appears to have very little on UEFI booting… Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trouble booting from EFI with 12-stable
On Fri, Jan 11, 2019 at 5:05 AM Stefan Bethke wrote: > > The loader stumbles over this error and then drops to the prompt: > efi-autoresizecons not found > > module_path is then not set, and loader can’t load the kernel. Typing in > everything by hand will boot the system OK. > > I just did a regular make installworld installkernel (previous install was > from mid-december). Do I need to update the boot blocks or the EFI partition? > Hi, Interesting; this is generally an indicator that your loader (/boot/loader.efi in 12.0 EFI-land) is out-of-date with respect to scripts. For that I'd go ahead and double-check that /boot/loader.efi was actually updated *and* update the contents of the ESP -- that particular change was paired with another one that stopped doing any resizing in boot1. Thanks, Kyle Evans ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Trouble booting from EFI with 12-stable
The loader stumbles over this error and then drops to the prompt: efi-autoresizecons not found module_path is then not set, and loader can’t load the kernel. Typing in everything by hand will boot the system OK. I just did a regular make installworld installkernel (previous install was from mid-december). Do I need to update the boot blocks or the EFI partition? Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
