My linux has got stuck in grub rescue mode
up vote
0
down vote
favorite
What all .mod files do I need?
I found normal.mod, but now it's asking for terminal.mod
So, instead of booting up a thousand times and getting a screen staring blankly at my face, asking for a new file every time, I thought it would be better to download all the .mod files needed in one go.
Please help.
16.04 dual-boot
asked Feb 24 at 11:00
kesarling
11
add a comment |
up vote
0
down vote
favorite
What all .mod files do I need?
I found normal.mod, but now it's asking for terminal.mod
So, instead of booting up a thousand times and getting a screen staring blankly at my face, asking for a new file every time, I thought it would be better to download all the .mod files needed in one go.
Please help.
16.04 dual-boot
asked Feb 24 at 11:00
kesarling
11
1
What are the results of the commandapt policy grub-efi-amd64-bin? Unless your computer has an ARM processor one of the files in grub-efi-* where the * is a wildcard has all the .mod files that you need.
– karel
Feb 24 at 11:06
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
What all .mod files do I need?
I found normal.mod, but now it's asking for terminal.mod
So, instead of booting up a thousand times and getting a screen staring blankly at my face, asking for a new file every time, I thought it would be better to download all the .mod files needed in one go.
Please help.
16.04 dual-boot
asked Feb 24 at 11:00
kesarling
11
What all .mod files do I need?
I found normal.mod, but now it's asking for terminal.mod
So, instead of booting up a thousand times and getting a screen staring blankly at my face, asking for a new file every time, I thought it would be better to download all the .mod files needed in one go.
Please help.
16.04 dual-boot
16.04 dual-boot
asked Feb 24 at 11:00
kesarling
11
asked Feb 24 at 11:00
kesarling
11
edited Dec 3 at 7:31
asked Feb 24 at 11:00
kesarling
11
asked Feb 24 at 11:00
kesarling
11
asked Feb 24 at 11:00
kesarling
11
11
1
What are the results of the commandapt policy grub-efi-amd64-bin? Unless your computer has an ARM processor one of the files in grub-efi-* where the * is a wildcard has all the .mod files that you need.
– karel
Feb 24 at 11:06
add a comment |
1
What are the results of the commandapt policy grub-efi-amd64-bin? Unless your computer has an ARM processor one of the files in grub-efi-* where the * is a wildcard has all the .mod files that you need.
– karel
Feb 24 at 11:06
1
1
What are the results of the command
apt policy grub-efi-amd64-bin ? Unless your computer has an ARM processor one of the files in grub-efi-* where the * is a wildcard has all the .mod files that you need.– karel
Feb 24 at 11:06
What are the results of the command
apt policy grub-efi-amd64-bin ? Unless your computer has an ARM processor one of the files in grub-efi-* where the * is a wildcard has all the .mod files that you need.– karel
Feb 24 at 11:06
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
- Switch on the laptop, wait till you get the Grub Rescue Screen
- Type the following commands
- ls
- It will show you a list of partions you have made
You will get something like this (hd0),(hd0,msdos1)(hd0,msdos2)(hd0,msdos4)
You need to find which drive is your Ubuntu root for which type the following:
- set prefix= (hd0,msdos1)/boot/grub
If it’s not the root drive you will get an error message "unknown filesystem".
In that case try the same command with the next partion, ex: - set prefix=(hd0,msdos2)/boot/grub
If you are not getting an error: Congrats, you have found your root drive. You can proceed to the next command after that:- set prefix=(hd0,msdos1)/boot/grub
- insmod normal
- normal
- Your PC will now boot successfully. Now select Ubuntu & login.
- Open Terminal( Ctr+Alt+T or use the search)
- sudo update-grub
- sudo grub-install /dev/sda
Now the bootloader error is fixed you should be able to boot your laptop normally & even your data is intact.
Note: If sudo update-grub didn't work, type sudo grub-update
Once In my case, grub-update didn't happen same day but few days alter alongwith sudo apt dist-upgrade
answered Feb 24 at 13:05
Manasvee Kumar
155
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
- Switch on the laptop, wait till you get the Grub Rescue Screen
- Type the following commands
- ls
- It will show you a list of partions you have made
You will get something like this (hd0),(hd0,msdos1)(hd0,msdos2)(hd0,msdos4)
You need to find which drive is your Ubuntu root for which type the following:
- set prefix= (hd0,msdos1)/boot/grub
If it’s not the root drive you will get an error message "unknown filesystem".
In that case try the same command with the next partion, ex: - set prefix=(hd0,msdos2)/boot/grub
If you are not getting an error: Congrats, you have found your root drive. You can proceed to the next command after that:- set prefix=(hd0,msdos1)/boot/grub
- insmod normal
- normal
- Your PC will now boot successfully. Now select Ubuntu & login.
- Open Terminal( Ctr+Alt+T or use the search)
- sudo update-grub
- sudo grub-install /dev/sda
Now the bootloader error is fixed you should be able to boot your laptop normally & even your data is intact.
Note: If sudo update-grub didn't work, type sudo grub-update
Once In my case, grub-update didn't happen same day but few days alter alongwith sudo apt dist-upgrade
answered Feb 24 at 13:05
Manasvee Kumar
155
add a comment |
up vote
0
down vote
- Switch on the laptop, wait till you get the Grub Rescue Screen
- Type the following commands
- ls
- It will show you a list of partions you have made
You will get something like this (hd0),(hd0,msdos1)(hd0,msdos2)(hd0,msdos4)
You need to find which drive is your Ubuntu root for which type the following:
- set prefix= (hd0,msdos1)/boot/grub
If it’s not the root drive you will get an error message "unknown filesystem".
In that case try the same command with the next partion, ex: - set prefix=(hd0,msdos2)/boot/grub
If you are not getting an error: Congrats, you have found your root drive. You can proceed to the next command after that:- set prefix=(hd0,msdos1)/boot/grub
- insmod normal
- normal
- Your PC will now boot successfully. Now select Ubuntu & login.
- Open Terminal( Ctr+Alt+T or use the search)
- sudo update-grub
- sudo grub-install /dev/sda
Now the bootloader error is fixed you should be able to boot your laptop normally & even your data is intact.
Note: If sudo update-grub didn't work, type sudo grub-update
Once In my case, grub-update didn't happen same day but few days alter alongwith sudo apt dist-upgrade
answered Feb 24 at 13:05
Manasvee Kumar
155
add a comment |
up vote
0
down vote
up vote
0
down vote
- Switch on the laptop, wait till you get the Grub Rescue Screen
- Type the following commands
- ls
- It will show you a list of partions you have made
You will get something like this (hd0),(hd0,msdos1)(hd0,msdos2)(hd0,msdos4)
You need to find which drive is your Ubuntu root for which type the following:
- set prefix= (hd0,msdos1)/boot/grub
If it’s not the root drive you will get an error message "unknown filesystem".
In that case try the same command with the next partion, ex: - set prefix=(hd0,msdos2)/boot/grub
If you are not getting an error: Congrats, you have found your root drive. You can proceed to the next command after that:- set prefix=(hd0,msdos1)/boot/grub
- insmod normal
- normal
- Your PC will now boot successfully. Now select Ubuntu & login.
- Open Terminal( Ctr+Alt+T or use the search)
- sudo update-grub
- sudo grub-install /dev/sda
Now the bootloader error is fixed you should be able to boot your laptop normally & even your data is intact.
Note: If sudo update-grub didn't work, type sudo grub-update
Once In my case, grub-update didn't happen same day but few days alter alongwith sudo apt dist-upgrade
answered Feb 24 at 13:05
Manasvee Kumar
155
- Switch on the laptop, wait till you get the Grub Rescue Screen
- Type the following commands
- ls
- It will show you a list of partions you have made
You will get something like this (hd0),(hd0,msdos1)(hd0,msdos2)(hd0,msdos4)
You need to find which drive is your Ubuntu root for which type the following:
- set prefix= (hd0,msdos1)/boot/grub
If it’s not the root drive you will get an error message "unknown filesystem".
In that case try the same command with the next partion, ex: - set prefix=(hd0,msdos2)/boot/grub
If you are not getting an error: Congrats, you have found your root drive. You can proceed to the next command after that:- set prefix=(hd0,msdos1)/boot/grub
- insmod normal
- normal
- Your PC will now boot successfully. Now select Ubuntu & login.
- Open Terminal( Ctr+Alt+T or use the search)
- sudo update-grub
- sudo grub-install /dev/sda
Now the bootloader error is fixed you should be able to boot your laptop normally & even your data is intact.
Note: If sudo update-grub didn't work, type sudo grub-update
Once In my case, grub-update didn't happen same day but few days alter alongwith sudo apt dist-upgrade
answered Feb 24 at 13:05
Manasvee Kumar
155
answered Feb 24 at 13:05
Manasvee Kumar
155
answered Feb 24 at 13:05
Manasvee Kumar
155
answered Feb 24 at 13:05
Manasvee Kumar
155
155
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009294%2fmy-linux-has-got-stuck-in-grub-rescue-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
What are the results of the command
apt policy grub-efi-amd64-bin? Unless your computer has an ARM processor one of the files in grub-efi-* where the * is a wildcard has all the .mod files that you need.– karel
Feb 24 at 11:06