Hi All,
After initiating "dnf system-upgrade reboot", my system reboots, prompts me for my LUKS password, then pops up "Upgrading you system 0%". Seconds later it reboot and I am back in Fedora 30.
I have completely removed qemu everything and virt everything.
Any words of wisdom?
Many thanks, -T
This is what I have been following
FC 30 -->> FC 31: https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
# rpm --rebuilddb # rpm -Va --nofiles --nodigest if anything is too new, do a # dnf downgrade offender(s)
# dnf --enablerepo=* update --refresh # dnf install python3-dnf-plugin-system-upgrade # dnf system-upgrade download --refresh --releasever=31 --allowerasing --best # rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-primary # dnf clean packages <-- optional # dnf system-upgrade reboot
On 11/3/19 12:15 PM, ToddAndMargo via users wrote:
After initiating "dnf system-upgrade reboot", my system reboots, prompts me for my LUKS password, then pops up "Upgrading you system 0%". Seconds later it reboot and I am back in Fedora 30.
I have completely removed qemu everything and virt everything.
Any words of wisdom?
Check the most recent
/var/log/dnf.log and dnf.rpm.log for messages which may offer clues.
On 11/2/19 9:40 PM, Ed Greshko wrote:
On 11/3/19 12:15 PM, ToddAndMargo via users wrote:
After initiating "dnf system-upgrade reboot", my system reboots, prompts me for my LUKS password, then pops up "Upgrading you system 0%". Seconds later it reboot and I am back in Fedora 30.
I have completely removed qemu everything and virt everything.
Any words of wisdom?
Check the most recent
The bottom of each
/var/log/dnf.log and
2019-11-03T05:21:23Z DEBUG reviving: 'rpmfusion-free' can be revived - metalink checksums match. 2019-11-03T05:21:23Z DEBUG rpmfusion-free: using metadata from Tue 16 Apr 2019 01:46:20 PM PDT. 2019-11-03T05:21:23Z DEBUG reviving: 'rpmfusion-nonfree-updates' can be revived - metalink checksums match. 2019-11-03T05:21:23Z DEBUG rpmfusion-nonfree-updates: using metadata from Mon 28 Oct 2019 01:33:42 AM PDT. 2019-11-03T05:21:24Z DEBUG reviving: 'rpmfusion-nonfree' can be revived - metalink checksums match. 2019-11-03T05:21:24Z DEBUG rpmfusion-nonfree: using metadata from Tue 16 Apr 2019 02:53:39 PM PDT. 2019-11-03T05:21:24Z DDEBUG timer: sack setup: 8038 ms 2019-11-03T05:21:24Z DEBUG Completion plugin: Generating completion cache... 2019-11-03T05:21:25Z INFO Metadata cache created. 2019-11-03T05:21:25Z DDEBUG Cleaning up.
dnf.rpm.log for messages which may offer clues.
2019-11-03T04:06:37Z SUBDEBUG Upgraded: kbd-misc-2.0.4-13.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: adobe-mappings-pdf-20180407-3.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: emacs-filesystem-1:26.2-1.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: mesa-filesystem-19.1.8-1.fc30.x86_64 2019-11-03T04:06:37Z SUBDEBUG Upgraded: hwdata-0.328-1.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: qt-settings-30.3-1.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: qt5-qtbase-common-5.12.5-1.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: libwacom-data-0.33-1.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: adwaita-cursor-theme-3.32.0-1.fc30.noarch 2019-11-03T04:06:37Z SUBDEBUG Upgraded: libgcc-9.2.1-1.fc30.x86_64 2019-11-03T04:06:58Z INFO --- logging initialized --- 2019-11-03T04:07:09Z INFO --- logging initialized --- 2019-11-03T04:10:18Z INFO --- logging initialized --- 2019-11-03T04:20:48Z INFO --- logging initialized --- 2019-11-03T05:21:15Z INFO --- logging initialized ---
On 11/3/19 1:54 PM, ToddAndMargo via users wrote:
The bottom of each
Nothing at the bottom.
FWIW, I would do....
dnf system-upgrade clean dnf system-upgrade download --releasever=31
and then
dnf system-upgrade -v reboot --debugsolver
And look through the new logs for and "CRIT" or "CRITICAL" notations
On 11/2/19 9:15 PM, ToddAndMargo via users wrote:
After initiating "dnf system-upgrade reboot", my system reboots, prompts me for my LUKS password, then pops up "Upgrading you system 0%". Seconds later it reboot and I am back in Fedora 30.
After doing that, run "journalctl -b-1" and see if there's anything relevant. Possibly "dnf system-upgrade log" and "dnf system-upgrade log --number=<number>" might be helpful.
On 11/2/19 11:23 PM, Ed Greshko wrote:
On 11/3/19 1:54 PM, ToddAndMargo via users wrote:
The bottom of each
Nothing at the bottom.
FWIW, I would do....
dnf system-upgrade clean dnf system-upgrade download --releasever=31
and then
dnf system-upgrade -v reboot --debugsolver
And look through the new logs for and "CRIT" or "CRITICAL" notations
Hi Ed,
That was it.
I had to remove the corked qemu* and *virt* stuff to get system-upgrade to take, but corked junk was alredy downloaded. "dnf system-upgrade clean" solved the issue.
Thank you!!!!
-T
On 11/4/19 7:23 AM, ToddAndMargo via users wrote:
On 11/2/19 11:48 PM, Ed Greshko wrote:
On 11/3/19 1:54 PM, ToddAndMargo via users wrote:
The bottom of each
Oh, you do have dnf-plugins-extras-4.0.7-2.fc30 installed, yes?
No. Is it a good think to have?
Well, it is moot now that you've upgraded.
However, that version contains a new version of dnf-plugin-system-upgrade which fixes a BZ that resulted in similar symptoms of an upgrade not completing upon reboot.
On 11/3/19 3:32 PM, Ed Greshko wrote:
On 11/4/19 7:23 AM, ToddAndMargo via users wrote:
On 11/2/19 11:48 PM, Ed Greshko wrote:
On 11/3/19 1:54 PM, ToddAndMargo via users wrote:
The bottom of each
Oh, you do have dnf-plugins-extras-4.0.7-2.fc30 installed, yes?
No. Is it a good think to have?
Well, it is moot now that you've upgraded.
However, that version contains a new version of dnf-plugin-system-upgrade which fixes a BZ that resulted in similar symptoms of an upgrade not completing upon reboot.
Hi Ed,
Seems dumb-dumb here had installed both 32 and 64 bit qemu and virt stuff. After cleaning out all the cob webs, things are working well.
Proper install is dnf install qemu virt-manager virt-viewer
not dnf install qemu* virt*
Well, well is relative. Perl 6 is can not find any of my subs in my modules. AAAAHHHH!!!!
Thank you for the help. Dude you rock!
-T