I’ve followed the command line procedure described here for the upgrade.
After all the steps and the reboot I still see the version 31.
[giuliohome@myfedora ~]$ cat /etc/fedora-release
Fedora release 31 (Thirty One)
Did the upgrade go through without any errors?
Can you check the output of:
rpm -qa | grep fc31
and
rpm -qa | grep fc32
That’ll give us an idea of how many packages from the F32 and F31 repositories you have.
All packages in fc31.
I didn’t notice any error though
Should I repeat the last step?
sudo dnf system-upgrade reboot
or also the step before?
sudo dnf system-upgrade download --releasever=32
Repeated, this is the output of the latter
[SKIPPED] broadcom-wl-6.30.223.271-14.fc32.noarch.rpm: Already downloaded
[SKIPPED] rpmfusion-nonfree-release-32-1.noarch.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Complete!
Download complete! Use 'dnf system-upgrade reboot' to start the upgrade.
To remove cached metadata and transaction use 'dnf system-upgrade clean'
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
And now I try sudo dnf system-upgrade reboot for the third time
I see a black screen, there is written “system is upgrading…” and “don’t turn off your computer” but then after a few minutes at 0% of upgrade there is another reboot and I’m back at the version 31 after the login.
( Also as a marginal note, a little off-topic in this question, I see many lines in the bootmanager every time I restart my pc for different upgrades of Fedora 31 but obviously only one Fedora is “active”, how can I clean the obsolete lines there? Notice the following command
[giuliohome@myfedora ~]$ sudo ls /boot/loader/entries
1cb178663c5e44d1a4ff2c09f5819ae7-0-rescue.conf
1cb178663c5e44d1a4ff2c09f5819ae7-5.5.10-200.fc31.x86_64.conf
1cb178663c5e44d1a4ff2c09f5819ae7-5.6.13-200.fc31.x86_64.conf
1cb178663c5e44d1a4ff2c09f5819ae7-5.6.15-200.fc31.x86_64.conf
Again, this should be a separate, minor question)
You mean that there is more entries than those three?
There are more entries because I have windows so ok, but are those 3 needed? I guess I should ony see the latest 5.6.15 or what are the others for?
And, regarding the main topic, any idea why the upgrade is silently failing? If I hit esc during the process I see the test succeeded and all seems ok but eventually nothing happens when I login after a few minutes. Is there a way to look at a log and find the actual problem?
Do you have third party (non-Fedora) repositories added and enabled? If so, disable those third party repositories.
You could check the logs in /var/log/dnf.log
2 Likes
Transaction Summary
==========================================================================================================================
Install 70 Packages
Upgrade 2178 Packages
Remove 11 Packages
Downgrade 8 Packages
2020-06-10T19:28:23Z INFO Total size: 2.5 G
2020-06-10T19:28:23Z INFO Downloading Packages:
2020-06-10T19:28:39Z INFO Running transaction check
2020-06-10T19:28:43Z INFO Transaction check succeeded.
2020-06-10T19:28:43Z INFO Running transaction test
2020-06-10T19:29:50Z INFO Transaction test succeeded.
2020-06-10T19:29:50Z DDEBUG timer: transaction test: 66587 ms
2020-06-10T19:29:50Z INFO Running transaction
2020-06-10T19:29:50Z DEBUG RPMDB altered outside of DNF.
2020-06-10T19:31:20Z DDEBUG RPM transaction start.
2020-06-10T19:42:29Z INFO --- logging initialized ---
2020-06-10T19:42:29Z DDEBUG timer: config: 90 ms
2020-06-10T19:42:30Z DEBUG Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync, system-upgrade
2020-06-10T19:42:30Z DEBUG DNF version: 4.2.21
2020-06-10T19:42:30Z DDEBUG Command: dnf makecache --timer
2020-06-10T19:42:30Z DDEBUG Installroot: /
2020-06-10T19:42:30Z DDEBUG Releasever: 31
2020-06-10T19:42:30Z DEBUG cachedir: /var/cache/dnf
2020-06-10T19:42:30Z DDEBUG Base command: makecache
2020-06-10T19:42:30Z DDEBUG Extra commands: ['makecache', '--timer']
2020-06-10T19:42:30Z DEBUG Making cache files for all metadata files.
2020-06-10T19:42:30Z INFO Metadata timer caching disabled when running on metered connection.
2020-06-10T19:42:30Z DDEBUG Cleaning up.
Well, look,
[giuliohome@myfedora ~]$ dnf repolist enabled
repo id repo name
adobe-linux-x86_64 Adobe Systems Incorporated
fedora Fedora 31 - x86_64
fedora-cisco-openh264 Fedora 31 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 31 - x86_64
packages-microsoft-com-prod packages-microsoft-com-prod
rpmfusion-free RPM Fusion for Fedora 31 - Free
rpmfusion-free-updates RPM Fusion for Fedora 31 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 31 - Nonfree
rpmfusion-nonfree-updates RPM Fusion for Fedora 31 - Nonfree - Updates
updates Fedora 31 - x86_64 - Updates
updates-modular Fedora Modular 31 - x86_64 - Updates
Which ones should I disable?
1 Like
I’ve also tried cleaning and downloading again that 2.5GB stuf
sudo dnf system-upgrade clean
sudo dnf system-upgrade download --allowerasing --releasever=32
sudo dnf system-upgrade reboot
But nothing changes, I’m again rebooted into Fedora 31 after a few minutes with the following log
Transaction Summary
==========================================================================================================================
Install 70 Packages
Upgrade 2178 Packages
Remove 11 Packages
Downgrade 8 Packages
2020-06-11T03:36:16Z INFO Total size: 2.5 G
2020-06-11T03:36:16Z INFO Downloading Packages:
2020-06-11T03:36:31Z INFO Running transaction check
2020-06-11T03:36:36Z INFO Transaction check succeeded.
2020-06-11T03:36:36Z INFO Running transaction test
2020-06-11T03:37:43Z INFO Transaction test succeeded.
2020-06-11T03:37:43Z DDEBUG timer: transaction test: 66796 ms
2020-06-11T03:37:43Z INFO Running transaction
2020-06-11T03:37:43Z DEBUG RPMDB altered outside of DNF.
2020-06-11T03:39:14Z DDEBUG RPM transaction start.
I’m disappointed this time.
2 Likes
Well, maybe the hint is from the /var/log/boot.log:
[ 236.437337] dnf[719]: Transaction test succeeded.
[ 236.437704] dnf[719]: Running transaction
[e[0;32m OK e[0m] Created slice e[0;1;39mUser and Session Slicee[0m.
Starting e[0;1;39mLogin Servicee[0m...
[e[0;32m OK e[0m] Started e[0;1;39mLogin Servicee[0m.
[ 356.394764] dnf[719]: Running scriptlet: filesystem-3.14-2.fc32.x86_64 1/1
[ 356.395794] dnf[719]: Running scriptlet: texlive-base-7:20190410-12.fc32.x86_64 1/1
[ 356.446201] dnf[719]: Running scriptlet: copy-jdk-configs-3.7-5.fc32.noarch 1/1
[ 356.459833] dnf[719]: Running scriptlet: java-1.8.0-openjdk-headless-1:1.8.0.252.b09-1.fc32.x 1/1
[ 356.464607] dnf[719]: Running scriptlet: npm-1:6.14.4-1.12.16.3.1.fc32.x86_64 1/1
[ 356.488382] dnf[719]: Running scriptlet: selinux-policy-minimum-3.14.5-39.fc32.noarch 1/1
[ 356.492578] dnf[719]: Running scriptlet: selinux-policy-targeted-3.14.5-39.fc32.noarch 1/1
[ 356.494823] dnf[719]: Running scriptlet: firefox-77.0.1-2.fc32.x86_64 1/1
[ 356.498439] dnf[719]: Running scriptlet: alsa-sof-firmware-1.5-1.fc32.noarch 1/1
[ 357.857238] dnf[719]: Running scriptlet: python3-notebook-6.0.2-4.fc32.noarch 1/1
[ 360.659581] dnf[719]: Preparing : 1/1
[e[0;1;31mFAILEDe[0m] Failed to start e[0;1;39mSystem Upgrade using DNFe[0m.
See 'systemctl status dnf-system-upgrade.service' for details.
[e[0;32m OK e[0m] Reached target e[0;1;39mOffline System Updatee[0m.
Starting e[0;1;39mSystem Upgrade using DNF failede[0m...
[e[0;32m OK e[0m] Started e[0;1;39mSystem Upgrade using DNF failede[0m.
1 Like
And
● dnf-system-upgrade.service - System Upgrade using DNF
Loaded: loaded (/usr/lib/systemd/system/dnf-system-upgrade.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: http://www.freedesktop.org/wiki/Software/systemd/SystemUpdates
1 Like
OK, but that indicates that the upgrade did not complete which is confirmed from your later post.
Does this step not give any errors/warnings?
sudo dnf system-upgrade download --refresh --releasever=32
Also, how much free space do you have? Could we have the output of:
df -lh
please?
3 Likes
I see that it doesn’t. Could we look at your disk space then? It’s possible your system runs out of space during the upgrade, so that would be start.
If you try the upgrade next time, when it starts, please press the right arrow key to see the upgrade process, and see how far it gets and if it says anything when it fails.
1 Like
I usually do Files>Other Locations>Then I look at the Computer and I read the GB.
I don’t understand why the above approximation is different from df -H anyway I had 24GB
or from an old df
/dev/sda7 44393768 18083332 24025636 43% /
before and now I have 21.2GB from the Computer in Files or
[giuliohome@myfedora ~]$ df -lh
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.9G 44M 3.8G 2% /dev/shm
tmpfs 3.9G 1.9M 3.9G 1% /run
/dev/sda7 43G 21G 20G 51% /
tmpfs 3.9G 92K 3.9G 1% /tmp
/dev/sda5 976M 264M 646M 29% /boot
tmpfs 781M 21M 761M 3% /run/user/1000
1 Like
Regarding your other question:
That is normal. DNF automatically keeps some previous kernel versions around, so that in case something goes wrong with the latest one, you can go back to a previous, working config. You can just ignore them, as newer kernels are installed, the older entries will be removed.
2 Likes
After that command the upgrade magically started. IDK why!?
It is on going now.
At the end of the upgrade, hopefully in a few minutes… I will mark it as a solution even if it is not fully clear to me what really happened.
2 Likes
Ah weird. Not sure either, but glad it got sorted 