Terminal crash during apt-upgrade on ubuntu and now upgrade fails
I was upgrading Ubuntu using
sudo apt-get upgrade -y
But, the terminal crashed in between. When I tried to run the same command again, it gave an error related to lock on dpkg. I deleted the lock files.
Now when I run the command, I get the following error
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up shim-signed (1.33.1~16.04.3+15+1533136590.3beb971-0ubuntu1) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
I am not sure what is wrong here.
ubuntu grub upgrade
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
add a comment |
I was upgrading Ubuntu using
sudo apt-get upgrade -y
But, the terminal crashed in between. When I tried to run the same command again, it gave an error related to lock on dpkg. I deleted the lock files.
Now when I run the command, I get the following error
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up shim-signed (1.33.1~16.04.3+15+1533136590.3beb971-0ubuntu1) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
I am not sure what is wrong here.
ubuntu grub upgrade
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
Of course, recognizing the error message in that output would have led to existing Q&As on the subject, including unix.stackexchange.com/questions/320014 , unix.stackexchange.com/questions/405472 , unix.stackexchange.com/questions/369748 , unix.stackexchange.com/questions/265556 , and unix.stackexchange.com/questions/311588 .
– JdeBP
Jan 30 at 6:23
add a comment |
I was upgrading Ubuntu using
sudo apt-get upgrade -y
But, the terminal crashed in between. When I tried to run the same command again, it gave an error related to lock on dpkg. I deleted the lock files.
Now when I run the command, I get the following error
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up shim-signed (1.33.1~16.04.3+15+1533136590.3beb971-0ubuntu1) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
I am not sure what is wrong here.
ubuntu grub upgrade
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
I was upgrading Ubuntu using
sudo apt-get upgrade -y
But, the terminal crashed in between. When I tried to run the same command again, it gave an error related to lock on dpkg. I deleted the lock files.
Now when I run the command, I get the following error
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up shim-signed (1.33.1~16.04.3+15+1533136590.3beb971-0ubuntu1) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
I am not sure what is wrong here.
ubuntu grub upgrade
ubuntu grub upgrade
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
edited Jan 30 at 7:13
Rui F Ribeiro
40k1479135
40k1479135
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
asked Jan 30 at 5:20
Ashwani KAshwani K
1084
1084
Of course, recognizing the error message in that output would have led to existing Q&As on the subject, including unix.stackexchange.com/questions/320014 , unix.stackexchange.com/questions/405472 , unix.stackexchange.com/questions/369748 , unix.stackexchange.com/questions/265556 , and unix.stackexchange.com/questions/311588 .
– JdeBP
Jan 30 at 6:23
add a comment |
Of course, recognizing the error message in that output would have led to existing Q&As on the subject, including unix.stackexchange.com/questions/320014 , unix.stackexchange.com/questions/405472 , unix.stackexchange.com/questions/369748 , unix.stackexchange.com/questions/265556 , and unix.stackexchange.com/questions/311588 .
– JdeBP
Jan 30 at 6:23
Of course, recognizing the error message in that output would have led to existing Q&As on the subject, including unix.stackexchange.com/questions/320014 , unix.stackexchange.com/questions/405472 , unix.stackexchange.com/questions/369748 , unix.stackexchange.com/questions/265556 , and unix.stackexchange.com/questions/311588 .
– JdeBP
Jan 30 at 6:23
Of course, recognizing the error message in that output would have led to existing Q&As on the subject, including unix.stackexchange.com/questions/320014 , unix.stackexchange.com/questions/405472 , unix.stackexchange.com/questions/369748 , unix.stackexchange.com/questions/265556 , and unix.stackexchange.com/questions/311588 .
– JdeBP
Jan 30 at 6:23
add a comment |
1 Answer
1
active
oldest
votes
First confirm whether or not you are running an EFI boot version of Ubuntu.
If you are not then:
- This will never work right, because shim-signed is a EFI application.
If you are then:
Make sure your EFI boot directory/partition is properly referenced.
Then purge shim-signed,
apt-get purge shim-signedthen I would attempt the update and upgrade or reinstall of shim-signed, after a reboot.
You could also try something similar to the following: (change to suit your situation)
Be vary sure you know what these commands do and where you want them to place things as doing it wrong will most likely render your system non-bootable.
mkdir /boot/efi
grub-install --efi-directory=/boot/efi --target=x86_64-efi /dev/sdX (path to drive where grub is installed).
apt-get update
apt-get upgrade
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
Thanks, but how to know if it EFI boot version. This used to work earlier. Only after the terminal crash during the upgrade, it gives this error.
– Ashwani K
Jan 30 at 6:09
How toMake sure your EFI boot directory/partition is properly referenced?
– Ashwani K
Jan 30 at 6:09
Check your fstab and see if you have a boot/efi entry if so good, if not do the following: Check to make sure the directory actually exists on the system ( /boot/efi ) if so good. If your system has both in place other things are amiss. If you have neither then look into why? Also check the permissions of the directory.
– Michael Prokopec
Jan 30 at 6:27
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%2f497609%2fterminal-crash-during-apt-upgrade-on-ubuntu-and-now-upgrade-fails%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
First confirm whether or not you are running an EFI boot version of Ubuntu.
If you are not then:
- This will never work right, because shim-signed is a EFI application.
If you are then:
Make sure your EFI boot directory/partition is properly referenced.
Then purge shim-signed,
apt-get purge shim-signedthen I would attempt the update and upgrade or reinstall of shim-signed, after a reboot.
You could also try something similar to the following: (change to suit your situation)
Be vary sure you know what these commands do and where you want them to place things as doing it wrong will most likely render your system non-bootable.
mkdir /boot/efi
grub-install --efi-directory=/boot/efi --target=x86_64-efi /dev/sdX (path to drive where grub is installed).
apt-get update
apt-get upgrade
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
Thanks, but how to know if it EFI boot version. This used to work earlier. Only after the terminal crash during the upgrade, it gives this error.
– Ashwani K
Jan 30 at 6:09
How toMake sure your EFI boot directory/partition is properly referenced?
– Ashwani K
Jan 30 at 6:09
Check your fstab and see if you have a boot/efi entry if so good, if not do the following: Check to make sure the directory actually exists on the system ( /boot/efi ) if so good. If your system has both in place other things are amiss. If you have neither then look into why? Also check the permissions of the directory.
– Michael Prokopec
Jan 30 at 6:27
add a comment |
First confirm whether or not you are running an EFI boot version of Ubuntu.
If you are not then:
- This will never work right, because shim-signed is a EFI application.
If you are then:
Make sure your EFI boot directory/partition is properly referenced.
Then purge shim-signed,
apt-get purge shim-signedthen I would attempt the update and upgrade or reinstall of shim-signed, after a reboot.
You could also try something similar to the following: (change to suit your situation)
Be vary sure you know what these commands do and where you want them to place things as doing it wrong will most likely render your system non-bootable.
mkdir /boot/efi
grub-install --efi-directory=/boot/efi --target=x86_64-efi /dev/sdX (path to drive where grub is installed).
apt-get update
apt-get upgrade
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
Thanks, but how to know if it EFI boot version. This used to work earlier. Only after the terminal crash during the upgrade, it gives this error.
– Ashwani K
Jan 30 at 6:09
How toMake sure your EFI boot directory/partition is properly referenced?
– Ashwani K
Jan 30 at 6:09
Check your fstab and see if you have a boot/efi entry if so good, if not do the following: Check to make sure the directory actually exists on the system ( /boot/efi ) if so good. If your system has both in place other things are amiss. If you have neither then look into why? Also check the permissions of the directory.
– Michael Prokopec
Jan 30 at 6:27
add a comment |
First confirm whether or not you are running an EFI boot version of Ubuntu.
If you are not then:
- This will never work right, because shim-signed is a EFI application.
If you are then:
Make sure your EFI boot directory/partition is properly referenced.
Then purge shim-signed,
apt-get purge shim-signedthen I would attempt the update and upgrade or reinstall of shim-signed, after a reboot.
You could also try something similar to the following: (change to suit your situation)
Be vary sure you know what these commands do and where you want them to place things as doing it wrong will most likely render your system non-bootable.
mkdir /boot/efi
grub-install --efi-directory=/boot/efi --target=x86_64-efi /dev/sdX (path to drive where grub is installed).
apt-get update
apt-get upgrade
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
First confirm whether or not you are running an EFI boot version of Ubuntu.
If you are not then:
- This will never work right, because shim-signed is a EFI application.
If you are then:
Make sure your EFI boot directory/partition is properly referenced.
Then purge shim-signed,
apt-get purge shim-signedthen I would attempt the update and upgrade or reinstall of shim-signed, after a reboot.
You could also try something similar to the following: (change to suit your situation)
Be vary sure you know what these commands do and where you want them to place things as doing it wrong will most likely render your system non-bootable.
mkdir /boot/efi
grub-install --efi-directory=/boot/efi --target=x86_64-efi /dev/sdX (path to drive where grub is installed).
apt-get update
apt-get upgrade
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
edited Jan 30 at 6:44
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
answered Jan 30 at 6:07
Michael ProkopecMichael Prokopec
1,448218
1,448218
Thanks, but how to know if it EFI boot version. This used to work earlier. Only after the terminal crash during the upgrade, it gives this error.
– Ashwani K
Jan 30 at 6:09
How toMake sure your EFI boot directory/partition is properly referenced?
– Ashwani K
Jan 30 at 6:09
Check your fstab and see if you have a boot/efi entry if so good, if not do the following: Check to make sure the directory actually exists on the system ( /boot/efi ) if so good. If your system has both in place other things are amiss. If you have neither then look into why? Also check the permissions of the directory.
– Michael Prokopec
Jan 30 at 6:27
add a comment |
Thanks, but how to know if it EFI boot version. This used to work earlier. Only after the terminal crash during the upgrade, it gives this error.
– Ashwani K
Jan 30 at 6:09
How toMake sure your EFI boot directory/partition is properly referenced?
– Ashwani K
Jan 30 at 6:09
Check your fstab and see if you have a boot/efi entry if so good, if not do the following: Check to make sure the directory actually exists on the system ( /boot/efi ) if so good. If your system has both in place other things are amiss. If you have neither then look into why? Also check the permissions of the directory.
– Michael Prokopec
Jan 30 at 6:27
Thanks, but how to know if it EFI boot version. This used to work earlier. Only after the terminal crash during the upgrade, it gives this error.
– Ashwani K
Jan 30 at 6:09
Thanks, but how to know if it EFI boot version. This used to work earlier. Only after the terminal crash during the upgrade, it gives this error.
– Ashwani K
Jan 30 at 6:09
How to
Make sure your EFI boot directory/partition is properly referenced?– Ashwani K
Jan 30 at 6:09
How to
Make sure your EFI boot directory/partition is properly referenced?– Ashwani K
Jan 30 at 6:09
Check your fstab and see if you have a boot/efi entry if so good, if not do the following: Check to make sure the directory actually exists on the system ( /boot/efi ) if so good. If your system has both in place other things are amiss. If you have neither then look into why? Also check the permissions of the directory.
– Michael Prokopec
Jan 30 at 6:27
Check your fstab and see if you have a boot/efi entry if so good, if not do the following: Check to make sure the directory actually exists on the system ( /boot/efi ) if so good. If your system has both in place other things are amiss. If you have neither then look into why? Also check the permissions of the directory.
– Michael Prokopec
Jan 30 at 6:27
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%2f497609%2fterminal-crash-during-apt-upgrade-on-ubuntu-and-now-upgrade-fails%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
Of course, recognizing the error message in that output would have led to existing Q&As on the subject, including unix.stackexchange.com/questions/320014 , unix.stackexchange.com/questions/405472 , unix.stackexchange.com/questions/369748 , unix.stackexchange.com/questions/265556 , and unix.stackexchange.com/questions/311588 .
– JdeBP
Jan 30 at 6:23