Date: Mon, 30 Apr 2018 19:24:30 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 227879] "Failed to load '/boot/loader.efi'" boot failure on RaspberryPi 3 Message-ID: <bug-227879-7@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227879 Bug ID: 227879 Summary: "Failed to load '/boot/loader.efi'" boot failure on RaspberryPi 3 Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: gjb@FreeBSD.org Somewhere seemingly recently, RPI3 images fail to boot due to failing to load /boot/loader.efi. I have so far been unsuccessful bisecting which change(s) introduced the problem, but it can be observed with the most recent RPI3 images on the download mirrors: https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180426-r333017.img.xz The output observed follows. >> FreeBSD EFI boot block Loader path: /boot/loader.efi Initializing modules: ZFS UFS Load Path: /\efi\boot\bootaa64.efi Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x81f,0x18fa8) Probing 3 block devices...... done ZFS found no pools UFS found no partitions Failed to load '/boot/loader.efi' panic: No bootable partitions found! ## Application terminated, r = 1 EFI LOAD FAILED: continuing... Device 0: unknown device Waiting for Ethernet connection... done. BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227879-7>