![]() ![]() The boot process can't find the root partition (the part of the disk, that contains the information for starting up the system), so you have to specify its location yourself. Maybe this additional bit of information can help figure out what is going on? I checked with the blkid command and that is the identifier of my linux partition. ![]() This did not fix the problem, but now when it starts in command prompt mode, GRUB shows the following message: error: no such device: 6fxxxxx-xxxx-xxxx-xxxx-xxxxxee. Why is this happening and how can I ensure that GRUB always loads the menu? EditĪs suggested in the comments, I tried purging the grub-efi package and reinstalling it. I think that the BIOS has EFI enabled, and I installed the GRUB bootloader in /dev/sda. Rebooting without pressing F12 always reboots in command line mode. Using this technique, it always loads the menu. What works is to reboot using Ctrl+Alt+Del, then pressing F12 repeatedly until the normal GRUB menu appears. There is probably a command that I can type to boot from that prompt, but I don't know it. When I turn on the computer, the normal GRUB menu appears most of the time:īut after booting either Linux or Windows then rebooting, I GRUB starts in command line mode, as seen in the following screenshot: I installed Linux Mint on my laptop along with a pre-installed Windows 10. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |