https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227808
--- Comment #11 from vmil...@verisign.com --- In an attempt to boot HP DL360 G9 into bootable media, which has proven problematic beyond FreeBSD 10.3, tests were performed on a total of 5 ISO files (from the most recent snapshots) in UEFI and legacy BIOS boot modes to ascertain the exhibited behavior. For the amd64 bootonly ISOs, the expected behavior is media suitable to boot and install FreeBSD of that version. All ISOs, with the exception of the 11.2 amd64 mfs, are project released ISOs. The 11.2 BETA2 amd64 ISO is custom built with a manually generated root.part from /rescue specified as MFS_IMAGE to be injected into the kernel. Described here are the behaviors exhibited in each boot mode. FreeBSD-11.2-PRERELEASE-amd64-bootonly (test1) * UEFI: mountroot error 19 (screenshot: test1_FreeBSD-11.2-PRERELEASE-bootonly_fail) * BIOS: mountroot error 19 (screenshot: test1_bios_FreeBSD-11.2-PRERELEASE-bootonly_fail) FreeBSD-11.2-PRERELEASE-i386-bootonly (test3) * UEFI: Could not boot image error via iPXE (screenshot: test3_FreeBSD-11.2-PRERELASE_i386-fail) * BIOS: Too many address bits (screenshot: test3_bios_FreeBSD-11.2-PRERELASE_i386-fail) FreeBSD-12-CURRENT-amd64-bootonly (test2) * UEFI: mountroot error 19 (screenshot: test2_FreeBSD-12-CURRENT-bootonly_fail) * BIOS: mountroot error 19 (screenshot: test2_bios_FreeBSD-12-CURRENT-bootonly_fail) FreeBSD-12-CURRENT-i386-bootonly (test4) * UEFI: Could not boot image error via iPXE (screenshot: test4_FreeBSD-12-CURRENT-i386-fail) * BIOS: Too many address bits (screenshot: test4_bios_FreeBSD-12-CURRENT-i386-fail) FreeBSD-11.2-BETA2-amd64-bootonly-mfs (test0) * UEFI: Media panics loading the kernel and root fs citing non-existent init (screenshot: test0_FreeBSD-11.2-md_root-fail) * BIOS: Media panics loading the kernel and root fs citing non-existent init (screenshot: test0_bios_FreeBSD-11.2-md_root-fail) This is custom built media including a MFS_IMAGE generated from /rescue. It is suspected that the error here is a result of an incomplete root.part rather than faulty ISO image. This problem is suspected to have existed with FreeBSD 10.3 also, which can be worked around by building an MFS-enabled ISO. The process that created the 10.3 image differs from that used to create the same for 11.2 suggesting discrepancies in the build of MFS-enabled ISOs. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
