I got the same error with the latest kernel update:from 2.6.31-14 to 2.6.31-15
When booting it ended up in the minimal grub shell.
HOWEVER, I could recover to a certain extent:
Noticed that there was already a (loop0) device listed, thus the grub could create the loop device from the root.disk
(one can check: if "ls /" gives linux-type of directory structure, it should be already in the loop device)
Then issued the following commands to get into linux:
linux vmlinuz-2.6.31-14-generic root=/dev/sda6 loop=/ubuntu/disks/root.disk ro
initrd initrd.img-2.6.31-14-generic
boot
Note!:
1) I had to do the old version (-14), the new version (-15) sent it into reboot immediately after issuing "boot"!
2) the root=/dev/sda6 is on my computer for others' machines it will be different
After that, being in Ubuntu, i think i issued a "sudu grub-update". At the next update the grub screen was back, -15 still rebooting, but -14 works fine for the moment....
What's in the kernel update that it brakes like this?
I got the same error with the latest kernel update:from 2.6.31-14 to 2.6.31-15
When booting it ended up in the minimal grub shell.
HOWEVER, I could recover to a certain extent:
Noticed that there was already a (loop0) device listed, thus the grub could create the loop device from the root.disk
(one can check: if "ls /" gives linux-type of directory structure, it should be already in the loop device)
Then issued the following commands to get into linux: 2.6.31- 14-generic root=/dev/sda6 loop=/ubuntu/ disks/root. disk ro img-2.6. 31-14-generic
linux vmlinuz-
initrd initrd.
boot
Note!:
1) I had to do the old version (-14), the new version (-15) sent it into reboot immediately after issuing "boot"!
2) the root=/dev/sda6 is on my computer for others' machines it will be different
After that, being in Ubuntu, i think i issued a "sudu grub-update". At the next update the grub screen was back, -15 still rebooting, but -14 works fine for the moment....
What's in the kernel update that it brakes like this?