- Code: Select all
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-legacy-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
# Pretty colours
color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
The /etc/grub/message.elyssa or the /etc/grub/message.mint are the image files that give you the pretty picture in the background of your GRUB Menu in Mint.
Probably if that file can't be found it will stop the boot loader from completing it's list of commands and booting your system.
You should first try booting your live CD and opening Gnome Partition Editor, right-click on your Mint partition and click 'check'.
Then click 'Apply', and then 'Apply' once again to confirm, and wait a few minutes (depending on the size of your partition), for the file system check to be completed. That might solve your problem and will at least do some good for your file system.
If that doesn't work, you may need to boot from GRUB's Command Line Interface instead of from your GRUB Main Menu, (as that relies on your menu.lst file which contains the problematic command).
Otherwise, you could mount your Mint file system in the Live CD and open your /media/disc/boot/grub/menu.lst file and comment out the line which is causing the problem for the time being until you find out why your gfxboot image file is missing.
By the way, another thing I should mention is, it's /etc/grub/, and not /ect/grub, if you have manually edited your /boot/grub/menu.lst file and made a mistake like that then that could be what your problem is right there!
EDIT: I just ran an experiment to test this by temporarily renaming my /etc/grub/message.elyssa file and removing the original copy. When I rebooted I was shown the same error message, but then I was given a colored GRUB Menu and Mint booted up okay. My system seems to be behaving itself and working normally. I am now wondering if the original poster's problem is the real problem or only a symptom of some deeper underlying problem? Maybe a file system check will fix it.