Okay, I made a foolish mistake a few months ago and upgraded my perfectly running CentOS 7 to CentOS 8 and have been struggling ever since. Looking to upgade to AlmaLinux or Rocky Linux. I have a number of things I need to clean up on this system before attempting a upgrade.
Does anyone have any idea as to how I can clean/straighten this out:
grub2-common.noarch 1:2.02-90.el8_3.1 BaseOS
grub2-pc-modules.noarch 1:2.02-90.el8_3.1 BaseOS
grub2-tools-minimal.x86_64 1:2.02-90.el8_3.1 BaseOS
grubby.x86_64 8.40-41.el8 BaseOS
kernel-abi-whitelists.noarch 4.18.0-240.15.1.el8_3 BaseOS
kernel-debug-devel.x86_64 4.18.0-240.15.1.el8_3 BaseOS
kernel-devel.x86_64 4.18.0-240.15.1.el8_3 BaseOS
libgdiplus.x86_64 6.0.4-3.el8 epel
libgdiplus-devel.x86_64 6.0.5-0.xamarin.1.epel7 download.mono-project.com_repo_centos_
libpwquality.x86_64 1.4.0-9.el8 BaseOS
lz4.x86_64 1.8.3-2.el8 BaseOS
t1lib.x86_64 5.1.2-28.el8 epel
Obsoleting Packages
centos-linux-release.noarch 8.3-1.2011.el8 BaseOS
centos-release.x86_64 8.2-2.2004.0.2.el8 @BaseOS
centos-linux-release.noarch 8.3-1.2011.el8 BaseOS
centos-repos.x86_64 8.2-2.2004.0.2.el8 @BaseOS
libgdiplus0.x86_64 3.12-1 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
libgdiplus0.x86_64 4.2-0.xamarin.2.epel7 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
libgdiplus0.x86_64 5.6-0.xamarin.1.epel7 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
libgdiplus0.x86_64 5.6-0.xamarin.2.epel7 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
libgdiplus0.x86_64 5.6.1-0.xamarin.3.epel7 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
libgdiplus0.x86_64 6.0.2-0.xamarin.1.epel7 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
libgdiplus0.x86_64 6.0.4-0.xamarin.1.epel7 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
libgdiplus0.x86_64 6.0.5-0.xamarin.1.epel7 download.mono-project.com_repo_centos_
libgdiplus.x86_64 6.0.4-2.el8 @epel
I'm unable to update grub2/grubby:
dnf update grubby
Last metadata expiration check: 0:46:20 ago on Fri 02 Apr 2021 08:57:14 AM CDT.
Error:
Problem: The operation would result in removing the following protected packages: kernel
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
..also for some reason, my kernel packages are being installed but the system is not booting to them:
ls /boot/vmlin*
/boot/vmlinuz-0-rescue-3e806a41305047db81c0e9f9b9a4e36c /boot/vmlinuz-4.18.0-240.10.1.el8_3.x86_64 /boot/vmlinuz-4.18.0-240.15.1.el8_3.x86_64
/boot/vmlinuz-3.10.0-1127.8.2.el7.x86_64 /boot/vmlinuz-4.18.0-240.1.1.el8_3.x86_64
.but it always boots to:
uname -r
3.10.0-1127.8.2.el7.x86_64
I found on the internet that this "The operations would.." Message was because of a kernel file in a protected.d (either yum or dnf), but I checked and it doesn't exist.
H E L P (TIA)
-Frank
On Sun, 4 Apr 2021 18:33:16 -0500 Frank Ramaekers wrote:
Okay, I made a foolish mistake a few months ago and upgraded my perfectly running CentOS 7 to CentOS 8 and have been struggling ever since.
How did you "upgrade" your computer? In-place upgrading from C7 to C8 isn't something that you're supposed to do. The best solution is/was/would have been to backup your data, then reformat your system with the new OS and restore your data.
Since kernel version 3.10 is a C7 kernel, at the least you're still running a C7 kernel on what might otherwise be (part of?) a C8 installation, and who knows what else behind the scenes. You've apparently got something going here that's neither fish nor fowl; it's isn't exactly C7 and it's not really C8 either.
Since you don't really know what's broken here, you'll find yourself spending an awful lot of time chasing gremlins. At this point, my suggestion would be take the recommended action. Backup your data, then reformat your system with the new OS and restore your data.
Yeah, that is the conclusion I've come to as well.
Thanks, Frank
-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Frank Cox Sent: Sunday, April 4, 2021 6:46 PM To: centos@centos.org Subject: Re: [CentOS] CentOS 8 issues.
On Sun, 4 Apr 2021 18:33:16 -0500 Frank Ramaekers wrote:
Okay, I made a foolish mistake a few months ago and upgraded my perfectly running CentOS 7 to CentOS 8 and have been struggling ever since.
How did you "upgrade" your computer? In-place upgrading from C7 to C8 isn't something that you're supposed to do. The best solution is/was/would have been to backup your data, then reformat your system with the new OS and restore your data.
Since kernel version 3.10 is a C7 kernel, at the least you're still running a C7 kernel on what might otherwise be (part of?) a C8 installation, and who knows what else behind the scenes. You've apparently got something going here that's neither fish nor fowl; it's isn't exactly C7 and it's not really C8 either.
Since you don't really know what's broken here, you'll find yourself spending an awful lot of time chasing gremlins. At this point, my suggestion would be take the recommended action. Backup your data, then reformat your system with the new OS and restore your data.
-
Frank Cox -
Frank Ramaekers