Quantcast
Channel: Ubuntu Forums - Virtualisation
Viewing all articles
Browse latest Browse all 4211

[ubuntu] grub> _ appears instead of starting ubuntu after deletion of snapshots in VirtualBox

$
0
0
Problem:
Ubuntu operating system is not started. Instead of it the gnu grub bash-like terminal appears:

Code:

GNU GRUB version 2.02~beta2-9ubuntu1.12

Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.

grub> _

problem.png

This is shown if I do grub> ls (hd0<TAB>:

no-known-filesystem-detected.png

Before the grub terminal appears I was able to catch some errors:

errors-before-grub-terminal-is-shown.png

The VirtualBox menu for selection of boot devices can be triggered:

f12-for-boot-devices-menu.png


Steps applied which lead to problem (Before having applied these steps everything worked since months without problems!):


  • Open Oracle VirtualBox Gui (v5.1.30).
  • Select virtual machine.
  • Go to tab "Snapshots".
  • Delete step by step each existing snapshot.
  • The deletion executed without failures (at least nothing poped up on the gui).
  • Start virtual machine in the same Oracle VirtualBox GUI.
  • Windows open and the grub terminal appears instead of loading the ubuntu operating system.



I already tried to create a new virtual machine and apply the same vdi hard disk to it but the same problem occurs. This tells me that something bad changed in the vdi file, or?

I'm able to assign an optical drive, e.g. a ubuntu live disc, and VirtualBox starts it normally without any problem.
Using a Ubuntu Live CD within VirtualBox I'm still able to access the partition and all of the data which means I can rescue that in that way. So, the system is still there, it is not deleted, but it cannot be started!

However, I don't want to do it in that way, since I think VirtualBox destroyed the grub menu.lst or any other configuration in the boot chain which finally prevents starting ubuntu correctly!
Currently I'm searching and trying to create the origin assignments within grub so that the right still existing kernel and so on can be triggered and the ubuntu system can be started again normally.
existing-kernel.png



There is a strange thing I discovered so far: the grub.cfg contains of this defect ubuntu (14.04) system contains non-UTF-8 content (checked witzh unix command less). I checked the grub.cfg of another working ubuntu (16.04) using same VirtualBox and the grub.cfg contains human-readable UTF-8 content...


  1. is the grub.cfg file corrupted?
  2. is maybe the menu-lst file missing or corrupted (how can I check this)?


Please help!

Viewing all articles
Browse latest Browse all 4211

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>