# Failed Migration tor Rocky: Found a full or partial RockyLinux install already in place **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [July 17, 2023, 2:40am UTC](https://forums.rockylinux.org/t/failed-migration-tor-rocky-found-a-full-or-partial-rockylinux-install-already-in-place/10720 "2023-07-17T02:40:14Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dolphinblue](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@dolphinblue](https://forums.rockylinux.org/u/dolphinblue)\ **Post date:** [July 17, 2023, 2:40am UTC](https://forums.rockylinux.org/t/failed-migration-tor-rocky-found-a-full-or-partial-rockylinux-install-already-in-place/10720/1 "2023-07-17T02:40:14Z")
I am trying to migrate from centos 8.5.2111 to Rocky 8 by using the script: [https://raw.githubusercontent.com/rocky-linux/rocky-tools/main/migrate2rocky/migrate2rocky.sh](https://raw.githubusercontent.com/rocky-linux/rocky-tools/main/migrate2rocky/migrate2rocky.sh) but I got this error: ```auto migrate2rocky - Begin logging at dom 16 jul 2023 21:14:43 -05. Removing dnf cache Preparing to migrate CentOS Linux 8 to Rocky Linux 8. Determining repository names for CentOS Linux 8...... Found the following repositories which map from CentOS Linux 8 to Rocky Linux 8: CentOS Linux 8 Rocky Linux 8 appstream appstream baseos baseos extras extras Getting system package names for CentOS Linux 8 Found a full or partial RockyLinux install already in place. Aborting An error occurred while we were attempting to convert your system to Rocky Linux. Your system may be unstable. Script will now exit to prevent possible damage. A log of this installation can be found at /var/log/migrate2rocky.log ``` Actually I applied all these steps to try to solve the issue, as is mentioned in [https://docs.linuxfabrik.ch/operating-systems/rockylinux.html](https://docs.linuxfabrik.ch/operating-systems/rockylinux.html) but it doesn’t work, the error persists. ```auto cd /tmp Example for CentOS 8.5 AppStream: wget http://vault.centos.org/centos/8.5.2111/AppStream/x86_64/os/Packages/centos-backgrounds-85.8-2.el8.noarch.rpm wget http://vault.centos.org/centos/8.5.2111/AppStream/x86_64/os/Packages/centos-logos-ipa-85.8-2.el8.noarch.rpm BaseOS: wget http://vault.centos.org/centos/8.5.2111/BaseOS/x86_64/os/Packages/centos-gpg-keys-8-3.el8.noarch.rpm wget http://vault.centos.org/centos/8.5.2111/BaseOS/x86_64/os/Packages/centos-indexhtml-8.0-0.el8.noarch.rpm wget http://vault.centos.org/centos/8.5.2111/BaseOS/x86_64/os/Packages/centos-linux-release-8.5-1.2111.el8.noarch.rpm wget http://vault.centos.org/centos/8.5.2111/BaseOS/x86_64/os/Packages/centos-linux-repos-8-3.el8.noarch.rpm wget http://vault.centos.org/centos/8.5.2111/BaseOS/x86_64/os/Packages/centos-logos-85.8-2.el8.x86_64.rpm wget http://vault.centos.org/centos/8.5.2111/BaseOS/x86_64/os/Packages/centos-logos-httpd-85.8-2.el8.noarch.rpm rpm -Uvh --force centos-*.rpm this removes all rocky stuff: dnf -y remove rocky-gpg-keys rm -f /etc/yum.repos.d/Rocky* dnf clean all ``` Could you help me please? ---
**Author:** ![wintpe](https://avatars.discourse-cdn.com/v4/letter/w/e47774/32.png) [@wintpe](https://forums.rockylinux.org/u/wintpe)\ **Post date:** [July 22, 2023, 9:45am UTC](https://forums.rockylinux.org/t/failed-migration-tor-rocky-found-a-full-or-partial-rockylinux-install-already-in-place/10720/2 "2023-07-22T09:45:05Z")
please cd /etc/yum.repos and show what is still there. also run a dnf history and see if anything actually updated. this is from dnf history on one of my systems that i migrated from centos 8 to rocky 8 a while ago. ``` 87 | -y update | 2021-10-28 03:47 | Upgrade | 1 86 | -y update | 2021-10-14 03:34 | Upgrade | 1 85 | -y distro-sync | 2021-10-01 17:45 | D, I, R, U | 1404 EE 84 | -y shell --disablerepo=* --noautoremove --setopt=protected_packages= --setopt=keepcache=True --repofrompath=rockyappstream | 2021-10-01 17:42 | E, I | 8 EE 83 | -y update | 2021-10-01 03:50 | Upgrade | 1 82 | -y update | 2021-09-24 03:13 | I, U | 23 EE 81 | -y update | 2021-09-16 03:46 | E, I, U | 15 EE ``` if you are not aware, each of those numbers are a transaction number, that can be rolled back to. But im not sure if the changes the rocky upgrade script does block rolling back, otherwise i would just say use dnf history rollback to a number prior to the upgrade. and rpm -qa --last|more will show you what were the last rpm changes that took place. what you need to establish is what actually got changed if anything before you move forward. the rocky specific packages (on my system at least ) are rpm -qa|grep rocky grub2-tools-extra-2.02-148.el8.rocky.0.3.x86\_64 rocky-logos-86.3-1.el8.x86\_64 chrony-4.2-1.el8.rocky.1.0.x86\_64 grub2-pc-2.02-148.el8.rocky.0.3.x86\_64 grub2-pc-modules-2.02-148.el8.rocky.0.3.noarch platform-python-pip-9.0.3-22.el8.rocky.0.noarch rocky-repos-8.8-1.8.el8.noarch libreport-filesystem-2.9.5-15.el8.rocky.6.3.x86\_64 grub2-common-2.02-148.el8.rocky.0.3.noarch platform-python-3.6.8-51.el8\_8.1.rocky.0.x86\_64 rocky-release-8.8-1.8.el8.noarch python3-pip-wheel-9.0.3-22.el8.rocky.0.noarch grub2-tools-minimal-2.02-148.el8.rocky.0.3.x86\_64 rocky-logos-httpd-86.3-1.el8.noarch grub2-tools-efi-2.02-148.el8.rocky.0.3.x86\_64 python3-libs-3.6.8-51.el8\_8.1.rocky.0.x86\_64 rocky-gpg-keys-8.8-1.8.el8.noarch grub2-tools-2.02-148.el8.rocky.0.3.x86\_64 regards peter