Pull in some recent FreeBSD fixes for ISO boot issues on legacy systems
M5A78L-M LX PLUS
16 GB DDR3 (ECC)
5 x 2TB SATA internal drives in raidz2 pool
1 x 4TB external USB drive
16GB USB system drive
Tried a GUI upgrade from 11.1-U5 to 11.2-BETA2 and ended up with an unbootable system. Tried using the ISO and boot loader on installer seems to get stuck on a white screen with the following text:
BTX Version is 1.02
Consoles: internal video/kernel
I’ve tried multiple boot devices, and multiple install devices (verified SHA256 on download) and I’m always stuck on the same screen. I’m not sure what to do next.
#3 Updated by Dru Lavigne about 2 years ago
- Private changed from No to Yes
- Reason for Blocked set to Need additional information from Author
Is the BIOS updated to its latest version? If it is, or if updating does not resolve the issue, please reboot into your previous boot environment, create a debug (System -> Advanced -> Save debug) and attach it to this ticket.
#6 Updated by Alexander Motin about 2 years ago
- Status changed from Unscreened to Screened
I do't remember I saw exactly the same screenshot before. It must be something new. As I understand you booted in legacy BIOS mode, right? Do you have exactly the same behavior when booting installer and installed (updated via Web) system? Have you tried UEFI on this system?
#7 Updated by Tony Scicchitano about 2 years ago
This result is from the 11.2-BETA2 ISO installer itself. I didn’t record it but I believe the same screen came up after upgrading via the web/GUI (11.1 installed using legacy BIOS mode).
Is there any value in trying UEFI install of 11.1-U5 and providing a debug?
#10 Updated by Ryan Moeller about 2 years ago
- Status changed from Screened to In Progress
- Severity changed from New to Low Medium
- Needs QA changed from No to Yes
- Needs Doc changed from No to Yes
- Needs Merging changed from No to Yes
I'm able to reproduce this on one of my test systems (and indeed it is annoying me, too). So far I've traced the hang to the INT 13h probe and am looking into why that is happening.
As a workaround you should be able to boot the installer by unplugging the 4TB external USB drive until the kernel starts booting.
#16 Updated by Ryan Moeller about 2 years ago
A regression was introduced in isoboot and gptboot which caused the incorrect argument format to be passed to loader, leading to memory corruption in the early boot process.
The regression was fixed upstream and I have cherry-picked the commit into FreeNAS.
This ticket describes the behavior exhibited by at least some versions of AMI BIOS for AMD processors. The system hangs indefinitely early in the boot process.
The fix should be tested by writing the ISO to a USB stick and booting in an affected system.
The expected behavior is for the system to boot normally without hanging early in the boot process.
The related issue describes booting with legacy BIOS and multiple USB drives. Rather than hanging as described in this ticket, these systems fail to detect the boot drive and drop to a loader prompt.
The fix should be tested by writing the ISO to a USB stick and booting in an affected system while another USB stick is also attached.
The expected behavior is for the system to boot normally without dropping to a loader prompt.
#18 Updated by Ryan Moeller about 2 years ago
Tony Scicchitano wrote:
With respect to my original screenshot, I just wanted to point out that it’s not a prompt on the screen. No text input is possible.
Happy to test a nightly ISO if/when available.
Thanks, I'll clarify that part of my previous note. I am experiencing the same behavior on my M5A88-V EVO board with an FX-8320, and this has fixed the problem in that system, so I am optimistic that it will help in your case, too. This fix should make it into the next nightly that gets built.