dpkg --configure -a unsuccessful due to battery running out of power

Question

I was updating my system as usual and sudo apt update showed me some packages to be updated. I ran sudo apt upgrade and it downloaded the packages. But while packages were being configured during the installation, the computer was turned off due to low battery. When I booted and tried to update using sudo apt update I got this message:

E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

When I executed sudo dpkg --configure -a I got this:

@mike-bravo:~$ sudo dpkg --configure -a
Setting up linux-image-4.4.0-96-generic (4.4.0-96.119) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
initrd.img(/boot/initrd.img-4.4.0-96-generic
) points to /boot/initrd.img-4.4.0-96-generic
 (/boot/initrd.img-4.4.0-96-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-96-generic.postinst line 491.
vmlinuz(/boot/vmlinuz-4.4.0-96-generic
) points to /boot/vmlinuz-4.4.0-96-generic
 (/boot/vmlinuz-4.4.0-96-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-96-generic.postinst line 491.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-
96-generic /boot/vmlinuz-4.4.0-96-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-96-
generic /boot/vmlinuz-4.4.0-96-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-96-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-96-generic 
/boot/vmlinuz-4.4.0-96-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-96-generic /boot/vmlinuz-4.4.0-96-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-96-
generic /boot/vmlinuz-4.4.0-96-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-96-
generic /boot/vmlinuz-4.4.0-96-generic
/usr/sbin/grub-mkconfig: 252: /usr/sbin/grub-mkconfig: cannot create 
/boot/grub/grub.cfg.new: Read-only file system
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return 
code 2
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-
image-4.4.0-96-generic.postinst line 1052.
dpkg: error processing package linux-image-4.4.0-96-generic (--
configure):
 subprocess installed post-installation script returned error exit 
status 2
dpkg: dependency problems prevent configuration of linux-signed-
image-4.4.0-96-generic:
 linux-signed-image-4.4.0-96-generic depends on linux-image-4.4.0-96-
generic (= 4.4.0-96.119); however:
  Package linux-image-4.4.0-96-generic is not configured yet.

dpkg: error processing package linux-signed-image-4.4.0-96-generic (-
-configure):
 dependency problems - leaving unconfigured
Setting up linux-libc-dev:amd64 (4.4.0-96.119) ...
dpkg: unrecoverable fatal error, aborting:
 unable to flush updated status of 'linux-libc-dev:amd64': Read-only 
file system

As a side effect(?) to this my system became read-only. I had to reboot it to be able to move files, add or copy files from the system.

uname -r gives me 4.4.0-93-generic

How can I delete this un-configured package (linux-image-4.4.0-96- generic) or configure it properly?

@George I have tried that. But its giving me same message that dpkg was interrupted and I should manually configure it. — Manish Kumar Bisht, Oct 02 '17 at 03:40
a read-only munt culd be because of a disk error. boot from a LiveCD and run file system checks on your parttions — ravery, Oct 02 '17 at 03:45
I fixed the error running fsck manually. system has been recovered so its not a problem. The actual problem which is causing this strange behaviour is the broken package. — Manish Kumar Bisht, Oct 02 '17 at 04:02
So you must set your own answer (with details, preferable) and close this issue. — Redbob, Oct 07 '17 at 16:59
@Redbob I would not have asked this question if I knew the solution. :-( — Manish Kumar Bisht, Oct 09 '17 at 13:17
You might know the solution, but someone that search for a solution to this issue may not know. It's very useful, post it! — Redbob, Oct 09 '17 at 20:48
Did you try removing the specified package? Since it seems you're using another kernel version anyway, which means removing the broken one shouldn't be an issue? — Ziazis, Oct 10 '17 at 11:55
You could try this answer from me aswell. https://askubuntu.com/questions/932228/cannot-remove-old-kernel-showing-error-code-1/932232#932232 — Ziazis, Oct 10 '17 at 12:07

score 2 · Accepted Answer · answered Oct 09 '17 at 19:06

Now that you've resolved the read-only mount and repaired the file system. You can clean up the mess and try again. Before doing so it would be wise to check the SMART status of your drive as an impending hardware failure can make all your efforts useless. If the drive is reported to be in good shape, it should be safe to continue.

sudo apt-get purge linux-signed-image-generic will purge the unconfigured, not fully installed package.

sudo apt install linux-signed-image-generic will install the currently supported version.

score 1 · Answer 2 · edited Jun 12 '20 at 14:37

1

The easy way of recovering from an interrupted kernel upgrade due to battery running out of juice is to:

ensure the laptop is connected to mains power now and every kernel upgrade you do in the future!
hold the Shift while booting and on the following screen:
take "advanced options"
boot into the second-to-last kernel
do sudo apt dist-upgrade again.

Done! :-)

edited Jun 12 '20 at 14:37

Community

1

answered Oct 10 '17 at 11:49

Fabby

34,259

dpkg --configure -a unsuccessful due to battery running out of power

2 Answers2

Done! :-)