GRUB2 problem “/boot/grub/grubenv not found”
I cannot boot into Ubuntu
as everytime I click on grub
, it boots me into a shell type command prompt window. I do not know which commands to type. However, on pressing TAB, it suggests a list of commands that the "grub2 shell
" can take. When I type, load_env
it returns /boot/grub/grubenv not found
. Please help.
boot dual-boot grub2 uefi
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I cannot boot into Ubuntu
as everytime I click on grub
, it boots me into a shell type command prompt window. I do not know which commands to type. However, on pressing TAB, it suggests a list of commands that the "grub2 shell
" can take. When I type, load_env
it returns /boot/grub/grubenv not found
. Please help.
boot dual-boot grub2 uefi
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I cannot boot into Ubuntu
as everytime I click on grub
, it boots me into a shell type command prompt window. I do not know which commands to type. However, on pressing TAB, it suggests a list of commands that the "grub2 shell
" can take. When I type, load_env
it returns /boot/grub/grubenv not found
. Please help.
boot dual-boot grub2 uefi
I cannot boot into Ubuntu
as everytime I click on grub
, it boots me into a shell type command prompt window. I do not know which commands to type. However, on pressing TAB, it suggests a list of commands that the "grub2 shell
" can take. When I type, load_env
it returns /boot/grub/grubenv not found
. Please help.
boot dual-boot grub2 uefi
boot dual-boot grub2 uefi
edited Sep 13 '15 at 4:17
Ravan
5,773154577
5,773154577
asked Sep 12 '15 at 23:22
SkySky
114
114
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 4 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It looks like your linux installation is not complete or somewhat broken.
Possibly you have everything except appropriate boot commands installed, in which case you can try manually locate your appropriate vmlinuz-xxx
, initrd-xxx
files, load them into memory with linux
and initrd
commands, and boot with boot
.
For reference, check out available commands at http://www.gnu.org/software/grub/manual/grub.html#Commands and try to locate your original grub.cfg
with ls
, and look into it with cat
command to find out what options you have to append to linux
command after vmlinuz-xxx
filename.
- Hint:
set pager=1
helps you to usecat
with long text files. - Hint2: files on other partitions can be referred as
(hd0,msdos2)/dir/file
, changing0
and2
to appropriate disk and partition number. Tab expansion is useful there, too.
add a comment |
A detailed file-by-file investigation could probably fix this problem with precision. That requires a great deal of expertise, though. Running the Boot Info Script, posting the RESULTS.txt
file to a pastebin site, and posting the URL to your document here can get you started down this path; however, this will be a tedious process and there's no guarantee you'll find a solution.
Three other relatively easy options come to mind:
- Re-install Ubuntu and hope that whatever created the problem doesn't recur. This is a reasonable course of action if this is a fresh install; however, if you'd previously been booting and it's suddenly failed, you presumably have personal data files that you don't want to risk in this way. (It's possible to re-install without damaging your personal files, but there are too many ways in which this can go wrong for me to blithely suggest that you attempt it.)
- Run the Boot Repair tool on your computer. This tool analyzes your installation and attempts to repair Ubuntu boot problems automatically. It often succeeds, but its success rate is not 100%. If you can't boot at all right now, it's unlikely you'll make matters worse; but if you can boot another OS in some way, there's a slim chance that Boot Repair will interfere with that boot.
- You've included the UEFI tag. If you're booting via EFI, or even if you've got an EFI firmware but are booting in BIOS/CSM/legacy mode, you can download and prepare the CD-R or USB flash drive version of my rEFInd boot manager. If Secure Boot is disabled, you should then be able to boot rEFInd, and it should enable you to start Ubuntu. You can then either attempt to repair your GRUB installation (by re-installing the GRUB package, doing a
sudo update-grub
, or otherwise analyzing and fixing the problem) or install the rEFInd PPA or Debian package to bypass GRUB and its current problem and use rEFInd instead. This approach is unlikely to create new problems, since it involves making no changes to your hard disk until you've already successfully booted Ubuntu; but it applies only to EFI-based computers, and even then there are a number of situations in which it won't work.
None of these approaches is guaranteed to work, but there's a good chance that one of them will help you out.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f673489%2fgrub2-problem-boot-grub-grubenv-not-found%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It looks like your linux installation is not complete or somewhat broken.
Possibly you have everything except appropriate boot commands installed, in which case you can try manually locate your appropriate vmlinuz-xxx
, initrd-xxx
files, load them into memory with linux
and initrd
commands, and boot with boot
.
For reference, check out available commands at http://www.gnu.org/software/grub/manual/grub.html#Commands and try to locate your original grub.cfg
with ls
, and look into it with cat
command to find out what options you have to append to linux
command after vmlinuz-xxx
filename.
- Hint:
set pager=1
helps you to usecat
with long text files. - Hint2: files on other partitions can be referred as
(hd0,msdos2)/dir/file
, changing0
and2
to appropriate disk and partition number. Tab expansion is useful there, too.
add a comment |
It looks like your linux installation is not complete or somewhat broken.
Possibly you have everything except appropriate boot commands installed, in which case you can try manually locate your appropriate vmlinuz-xxx
, initrd-xxx
files, load them into memory with linux
and initrd
commands, and boot with boot
.
For reference, check out available commands at http://www.gnu.org/software/grub/manual/grub.html#Commands and try to locate your original grub.cfg
with ls
, and look into it with cat
command to find out what options you have to append to linux
command after vmlinuz-xxx
filename.
- Hint:
set pager=1
helps you to usecat
with long text files. - Hint2: files on other partitions can be referred as
(hd0,msdos2)/dir/file
, changing0
and2
to appropriate disk and partition number. Tab expansion is useful there, too.
add a comment |
It looks like your linux installation is not complete or somewhat broken.
Possibly you have everything except appropriate boot commands installed, in which case you can try manually locate your appropriate vmlinuz-xxx
, initrd-xxx
files, load them into memory with linux
and initrd
commands, and boot with boot
.
For reference, check out available commands at http://www.gnu.org/software/grub/manual/grub.html#Commands and try to locate your original grub.cfg
with ls
, and look into it with cat
command to find out what options you have to append to linux
command after vmlinuz-xxx
filename.
- Hint:
set pager=1
helps you to usecat
with long text files. - Hint2: files on other partitions can be referred as
(hd0,msdos2)/dir/file
, changing0
and2
to appropriate disk and partition number. Tab expansion is useful there, too.
It looks like your linux installation is not complete or somewhat broken.
Possibly you have everything except appropriate boot commands installed, in which case you can try manually locate your appropriate vmlinuz-xxx
, initrd-xxx
files, load them into memory with linux
and initrd
commands, and boot with boot
.
For reference, check out available commands at http://www.gnu.org/software/grub/manual/grub.html#Commands and try to locate your original grub.cfg
with ls
, and look into it with cat
command to find out what options you have to append to linux
command after vmlinuz-xxx
filename.
- Hint:
set pager=1
helps you to usecat
with long text files. - Hint2: files on other partitions can be referred as
(hd0,msdos2)/dir/file
, changing0
and2
to appropriate disk and partition number. Tab expansion is useful there, too.
answered Sep 13 '15 at 0:37
korckorc
43443
43443
add a comment |
add a comment |
A detailed file-by-file investigation could probably fix this problem with precision. That requires a great deal of expertise, though. Running the Boot Info Script, posting the RESULTS.txt
file to a pastebin site, and posting the URL to your document here can get you started down this path; however, this will be a tedious process and there's no guarantee you'll find a solution.
Three other relatively easy options come to mind:
- Re-install Ubuntu and hope that whatever created the problem doesn't recur. This is a reasonable course of action if this is a fresh install; however, if you'd previously been booting and it's suddenly failed, you presumably have personal data files that you don't want to risk in this way. (It's possible to re-install without damaging your personal files, but there are too many ways in which this can go wrong for me to blithely suggest that you attempt it.)
- Run the Boot Repair tool on your computer. This tool analyzes your installation and attempts to repair Ubuntu boot problems automatically. It often succeeds, but its success rate is not 100%. If you can't boot at all right now, it's unlikely you'll make matters worse; but if you can boot another OS in some way, there's a slim chance that Boot Repair will interfere with that boot.
- You've included the UEFI tag. If you're booting via EFI, or even if you've got an EFI firmware but are booting in BIOS/CSM/legacy mode, you can download and prepare the CD-R or USB flash drive version of my rEFInd boot manager. If Secure Boot is disabled, you should then be able to boot rEFInd, and it should enable you to start Ubuntu. You can then either attempt to repair your GRUB installation (by re-installing the GRUB package, doing a
sudo update-grub
, or otherwise analyzing and fixing the problem) or install the rEFInd PPA or Debian package to bypass GRUB and its current problem and use rEFInd instead. This approach is unlikely to create new problems, since it involves making no changes to your hard disk until you've already successfully booted Ubuntu; but it applies only to EFI-based computers, and even then there are a number of situations in which it won't work.
None of these approaches is guaranteed to work, but there's a good chance that one of them will help you out.
add a comment |
A detailed file-by-file investigation could probably fix this problem with precision. That requires a great deal of expertise, though. Running the Boot Info Script, posting the RESULTS.txt
file to a pastebin site, and posting the URL to your document here can get you started down this path; however, this will be a tedious process and there's no guarantee you'll find a solution.
Three other relatively easy options come to mind:
- Re-install Ubuntu and hope that whatever created the problem doesn't recur. This is a reasonable course of action if this is a fresh install; however, if you'd previously been booting and it's suddenly failed, you presumably have personal data files that you don't want to risk in this way. (It's possible to re-install without damaging your personal files, but there are too many ways in which this can go wrong for me to blithely suggest that you attempt it.)
- Run the Boot Repair tool on your computer. This tool analyzes your installation and attempts to repair Ubuntu boot problems automatically. It often succeeds, but its success rate is not 100%. If you can't boot at all right now, it's unlikely you'll make matters worse; but if you can boot another OS in some way, there's a slim chance that Boot Repair will interfere with that boot.
- You've included the UEFI tag. If you're booting via EFI, or even if you've got an EFI firmware but are booting in BIOS/CSM/legacy mode, you can download and prepare the CD-R or USB flash drive version of my rEFInd boot manager. If Secure Boot is disabled, you should then be able to boot rEFInd, and it should enable you to start Ubuntu. You can then either attempt to repair your GRUB installation (by re-installing the GRUB package, doing a
sudo update-grub
, or otherwise analyzing and fixing the problem) or install the rEFInd PPA or Debian package to bypass GRUB and its current problem and use rEFInd instead. This approach is unlikely to create new problems, since it involves making no changes to your hard disk until you've already successfully booted Ubuntu; but it applies only to EFI-based computers, and even then there are a number of situations in which it won't work.
None of these approaches is guaranteed to work, but there's a good chance that one of them will help you out.
add a comment |
A detailed file-by-file investigation could probably fix this problem with precision. That requires a great deal of expertise, though. Running the Boot Info Script, posting the RESULTS.txt
file to a pastebin site, and posting the URL to your document here can get you started down this path; however, this will be a tedious process and there's no guarantee you'll find a solution.
Three other relatively easy options come to mind:
- Re-install Ubuntu and hope that whatever created the problem doesn't recur. This is a reasonable course of action if this is a fresh install; however, if you'd previously been booting and it's suddenly failed, you presumably have personal data files that you don't want to risk in this way. (It's possible to re-install without damaging your personal files, but there are too many ways in which this can go wrong for me to blithely suggest that you attempt it.)
- Run the Boot Repair tool on your computer. This tool analyzes your installation and attempts to repair Ubuntu boot problems automatically. It often succeeds, but its success rate is not 100%. If you can't boot at all right now, it's unlikely you'll make matters worse; but if you can boot another OS in some way, there's a slim chance that Boot Repair will interfere with that boot.
- You've included the UEFI tag. If you're booting via EFI, or even if you've got an EFI firmware but are booting in BIOS/CSM/legacy mode, you can download and prepare the CD-R or USB flash drive version of my rEFInd boot manager. If Secure Boot is disabled, you should then be able to boot rEFInd, and it should enable you to start Ubuntu. You can then either attempt to repair your GRUB installation (by re-installing the GRUB package, doing a
sudo update-grub
, or otherwise analyzing and fixing the problem) or install the rEFInd PPA or Debian package to bypass GRUB and its current problem and use rEFInd instead. This approach is unlikely to create new problems, since it involves making no changes to your hard disk until you've already successfully booted Ubuntu; but it applies only to EFI-based computers, and even then there are a number of situations in which it won't work.
None of these approaches is guaranteed to work, but there's a good chance that one of them will help you out.
A detailed file-by-file investigation could probably fix this problem with precision. That requires a great deal of expertise, though. Running the Boot Info Script, posting the RESULTS.txt
file to a pastebin site, and posting the URL to your document here can get you started down this path; however, this will be a tedious process and there's no guarantee you'll find a solution.
Three other relatively easy options come to mind:
- Re-install Ubuntu and hope that whatever created the problem doesn't recur. This is a reasonable course of action if this is a fresh install; however, if you'd previously been booting and it's suddenly failed, you presumably have personal data files that you don't want to risk in this way. (It's possible to re-install without damaging your personal files, but there are too many ways in which this can go wrong for me to blithely suggest that you attempt it.)
- Run the Boot Repair tool on your computer. This tool analyzes your installation and attempts to repair Ubuntu boot problems automatically. It often succeeds, but its success rate is not 100%. If you can't boot at all right now, it's unlikely you'll make matters worse; but if you can boot another OS in some way, there's a slim chance that Boot Repair will interfere with that boot.
- You've included the UEFI tag. If you're booting via EFI, or even if you've got an EFI firmware but are booting in BIOS/CSM/legacy mode, you can download and prepare the CD-R or USB flash drive version of my rEFInd boot manager. If Secure Boot is disabled, you should then be able to boot rEFInd, and it should enable you to start Ubuntu. You can then either attempt to repair your GRUB installation (by re-installing the GRUB package, doing a
sudo update-grub
, or otherwise analyzing and fixing the problem) or install the rEFInd PPA or Debian package to bypass GRUB and its current problem and use rEFInd instead. This approach is unlikely to create new problems, since it involves making no changes to your hard disk until you've already successfully booted Ubuntu; but it applies only to EFI-based computers, and even then there are a number of situations in which it won't work.
None of these approaches is guaranteed to work, but there's a good chance that one of them will help you out.
answered Sep 13 '15 at 18:47
Rod SmithRod Smith
35.4k43970
35.4k43970
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.
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%2f673489%2fgrub2-problem-boot-grub-grubenv-not-found%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