Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Nov 2020 20:01:49 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 251276] [boot] Legacy BIOS boot hangs indefinitely with post-12.0-RELEASE loader
Message-ID:  <bug-251276-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251276

            Bug ID: 251276
           Summary: [boot] Legacy BIOS boot hangs indefinitely with
                    post-12.0-RELEASE loader
           Product: Base System
           Version: 12.2-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: misc
          Assignee: bugs@FreeBSD.org
          Reporter: ncollins@xes-inc.com

Created attachment 219835
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D219835&action=
=3Dedit
screenshot of the step where booting hangs

With 12.1-RELEASE, 12.2-RELEASE, and 13.0-CURRENT's /boot/loader, my server
prints "BIOS drive X: is diskXX" lines, spins the cursor for a bit, and han=
gs
indefinitely. Removing all non-OS drives does not resolve the issue. I can
replace /boot/loader with the version from 12.0-RELEASE and boot fine, so t=
his
seems like a regression.

This is likely hardware-specific; the server is a Supermicro SuperStorage
6049P-E1CR36L with a mirrored zpool as the root. It was initially installed
with 12.0-RELEASE, freebsd-update'd to 12.1-RELEASE, where this issue first
occurred (was worked around via UEFI, see below), then freebsd-update'd to
12.2-RELEASE, which didn't resolve the issue. I then tested 13.0-CURRENT's
loader and reverted to 12.0-RELEASE's loader.

UEFI boot has other problems - it hangs at the "Consoles: EFI" line and will
only boot normally if two drives are removed (all drive bays are usually
populated). The behavior is the same with 12.0-RELEASE's /boot/loader.efi, =
so
while it's an issue, it's probably unrelated and not a regression from
12.0-RELEASE.

This is potentially related to bug #241118, but the fix in base r356003
released in 12.2-RELEASE/13.0-CURRENT has not resolved the problem.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251276-227>