Raided drive using linux software raid - MD │ The GRUB boot loader was previously installed to a disk that is no │ longer present, or whose normally unique identifier has changed for some │ reason. It is important to make sure that the installed GRUB stays in │ sync with other components such as grub.cfg or with newer Linux images │ it will have to load, and so you should check again to make sure that │ GRUB is installed to the appropriate boot devices. │ If you're unsure which drive is designated as boot drive by your BIOS, │ it is often a good idea to install GRUB to all of them. │ │ Note: It is possible to install GRUB to partition boot records as well. │ However, this forces GRUB to use the blocklist mechanism, which makes it │ less reliable, and therefore is not recommended.
│ GRUB failed to install to the following devices: │ │ /dev/sda1 │ │ Do you want to continue anyway? If you do, your computer may not start │ up properly. │ │ │ GRUB installation failed. Continue? Installation finished. No error reported. /usr/sbin/grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea.. /usr/sbin/grub-setup: error: embedding is not possible, but this is required when the root device is on a RAID array or LVM volume. Installation finished. No error reported. Generating grub.cfg ... Found linux image: /boot/vmlinuz-2.6.32-22-generic Found initrd image: /boot/initrd.img-2.6.32-22-generic Found linux image: /boot/vmlinuz-2.6.32-21-generic Found initrd image: /boot/initrd.img-2.6.32-21-generic Found memtest86+ image: /boot/memtest86+.bin done -- Grub needs interaction on where to install it on upgrade https://bugs.launchpad.net/bugs/545989 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
