I am seeing this too (late upgrade to the system)
For me, this is caused by /usr/lib/grub/grub-multi-install:
# /usr/lib/grub/grub-multi-install
mount: /var/lib/grub/esp: special device /dev/sdb1 does not exist.
I have a /dev/sdb, but it's a raw disk, no part. table
# ls /dev/sdb*
/dev/sdb
Philipp Classen #13
> (Another issue, which I will mention as there is a tiny chance that it
is related, although I doubt it: After rebooting, I was not able to boot
(not even reaching the question for the passphrase). To solve it, I had
to disable Secure Boot, then I reached the state where I
I too am seeing this error. Same circumstances as #23.
I have recently installed Win 10 on sda but sda1 is not the NTFS partition,
that is sda2.
Ubuntu is on sdb, / on sdb2, /boot/efi on sdb1.
I can find no reference to sda1 in my Ubuntu /etc or /boot so I don't know
where it's coming from.
I am seeing this and I suspect it is because I installed Windows on an
extra SSD that was a Linux partition. /dev/sda is that device
```
Setting up grub-efi-amd64-signed (1.155.1+2.04-1ubuntu35.1) ...
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1'
We're seeing this one too, on Ubuntu 20.04. I think something
interesting to note is the disk layout which might be causing it to
happen.
During apt upgrade or forced grub package installation, I get:
mount: /var/lib/grub/esp: special device /dev/sda1 does not exist.
dpkg: error
For me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
dpkg fails to install grub-efi-amd64 signed and shim-signed
To manage notifications about this bug go to:
An update released this morning of I don't know what package fixed the
issue on multiple servers, so this appears to have been fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
I just completely reinstalled an OVH server, and got the error while
upgrading to ubuntu 20 from ubuntu 18. On the other server, an update
created the error, it wasn't there when I installed ubuntu 20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the same problem as the #17. I have tried everything from
stackoverflow but nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
dpkg fails to install grub-efi-amd64 signed
I've tried everything, the patch was already applied, and the
stackoverflow solution didn't work; I still have the error on ubuntu 20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
It seems to only happen when doing:
# DEBIAN_FRONTEND=noninteractive apt-get -f install
When it is interactive, it asks to select /dev/sda and then it upgrades.
How to upgrade this package non interactive?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not sure what to do now.
mike@mike-desktop:~$ sudo apt-get purge grub\*
[sudo] password for mike:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'grub-legacy' for glob 'grub*'
Note, selecting 'grub-doc' for glob 'grub*'
Note,
Had the same issue as philipp-classen, upgrade from 19.10 to 20.04 and
install failed:
grub-efi-amd64-signed (1.142+2.04-1ubuntu26) wird eingerichtet ...
dpkg: Fehler beim Bearbeiten des Paketes grub-efi-amd64-signed (--configure):
»installiertes grub-efi-amd64-signed-Skript des Paketes
Just had the same issue as Deepak. Same error after upgrading from 18.04
to 20.04, but I checked and apparently also had the fix of the semicolon
in /var/lib/dpkg/info/grub-efi-amd64-signed.postinst. So, there might be
another issue that is causing the same problem.
Running it with "set -x", I
Hello,
There is no semicolon in the file but I still have same problem.
Do you want to continue? [Y/n] y
Setting up grub-efi-amd64-signed (1.142+2.04-1ubuntu26) ...
dpkg: error processing package
Brett,
Thanks for the update. I know how to unlock the lock files.
Ken Wagner
On 4/11/20 12:24 PM, Brett Bogert wrote:
> Rob,
>
> Your problem is due to another process having the
> /var/cache/debconf.dat
> file in a locked state:
>
> debconf: DbDriver "config":
Rob,
Your problem is due to another process having the
/var/cache/debconf.dat
file in a locked state:
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked
by another process: Resource temporarily unavailable
The original problem reported was due to a
For me there as no semicolon, but I still get the error.
rohro@frohro-260:~/Projects/IQ_SDR/Receiver$ sudo vi
/var/lib/dpkg/info/grub-efi-amd64-signed.postinst
frohro@frohro-260:~/Projects/IQ_SDR/Receiver$ sudo apt upgrade -f
Reading package lists... Done
Building dependency tree
Thanks! It worked just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
dpkg fails to install grub-efi-amd64 signed and shim-signed
To manage notifications about this bug go to:
Abdel, you can edit the file :
/var/lib/dpkg/info/grub-efi-amd64-signed.postinst
And replace this line :
target=x86_64-efi ;;
For that (remove the ";;") :
target=x86_64-efi
Save and try to update again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi, I see it says (Fix Released).
How can I apply the fix to my pc?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
dpkg fails to install grub-efi-amd64 signed and shim-signed
Fixed in the version in -proposed, and the broken grub2-signed has been
backed out of the release pocket.
** Changed in: dpkg (Ubuntu)
Status: Confirmed => Invalid
** Changed in: grub2-signed (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because
** Package changed: grub2 (Ubuntu) => grub2-signed (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
dpkg fails to install grub-efi-amd64 signed and shim-signed
To manage
** Package changed: grub (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
dpkg fails to install grub-efi-amd64 signed and shim-signed
To manage notifications
It looks like there is an extra ';;' in the script, the following patch
fixes it.
--- /tmp/grub-efi-amd64-signed.postinst 2020-04-09 16:50:58.585757438 -0700
+++ /var/lib/dpkg/info/grub-efi-amd64-signed.postinst 2020-04-09
16:51:12.029644653 -0700
@@ -16,7 +16,7 @@
case $1 in
Just confirming this as well
sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dpkg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871963
Title:
dpkg
27 matches
Mail list logo
