This has completely bricked an AMD E-350-based mini PC.

I recently installed ubuntu 18.04 server; and 3 updates later, I can't
boot the device at all. Not even POST video output. Pulling the CMOS
battery didn't help.

The system ran fine for 4+ years running CentOS 7 server.

Here's the apt update output:

# apt update
...
10 packages can be upgraded. Run 'apt list --upgradable' to see them.

# apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  grub-common grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed 
grub2-common libidn11
  libunistring2 python3-httplib2 ufw unattended-upgrades
10 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
...
Setting up grub-efi-amd64-bin (2.02-2ubuntu8.13) ...
Setting up grub2-common (2.02-2ubuntu8.13) ...
Processing triggers for systemd (237-3ubuntu10.19) ...
Setting up grub-efi-amd64 (2.02-2ubuntu8.13) ...
Installing for x86_64-efi platform.
Could not delete variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Block device 
required.
Failed: grub-install --target=x86_64-efi  
WARNING: Bootloader is not properly installed, system may not be bootable
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-47-generic
Found initrd image: /boot/initrd.img-4.15.0-47-generic
Found linux image: /boot/vmlinuz-4.15.0-46-generic
Found initrd image: /boot/initrd.img-4.15.0-46-generic
done
Setting up grub-efi-amd64-signed (1.93.14+2.02-2ubuntu8.13) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output 
error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess 
returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
 grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

During the failed update, I was prompted for a new grub config file. I
chose to keep my existing file (the default, believe).

Next, I tried:

# dpkg-reconfigure grub-efi-amd64-signed
/usr/sbin/dpkg-reconfigure: grub-efi-amd64-signed is broken or not fully 
installed
root@giraffe:/home/dietmar# apt install grub-efi-amd64-signed
Reading package lists... Done
Building dependency tree       
Reading state information... Done
grub-efi-amd64-signed is already the newest version (1.93.14+2.02-2ubuntu8.13).
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 will be used.
Do you want to continue? [Y/n] y           
Setting up grub-efi-amd64-signed (1.93.14+2.02-2ubuntu8.13) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output 
error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess 
returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
 shim-signed depends on grub-efi-amd64-signed; however:
  Package grub-efi-amd64-signed is not configured yet.

df showed plenty of free space on all partitions:

Filesystem     1K-blocks    Used Available Use% Mounted on
udev             4035776       0   4035776   0% /dev
tmpfs             813184    2336    810848   1% /run
/dev/sda2       45876068 4616084  38899872  11% /
tmpfs            4065908       0   4065908   0% /dev/shm
tmpfs               5120       0      5120   0% /run/lock
tmpfs            4065908       0   4065908   0% /sys/fs/cgroup
/dev/sda1         523248    6152    517096   2% /boot/efi
/dev/sda4      106674880   65120 101147952   1% /home
tmpfs             813180       0    813180   0% /run/user/1000

I tried the workaround from Ronan Mooney.
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/comments/11

That allowed apt to complete without an error; however, it left the
system in an unbootable state.

# mv ubuntu/ ubuntu.bak

# 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.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up grub-efi-amd64-signed (1.93.14+2.02-2ubuntu8.13) ...
Setting up shim-signed (1.37~18.04.3+15+1533136590.3beb971-0ubuntu1) ...
W: APT had planned for dpkg to do more than it reported back (3 vs 7).
   Affected packages: grub-efi-amd64-signed:amd64

# apt install --reinstall grub-common grub-efi-amd64 grub-efi-amd64-bin 
grub2-common
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 4 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/3,006 kB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 107658 files and directories currently installed.)
Preparing to unpack .../grub-common_2.02-2ubuntu8.13_amd64.deb ...
Unpacking grub-common (2.02-2ubuntu8.13) over (2.02-2ubuntu8.13) ...
Preparing to unpack .../grub2-common_2.02-2ubuntu8.13_amd64.deb ...
Unpacking grub2-common (2.02-2ubuntu8.13) over (2.02-2ubuntu8.13) ...
Preparing to unpack .../grub-efi-amd64_2.02-2ubuntu8.13_amd64.deb ...
Unpacking grub-efi-amd64 (2.02-2ubuntu8.13) over (2.02-2ubuntu8.13) ...
Preparing to unpack .../grub-efi-amd64-bin_2.02-2ubuntu8.13_amd64.deb ...
Unpacking grub-efi-amd64-bin (2.02-2ubuntu8.13) over (2.02-2ubuntu8.13) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for install-info (6.5.0.dfsg.1-2) ...
Setting up grub-common (2.02-2ubuntu8.13) ...
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Processing triggers for systemd (237-3ubuntu10.19) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up grub-efi-amd64-bin (2.02-2ubuntu8.13) ...
Setting up grub2-common (2.02-2ubuntu8.13) ...
Setting up grub-efi-amd64 (2.02-2ubuntu8.13) ...
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-47-generic
Found initrd image: /boot/initrd.img-4.15.0-47-generic
Found linux image: /boot/vmlinuz-4.15.0-46-generic
Found initrd image: /boot/initrd.img-4.15.0-46-generic
done
Processing triggers for shim-signed 
(1.37~18.04.3+15+1533136590.3beb971-0ubuntu1) ...

# mv ubuntu.bak ubuntu

The system would no longer boot from SATA, and prompted to insert
bootable media.

I was able to get into the BIOS setup page 1 time following boot. I
changed the boot order to boot from removable media first, saved and
exited.

After that, the system power light comes on, but the system will not
POST. I've pulled CMOS and tried again, but the device is completely
catatonic and non-responsive.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518

Title:
  package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to