Boot-repair Failure: Unable to locate package grub-common:i386Windows 8 ask for repair when launched from...
Why are they 'nude photos'?
RPI3B+: What are the four components below the HDMI connector called?
Is it possible to create a craft with specific bones, like the bones of a forgotten beast?
How can I truly shut down ssh server?
Why does this potentiometer in an op-amp feedback path cause noise when adjusted?
Why is the ladder of the LM always in the dark side of the LM?
Is it unbalanced to allow a monk with the Tavern Brawler feat to use improvised weapons as monk weapons?
Some interesting calculation puzzle that I made
Is anyone advocating the promotion of homosexuality in UK schools?
How can I fix the dull colors I am getting in Ubuntu 19.04 Terminal?
What is the measurable difference between dry basil and fresh?
Is "De qui parles-tu" (for example) as formal as it is in English, or is it normal for the French to casually say that
Adding labels to a matrix
Is there any word for "disobedience to God"?
What happens to unproductive professors?
Is a request to book a business flight ticket for a graduate student an unreasonable one?
Why did Harry Potter get a bedroom?
How to deal with moral/legal subjects in writing?
Can you cast a blanket Invisibility and let the targets see each other?
Received a dinner invitation through my employer's email, is it ok to attend?
Linking a filetype to a syntax file of a different name
How would vampires avoid contracting diseases?
Is English unusual in having no second person plural form?
Terry Pratchett book with a lawyer dragon and sheep
Boot-repair Failure: Unable to locate package grub-common:i386
Windows 8 ask for repair when launched from grubReparing grub/bootboot repair doesn't find windowsDual-boot windows/debian, no boot menu?how to repair uefi boot optionAdding Linux to GRUB boot menu in UEFI mode to dual boot with Windows 10Grub repair after Window installBest way to repair the grub in this caseboot-repair: An error occured during repairBoot repair disk on mint live usb
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am on a system dual-booting Windows and Debian (usually using the latter), and a recent Windows update appears to have wreaked havoc on the Debian boot system. I managed to boot Windows again, but not Linux. Following online suggestions, I created a Live USB of Ubuntu, and booted from that. Then I have installed and run the boot-repair utility. The utility instructs me to type several lines including
sudo chroot "/mnt/boot-sav/sda6" apt-get purge -y grub*-common grub-common:i386
To which I receive the error
E: Unable to locate package grub-common:i386
I am given to understand the issue may have to do with having UEFI vs BIOS (I believe I have UEFI), but do not understand this well. In any case I have subsequently run the boot-repair BootInfo Summary utility which created the following file http://paste.ubuntu.com/p/N8Z95MwB9p/
Any suggestions on how to fix this issue with boot-repair / the boot system would be greatly appreciated.
Thanks!
--Edit--
In what was probably an ill-advised move, I decided to try once again to solve the issue using online resources. From a Linux live disk I ran the following sudo mount /dev/sda1 /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sda I cancelled the second command partway through with CTRL-C when I saw it was trying to install i386 version. Here is a new pastebin, which I believe to be different (and worse..) than the previous one. https://paste.ubuntu.com/p/ZpCm38wmRc/
--Edit--
As per my comment below, I managed to fix the grub by not using boot-repair and simply reinstalling grub (sorry, I do not remember the exact commands used). Booting Debian still did not seem to work, so I just used Windows for a few days until I had time to work on the problem more. I sat down to work on it today and ... Debian boots fine. Everything is working as normal. I have no idea why it suddenly works (and am a bit afraid that something is wrong behind the scenes), but that's all for now I guess. I will note that in the meantime I disabled Windows Fast Boot (must have been reenabled by the Windows update) so maybe that did the trick, although I didn't see any immediate change.
Also I realize that none of this is directly related to the original question about boot-repair, which I did not solve.
debian boot dual-boot grub uefi
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
bumped to the homepage by Community♦ 1 hour 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 am on a system dual-booting Windows and Debian (usually using the latter), and a recent Windows update appears to have wreaked havoc on the Debian boot system. I managed to boot Windows again, but not Linux. Following online suggestions, I created a Live USB of Ubuntu, and booted from that. Then I have installed and run the boot-repair utility. The utility instructs me to type several lines including
sudo chroot "/mnt/boot-sav/sda6" apt-get purge -y grub*-common grub-common:i386
To which I receive the error
E: Unable to locate package grub-common:i386
I am given to understand the issue may have to do with having UEFI vs BIOS (I believe I have UEFI), but do not understand this well. In any case I have subsequently run the boot-repair BootInfo Summary utility which created the following file http://paste.ubuntu.com/p/N8Z95MwB9p/
Any suggestions on how to fix this issue with boot-repair / the boot system would be greatly appreciated.
Thanks!
--Edit--
In what was probably an ill-advised move, I decided to try once again to solve the issue using online resources. From a Linux live disk I ran the following sudo mount /dev/sda1 /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sda I cancelled the second command partway through with CTRL-C when I saw it was trying to install i386 version. Here is a new pastebin, which I believe to be different (and worse..) than the previous one. https://paste.ubuntu.com/p/ZpCm38wmRc/
--Edit--
As per my comment below, I managed to fix the grub by not using boot-repair and simply reinstalling grub (sorry, I do not remember the exact commands used). Booting Debian still did not seem to work, so I just used Windows for a few days until I had time to work on the problem more. I sat down to work on it today and ... Debian boots fine. Everything is working as normal. I have no idea why it suddenly works (and am a bit afraid that something is wrong behind the scenes), but that's all for now I guess. I will note that in the meantime I disabled Windows Fast Boot (must have been reenabled by the Windows update) so maybe that did the trick, although I didn't see any immediate change.
Also I realize that none of this is directly related to the original question about boot-repair, which I did not solve.
debian boot dual-boot grub uefi
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
but do not understand this well... Yes, it show and that's the problem, not understanding you have UEFI, not BIOS, and that fact alone changes a lot of things. In order to understand UEFI and dual-booting with Windows read this: askubuntu.com/questions/221835/… Whatever you've been reading is NOT applicable in UEFI. Next, the good news:
– user252181
May 9 '18 at 16:33
These articles might be useful for understanding: rodsbooks.com/efi-bootloaders (start right with "principles" and see if it helps).
– Michael Shigorin
May 10 '18 at 7:31
add a comment |
I am on a system dual-booting Windows and Debian (usually using the latter), and a recent Windows update appears to have wreaked havoc on the Debian boot system. I managed to boot Windows again, but not Linux. Following online suggestions, I created a Live USB of Ubuntu, and booted from that. Then I have installed and run the boot-repair utility. The utility instructs me to type several lines including
sudo chroot "/mnt/boot-sav/sda6" apt-get purge -y grub*-common grub-common:i386
To which I receive the error
E: Unable to locate package grub-common:i386
I am given to understand the issue may have to do with having UEFI vs BIOS (I believe I have UEFI), but do not understand this well. In any case I have subsequently run the boot-repair BootInfo Summary utility which created the following file http://paste.ubuntu.com/p/N8Z95MwB9p/
Any suggestions on how to fix this issue with boot-repair / the boot system would be greatly appreciated.
Thanks!
--Edit--
In what was probably an ill-advised move, I decided to try once again to solve the issue using online resources. From a Linux live disk I ran the following sudo mount /dev/sda1 /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sda I cancelled the second command partway through with CTRL-C when I saw it was trying to install i386 version. Here is a new pastebin, which I believe to be different (and worse..) than the previous one. https://paste.ubuntu.com/p/ZpCm38wmRc/
--Edit--
As per my comment below, I managed to fix the grub by not using boot-repair and simply reinstalling grub (sorry, I do not remember the exact commands used). Booting Debian still did not seem to work, so I just used Windows for a few days until I had time to work on the problem more. I sat down to work on it today and ... Debian boots fine. Everything is working as normal. I have no idea why it suddenly works (and am a bit afraid that something is wrong behind the scenes), but that's all for now I guess. I will note that in the meantime I disabled Windows Fast Boot (must have been reenabled by the Windows update) so maybe that did the trick, although I didn't see any immediate change.
Also I realize that none of this is directly related to the original question about boot-repair, which I did not solve.
debian boot dual-boot grub uefi
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
I am on a system dual-booting Windows and Debian (usually using the latter), and a recent Windows update appears to have wreaked havoc on the Debian boot system. I managed to boot Windows again, but not Linux. Following online suggestions, I created a Live USB of Ubuntu, and booted from that. Then I have installed and run the boot-repair utility. The utility instructs me to type several lines including
sudo chroot "/mnt/boot-sav/sda6" apt-get purge -y grub*-common grub-common:i386
To which I receive the error
E: Unable to locate package grub-common:i386
I am given to understand the issue may have to do with having UEFI vs BIOS (I believe I have UEFI), but do not understand this well. In any case I have subsequently run the boot-repair BootInfo Summary utility which created the following file http://paste.ubuntu.com/p/N8Z95MwB9p/
Any suggestions on how to fix this issue with boot-repair / the boot system would be greatly appreciated.
Thanks!
--Edit--
In what was probably an ill-advised move, I decided to try once again to solve the issue using online resources. From a Linux live disk I ran the following sudo mount /dev/sda1 /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sda I cancelled the second command partway through with CTRL-C when I saw it was trying to install i386 version. Here is a new pastebin, which I believe to be different (and worse..) than the previous one. https://paste.ubuntu.com/p/ZpCm38wmRc/
--Edit--
As per my comment below, I managed to fix the grub by not using boot-repair and simply reinstalling grub (sorry, I do not remember the exact commands used). Booting Debian still did not seem to work, so I just used Windows for a few days until I had time to work on the problem more. I sat down to work on it today and ... Debian boots fine. Everything is working as normal. I have no idea why it suddenly works (and am a bit afraid that something is wrong behind the scenes), but that's all for now I guess. I will note that in the meantime I disabled Windows Fast Boot (must have been reenabled by the Windows update) so maybe that did the trick, although I didn't see any immediate change.
Also I realize that none of this is directly related to the original question about boot-repair, which I did not solve.
debian boot dual-boot grub uefi
debian boot dual-boot grub uefi
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
edited May 12 '18 at 2:32
ERosenberg
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
asked May 8 '18 at 16:04
ERosenbergERosenberg
12 bronze badges
12 bronze badges
bumped to the homepage by Community♦ 1 hour 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♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
but do not understand this well... Yes, it show and that's the problem, not understanding you have UEFI, not BIOS, and that fact alone changes a lot of things. In order to understand UEFI and dual-booting with Windows read this: askubuntu.com/questions/221835/… Whatever you've been reading is NOT applicable in UEFI. Next, the good news:
– user252181
May 9 '18 at 16:33
These articles might be useful for understanding: rodsbooks.com/efi-bootloaders (start right with "principles" and see if it helps).
– Michael Shigorin
May 10 '18 at 7:31
add a comment |
but do not understand this well... Yes, it show and that's the problem, not understanding you have UEFI, not BIOS, and that fact alone changes a lot of things. In order to understand UEFI and dual-booting with Windows read this: askubuntu.com/questions/221835/… Whatever you've been reading is NOT applicable in UEFI. Next, the good news:
– user252181
May 9 '18 at 16:33
These articles might be useful for understanding: rodsbooks.com/efi-bootloaders (start right with "principles" and see if it helps).
– Michael Shigorin
May 10 '18 at 7:31
but do not understand this well... Yes, it show and that's the problem, not understanding you have UEFI, not BIOS, and that fact alone changes a lot of things. In order to understand UEFI and dual-booting with Windows read this: askubuntu.com/questions/221835/… Whatever you've been reading is NOT applicable in UEFI. Next, the good news:
– user252181
May 9 '18 at 16:33
but do not understand this well... Yes, it show and that's the problem, not understanding you have UEFI, not BIOS, and that fact alone changes a lot of things. In order to understand UEFI and dual-booting with Windows read this: askubuntu.com/questions/221835/… Whatever you've been reading is NOT applicable in UEFI. Next, the good news:
– user252181
May 9 '18 at 16:33
These articles might be useful for understanding: rodsbooks.com/efi-bootloaders (start right with "principles" and see if it helps).
– Michael Shigorin
May 10 '18 at 7:31
These articles might be useful for understanding: rodsbooks.com/efi-bootloaders (start right with "principles" and see if it helps).
– Michael Shigorin
May 10 '18 at 7:31
add a comment |
1 Answer
1
active
oldest
votes
Except for the fact the Windows update changed the boot order, there's nothing wrong with your dual-boot.
Please stop doing things that can't possibly work (but can make it worse), right NOW.
Just open UEFI settings > Boot menu and change the order back to "Debian" (You'll find that instead of "Debian" there's now "Windows boot manager") and it should boot with Grub as before. Boot Debian and do sudo update-grub for good measure.
The reason why you can do this (and don't need any commands or even booting a live session) is due to the UEFI specifications that allow for any and all installed OSes to be booted independently unlike what happened before with the old BIOS/MBR where only one bootloader - typically Grub in a Windows/Linux multi-boot replacing the Windows boot loader - could be installed in the MBR (Master Boot Record). As long as the ESP (EFI System Partition) still has the EFI files for a given OS it should boot. Yours are still there:
/EFI/Boot/bootx64.efi /EFI/debian/grubx64.efi
Hello, thank you for your reply! Firstly, I found your two comments, especially "yes it shows" in the first, to be unnecessarily condescending and rude -- I'm very grateful that you are trying to help, but would prefer not to be talked down to. Regarding your answer, I regret to say that it is incorrect, although I take responsibility for insufficiently describng the situation. At the time I originally posted GRUB was not booting at all. I went to the boot menu and switched to Windows in order to use my machine and make the live disk.
– ERosenberg
May 10 '18 at 16:58
From the live disk I reinstalled GRUBx64. The current state of the machine is as follows: The normal GRUB boot menu now appears when I turn it on. From there I can select the Windows boot and everything will work normally. Alternately I can boot Debian in Recovery Mode and it will boot up just fine. However if I try to boot Debian normally it hangs almost immediately. I may post another question about this, since it is a different problem than that listed here.
– ERosenberg
May 10 '18 at 17:03
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f442586%2fboot-repair-failure-unable-to-locate-package-grub-commoni386%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Except for the fact the Windows update changed the boot order, there's nothing wrong with your dual-boot.
Please stop doing things that can't possibly work (but can make it worse), right NOW.
Just open UEFI settings > Boot menu and change the order back to "Debian" (You'll find that instead of "Debian" there's now "Windows boot manager") and it should boot with Grub as before. Boot Debian and do sudo update-grub for good measure.
The reason why you can do this (and don't need any commands or even booting a live session) is due to the UEFI specifications that allow for any and all installed OSes to be booted independently unlike what happened before with the old BIOS/MBR where only one bootloader - typically Grub in a Windows/Linux multi-boot replacing the Windows boot loader - could be installed in the MBR (Master Boot Record). As long as the ESP (EFI System Partition) still has the EFI files for a given OS it should boot. Yours are still there:
/EFI/Boot/bootx64.efi /EFI/debian/grubx64.efi
Hello, thank you for your reply! Firstly, I found your two comments, especially "yes it shows" in the first, to be unnecessarily condescending and rude -- I'm very grateful that you are trying to help, but would prefer not to be talked down to. Regarding your answer, I regret to say that it is incorrect, although I take responsibility for insufficiently describng the situation. At the time I originally posted GRUB was not booting at all. I went to the boot menu and switched to Windows in order to use my machine and make the live disk.
– ERosenberg
May 10 '18 at 16:58
From the live disk I reinstalled GRUBx64. The current state of the machine is as follows: The normal GRUB boot menu now appears when I turn it on. From there I can select the Windows boot and everything will work normally. Alternately I can boot Debian in Recovery Mode and it will boot up just fine. However if I try to boot Debian normally it hangs almost immediately. I may post another question about this, since it is a different problem than that listed here.
– ERosenberg
May 10 '18 at 17:03
add a comment |
Except for the fact the Windows update changed the boot order, there's nothing wrong with your dual-boot.
Please stop doing things that can't possibly work (but can make it worse), right NOW.
Just open UEFI settings > Boot menu and change the order back to "Debian" (You'll find that instead of "Debian" there's now "Windows boot manager") and it should boot with Grub as before. Boot Debian and do sudo update-grub for good measure.
The reason why you can do this (and don't need any commands or even booting a live session) is due to the UEFI specifications that allow for any and all installed OSes to be booted independently unlike what happened before with the old BIOS/MBR where only one bootloader - typically Grub in a Windows/Linux multi-boot replacing the Windows boot loader - could be installed in the MBR (Master Boot Record). As long as the ESP (EFI System Partition) still has the EFI files for a given OS it should boot. Yours are still there:
/EFI/Boot/bootx64.efi /EFI/debian/grubx64.efi
Hello, thank you for your reply! Firstly, I found your two comments, especially "yes it shows" in the first, to be unnecessarily condescending and rude -- I'm very grateful that you are trying to help, but would prefer not to be talked down to. Regarding your answer, I regret to say that it is incorrect, although I take responsibility for insufficiently describng the situation. At the time I originally posted GRUB was not booting at all. I went to the boot menu and switched to Windows in order to use my machine and make the live disk.
– ERosenberg
May 10 '18 at 16:58
From the live disk I reinstalled GRUBx64. The current state of the machine is as follows: The normal GRUB boot menu now appears when I turn it on. From there I can select the Windows boot and everything will work normally. Alternately I can boot Debian in Recovery Mode and it will boot up just fine. However if I try to boot Debian normally it hangs almost immediately. I may post another question about this, since it is a different problem than that listed here.
– ERosenberg
May 10 '18 at 17:03
add a comment |
Except for the fact the Windows update changed the boot order, there's nothing wrong with your dual-boot.
Please stop doing things that can't possibly work (but can make it worse), right NOW.
Just open UEFI settings > Boot menu and change the order back to "Debian" (You'll find that instead of "Debian" there's now "Windows boot manager") and it should boot with Grub as before. Boot Debian and do sudo update-grub for good measure.
The reason why you can do this (and don't need any commands or even booting a live session) is due to the UEFI specifications that allow for any and all installed OSes to be booted independently unlike what happened before with the old BIOS/MBR where only one bootloader - typically Grub in a Windows/Linux multi-boot replacing the Windows boot loader - could be installed in the MBR (Master Boot Record). As long as the ESP (EFI System Partition) still has the EFI files for a given OS it should boot. Yours are still there:
/EFI/Boot/bootx64.efi /EFI/debian/grubx64.efi
Except for the fact the Windows update changed the boot order, there's nothing wrong with your dual-boot.
Please stop doing things that can't possibly work (but can make it worse), right NOW.
Just open UEFI settings > Boot menu and change the order back to "Debian" (You'll find that instead of "Debian" there's now "Windows boot manager") and it should boot with Grub as before. Boot Debian and do sudo update-grub for good measure.
The reason why you can do this (and don't need any commands or even booting a live session) is due to the UEFI specifications that allow for any and all installed OSes to be booted independently unlike what happened before with the old BIOS/MBR where only one bootloader - typically Grub in a Windows/Linux multi-boot replacing the Windows boot loader - could be installed in the MBR (Master Boot Record). As long as the ESP (EFI System Partition) still has the EFI files for a given OS it should boot. Yours are still there:
/EFI/Boot/bootx64.efi /EFI/debian/grubx64.efi
answered May 9 '18 at 16:44
user252181
Hello, thank you for your reply! Firstly, I found your two comments, especially "yes it shows" in the first, to be unnecessarily condescending and rude -- I'm very grateful that you are trying to help, but would prefer not to be talked down to. Regarding your answer, I regret to say that it is incorrect, although I take responsibility for insufficiently describng the situation. At the time I originally posted GRUB was not booting at all. I went to the boot menu and switched to Windows in order to use my machine and make the live disk.
– ERosenberg
May 10 '18 at 16:58
From the live disk I reinstalled GRUBx64. The current state of the machine is as follows: The normal GRUB boot menu now appears when I turn it on. From there I can select the Windows boot and everything will work normally. Alternately I can boot Debian in Recovery Mode and it will boot up just fine. However if I try to boot Debian normally it hangs almost immediately. I may post another question about this, since it is a different problem than that listed here.
– ERosenberg
May 10 '18 at 17:03
add a comment |
Hello, thank you for your reply! Firstly, I found your two comments, especially "yes it shows" in the first, to be unnecessarily condescending and rude -- I'm very grateful that you are trying to help, but would prefer not to be talked down to. Regarding your answer, I regret to say that it is incorrect, although I take responsibility for insufficiently describng the situation. At the time I originally posted GRUB was not booting at all. I went to the boot menu and switched to Windows in order to use my machine and make the live disk.
– ERosenberg
May 10 '18 at 16:58
From the live disk I reinstalled GRUBx64. The current state of the machine is as follows: The normal GRUB boot menu now appears when I turn it on. From there I can select the Windows boot and everything will work normally. Alternately I can boot Debian in Recovery Mode and it will boot up just fine. However if I try to boot Debian normally it hangs almost immediately. I may post another question about this, since it is a different problem than that listed here.
– ERosenberg
May 10 '18 at 17:03
Hello, thank you for your reply! Firstly, I found your two comments, especially "yes it shows" in the first, to be unnecessarily condescending and rude -- I'm very grateful that you are trying to help, but would prefer not to be talked down to. Regarding your answer, I regret to say that it is incorrect, although I take responsibility for insufficiently describng the situation. At the time I originally posted GRUB was not booting at all. I went to the boot menu and switched to Windows in order to use my machine and make the live disk.
– ERosenberg
May 10 '18 at 16:58
Hello, thank you for your reply! Firstly, I found your two comments, especially "yes it shows" in the first, to be unnecessarily condescending and rude -- I'm very grateful that you are trying to help, but would prefer not to be talked down to. Regarding your answer, I regret to say that it is incorrect, although I take responsibility for insufficiently describng the situation. At the time I originally posted GRUB was not booting at all. I went to the boot menu and switched to Windows in order to use my machine and make the live disk.
– ERosenberg
May 10 '18 at 16:58
From the live disk I reinstalled GRUBx64. The current state of the machine is as follows: The normal GRUB boot menu now appears when I turn it on. From there I can select the Windows boot and everything will work normally. Alternately I can boot Debian in Recovery Mode and it will boot up just fine. However if I try to boot Debian normally it hangs almost immediately. I may post another question about this, since it is a different problem than that listed here.
– ERosenberg
May 10 '18 at 17:03
From the live disk I reinstalled GRUBx64. The current state of the machine is as follows: The normal GRUB boot menu now appears when I turn it on. From there I can select the Windows boot and everything will work normally. Alternately I can boot Debian in Recovery Mode and it will boot up just fine. However if I try to boot Debian normally it hangs almost immediately. I may post another question about this, since it is a different problem than that listed here.
– ERosenberg
May 10 '18 at 17:03
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f442586%2fboot-repair-failure-unable-to-locate-package-grub-commoni386%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
but do not understand this well... Yes, it show and that's the problem, not understanding you have UEFI, not BIOS, and that fact alone changes a lot of things. In order to understand UEFI and dual-booting with Windows read this: askubuntu.com/questions/221835/… Whatever you've been reading is NOT applicable in UEFI. Next, the good news:
– user252181
May 9 '18 at 16:33
These articles might be useful for understanding: rodsbooks.com/efi-bootloaders (start right with "principles" and see if it helps).
– Michael Shigorin
May 10 '18 at 7:31