Date: Fri, 6 Oct 2017 10:42:08 -0500 From: Karl Denninger <karl@denninger.net> To: freebsd-stable@freebsd.org Subject: Re: Installing amd64 FreeBSD 11.1 in dual-boot with Windows 7 on an MBR partitioned disk Message-ID: <22388e92-c83e-eacd-4151-e473033091d1@denninger.net> In-Reply-To: <CANt7McGqZG0mJFmuQgE4_rFu_0kmnyUCUCZyrrThKMjJtnyewA@mail.gmail.com> References: <CANt7McGqZG0mJFmuQgE4_rFu_0kmnyUCUCZyrrThKMjJtnyewA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On 10/6/2017 10:17, Rostislav Krasny wrote:
> Hi there,
>
> I try to install amd64 FreeBSD 11.1 in dual-boot with Windows 7 on an
> MBR partitioned disk and I can't make it bootable. My Windows 7 uses
> its standard MBR partitioning scheme (1. 100MB System Reserved
> Partition; 2 - 127GB disk C partition) and there is about 112GB of
> free unallocated disk space that I want to use to install FreeBSD on
> it. As an installation media I use the
> FreeBSD-11.1-RELEASE-amd64-mini-memstick.img flashed on a USB drive.
>
> During the installation, if I choose to use Guided Partitioning Tool
> and automatic partitioning of the free space, I get a pop-up message
> that says:
>
> ======
> The existing partition scheme on this disk
> (MBR) is not bootable on this platform. To
> install FreeBSD, it must be repartitioned.
> This will destroy all data on the disk.
> Are you sure you want to proceed?
> [Yes] [No]
> ======
>
> If instead of the Guided Partitioning Tool I choose to partition the
> disk manually I get a similar message as a warning and the
> installation process continues without an error, but the installed
> FreeBSD system is not bootable. Installing boot0 manually (boot0cfg
> -Bv /dev/ada0) doesn't fix it. The boot0 boot loader is able to boot
> Windows but it's unable to start the FreeBSD boot process. It only
> prints hash symbols when I press F3 (the FreeBSD slice/MBR partition
> number).
>
> I consider this as a critical bug. But maybe there is some workaround
> that allows me to install the FreeBSD 11.1 as a second OS without
> repartitioning the entire disk?
>
> My hardware is an Intel Core i7 4790 3.6GHz based machine with 16GB
> RAM. The ada0 disk is 238GB SanDisk SD8SBAT256G1122 (SSD).
>
You have to do the partitioning and then install FreeBSD's boot manager
by hand. It /does /work; I ran into the same thing with my Lenovo X220
and was able to manually install it, which works fine to dual-boot
between Windows and FreeBSD-11. I had to do it manually because the
installer detected that the X220 was UEFI capable and insisted on
GPT-partitioning the disk, which is incompatible with dual-boot and the
existing MBR-partitioned Windows installation.
You want the partition layout to look like this:
$ gpart show
=> 63 500118129 ada0 MBR (238G)
63 4208967 1 ntfs (2.0G)
4209030 307481727 2 ntfs (147G)
311690757 3 - free - (1.5K)
311690760 165675008 3 freebsd [active] (79G)
477365768 808957 - free - (395M)
478174725 21928725 4 ntfs (10G)
500103450 14742 - free - (7.2M)
=> 0 165675008 ada0s3 BSD (79G)
0 8388608 1 freebsd-ufs (4.0G)
8388608 136314880 2 freebsd-ufs (65G)
144703488 20971519 4 freebsd-swap (10G)
165675007 1 - free - (512B)
MBR has only four partitions; the "standard" Windows (7+) install uses
/three. /The "boot"/repair area, the main partition and, on most
machines, a "recovery" partition. That usually leaves partition 3 free
which is where I stuck FreeBSD. Note that you must then set up slices
on Partition 3 (e.g. root/usr/swap) as usual.
--
Karl Denninger
karl@denninger.net <mailto:karl@denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
[-- Attachment #2 --]
0 *H
010
`He 0 *H
00 H^Ōc!5
H0
*H
010 UUS10UFlorida10U Niceville10U
Cuda Systems LLC10UCuda Systems CA1!0UCuda Systems LLC 2017 CA0
170817164217Z
270815164217Z0{10 UUS10UFlorida10U
Cuda Systems LLC10UCuda Systems CA1%0#UCuda Systems LLC 2017 Int CA0"0
*H
0
h-5B>[;olӴ0~͎O9}9Ye*$g!ukvʶLzN`jL>MD'7U 45CB+kY`bd~b*c3Ny-78ju]9HeuέsӬDؽmgwER?&UURj'}9nWD i`XcbGz \gG=u%\Oi13ߝ4
K44pYQr]Ie/r0+eEޝݖ0C15Mݚ@JSZ(zȏ NTa(25DD5.l<g[[ZarQQ%Buȴ~~`IohRbʳڟu2MS8EdFUClCMaѳ !}ș+2k/bųE,n当ꖛ\(8WV8 d]b yXw ܊:I39
00U]^§Q\ӎ0U#0T039N0b010 UUS10UFlorida10U Niceville10U
Cuda Systems LLC10UCuda Systems CA1!0UCuda Systems LLC 2017 CA @Ui0U0 0U0
*H
:P U!>vJnio-#ן]WyujǑR̀Q
nƇ!GѦFg\yLxgw=OPycehf[}ܷ['4ڝ\[p 6\o.B&JF"ZC{;*o*mcCcLY߾`
t*S!(`]DHP5A~/NPp6=mhk밣'doA$86hm5ӚS@jެEgl
)0JG`%k35PaC?σ
׳HEt}!P㏏%*BxbQwaKG$6h¦Mve;[o-Iی&
I,Tcߎ#t wPA@l0P+KXBպT zGv;NcI3&JĬUPNa?/%W6G۟N000 k#Xd\=0
*H
0{10 UUS10UFlorida10U
Cuda Systems LLC10UCuda Systems CA1%0#UCuda Systems LLC 2017 Int CA0
170817212120Z
220816212120Z0W10 UUS10UFlorida10U
Cuda Systems LLC10Ukarl@denninger.net0"0
*H
0
T[I-ΆϏ dn;Å@שy.us~_ZG%<MYd\gvfnsa1'6Egyjs"C [{~_K Pn+<*pv#Q+H/7[-vqDV^U>f%GX)H.|l`M(Cr>е͇6#odc"YljҦln8@5SA0&ۖ"OGj?UDWZ5 dDB7k-)9Izs-JAv
J6L$Ն1SmY.Lqw*SH;EF'DĦH]MOgQQ|Mٙג2Z9y@y]}6ٽeY9Y2xˆ$T=eCǺǵbn֛{j|@LLt1[Dk5:$= ` M 00<+00.0,+0 http://ocsp.cudasystems.net:88880 U0 0 `HB0U0U%0++03 `HB
&$OpenSSL Generated Client Certificate0U%՞V=;bzQ0U#0]^§Q\ӎϡ010 UUS10UFlorida10U Niceville10U
Cuda Systems LLC10UCuda Systems CA1!0UCuda Systems LLC 2017 CA H^Ōc!5
H0U0karl@denninger.net0
*H
۠A0-j%--$%g2#ޡ1^>{K+uGEv1ş7Af&b&O;.;A5*U)ND2bF|\=]<sˋL!wrw٧>YMÄ3\mWR hSv!_zvl? 3_ xU%\^#O*Gk̍YI_&Fꊛ@&1n } ͬ:{hTP3B.;bU8:Z=^Gw8!k-@xE@i,+'Iᐚ:fhztX7/(hY` O.1}a`%RW^akǂpCAufgDix UTЩ/7}%=jnVZvcF<M=
2^GKH5魉
_O4ެByʈySkw=5@h.0z>
W1000{10 UUS10UFlorida10U
Cuda Systems LLC10UCuda Systems CA1%0#UCuda Systems LLC 2017 Int CA k#Xd\=0
`He E0 *H
1 *H
0 *H
1
171006154208Z0O *H
1B@T&¢_Bogq*SufO7P6\LgXK<X0l *H
1_0]0 `He*0 `He0
*H
0*H
0
*H
@0+0
*H
(0 +7100{10 UUS10UFlorida10U
Cuda Systems LLC10UCuda Systems CA1%0#UCuda Systems LLC 2017 Int CA k#Xd\=0*H
10{10 UUS10UFlorida10U
Cuda Systems LLC10UCuda Systems CA1%0#UCuda Systems LLC 2017 Int CA k#Xd\=0
*H
}[m8$8哊. Pibz6;ׄ{M5s(p@aW}ZÏR҉ʓWϭ^Tæ4迤̞r ?#q.9/B˱:BNcU12nP@jvɵ1 <e_ϿNn=#]7BU- +
>7j-պcd8FqHN^2WzVQ?[1c]h)=-r#} ?am3{h<HS:$&Ƒl$Ifp;s0g)[9E01}Ȋ`!фR<G<Xs ~vr ѱukIi.$!.V /!i7elD;4n,/!{C
[
=Z)Dtt(|6)F#Oپ$sġlC2WlS߾tOh1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22388e92-c83e-eacd-4151-e473033091d1>
