On April 6, 2019 5:01:17 PM UTC, Leonid Bobrov <mazoc...@disroot.org> wrote: >Hi! > >Here's a small story: my boyfriend temporary has a laptop and he's not >allowed to prune Windows 8.1 from it, so he has to setup dualboot. Also >he wants OpenBSD part of the disk to be encrypted. And one more thing: >this laptop doesn't support EFI at all, otherwise dualboot would be >easy. He did everything according to FAQ both full disk encryption and >multibooting, but that didn't work, installboot refused to install at >/dev/sda4 with error "no OpenBSD partition found", he quickly fixed >that >issue, but then when he gave PBR, OpenBSD refused to boot, then he >tried >to give PBR of softraid0 and that lead to a new error after reboot: >"No active partition", that can't be helped, so he wiped everything >out, >now thanks to your FAQ he has to reinstall Windows 8.1 which is tedious >with his slow ISP. > >Conclusion: OpenBSD is not designed to be multibooted, so this section >of FAQ is obsolete. > >Index: index.html >=================================================================== >RCS file: /cvs/www/faq/index.html,v >retrieving revision 1.538 >diff -u -p -r1.538 index.html >--- index.html 26 Feb 2019 23:53:55 -0000 1.538 >+++ index.html 6 Apr 2019 16:36:14 -0000 >@@ -76,7 +76,6 @@ that are not covered in the FAQ. > <li><a href="faq4.html#Partitioning">Disk Partitioning</a> ><li><a href="faq4.html#SendDmesg" >Sending Your dmesg After the >Install</a> ><li><a href="faq4.html#site" >Customizing the Install >Process</a> >-<li><a href="faq4.html#Multibooting">Multibooting</a> > </ul> > > <h3><a href="faq10.html">System Management</a></h3> >Index: faq4.html >=================================================================== >RCS file: /cvs/www/faq/faq4.html,v >retrieving revision 1.527 >diff -u -p -r1.527 faq4.html >--- faq4.html 26 Feb 2019 23:53:55 -0000 1.527 >+++ faq4.html 6 Apr 2019 16:36:14 -0000 >@@ -36,7 +36,6 @@ FAQ - Installation Guide > <li><a href="#Partitioning">Disk Partitioning</a> > <li><a href="#SendDmesg" >Sending Your dmesg After the Install</a> > <li><a href="#site" >Customizing the Install Process</a> >- <li><a href="#Multibooting">Multibooting</a> > </ul> > <hr> > >@@ -517,96 +516,3 @@ Example usage: > write to this file). > At boot time, <code>rc.firsttime</code> is executed once then deleted. > </ul> >- >-<h2 id="Multibooting">Multibooting</h2> >- >-Multibooting is having several operating systems on one computer, with >some >-means of selecting which OS is to boot. >-You may want to familiarize yourself with the >-<a href="faq14.html#BootAmd64">OpenBSD boot process</a> before you >start. >-A brief introduction to <a >href="https://man.openbsd.org/fdisk";>fdisk(8)</a> >-is in the section on <a href="faq14.html#fdisk">using OpenBSD's >fdisk</a>. >- >-<p> >-If you are adding OpenBSD to an existing system, you will probably >need to >-create some free space before installing OpenBSD. >-In addition to your existing system's native tools, >-<a href="http://gparted.org/";>gparted</a> >-may be useful for deleting or resizing existing partitions. >-Preferably use one of the four primary MBR partitions for booting >OpenBSD. >-Extended partitions may not work. >- >-<h3>Boot Loaders</h3> >- >-On Macs, <a href="http://www.rodsbooks.com/refind/";>rEFInd</a> should >work out >-of the box. >- >-<p> >-You can set up dual booting with >-<a href="https://www.gnu.org/software/grub/";>GRUB 2</a> as follows. >-Assuming OpenBSD is installed on the fourth MBR partition (fdisk >partition 3) of >-the first hard disk <code>hd0</code>, append the following to >-<code>/etc/grub.d/40_custom</code>. >- >-<pre class="cmdbox"> >-menuentry "OpenBSD" { >- set root=(hd0,4) >- chainloader +1 >-} >-</pre> >- >-Then regenerate the GRUB 2 configuration file, ><code>/boot/grub/grub.cfg</code>. >-On Debian-based distros, you should run <code>update-grub</code>. >-Otherwise, do >- >-<pre class="cmdbox"> >-# <b>grub-mkconfig -o /boot/grub/grub.cfg</b> >-</pre> >- >-See the >-<a >href="https://www.gnu.org/software/grub/manual/grub.html#Invoking-grub_002dmkconfig";> >-GRUB 2 manual</a> or >-<a >href="https://manpages.debian.org/jessie/grub2-common/update-grub2.8";> >-update-grub2(8)</a> >-for more information. >- >-<h3>Windows</h3> >- >-The Boot Configuration Data (BCD) store allows multiple versions of >Windows >-to be booted through <code>bcdedit</code>. >-A good introduction can be found in >-<a >href="https://technet.microsoft.com/en-us/library/cc721886%28WS.10%29.aspx";> >-this article</a>. >-If you want a GUI alternative, you may want to try >-<a href="https://neosmart.net/EasyBCD/";>EasyBCD</a>. >- >-<p> >-You will need a copy of your OpenBSD install's >-<a href="faq14.html#BootAmd64">Partition Boot Record (PBR)</a>. >-You can copy it to a file using a process similar to: >-<pre class="cmdbox"> >-# <b>dd if=/dev/rsd0a of=openbsd.pbr bs=512 count=1</b> >-</pre> >-where <code>sd0a</code> is your boot device, and you will need to get >the >-file <code>openbsd.pbr</code> to your Windows system partition. >- >-<p> >-Once OpenBSD's PBR is copied to the Windows system partition, you need >a shell >-with administrative privileges to run the following commands: >- >-<pre class="cmdbox"> >-C:\Windows\system32> <b>bcdedit /create /d "OpenBSD/i386" /application >bootsector</b> >-The entry {0154a872-3d41-11de-bd67-a7060316bbb1} was successfully >created. >-C:\Windows\system32> <b>bcdedit /set >{0154a872-3d41-11de-bd67-a7060316bbb1} device boot</b> >-The operation completed successfully. >-C:\Windows\system32> <b>bcdedit /set >{0154a872-3d41-11de-bd67-a7060316bbb1} path \openbsd.pbr</b> >-The operation completed successfully. >-C:\Windows\system32> <b>bcdedit /set >{0154a872-3d41-11de-bd67-a7060316bbb1} device partition=c:</b> >-The operation completed successfully. >-C:\Windows\system32> <b>bcdedit /displayorder >{0154a872-3d41-11de-bd67-7060316bbb1} /addlast</b> >-The operation completed successfully. >-</pre> >- >-Note that OpenBSD expects the computer's real-time clock to be set to >-Coordinated Universal Time (UTC). >-See <a href="faq8.html#TimeZone">this section</a> for more info.
I run a dual-boot with Windows 10 on the same partition and the section that you want removed was extremely helpful at the time. That is _with_ softraid encryption of the OpenBSD partition. Setting this up is not for the faint of heart and you have to have backups and a restore strategy before tinkering with multi-booting. Your removal request rests on the assumption that because you didn't managed to configure dual-booting nobody can (or should). How about instead you reach out to compare yours to other people's experience? Who knows, maybe a _useful_ addition to the FAQ might come out of it that can help reduce the risk of similar problems for others in the future?
