One method: Append init=/bin/bash to the end of the grub line which begins with linux (and ends with quiet). Reset your password and reboot normally. Don’t forget it again. Consider installing sudo. Another method: Since this is apparently a virtual machine, you can mount its disk on another (working) virtual machine and manually remove the … Read more
You can indeed use Grub to boot once only. You can also specify a fallback boot. Essentially, you use default saved at the start of your grub.conf, to indicate that you want to boot a saved entry by default. Then at the end of your experimental boot, use savedefault # to set the older boot … Read more
I was having the same problem while rebuilding a degraded SW-RAID array, and tripped over this on another website: The grub-2.00 source where the warning arises is in ./grub-core/disk/diskfilter.c and has this comment: /* TRANSLATORS: This message kicks in during the detection of which modules needs to be included in core image. This happens in … Read more
Those messages are nothing to worry about. The symlinks that are being complained about are only needed if you’re using lilo as your bootloader, because it uses those symlinks to find your “current” kernel. Grub, being more flexible, has it’s own way of doing things, and doesn’t need the symlinks.
This is a simple way to tell if GRUB is installed. If it doesn’t work your file command’s database is likely out of date and you can either update the its database or use an alternate method from another answer. You can use file to identify GRUB in an MBR. e.g. # file -s /dev/sda … Read more
For Ubuntu 12.04 LTS there is a specific option that can be set in /etc/default/grub. For example, if you want to have a 2 seconds timeout (thus avoiding hangs for unattended reboots) just add the following line in /etc/default/grub: GRUB_RECORDFAIL_TIMEOUT=2 Remember to run update-grub after that…