>Number: 164950
>Category: misc
>Synopsis: new bsd installer, pc-style partitions: no way to set
>'bootable' ('active') flag
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Feb 10 11:40:07 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Alexander Kirillov
>Release: 9.0
>Organization:
private person
>Environment:
After-install boot problem, so no 'uname -a' available.
>Description:
New installer allows create more than one slices, but not allows to set
'active' or 'bootable' flag to any slice (see old sysinstall -> configure ->
fdisk -> "(S)et bootable" option).
In case of single slice, probably, this bit is not needed. But multiple slices
sometimes is also usable.
In case of multiple slices, if no slice with 'bootable' bit, "standard" mbr
boot code will not be able to boot the system ("/boot/kernel/kernel not
found"). "Boot manager" mbr code, i thing, will be stopped at the same point
with message like "Press F1 to boot FreeBSD\nPress F2 to boot FreeBSD" (not
good for server systems).
Please add ability to set this bit in new bsd installer.
>How-To-Repeat:
In process of standard installation:
-- created 2 slices in master boot record of FreeBSD (type 165),
-- created bsd partitions: /, swap, /var, /tmp and /usr in 1st slice;
/etc/nfsshare in 2nd slice with "standard" mbr boot code;
-- proceed installation process;
-- reboot.
After reboot got the message "/boot/kernel/kernel not found" and can't go into
installed system.
>Fix:
Run FreeBSD in LiveCD mode, run sysinstall and set "active partition" bit on
the 1st slice.
>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
