[haiku-bugs] Re: [Haiku] #7930: Boot failure in Virtualbox and Virtual PC with Latest nightly build when a BeFS partition is created within an Intel Partition Map instead of initializing the entire disk as BeFS without the Intel Partition Map
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Thu, 18 Aug 2011 17:59:10 -0000
#7930: Boot failure in Virtualbox and Virtual PC with Latest nightly build when
a
BeFS partition is created within an Intel Partition Map instead of
initializing the entire disk as BeFS without the Intel Partition Map
--------------------------------+----------------------------
Reporter: HaikuReactOSTrac | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: - General | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
--------------------------------+----------------------------
Comment (by bonefish):
Replying to [comment:7 deejam]:
> If I understand this correctly, the "No bootable active volume" is an
error message from Haiku's boot loader and "ROM BASIC FATAL: INIT18: BOOT
FAILURE" is VirtualBox's counterpart. They do say the same thing; no
bootable volume is found.
Not quite. The former message is likely from the MBR boot code -- Haiku's
boot loader (both stage 1 and stage 2) doesn't care whether the partition
is active. Since there's no indicator in the partition table whether a
partition is bootable or not, the message means that none of the defined
partitions has been marked active.
Please check in DriveSetup whether the partition exists and is marked
active. If so, please provide the MBR (the first 512 bytes of the disk).
--
Ticket URL: <http://dev.haiku-os.org/ticket/7930#comment:12>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
