How do I boot my PC from GRUB? [duplicate]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
8
down vote

favorite
4













This question already has an answer here:



  • How can I repair grub? (How to get Ubuntu back after installing Windows?)

    12 answers



I can no longer boot Ubuntu following a corruption problem initially reported here (How do I solve the "invalid arch dependent elf magic" error message).



When I power my laptop, I now get the following message:



GNU GRUB version 2.02~beta2-9ubuntu1.7
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." and then the prompt

grub>


Can anyone help me get back to Ubuntu ?










share|improve this question















marked as duplicate by David Foerster, N0rbert, Fabby, Kevin Bowen, Melebius May 21 at 9:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward♦
    Jul 2 '17 at 19:03










  • Big thumbs up to everybody. I chased down a few leads and finally solved the problem by booting from a live CD and entering the command "sudo update-grub" @derHugo your help was massively useful.
    – Mons
    Jul 2 '17 at 19:29






  • 1




    The various hints given by @derHugo can be found on the chat site on Stack Exchange here: chat.stackexchange.com/rooms/61451/… and in particular when he recommended googling the question, here: "Haha sorry always forget that ^^ anyway please Google it there are tons of articles addressing this issue e.g. here is another one". Anyway, I'm absolutely made up to be up and running on my laptop again. I know I'm not supposed to say thanks, but I will all the same. THANKS !
    – Mons
    Jul 2 '17 at 21:59














up vote
8
down vote

favorite
4













This question already has an answer here:



  • How can I repair grub? (How to get Ubuntu back after installing Windows?)

    12 answers



I can no longer boot Ubuntu following a corruption problem initially reported here (How do I solve the "invalid arch dependent elf magic" error message).



When I power my laptop, I now get the following message:



GNU GRUB version 2.02~beta2-9ubuntu1.7
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." and then the prompt

grub>


Can anyone help me get back to Ubuntu ?










share|improve this question















marked as duplicate by David Foerster, N0rbert, Fabby, Kevin Bowen, Melebius May 21 at 9:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward♦
    Jul 2 '17 at 19:03










  • Big thumbs up to everybody. I chased down a few leads and finally solved the problem by booting from a live CD and entering the command "sudo update-grub" @derHugo your help was massively useful.
    – Mons
    Jul 2 '17 at 19:29






  • 1




    The various hints given by @derHugo can be found on the chat site on Stack Exchange here: chat.stackexchange.com/rooms/61451/… and in particular when he recommended googling the question, here: "Haha sorry always forget that ^^ anyway please Google it there are tons of articles addressing this issue e.g. here is another one". Anyway, I'm absolutely made up to be up and running on my laptop again. I know I'm not supposed to say thanks, but I will all the same. THANKS !
    – Mons
    Jul 2 '17 at 21:59












up vote
8
down vote

favorite
4









up vote
8
down vote

favorite
4






4






This question already has an answer here:



  • How can I repair grub? (How to get Ubuntu back after installing Windows?)

    12 answers



I can no longer boot Ubuntu following a corruption problem initially reported here (How do I solve the "invalid arch dependent elf magic" error message).



When I power my laptop, I now get the following message:



GNU GRUB version 2.02~beta2-9ubuntu1.7
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." and then the prompt

grub>


Can anyone help me get back to Ubuntu ?










share|improve this question
















This question already has an answer here:



  • How can I repair grub? (How to get Ubuntu back after installing Windows?)

    12 answers



I can no longer boot Ubuntu following a corruption problem initially reported here (How do I solve the "invalid arch dependent elf magic" error message).



When I power my laptop, I now get the following message:



GNU GRUB version 2.02~beta2-9ubuntu1.7
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." and then the prompt

grub>


Can anyone help me get back to Ubuntu ?





This question already has an answer here:



  • How can I repair grub? (How to get Ubuntu back after installing Windows?)

    12 answers







boot grub2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 2 '17 at 18:17









Android Dev

10.5k63257




10.5k63257










asked Jun 28 '17 at 7:49









Mons

41116




41116




marked as duplicate by David Foerster, N0rbert, Fabby, Kevin Bowen, Melebius May 21 at 9:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by David Foerster, N0rbert, Fabby, Kevin Bowen, Melebius May 21 at 9:42


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.













  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward♦
    Jul 2 '17 at 19:03










  • Big thumbs up to everybody. I chased down a few leads and finally solved the problem by booting from a live CD and entering the command "sudo update-grub" @derHugo your help was massively useful.
    – Mons
    Jul 2 '17 at 19:29






  • 1




    The various hints given by @derHugo can be found on the chat site on Stack Exchange here: chat.stackexchange.com/rooms/61451/… and in particular when he recommended googling the question, here: "Haha sorry always forget that ^^ anyway please Google it there are tons of articles addressing this issue e.g. here is another one". Anyway, I'm absolutely made up to be up and running on my laptop again. I know I'm not supposed to say thanks, but I will all the same. THANKS !
    – Mons
    Jul 2 '17 at 21:59
















  • Comments are not for extended discussion; this conversation has been moved to chat.
    – Thomas Ward♦
    Jul 2 '17 at 19:03










  • Big thumbs up to everybody. I chased down a few leads and finally solved the problem by booting from a live CD and entering the command "sudo update-grub" @derHugo your help was massively useful.
    – Mons
    Jul 2 '17 at 19:29






  • 1




    The various hints given by @derHugo can be found on the chat site on Stack Exchange here: chat.stackexchange.com/rooms/61451/… and in particular when he recommended googling the question, here: "Haha sorry always forget that ^^ anyway please Google it there are tons of articles addressing this issue e.g. here is another one". Anyway, I'm absolutely made up to be up and running on my laptop again. I know I'm not supposed to say thanks, but I will all the same. THANKS !
    – Mons
    Jul 2 '17 at 21:59















Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
Jul 2 '17 at 19:03




Comments are not for extended discussion; this conversation has been moved to chat.
– Thomas Ward♦
Jul 2 '17 at 19:03












Big thumbs up to everybody. I chased down a few leads and finally solved the problem by booting from a live CD and entering the command "sudo update-grub" @derHugo your help was massively useful.
– Mons
Jul 2 '17 at 19:29




Big thumbs up to everybody. I chased down a few leads and finally solved the problem by booting from a live CD and entering the command "sudo update-grub" @derHugo your help was massively useful.
– Mons
Jul 2 '17 at 19:29




1




1




The various hints given by @derHugo can be found on the chat site on Stack Exchange here: chat.stackexchange.com/rooms/61451/… and in particular when he recommended googling the question, here: "Haha sorry always forget that ^^ anyway please Google it there are tons of articles addressing this issue e.g. here is another one". Anyway, I'm absolutely made up to be up and running on my laptop again. I know I'm not supposed to say thanks, but I will all the same. THANKS !
– Mons
Jul 2 '17 at 21:59




The various hints given by @derHugo can be found on the chat site on Stack Exchange here: chat.stackexchange.com/rooms/61451/… and in particular when he recommended googling the question, here: "Haha sorry always forget that ^^ anyway please Google it there are tons of articles addressing this issue e.g. here is another one". Anyway, I'm absolutely made up to be up and running on my laptop again. I know I'm not supposed to say thanks, but I will all the same. THANKS !
– Mons
Jul 2 '17 at 21:59










3 Answers
3






active

oldest

votes

















up vote
18
down vote













Ok, from grub type ls (hd0,1)/

you should see a file named vmlinuz or linux, and initrd.img



Type linux (hd0,1)/vmlinuz root=/dev/sda1 or linux (hd0,1)/linux root=/dev/sda1 depending on what you found with ls (hd0,1)/, then:



initrd (hd0,1)/initrd.img
boot


If you get initramfs rescue mode enter your password, then startx.
You should now have a desktop.



Use gparted to check your file system, if it reports an error, then you need to boot from a LiveCD or other media to fix it .... DO NOT attempt to repair a mounted partition.



The following three commands fix many grub boot problems. They run quick so just do all three instead of trying to find which one you need.



sudo grub-install /dev/sda && sudo update-grub && sudo update-initramfs -u


Reboot and see what you get.






share|improve this answer


















  • 3




    Is it really innitrd or should it be initrd?
    – WinEunuuchs2Unix
    Jul 2 '17 at 19:52






  • 1




    It is actually initrd
    – answerSeeker
    Jul 2 '17 at 20:19











  • @wineunuuchs2unix -- thanks fixed. thou you could ave edited the typo
    – ravery
    Jul 2 '17 at 21:57






  • 1




    @ravery Yes I could have corrected the typo. I have a weird point of view thinking it's more polite to point out to the author and letting them make the change. That way an otherwise spotless answer doesn't have the "blemish" of an "edited by someone else" flag. I do edit new users' questions frequently though... Have another +1 :)
    – WinEunuuchs2Unix
    Jul 2 '17 at 22:18











  • You can't start a x session or run a GUI program from Initramfs... nothing has been mounted yet.
    – Ravexina
    Jul 5 '17 at 8:42

















up vote
1
down vote













The most probable cause to that issue is installing the OS to a disk, grub to a different disk that is not removable. Then removing the OS disk.



You could just plug the USB stick back in. Problem solved.






share|improve this answer






















  • Solution found (see above).
    – Mons
    Jul 2 '17 at 19:29










  • I saw the chat conversation. Solved with update-grub, which supports not refutes this answer.
    – RobotHumans
    Jul 2 '17 at 19:32

















up vote
0
down vote













Restart your system.
Press f2 key while loading.
Goto boot option.
Press f5/f6 to change values (which os you want to install keep it in first place.).
Enter f10 key....It may solve your problem.
.
.
.
If not enter this in grub rescue mode....
ls
(hd0) (hd0,msdos6) (hd0,msdos5)....(hd0,msdos1)
OR
(hd0) (hd0,gpt6).....(hd0,gpt1)



set boot=(hd0,gpt6) OR set boot=(hd0,msdos6)
set prefix=(hd0,gpt6)/boot/grub OR use msdos6 instead.
insmod normal
normal
This may solve your problem.






share|improve this answer




















  • these are various ways to launch grub. this is not the issue as OP states. grub launches but drops to recovery mode. The issue is that the grub config file is missing
    – ravery
    Jul 9 '17 at 8:23

















3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
18
down vote













Ok, from grub type ls (hd0,1)/

you should see a file named vmlinuz or linux, and initrd.img



Type linux (hd0,1)/vmlinuz root=/dev/sda1 or linux (hd0,1)/linux root=/dev/sda1 depending on what you found with ls (hd0,1)/, then:



initrd (hd0,1)/initrd.img
boot


If you get initramfs rescue mode enter your password, then startx.
You should now have a desktop.



Use gparted to check your file system, if it reports an error, then you need to boot from a LiveCD or other media to fix it .... DO NOT attempt to repair a mounted partition.



The following three commands fix many grub boot problems. They run quick so just do all three instead of trying to find which one you need.



sudo grub-install /dev/sda && sudo update-grub && sudo update-initramfs -u


Reboot and see what you get.






share|improve this answer


















  • 3




    Is it really innitrd or should it be initrd?
    – WinEunuuchs2Unix
    Jul 2 '17 at 19:52






  • 1




    It is actually initrd
    – answerSeeker
    Jul 2 '17 at 20:19











  • @wineunuuchs2unix -- thanks fixed. thou you could ave edited the typo
    – ravery
    Jul 2 '17 at 21:57






  • 1




    @ravery Yes I could have corrected the typo. I have a weird point of view thinking it's more polite to point out to the author and letting them make the change. That way an otherwise spotless answer doesn't have the "blemish" of an "edited by someone else" flag. I do edit new users' questions frequently though... Have another +1 :)
    – WinEunuuchs2Unix
    Jul 2 '17 at 22:18











  • You can't start a x session or run a GUI program from Initramfs... nothing has been mounted yet.
    – Ravexina
    Jul 5 '17 at 8:42














up vote
18
down vote













Ok, from grub type ls (hd0,1)/

you should see a file named vmlinuz or linux, and initrd.img



Type linux (hd0,1)/vmlinuz root=/dev/sda1 or linux (hd0,1)/linux root=/dev/sda1 depending on what you found with ls (hd0,1)/, then:



initrd (hd0,1)/initrd.img
boot


If you get initramfs rescue mode enter your password, then startx.
You should now have a desktop.



Use gparted to check your file system, if it reports an error, then you need to boot from a LiveCD or other media to fix it .... DO NOT attempt to repair a mounted partition.



The following three commands fix many grub boot problems. They run quick so just do all three instead of trying to find which one you need.



sudo grub-install /dev/sda && sudo update-grub && sudo update-initramfs -u


Reboot and see what you get.






share|improve this answer


















  • 3




    Is it really innitrd or should it be initrd?
    – WinEunuuchs2Unix
    Jul 2 '17 at 19:52






  • 1




    It is actually initrd
    – answerSeeker
    Jul 2 '17 at 20:19











  • @wineunuuchs2unix -- thanks fixed. thou you could ave edited the typo
    – ravery
    Jul 2 '17 at 21:57






  • 1




    @ravery Yes I could have corrected the typo. I have a weird point of view thinking it's more polite to point out to the author and letting them make the change. That way an otherwise spotless answer doesn't have the "blemish" of an "edited by someone else" flag. I do edit new users' questions frequently though... Have another +1 :)
    – WinEunuuchs2Unix
    Jul 2 '17 at 22:18











  • You can't start a x session or run a GUI program from Initramfs... nothing has been mounted yet.
    – Ravexina
    Jul 5 '17 at 8:42












up vote
18
down vote










up vote
18
down vote









Ok, from grub type ls (hd0,1)/

you should see a file named vmlinuz or linux, and initrd.img



Type linux (hd0,1)/vmlinuz root=/dev/sda1 or linux (hd0,1)/linux root=/dev/sda1 depending on what you found with ls (hd0,1)/, then:



initrd (hd0,1)/initrd.img
boot


If you get initramfs rescue mode enter your password, then startx.
You should now have a desktop.



Use gparted to check your file system, if it reports an error, then you need to boot from a LiveCD or other media to fix it .... DO NOT attempt to repair a mounted partition.



The following three commands fix many grub boot problems. They run quick so just do all three instead of trying to find which one you need.



sudo grub-install /dev/sda && sudo update-grub && sudo update-initramfs -u


Reboot and see what you get.






share|improve this answer














Ok, from grub type ls (hd0,1)/

you should see a file named vmlinuz or linux, and initrd.img



Type linux (hd0,1)/vmlinuz root=/dev/sda1 or linux (hd0,1)/linux root=/dev/sda1 depending on what you found with ls (hd0,1)/, then:



initrd (hd0,1)/initrd.img
boot


If you get initramfs rescue mode enter your password, then startx.
You should now have a desktop.



Use gparted to check your file system, if it reports an error, then you need to boot from a LiveCD or other media to fix it .... DO NOT attempt to repair a mounted partition.



The following three commands fix many grub boot problems. They run quick so just do all three instead of trying to find which one you need.



sudo grub-install /dev/sda && sudo update-grub && sudo update-initramfs -u


Reboot and see what you get.







share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 2 at 5:55

























answered Jul 2 '17 at 18:49









ravery

5,28451131




5,28451131







  • 3




    Is it really innitrd or should it be initrd?
    – WinEunuuchs2Unix
    Jul 2 '17 at 19:52






  • 1




    It is actually initrd
    – answerSeeker
    Jul 2 '17 at 20:19











  • @wineunuuchs2unix -- thanks fixed. thou you could ave edited the typo
    – ravery
    Jul 2 '17 at 21:57






  • 1




    @ravery Yes I could have corrected the typo. I have a weird point of view thinking it's more polite to point out to the author and letting them make the change. That way an otherwise spotless answer doesn't have the "blemish" of an "edited by someone else" flag. I do edit new users' questions frequently though... Have another +1 :)
    – WinEunuuchs2Unix
    Jul 2 '17 at 22:18











  • You can't start a x session or run a GUI program from Initramfs... nothing has been mounted yet.
    – Ravexina
    Jul 5 '17 at 8:42












  • 3




    Is it really innitrd or should it be initrd?
    – WinEunuuchs2Unix
    Jul 2 '17 at 19:52






  • 1




    It is actually initrd
    – answerSeeker
    Jul 2 '17 at 20:19











  • @wineunuuchs2unix -- thanks fixed. thou you could ave edited the typo
    – ravery
    Jul 2 '17 at 21:57






  • 1




    @ravery Yes I could have corrected the typo. I have a weird point of view thinking it's more polite to point out to the author and letting them make the change. That way an otherwise spotless answer doesn't have the "blemish" of an "edited by someone else" flag. I do edit new users' questions frequently though... Have another +1 :)
    – WinEunuuchs2Unix
    Jul 2 '17 at 22:18











  • You can't start a x session or run a GUI program from Initramfs... nothing has been mounted yet.
    – Ravexina
    Jul 5 '17 at 8:42







3




3




Is it really innitrd or should it be initrd?
– WinEunuuchs2Unix
Jul 2 '17 at 19:52




Is it really innitrd or should it be initrd?
– WinEunuuchs2Unix
Jul 2 '17 at 19:52




1




1




It is actually initrd
– answerSeeker
Jul 2 '17 at 20:19





It is actually initrd
– answerSeeker
Jul 2 '17 at 20:19













@wineunuuchs2unix -- thanks fixed. thou you could ave edited the typo
– ravery
Jul 2 '17 at 21:57




@wineunuuchs2unix -- thanks fixed. thou you could ave edited the typo
– ravery
Jul 2 '17 at 21:57




1




1




@ravery Yes I could have corrected the typo. I have a weird point of view thinking it's more polite to point out to the author and letting them make the change. That way an otherwise spotless answer doesn't have the "blemish" of an "edited by someone else" flag. I do edit new users' questions frequently though... Have another +1 :)
– WinEunuuchs2Unix
Jul 2 '17 at 22:18





@ravery Yes I could have corrected the typo. I have a weird point of view thinking it's more polite to point out to the author and letting them make the change. That way an otherwise spotless answer doesn't have the "blemish" of an "edited by someone else" flag. I do edit new users' questions frequently though... Have another +1 :)
– WinEunuuchs2Unix
Jul 2 '17 at 22:18













You can't start a x session or run a GUI program from Initramfs... nothing has been mounted yet.
– Ravexina
Jul 5 '17 at 8:42




You can't start a x session or run a GUI program from Initramfs... nothing has been mounted yet.
– Ravexina
Jul 5 '17 at 8:42












up vote
1
down vote













The most probable cause to that issue is installing the OS to a disk, grub to a different disk that is not removable. Then removing the OS disk.



You could just plug the USB stick back in. Problem solved.






share|improve this answer






















  • Solution found (see above).
    – Mons
    Jul 2 '17 at 19:29










  • I saw the chat conversation. Solved with update-grub, which supports not refutes this answer.
    – RobotHumans
    Jul 2 '17 at 19:32














up vote
1
down vote













The most probable cause to that issue is installing the OS to a disk, grub to a different disk that is not removable. Then removing the OS disk.



You could just plug the USB stick back in. Problem solved.






share|improve this answer






















  • Solution found (see above).
    – Mons
    Jul 2 '17 at 19:29










  • I saw the chat conversation. Solved with update-grub, which supports not refutes this answer.
    – RobotHumans
    Jul 2 '17 at 19:32












up vote
1
down vote










up vote
1
down vote









The most probable cause to that issue is installing the OS to a disk, grub to a different disk that is not removable. Then removing the OS disk.



You could just plug the USB stick back in. Problem solved.






share|improve this answer














The most probable cause to that issue is installing the OS to a disk, grub to a different disk that is not removable. Then removing the OS disk.



You could just plug the USB stick back in. Problem solved.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jul 2 '17 at 19:17

























answered Jul 2 '17 at 19:02









RobotHumans

22.4k359102




22.4k359102











  • Solution found (see above).
    – Mons
    Jul 2 '17 at 19:29










  • I saw the chat conversation. Solved with update-grub, which supports not refutes this answer.
    – RobotHumans
    Jul 2 '17 at 19:32
















  • Solution found (see above).
    – Mons
    Jul 2 '17 at 19:29










  • I saw the chat conversation. Solved with update-grub, which supports not refutes this answer.
    – RobotHumans
    Jul 2 '17 at 19:32















Solution found (see above).
– Mons
Jul 2 '17 at 19:29




Solution found (see above).
– Mons
Jul 2 '17 at 19:29












I saw the chat conversation. Solved with update-grub, which supports not refutes this answer.
– RobotHumans
Jul 2 '17 at 19:32




I saw the chat conversation. Solved with update-grub, which supports not refutes this answer.
– RobotHumans
Jul 2 '17 at 19:32










up vote
0
down vote













Restart your system.
Press f2 key while loading.
Goto boot option.
Press f5/f6 to change values (which os you want to install keep it in first place.).
Enter f10 key....It may solve your problem.
.
.
.
If not enter this in grub rescue mode....
ls
(hd0) (hd0,msdos6) (hd0,msdos5)....(hd0,msdos1)
OR
(hd0) (hd0,gpt6).....(hd0,gpt1)



set boot=(hd0,gpt6) OR set boot=(hd0,msdos6)
set prefix=(hd0,gpt6)/boot/grub OR use msdos6 instead.
insmod normal
normal
This may solve your problem.






share|improve this answer




















  • these are various ways to launch grub. this is not the issue as OP states. grub launches but drops to recovery mode. The issue is that the grub config file is missing
    – ravery
    Jul 9 '17 at 8:23














up vote
0
down vote













Restart your system.
Press f2 key while loading.
Goto boot option.
Press f5/f6 to change values (which os you want to install keep it in first place.).
Enter f10 key....It may solve your problem.
.
.
.
If not enter this in grub rescue mode....
ls
(hd0) (hd0,msdos6) (hd0,msdos5)....(hd0,msdos1)
OR
(hd0) (hd0,gpt6).....(hd0,gpt1)



set boot=(hd0,gpt6) OR set boot=(hd0,msdos6)
set prefix=(hd0,gpt6)/boot/grub OR use msdos6 instead.
insmod normal
normal
This may solve your problem.






share|improve this answer




















  • these are various ways to launch grub. this is not the issue as OP states. grub launches but drops to recovery mode. The issue is that the grub config file is missing
    – ravery
    Jul 9 '17 at 8:23












up vote
0
down vote










up vote
0
down vote









Restart your system.
Press f2 key while loading.
Goto boot option.
Press f5/f6 to change values (which os you want to install keep it in first place.).
Enter f10 key....It may solve your problem.
.
.
.
If not enter this in grub rescue mode....
ls
(hd0) (hd0,msdos6) (hd0,msdos5)....(hd0,msdos1)
OR
(hd0) (hd0,gpt6).....(hd0,gpt1)



set boot=(hd0,gpt6) OR set boot=(hd0,msdos6)
set prefix=(hd0,gpt6)/boot/grub OR use msdos6 instead.
insmod normal
normal
This may solve your problem.






share|improve this answer












Restart your system.
Press f2 key while loading.
Goto boot option.
Press f5/f6 to change values (which os you want to install keep it in first place.).
Enter f10 key....It may solve your problem.
.
.
.
If not enter this in grub rescue mode....
ls
(hd0) (hd0,msdos6) (hd0,msdos5)....(hd0,msdos1)
OR
(hd0) (hd0,gpt6).....(hd0,gpt1)



set boot=(hd0,gpt6) OR set boot=(hd0,msdos6)
set prefix=(hd0,gpt6)/boot/grub OR use msdos6 instead.
insmod normal
normal
This may solve your problem.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 9 '17 at 8:11









Pavan Rao

11




11











  • these are various ways to launch grub. this is not the issue as OP states. grub launches but drops to recovery mode. The issue is that the grub config file is missing
    – ravery
    Jul 9 '17 at 8:23
















  • these are various ways to launch grub. this is not the issue as OP states. grub launches but drops to recovery mode. The issue is that the grub config file is missing
    – ravery
    Jul 9 '17 at 8:23















these are various ways to launch grub. this is not the issue as OP states. grub launches but drops to recovery mode. The issue is that the grub config file is missing
– ravery
Jul 9 '17 at 8:23




these are various ways to launch grub. this is not the issue as OP states. grub launches but drops to recovery mode. The issue is that the grub config file is missing
– ravery
Jul 9 '17 at 8:23


Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491