Tom H <tomh0...@gmail.com> writes: > On Tue, Oct 11, 2011 at 5:58 PM, Kurt Flex <flx...@aol.com> wrote: >> >> # grub-install /dev/sda >> /usr/sbin/grub-setup: warn: This msdos-style partition label has no >> post-MBR gap; embedding won't be possible!. >> /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. > > As the error message says, you don't have a "post-MBR gap". Your first > partition starts too early. Typically, the first partition is preceded > by 63 sectors of 512 bytes, The first sector is the MBR and the next > 62 are the post-MBR gap in which both grub1 and grub2 save an image > that can read a filesystem and therefore locate and boot a kernel. > > What I don't understand is that this has happened after running > "aptitude safe-upgrade". How was grub2 booting your system before > running aptitude?!
After reading the other replies that is the question I'm also asking to myself. Well I haven't setup the server myself, it's a rented server und was installed by the lessor. Currently I guess the real bootloader is not on the raid at all. Maybe it's some other device they are hiding from me. (There is also a rescue system I can boot, but i can't find it in normal state). Next week I should have a bit more time to take the risk to type `sudo reboot' and see what happens. Thank you for all the explanations. Kurt -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j74453$v4c$1...@dough.gmane.org
