If you suspect the problem lies with dnf, then an attempt to repair it would include sudo dnf clean all followed by sudo dnf reinstall *dnf*
Doing so would reinstall all the dnf packages and should fix any glitches.
Yes, it is possible that something in dnf is glitched.
Nothing we have seen so far directly indicates a dnf problem, although the system upgrade process is glitching so maybe removing that plugin itself and reinstalling it could help. sudo dnf remove python3-dnf-plugin-system-upgrade followed by a reboot then sudo dnf install python3-dnf-plugin-system-upgrade to reinstall it.
Digging deeper than that makes it seem more likely that a clean install of fedora 35 will be simpler in the long run.
Morning, JV. The dnf, etc., process did not change the outcome. I noticed, tho, when I did the dnf clean step only 112 files were removed, far fewer than I was expecting.
I’m going to walk away from all this for a while and will do a fresh install when I have more time to prepare for it. Obviously, I’m very disappointed in the outcome.
I do appreciate your help and that of the others who participated. Thanks again!
To everyone who helped me with. The problem’s resolved and the upgrade completed using the method suggested by jbkt23 on [SOLVED] Upgrading from F33 to F34: on reboot system boots into F33 - Page 2. His method is to use dnf --releasever=34 distro-sync (don’t forget sudo!); the process mimicked a normal update - just took longer.
Thank you for the update, and I am glad you got it working.
One thing that would help others though would be if you could connect that link directly to the post (or at least the thread) that gave you the solution you used. The link as it is does not directly give anyone usable information.
After searching for some time I found this thread/post that may be the one you referenced.