sh4d0wKöszönöm a reagálást; a leírtak szerint nem megy, mert a grub telepítés ugyan megy, de új könyvtárba, külön. A Launchpad böngészésének eredménye:
I've got the same problem today. Seems like grub2 don't like something in its configuration file. I did something like that to boot the system:
sh:grub> linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro
sh:grub> initrd /boot/initrd.img-2.6.31-14-generic
sh:grub> boot
sda2=(hdd0,2) in my is a windows partition with /ubuntu folder on it. Sure thing, you will have to change your kernel version in files (or just hit TAB to suggestions).
To find what drive is what you can use 'ls -l ' command or 'ls (hdd0,2)/' for the content. I've had (loop0) as an image of my linux root folder, supplementary partition (hdd0,1) and windows partition (hdd0,2). This will not solve the bug, but at least you will be able to use OS until it will be solved.
It is really disappointing, that this things still happening. After this bug will be gone, I'll definitely disable updates.
#
This is how I fixed it:
1) Boot from a Live CD
2) Reinstall grub as explained here: https://wiki.ubuntu.com/Grub2#Recover%20Grub%202%20via%20LiveCD
Just in case the link above stops working, this is what I did:
# sudo mount /dev/sda4 /mnt
("/dev/sda4" is where my linux data partition -containing also "/boot"- can be found. The other three previous ones are OSX stuff).
# sudo mount --bind /dev/ /mnt/dev
# sudo chroot /mnt
# upgrade-grub
# grub-install /dev/sda
(yes... this is "/dev/sda", without the "4")
Once it boots again, the "update manager" does not find any new grub package... so I guess this won't happen again (after all the new grub was installed, we just re-created its config file)
Talán másoknak is segít.
