(Reading database … 549145 files and directories currently installed.)
Preparing to unpack …/microsoft-edge-stable_110.0.1587.49-1_amd64.deb …
Unpacking microsoft-edge-stable (110.0.1587.49-1) over (110.0.1587.41-1) …
Setting up microsoft-edge-stable (110.0.1587.49-1) …
Setting up grub-efi-amd64-signed (1.187.2+2.06-2ubuntu14) …
mount: /var/lib/grub/esp: special device /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_250GB_S465NB0K446788D-part1 does not exist.
dpkg: error processing package grub-efi-amd64-signed (–configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
Processing triggers for man-db (2.10.2-1) …
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
Package grub-efi-arm64-signed is not installed.
dpkg: error processing package shim-signed (–configure):
dependency problems - leaving triggers unprocessed
Processing triggers for mailcap (3.70+nmu1ubuntu1) …
Processing triggers for desktop-file-utils (0.26+mint2+vera) …
Processing triggers for gnome-menus (3.36.0-1ubuntu3) …
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up grub-efi-amd64-signed (1.187.2+2.06-2ubuntu14) …
mount: /var/lib/grub/esp: special device /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_250GB_S465NB0K446788D-part1 does not exist.
dpkg: error processing package grub-efi-amd64-signed (–configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
Package grub-efi-arm64-signed is not installed.
dpkg: error processing package shim-signed (–configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
just spotted it shows old 250gb drive on this not the new 500gb
Has it mounted the wrong disk? Do you have both disks present.?
That old disk name may be somehow built into the grub configuration.
Your could try remove and the reinstall grub
Maybe you could just delete the grub.cfg fiile ( it is in /boot/grub)
Also have a look in /etc/default/grub… is there any diskname stored there?
What does
apt-get check
produce
Could also try
apt-get -f update
that often fixes dependency issues but I am not sure what it will do with wrong disk name
thanks for advice unfortunately tried your options & no luck so far
old ssd (250gb) has been removed and replaced with larger one (500gb). cloned the drive using clonezilla.
everything else works fine it just gives the above errors on each update now.
Setting up grub-efi-amd64-signed (1.187.2+2.06-2ubuntu14) …
mount: /var/lib/grub/esp: special device /dev/disk/by-id/nvme-Samsung_SSD_970_EV
O_250GB_S465NB0K446788D-part1 does not exist.
dpkg: error processing package grub-efi-amd64-signed (–configure):
installed grub-efi-amd64-signed package post-installation script subprocess ret
urned error exit status 32
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
Package grub-efi-arm64-signed is not installed.
dpkg: error processing package shim-signed (–configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
That disk name is stored somewhere. You need to go looking.
I would be looking in
/var/lib/grub
/etc/apt
the efi system partition which should be mounted
/etc/default/grub
or use grep to search the whole of /etc for that disk name
cd /etc
grep Samsung * */*
grep S465NB * */*
and maybe in /var too
and maybe in efi system partition
When you find it , you obviously need to edit some file and change it.
We have to hope that it is not stored in some binary file that you cant search or edit
If you edit any file, be careful, take a copy first so you can recover.
The only other approach is to google your error message and see if anyone else has had the problem and found a solution. It would really help if we could understand exactly what Clonezilla has done, or whether this disk name was put there by your OS when it was installed.