[Bug 194359] bsdinstall(8) should set active flag in GPT PMBR if not booting using EFI

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Oct 22 16:45:40 UTC 2014


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194359

--- Comment #22 from hans at beastielabs.net ---
(In reply to Allan Jude from comment #21)
> (In reply to hans from comment #20)
> > (In reply to Allan Jude from comment #19)
> > 
> > I just tried the modified boot-only iso on an Intel DP965LT. After an Auto
> > (ZFS) install the system now reboots without any problems. Auto (UFS) still
> > has the same issue as before ("No bootable device -- insert boot disk and
> > press any key"). which of course is as expected.
> > 
> 
> Thanks for taking the time to test this for me. So it does seem that this is
> solving the problem
> 

Definitely, but for ZFS only. A similar change could be done for UFS, or
something like in comment #16 could be implemented.

> > On my Asus NL4VM-DH installing UFS works, but I still get a message about 
> > being unable to read the backup GPT header. Rebooting a ZFS installation
> > fails (register dump followed by "BTX halted"), but that also happens when
> > installing 10-RC2 on ZFS, so I do not think this is relevant to the issue at
> > hand.
> 
> Is there anything special about your disk setup that might cause issues with
> the very last sector? Some motherboard RAID and other types of things store
> their metadata in the last sector, and can clash with GPT, although those
> are supposed to make the logical drive 1 sector smaller so that this doesn't
> happen.
> 

The disk was in use as single disk for ages in this same system. For now I
blame it on the BIOS.

> Is that NL4VM-DH using UEFI?

No, it is a board from 2006, it has a BIOS. I only included these results to
show that something that worked before, i.e. installing UFS without the "does
not boot" issue, still works with your change. The NL4VM-DH is too rare to
worry about much.

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


More information about the freebsd-bugs mailing list