grub2 cannot read core.img

When trying to install grub2 (whatever snapshot was current as of today) I kept getting the following error:
$ sudo /sbin/grub-setup -v --directory=/media/sysrescd/boot/grub \
  --device-map=/media/sysrescd/boot/grub/device.map -r '(hd1,1)' '(hd1)'
.... snip ...
grub-setup: error: Cannot read `/media/sysrescd/boot/grub/core.img' correctly

The error was not very descriptive because grub was apparently able to read other important files like boot.img and such. The filesystem on my USB stick was identical (feature wise) to the /boot on my HDD -- ext2. And the same command worked just fine for installing to my hard disk.

Digging through the code revealed where the problem is. The error was caused by grub-setup being unable to embed core.img in the MBR. The core.img prepared by grub-mkimage was 25k big. That is about 50 sectors. The first partition on my hard disk starts on sector 63. The first partition on my USB stick was starting on sector 32 (or was it 31?). 32 < 50 => core.img cannot be embedded. If only the error message had been a little clearer it would have saved me some headache.

Destroying the first partition on the USB stick and recreating it starting from sector 63 fixed the problem.

Comments

  1. MatthewNovember 27, 2009 at 11:04 PM

    Thanks for posting this information. This helped me with my long-standing problem. Grub2 despirately needs some basic technical documentation, including common issues like this one. So sad that it is so neglected, since it is so important.

    ReplyDelete
  2. MaxJanuary 31, 2010 at 12:27 AM

    Thanks pal. You've saved lot of my time.

    ReplyDelete
  3. cmhFebruary 16, 2010 at 1:01 PM

    how do you destroy the first partition and recreate it from sector 63?

    ReplyDelete
  4. chutzFebruary 21, 2010 at 4:56 AM

    @cmh: You can do it with fdisk, but you should tell it to use sectors as a unit. Either start fdisk as "fdisk -u", or type "u" once you are in the fdisk interface. Then delete the partition and create it again (you will of course lose all data on the partition). A snipped down fdisk session:


    $ sudo fdisk /dev/sdb
    Command (m for help): p
    ...
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 3011 3915204 b W95 FAT32
    Command (m for help): u
    Changing display/entry units to sectors
    Command (m for help): p
    ...
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1144 7831551 3915204 b W95 FAT32
    Command (m for help): d
    Selected partition 1
    Command (m for help): n
    Command action
    e extended
    p primary partition (1-4)
    p
    Partition number (1-4): 1
    First sector (51-7831551, default 51): 63
    Last sector, +sectors or +size{K,M,G} (63-7831551, default 7831551): +1G
    Command (m for help): p
    ...
    Device Boot Start End Blocks Id System
    /dev/sdb1 63 2097215 1048576+ 83 Linux

    ReplyDelete

Post a Comment

Popular posts from this blog

FreeIPA cluster with containers

Notes on how to install a FreeIPA cluster on Ubuntu. Mostly following the instructions on https://github.com/freeipa/freeipa-container Start with what would be the primary host. If you install a third replica you would want to review the replica agreements to ensure you have a two-way replication between all pairs of nodes.
Read more

ADSL Router Model CT-5367 user and pass (VIVACOM)

Writing down the username and password for the vivacom ADSL router, in case I need it again. user: root pass: warmWLspot Useful to telnet 192.168.1.1 and then reboot . Originally found at Neo2SHYAlien blog . And here I found passwords for other models, just in case. ZTE ZXDSL 832 username: root password: GSrootaccess ZTE ZXDSL 831 username: root password: GSrootaccess ZTE username: root password: 831access Huawei SmartAX MT882 username: root password: MT882rootaccess ZTE ZXDSL-531b username: root password: rootWLaccess Pirelli – DRG – A124G username: root password: warmWLspot Comtrend CT-5367 username: root password: warmWLspot HG530 Home Gateway username: root password: warmWLspot
Read more

Installing Gentoo with full disk encryption

The purpose of this exercise - install Gentoo where all disk partitions are encrypted. Boot from a system rescue disk and partition the disk - use GPT partition table where the first partition is reserved, second is the boot, and the third one is for the rest of the data. Device Start End Sectors Size Type /dev/sda1 2048 32767 30720 15M BIOS boot /dev/sda2 32768 442367 409600 200M Linux filesystem /dev/sda3 442368 375093902 374651535 178.7G Linux filesystem Encrypt partitions number 2 and 3, and open them cryptsetup luksFormat /dev/sda2 cryptsetup luksFormat /dev/sda3 cryptsetup luksOpen /dev/sda2 crypt_boot cryptsetup luksOpen /dev/sda3 crypt_data Format the boot partition mkfs.btrfs /dev/mapper/crypt_boot Prepare LVM for the rest, and format the top level vgcreate vg0 /dev/mapper/crypt_data lvcreate -l 100%FREE -n data vg0 mkfs.btrfs /dev/vg0/data Mount and set up any subvolumes mount /dev/vg0/data /mnt/gentoo btrfs subvol create /mnt/gentoo/@ /mnt/gentoo/@home umount /mnt/gentoo Now...
Read more