[Bug 239052] [boot] BTX halt error after freebsd-update from 12.0-RELEASE-p4 to 12.0-RELEASE-p7
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Jul 8 18:30:33 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239052
Bug ID: 239052
Summary: [boot] BTX halt error after freebsd-update from
12.0-RELEASE-p4 to 12.0-RELEASE-p7
Product: Base System
Version: 12.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: m.rebele at web.de
Created attachment 205591
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205591&action=edit
BTX halted screenshot
After applying
freebsd-update fetch
and
freebsd-update install
and the initiated reboot, the Systems stops booting with
„BTX halted“ and a CPU-Register dump.
In the previous screen where BTX enumerates the drives, you can see the
following text:
„read 1 from 0 to 0xdd78f340, error: 0x1“
This messages comes twice.
The machine is a Dell PowerEdge R515 with a LSI-RAID Controller (mps). The
system is on a Hardware-RAID1 with UFS. The machine runs FreeBSD since several
years and FBSD12 is an upgraded Version of FBSD11. FBSD12 ran fine all the time
since its release.
The disks seems to be ok and error free. I’ve booted a 11.2 live disk, gpart
list|status|show shows no errors or unusual things on the disk layout. „gpart
recover“ says everything’s ok and nothing is to be done. I also can mount the
12.0 ufs partition in the live system and access the data there. fsck is also
ok and says there’s no error. Though i doubt there is a hardware error.
Booting the FreeBSD-12.0-RELEASE-amd64-disc1-ISO fails with the same error.
Booting the FreeBSD-12.0-RELEASE-amd64-disc1-IMG (for USB-Stick) is booting but
i have to modifiy the Boot-Settings to UEFI to make it boot (this is a known
issue since the release of 12.0). I’m booting the ISO-Images with idrac virtual
drives, the USB-Image is copied to an SD-Card and booted from there (but as
idrac-Emulated disk).
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list