PDA

View Full Version : [SOLVED] I shutdown my system during an system upgrade, now can't continue to upgrade



lassade
22nd October 2017, 05:37 AM
Hello guys,

Like the title says, I forgot that my I put my system to do an upgrade today and shutdown my computer, at first it would not shutdown putting me back to the login screen but after clicking the shutdown once more the my pc goes off.

Now here is what happen, very thing works just fine as far I can tell. But my kernel is still in the last version namely 12, and I'm pretty sure that this upgrade was installing the new 13 version.


$uname -a
Linux wshost 4.12.11-300.fc26.x86_64 #1 SMP Thu Sep 7 18:32:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

trying to continue the upgrade process gives me this


# dnf upgrade --refresh
Last metadata expiration check: 0:00:00 ago on Sun 22 Oct 2017 01:34:07 AM -03.
Dependencies resolved.
Nothing to do.
Complete!

What I should do? Do I need to get worried? I mean things are working, but I'm maybe be missing the new kernel and some updates

srakitnican
22nd October 2017, 05:51 AM
What is the output of:

$ sudo dnf repoquery --duplicated

lassade
22nd October 2017, 06:03 AM
Really big



Last metadata expiration check: 0:24:09 ago on Sun 22 Oct 2017 01:34:07 AM -03.
GeoIP-GeoLite-data-0:2017.07-1.fc26.noarch
GeoIP-GeoLite-data-0:2017.10-1.fc26.noarch
ImageMagick-0:6.9.3.0-6.fc26.x86_64
LibRaw-0:0.18.2-1.fc26.x86_64
LibRaw-0:0.18.5-1.fc26.x86_64
OpenImageIO-0:1.7.15-1.fc26.x86_64
....
The list goes on


I spotted a few kernel packages in there.


abrt-addon-kerneloops-0:2.10.3-1.fc26.x86_64
abrt-addon-kerneloops-0:2.10.3-3.fc26.x86_64
kernel-headers-0:4.12.11-300.fc26.x86_64
kernel-headers-0:4.13.5-200.fc26.x86_64
libreport-plugin-kerneloops-0:2.9.1-2.fc26.x86_64
libreport-plugin-kerneloops-0:2.9.1-3.fc26.x86_64

srakitnican
22nd October 2017, 06:09 AM
We don't need a full list, but a reference number of packages would be nice, do a


$ sudo dnf repoquery --duplicated --latest-limit=-1 -q | wc -l


Then try the following and report if number of removed packages greatly differ.


$ sudo dnf remove --duplicates

You might need to add `--setopt=protected_packages=` if there is dnf or systemd in the list.

lassade
22nd October 2017, 07:42 AM
I run


# dnf remove --duplicates

This clears the big duplicate list, last time I remember it have a few dnf packages but is too late for them, could not see the edit in time. (No problem in using dnf until now)

Then after that I had to reinstall kernel-core so to generate both vmlinuz and initramfs for the new kernel, with:


# dnf reinstall kernel-core

Guess that it, thanks you helped a lot!