[haiku-bugs] Re: [Haiku] #7930: Installer doesn't install bootman and DriveSetup doesn't set the created partition as active, leading to unbootable system

From: "pulkomandy" <trac@xxxxxxxxxxxx>
Date: Fri, 31 Oct 2014 10:12:42 -0000

#7930: Installer doesn't install bootman and DriveSetup doesn't set the created
partition as active, leading to unbootable system
--------------------------------------+----------------------------
   Reporter:  HaikuReactOSTrac        |      Owner:  korli
       Type:  enhancement             |     Status:  new
   Priority:  normal                  |  Milestone:  R1
  Component:  Applications/Installer  |    Version:  R1/Development
 Resolution:                          |   Keywords:
 Blocked By:                          |   Blocking:
Has a Patch:  0                       |   Platform:  All
--------------------------------------+----------------------------

Comment (by pulkomandy):

 What we need here is (I think) an MBR that just chainloads to the active
 partition. Our MBR code does not does that, and instead relies on
 makebootable being run on it to point to the stage2 loader at the right
 place.

 The other one we have is bootman, which works fine too but needs some user
 configuration to setup the boot menu. Which you can't do when you are
 creating the partition map, because no partitions are there yet. So I
 don't think it can be used in that case.

 I can confirm that starting with an empty disk (dd if=/dev/zero), creating
 a partition map on it, and installing haiku (but no bootman) results in a
 system that won't boot. It may work if you don't clear the disk first
 because the disk may already have a standard MBR on it which we don't
 erase. But if there's nothing there, you get an unbootable system.

 At a minimum we need a clearer warning message that setting up bootman or
 some other MBR is required in that case.

--
Ticket URL: <https://dev.haiku-os.org/ticket/7930#comment:21>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.

[haiku-bugs] Re: [Haiku] #7930: Installer doesn't install bootman and DriveSetup doesn't set the created partition as active, leading to unbootable system

Other related posts: