#95 Refit wont allow me to boot into Ubuntu


Ok so i followed the instructions on this site to dual boot ubuntu and mac osx. All goes well until the last step, where i used refit to sync my partition tables. Refit says: Analysis inconclusive: will not touch this disk
Then on the line beneath it says
Error: Not Found returned from gptsync.efi
Then it gives me the option to return to the menu.
A few facts:
Before install, in the refit menu there was already a option to boot into linux, which i had never installed. After installation, there were 2 linux's
I did this right after a clean install of OSX, using boot camp to create space, then i removed the bootcamp partition using gparted on the live cd (ubuntu)
Ubuntu Version: 11.10
Here is the code from partition inspector:

*** Report for internal hard disk ***

Current GPT partition table:
# Start LBA End LBA Type
1 40 409639 EFI System (FAT)
2 409640 367149095 Mac OS X HFS+
3 367151104 369199103 Linux Swap
4 369199104 625141759 Basic Data

Current MBR partition table:
# A Start LBA End LBA Type
1 1 39 ee EFI Protective
2 40 409639 0b FAT32 (CHS)
3 * 409640 367149095 af Mac OS X HFS+
4 367151104 369199103 82 Linux swap / Solaris

MBR contents:
Boot Code: GRUB

Partition at LBA 40:
Boot Code: None (Non-system disk message)
File System: FAT32
Listed in GPT as partition 1, type EFI System (FAT)
Listed in MBR as partition 2, type 0b FAT32 (CHS)

Partition at LBA 409640:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 2, type Mac OS X HFS+
Listed in MBR as partition 3, type af Mac OS X HFS+, active

Partition at LBA 367151104:
Boot Code: None
File System: Unknown
Listed in GPT as partition 3, type Linux Swap
Listed in MBR as partition 4, type 82 Linux swap / Solaris

Partition at LBA 369199104:
Boot Code: GRUB
File System: ext4
Listed in GPT as partition 4, type Basic Data


  • Comment has been marked as spam. 

    You can see all pending comments posted by this user  here

    Anonymous - 2011-11-03
    • priority: 5 --> 8
  • Joe van Tunen

    Joe van Tunen - 2011-11-07

    What exactly does rEFIt say about each Linux option? Is there something different about each one such as Partition Number?

    Use fdisk on the Mac to fix your MBR.

    Are there any boot files or whatever on the EFI partition at block 40? Usually the EFI partition is not included in the MBR and the EFI Protective partition covers that partition.

    The boot flag should not be on the Mac OS partition at 409640 since Mac OS doesn't use BIOS to boot.

    The Linux swap partition at 367151104 probably doesn't need to be in the MBR since Linux can probably find it using the GPT. When you boot Linux, verify that the swap partition is being used correctly.

    The Linux partition at 369199104 is not in the MBR. It probably should be especially if the MBR boot code requires it to be there (i.e. if the boot code was standard Windows boot code and grub was installed to that partition). The output you show says that the MBR has GRUB boot code. I don't know if GRUB requires the Linux partition to be in the MBR. I don't think it would need that since the 1st stage of the GRUB boot code doesn't use it to find the 2nd stage of the GRUB boot code.

    The block number of the first block of the 2nd stage of the GRUB boot code is stored in the 1st stage of the GRUB boot code. In Grub 1.99, the location is stored as an 8 byte little endian number at offset 0x5C:
    startblock=$(sudo dd if=/dev/sda skip=$((0x5C)) count=8 bs=1 2> /dev/null | xxd -c 1 -p | tac | tr -d \\n)
    echo $((0x$startblock))

    The block number may point to somewhere after the MBR (not good for you, since you have a GPT) or to a boot partition (which you don't seem to have) or to a file in one of the partitions, maybe /boot/grub/core.img. The following command will output the list of blocks where the /boot/grub/core.img file is located:
    sudo /sbin/hdparm --fibmap /boot/grub/core.img


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks