Ask Your Question

Fedora 27 upgrade fails after crash

asked 2017-11-16 01:24:29 -0500

PMatos gravatar image

updated 2017-11-16 01:25:45 -0500


I started the Fedora 27 upgrade using the dnf method. After a dnf system-upgrade reboot the system does reboot and starts an upgrade. While running scriptlet for protobuf at around package 1471 of 4000 (or thereabout), the system crashes. Most likely due to the nvidia driver on my optimus setup which has been giving me trouble for ages.

Anyway, I reboot just to find the system actually starts but some packages seems to be broken - for example, the wifi doesn't work properly. So, I trigger another dnf system-upgrade just to find it says that I am already in version 27 and cannot upgrade. So I try a system-upgrade reboot and the system reboots, does nothing and reboots again automatically.

So I wonder what would happen if I do a dnf --refresh upgrade. Well, it tried to install some new packages (147 of them) and when it got to the running scriptlet part all went wrong with:

Running scriptlet: glibc-common-2.26-15.fc27.x86_64
/usr/bin/mandb: fork failed: Resource temporarily unavailable
error: lua script failed: [string "%triggerin(systemd-233-7.fc26.x86_64)"]:9: attempt to compare number with nil

And a few others smilar to this one until my system stops during the running scriptlet but doesn't hang. I.e. dnf hangs but not the system itself.

So now I have a partially upgraded Fedora 27, broken system, and no idea on how to make things right. Any suggestions?

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2017-11-16 06:48:53 -0500

PMatos gravatar image

I have fixed this by using rpm -Va, finding all the packages responsible for all reported files which came up with both Fedora 26 and Fedora 27 packages.

I then did a dnf reinstall on the Fedora 27 packages. This seems to bring back a stable system.

edit flag offensive delete link more

answered 2017-11-16 05:02:31 -0500

Aeyoun gravatar image

updated 2017-11-16 05:03:28 -0500

It kind of looks like a lua script is trying to compare a version string with nothing. What version(s) does dnf info systemd say you have installed?

Have you tried dnf reinstall systemd glibc-common?

You can also try disabling all third-party repositories (at least until the upgrade is done) and then running dnf distro-sync.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2017-11-16 01:24:29 -0500

Seen: 1,529 times

Last updated: Nov 16 '17