Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just did this:

  1. made an Intel Extended partition covering the whole HD using Haiku Alpha 4.1's DriveSetup
  2. made several BeOS partitions
  3. deleted the first one
  4. installed Haiku onto one of the other ones
  5. installed CentOS 6.4 i386 into the empty space, which created two partitions within the empty space, the first being 500 MB
  6. ran BootManager from Haiku and set up the menu to be able to boot to any partition

Now, when I boot, if I select Haiku, it boots fine. If I select either of the CentOS partitions, it says, "Not a bootable partition".

Did CentOS forget to install GRUB or something? Is this an issue with my CentOS setup, Haiku's BootManager, or with my use of Extended Intel partitions?

FWIW, I used to run PC-BSD, and IIRC Peppermint Linux also, on here using the same methodology--except for the Extended Intel part, because I only needed four partitions--and they would boot from Haiku's BootManager just fine.

share|improve this question
up vote 0 down vote accepted

I think it didn't install GRUB, probably to avoid trashing an existing bootloader since I wasn't using the whole drive.

To fix it, I booted into the install medium again (minimal, prepared using ISO2USB), chose the rescue option from the initial menu, went through until I got a command prompt, then:

chroot /mnt/sysimage/
cat /boot/grub/grub.conf

Then seeing it's installed at (hd0,8) in grub notation, did this:

grub-install hd0,8

Now it boots (from the 500MB partition, but not the other one) when I select it in Haiku's BootManager.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.