Microsoft's Windows kills Debian grub after each start
I’m experiencing a trouble with my dual-boot windows and Debian ASUS PC.
Everything worked fine until a weeks ago when I entered into MS-windows after some months that I didn’t.
The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, if I select Debian boot it goes into the advanced setup menu of ASUS booting.
I then restored the grub, following the instructions for Debian and everything worked fine again, but if I enter into windows it happens again.
The only thing, when I do a “boot-install —recheck /dev/sda” from chroot it just tells me that the /efi/debian/grubx64.efi is a read-only file.
debian dual-boot grub asus
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
add a comment |
I’m experiencing a trouble with my dual-boot windows and Debian ASUS PC.
Everything worked fine until a weeks ago when I entered into MS-windows after some months that I didn’t.
The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, if I select Debian boot it goes into the advanced setup menu of ASUS booting.
I then restored the grub, following the instructions for Debian and everything worked fine again, but if I enter into windows it happens again.
The only thing, when I do a “boot-install —recheck /dev/sda” from chroot it just tells me that the /efi/debian/grubx64.efi is a read-only file.
debian dual-boot grub asus
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
fwiw, I was always told to install Windows first, then a second OS, because Windows will attempt to take over everything by rewriting boot code.
– Rob
Dec 27 '18 at 12:57
Yes, windows was already installed and I put Debian later
– ccc.nrc
Dec 27 '18 at 13:05
“The PC then booted directly into MS-windows and when I enter the boot menu at restart,… ” do you mean “The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, …”?
– ctrl-alt-delor
Dec 27 '18 at 13:19
@ctrl-alt-delor thanks a lot for your reply. Yes, I mean that when I later reboot and enter the boot menu (press ESC), if I select “Debian”, it does not start and goes straight to the “advanced menu” (like if I press F2 when PC reboot)
– ccc.nrc
Dec 27 '18 at 13:24
@ccc.nrc I updated your question for you (you can also do this).
– ctrl-alt-delor
Dec 27 '18 at 13:27
add a comment |
I’m experiencing a trouble with my dual-boot windows and Debian ASUS PC.
Everything worked fine until a weeks ago when I entered into MS-windows after some months that I didn’t.
The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, if I select Debian boot it goes into the advanced setup menu of ASUS booting.
I then restored the grub, following the instructions for Debian and everything worked fine again, but if I enter into windows it happens again.
The only thing, when I do a “boot-install —recheck /dev/sda” from chroot it just tells me that the /efi/debian/grubx64.efi is a read-only file.
debian dual-boot grub asus
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
I’m experiencing a trouble with my dual-boot windows and Debian ASUS PC.
Everything worked fine until a weeks ago when I entered into MS-windows after some months that I didn’t.
The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, if I select Debian boot it goes into the advanced setup menu of ASUS booting.
I then restored the grub, following the instructions for Debian and everything worked fine again, but if I enter into windows it happens again.
The only thing, when I do a “boot-install —recheck /dev/sda” from chroot it just tells me that the /efi/debian/grubx64.efi is a read-only file.
debian dual-boot grub asus
debian dual-boot grub asus
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
edited Dec 27 '18 at 14:10
Rui F Ribeiro
39.3k1479131
39.3k1479131
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
asked Dec 27 '18 at 12:50
ccc.nrcccc.nrc
42
42
fwiw, I was always told to install Windows first, then a second OS, because Windows will attempt to take over everything by rewriting boot code.
– Rob
Dec 27 '18 at 12:57
Yes, windows was already installed and I put Debian later
– ccc.nrc
Dec 27 '18 at 13:05
“The PC then booted directly into MS-windows and when I enter the boot menu at restart,… ” do you mean “The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, …”?
– ctrl-alt-delor
Dec 27 '18 at 13:19
@ctrl-alt-delor thanks a lot for your reply. Yes, I mean that when I later reboot and enter the boot menu (press ESC), if I select “Debian”, it does not start and goes straight to the “advanced menu” (like if I press F2 when PC reboot)
– ccc.nrc
Dec 27 '18 at 13:24
@ccc.nrc I updated your question for you (you can also do this).
– ctrl-alt-delor
Dec 27 '18 at 13:27
add a comment |
fwiw, I was always told to install Windows first, then a second OS, because Windows will attempt to take over everything by rewriting boot code.
– Rob
Dec 27 '18 at 12:57
Yes, windows was already installed and I put Debian later
– ccc.nrc
Dec 27 '18 at 13:05
“The PC then booted directly into MS-windows and when I enter the boot menu at restart,… ” do you mean “The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, …”?
– ctrl-alt-delor
Dec 27 '18 at 13:19
@ctrl-alt-delor thanks a lot for your reply. Yes, I mean that when I later reboot and enter the boot menu (press ESC), if I select “Debian”, it does not start and goes straight to the “advanced menu” (like if I press F2 when PC reboot)
– ccc.nrc
Dec 27 '18 at 13:24
@ccc.nrc I updated your question for you (you can also do this).
– ctrl-alt-delor
Dec 27 '18 at 13:27
fwiw, I was always told to install Windows first, then a second OS, because Windows will attempt to take over everything by rewriting boot code.
– Rob
Dec 27 '18 at 12:57
fwiw, I was always told to install Windows first, then a second OS, because Windows will attempt to take over everything by rewriting boot code.
– Rob
Dec 27 '18 at 12:57
Yes, windows was already installed and I put Debian later
– ccc.nrc
Dec 27 '18 at 13:05
Yes, windows was already installed and I put Debian later
– ccc.nrc
Dec 27 '18 at 13:05
“The PC then booted directly into MS-windows and when I enter the boot menu at restart,… ” do you mean “The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, …”?
– ctrl-alt-delor
Dec 27 '18 at 13:19
“The PC then booted directly into MS-windows and when I enter the boot menu at restart,… ” do you mean “The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, …”?
– ctrl-alt-delor
Dec 27 '18 at 13:19
@ctrl-alt-delor thanks a lot for your reply. Yes, I mean that when I later reboot and enter the boot menu (press ESC), if I select “Debian”, it does not start and goes straight to the “advanced menu” (like if I press F2 when PC reboot)
– ccc.nrc
Dec 27 '18 at 13:24
@ctrl-alt-delor thanks a lot for your reply. Yes, I mean that when I later reboot and enter the boot menu (press ESC), if I select “Debian”, it does not start and goes straight to the “advanced menu” (like if I press F2 when PC reboot)
– ccc.nrc
Dec 27 '18 at 13:24
@ccc.nrc I updated your question for you (you can also do this).
– ctrl-alt-delor
Dec 27 '18 at 13:27
@ccc.nrc I updated your question for you (you can also do this).
– ctrl-alt-delor
Dec 27 '18 at 13:27
add a comment |
1 Answer
1
active
oldest
votes
Solved. I finally reinstalled GRUB through debian rescue mode from USB (as explained in https://wiki.debian.org/GrubEFIReinstall) and then, once rebooted and entered in my debian OS (and connected to a network), I re-installed the updated grub:
apt-get install --reinstall grub-efi
At this point, I don't know exactly why, but if I asked the efi boot entries with:
efibootmgr --verbose
it showed 4 entries:
- boot0000* debian on HD pointing to file EFIdebiangrubx64x.efi
- boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- boot0002* Windows Boot Manager on HD pointing to file EFIMICROSOFTBOOTBOOTMGFW.EFI
- boot0003* UEFI (my USB with debian): note that it was inserted during installation and chroot session but no longer inserted.
So I supposed that it probably didn't "update weel" the boot entries and so I did:
sudo update-grub
and now everything goes well and if I ask for boot entries (efibootmgr --verbose):
- Boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- Boot0002* Windows Boot Manager on HD pointing to file
EFIMICROSOFTBOOTBOOTMGFW.EFI
Do not know exactly what happened, if somebody got a clue is welcomed!
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
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%2f491118%2fmicrosofts-windows-kills-debian-grub-after-each-start%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
Solved. I finally reinstalled GRUB through debian rescue mode from USB (as explained in https://wiki.debian.org/GrubEFIReinstall) and then, once rebooted and entered in my debian OS (and connected to a network), I re-installed the updated grub:
apt-get install --reinstall grub-efi
At this point, I don't know exactly why, but if I asked the efi boot entries with:
efibootmgr --verbose
it showed 4 entries:
- boot0000* debian on HD pointing to file EFIdebiangrubx64x.efi
- boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- boot0002* Windows Boot Manager on HD pointing to file EFIMICROSOFTBOOTBOOTMGFW.EFI
- boot0003* UEFI (my USB with debian): note that it was inserted during installation and chroot session but no longer inserted.
So I supposed that it probably didn't "update weel" the boot entries and so I did:
sudo update-grub
and now everything goes well and if I ask for boot entries (efibootmgr --verbose):
- Boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- Boot0002* Windows Boot Manager on HD pointing to file
EFIMICROSOFTBOOTBOOTMGFW.EFI
Do not know exactly what happened, if somebody got a clue is welcomed!
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
add a comment |
Solved. I finally reinstalled GRUB through debian rescue mode from USB (as explained in https://wiki.debian.org/GrubEFIReinstall) and then, once rebooted and entered in my debian OS (and connected to a network), I re-installed the updated grub:
apt-get install --reinstall grub-efi
At this point, I don't know exactly why, but if I asked the efi boot entries with:
efibootmgr --verbose
it showed 4 entries:
- boot0000* debian on HD pointing to file EFIdebiangrubx64x.efi
- boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- boot0002* Windows Boot Manager on HD pointing to file EFIMICROSOFTBOOTBOOTMGFW.EFI
- boot0003* UEFI (my USB with debian): note that it was inserted during installation and chroot session but no longer inserted.
So I supposed that it probably didn't "update weel" the boot entries and so I did:
sudo update-grub
and now everything goes well and if I ask for boot entries (efibootmgr --verbose):
- Boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- Boot0002* Windows Boot Manager on HD pointing to file
EFIMICROSOFTBOOTBOOTMGFW.EFI
Do not know exactly what happened, if somebody got a clue is welcomed!
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
add a comment |
Solved. I finally reinstalled GRUB through debian rescue mode from USB (as explained in https://wiki.debian.org/GrubEFIReinstall) and then, once rebooted and entered in my debian OS (and connected to a network), I re-installed the updated grub:
apt-get install --reinstall grub-efi
At this point, I don't know exactly why, but if I asked the efi boot entries with:
efibootmgr --verbose
it showed 4 entries:
- boot0000* debian on HD pointing to file EFIdebiangrubx64x.efi
- boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- boot0002* Windows Boot Manager on HD pointing to file EFIMICROSOFTBOOTBOOTMGFW.EFI
- boot0003* UEFI (my USB with debian): note that it was inserted during installation and chroot session but no longer inserted.
So I supposed that it probably didn't "update weel" the boot entries and so I did:
sudo update-grub
and now everything goes well and if I ask for boot entries (efibootmgr --verbose):
- Boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- Boot0002* Windows Boot Manager on HD pointing to file
EFIMICROSOFTBOOTBOOTMGFW.EFI
Do not know exactly what happened, if somebody got a clue is welcomed!
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
Solved. I finally reinstalled GRUB through debian rescue mode from USB (as explained in https://wiki.debian.org/GrubEFIReinstall) and then, once rebooted and entered in my debian OS (and connected to a network), I re-installed the updated grub:
apt-get install --reinstall grub-efi
At this point, I don't know exactly why, but if I asked the efi boot entries with:
efibootmgr --verbose
it showed 4 entries:
- boot0000* debian on HD pointing to file EFIdebiangrubx64x.efi
- boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- boot0002* Windows Boot Manager on HD pointing to file EFIMICROSOFTBOOTBOOTMGFW.EFI
- boot0003* UEFI (my USB with debian): note that it was inserted during installation and chroot session but no longer inserted.
So I supposed that it probably didn't "update weel" the boot entries and so I did:
sudo update-grub
and now everything goes well and if I ask for boot entries (efibootmgr --verbose):
- Boot0001* Windows Boot Manager on HD pointing to file EFIDEBIANGRUBX64.EFI
- Boot0002* Windows Boot Manager on HD pointing to file
EFIMICROSOFTBOOTBOOTMGFW.EFI
Do not know exactly what happened, if somebody got a clue is welcomed!
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
answered Dec 27 '18 at 18:48
ccc.nrcccc.nrc
42
42
add a comment |
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.
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%2funix.stackexchange.com%2fquestions%2f491118%2fmicrosofts-windows-kills-debian-grub-after-each-start%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
fwiw, I was always told to install Windows first, then a second OS, because Windows will attempt to take over everything by rewriting boot code.
– Rob
Dec 27 '18 at 12:57
Yes, windows was already installed and I put Debian later
– ccc.nrc
Dec 27 '18 at 13:05
“The PC then booted directly into MS-windows and when I enter the boot menu at restart,… ” do you mean “The PC then booted directly into MS-windows, later when I restart, and enter the boot menu, …”?
– ctrl-alt-delor
Dec 27 '18 at 13:19
@ctrl-alt-delor thanks a lot for your reply. Yes, I mean that when I later reboot and enter the boot menu (press ESC), if I select “Debian”, it does not start and goes straight to the “advanced menu” (like if I press F2 when PC reboot)
– ccc.nrc
Dec 27 '18 at 13:24
@ccc.nrc I updated your question for you (you can also do this).
– ctrl-alt-delor
Dec 27 '18 at 13:27