I just upgraded my home server from 12.04.1 to 12.10. During the upgrade, I got a message that GRUB could not be installed. I found some web pages suggesting to ignore the message and carry on. So I did.
Now the system won't boot I get:
I'm not very good with GRUB, so I am trying to solve the problem with Boot Repair, which looks like it should help. I use LVM so I am using "Ubuntu Secure Remix 12.10 64-bit" with Boot Repair.
error: file not found
I booted from the CD, selected "Try Ubuntu". I made sure the network connection is active and then started Boot Repair.
I got a message:
I clicked OK and the main Boot Repair window appeared. Then I clicked "Recommended Repair" and got this message:
RAID detected. You may want to retry after installing the [mdadm] packages. (sudo apt-get install -y --force-yes mdadm --no-install-recommends)
I'm not running any package managers. Strange message!
Please close all your package managers (Software Center, Update Manager, Synaptic, ...). Then try again.
I quit Boot Repair and installed the mdadm packages as suggested then ran boot-repair again.
This time it said:
I clicked Yes, and chose Recommended Repair but again I get the message about package managers. I'm really confused!
[dmraid] packages may interfere with MDraid. Do you want to remove them?
Boot Repair has provided this diagnostic URL: http://paste.ubuntu.com/1519188/
Thanks in advance.
I tried running grub-install manually. I mounted the server's root volume at /mnt/root, chdir'd into it and created bind mounts for /sys, /proc and /dev:
I'm thinking this is why the grub-install failed in the first place.
# mount /dev/mapper/os-root /mnt/root
# cd /mnt/root
# mount -o bind /dev/ dev
# mount -o bind /proc/ proc
# mount -o bind /sys/ sys
# chroot .
# grub-install /dev/sda
/usr/sbin/grub-bios-setup: warning: your core.img is unusually large. It won't fit in the embedding area.
/usr/sbin/grub-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.
So, it seems I either need to get my /boot onto non-LVM disk or have a smaller core.img. I don't have any non-LVM disk in this server, so I would have to free some up from LVM which will be a bit of a project, and seems a bit risky; the other option is to have a core.img that is not unusually large!
Why is my core.img unusually large? Is it possible to have a smaller core.img?