Hi guys,
I'm running kernel-5.11.17-200.fc33.x86_64 with my F33, and I tried to upgrade from F33 tp F34. I performed all adviced steps sucessfully, including the last download step "sudo dnf system-upgrade download --releasever=34".
But nothing special happens when calling the last step "sudo dnf system-upgrade reboot": The system is booted without any message into F33 again, and I dont know, why.
Anybody has an idea what to do for getting some important infos?
Kind regards
Joachim Backes
--
Fedora release 33 (Thirty Three) Kernel-5.11.17-200.fc33.x86_64
Joachim Backes joachim.backes@rhrk.uni-kl.de https://www-user.rhrk.uni-kl.de/~backes/
On 4/30/21 1:13 PM, Thomas Mittelstaedt wrote:
Have you checked the logs with journalctl?
Gruß, Thomas Mittelstaedt
Thank you. Is there any text in the system journal I should search for?
Regards and "Danke"
Joachim Backes
Am 30.04.2021 12:12 schrieb Joachim Backes joachim.backes@rhrk.uni-kl.de:
Hi guys, I'm running kernel-5.11.17-200.fc33.x86_64 with my F33, and I tried to upgrade from F33 tp F34. I performed all adviced steps sucessfully, including the last download step "sudo dnf system-upgrade download --releasever=34". But nothing special happens when calling the last step "sudo dnf system-upgrade reboot": The system is booted without any message into F33 again, and I dont know, why. Anybody has an idea what to do for getting some important infos? Kind regards Joachim Backes -- Fedora release 33 (Thirty Three) Kernel-5.11.17-200.fc33.x86_64 Joachim Backes <joachim.backes@rhrk.uni-kl.de> https://www-user.rhrk.uni-kl.de/~backes/ _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 30/04/2021 20:29, Joachim Backes wrote:
On 4/30/21 1:13 PM, Thomas Mittelstaedt wrote:
Have you checked the logs with journalctl?
Gruß, Thomas Mittelstaedt
Thank you. Is there any text in the system journal I should search for?
Regards and "Danke"
I don't know if this helps at all....
But after doing the dnf system-upgrade reboot the kernel selection is, of course, for the F33 kernel. But the journal for that boot then shows....
Apr 30 08:35:19 meimei.greshko.com dnf[722]: Last metadata expiration check: 0:35:51 ago on Fri 30 Apr 2021 07:59:28 AM CST. Apr 30 08:35:19 meimei.greshko.com python3[722]: Starting system upgrade. This will take a while. Apr 30 08:35:38 meimei.greshko.com dnf[722]: Dependencies resolved.
and so on.
After upgrade from F33 to F34, the newly-installed kernel was not the default to boot. I had to explicitly select the F34 kernel in lieu of an older F33 kernel at boot time. This was a surprise for me (I expected the last kernal installed to become the default), but it may not be germane in your situation.
Hi Richard,
thanks for your reply.
What I saw, is: No kernel had been recently installed for the new system, Why? Do I have to install it manually before running the whole dnf upgrade procedure?
What is your opinion?
Reagrds
Joachim Backes
On 4/30/21 2:57 PM, Richard Ryniker wrote:
After upgrade from F33 to F34, the newly-installed kernel was not the default to boot. I had to explicitly select the F34 kernel in lieu of an older F33 kernel at boot time. This was a surprise for me (I expected the last kernal installed to become the default), but it may not be germane in your situation. _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
If no F34 kernal is installed, something went awry during the offline upgrade.
Perhaps try the upgrade again, to learn whether this is a consistent failure?
One of my systems has a /boot filesystem that is too small. Before I can install a new kernel, I have to manually remove an older kernal in order to have sufficient space. With "dnf upgrade" the operation emits a message about not enough space and does not start. Could it be that "dnf system-upgrade" fails to detect insufficient space, at least in some cases? You can check how much space is available in /boot to learn whether this might possibly be a concern in your case.
Despite its great convenience compared to a fresh install, upgrade often preserves old, no-longer-used data that sometimes causes problems. Successive system-upgrades makes this worse. If you cannot find a solution to your system-upgrade difficulty, I would do a new install in order to start with a clean slate.
On Fri, Apr 30, 2021, 6:58 AM Richard Ryniker ryniker@ryniker.org wrote:
After upgrade from F33 to F34, the newly-installed kernel was not the default to boot. I had to explicitly select the F34 kernel in lieu of an older F33 kernel at boot time. This was a surprise for me (I expected the last kernal installed to become the default), but it may not be germane in your situation. ______________________________
This sounds like a grubenv grub.cfg disconnect. The usual cause it's running 'grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg' after upgrading to Fedora 34. But we might have a rare bug with converting from the old to new (same as BIOS) location.
What do you get for grub2-editenv list
If the default kernel listed is correct, but isn't used as a default, do:
grep configfile /boot/efi/EFI/fedora/grub.cfg
Possibly related are a few reports of grub> prompt following upgrades.
-- Chris Murphy
在 2021-04-30星期五的 08:57 -0400，Richard Ryniker写道：
After upgrade from F33 to F34, the newly-installed kernel was not the default to boot. I had to explicitly select the F34 kernel in lieu of an older F33 kernel at boot time. This was a surprise for me (I expected the last kernal installed to become the default), but it may not be germane in your situation.
It not the last installed becomes the dafault, but the one with highest version nummber. And unlickily, there is a kernel downgrade with the upgrade from f33 to f34.
But that should not hurt, Using f33 kernel on f34 shouldn't break things.
Qiyu Yan yanqiyu@fedoraproject.org wrote on Sat, 01 May 2021 14:40:34 +0800:
It not the last installed becomes the dafault, but the one with highest version nummber. And unluckily, there is a kernel downgrade with the upgrade from f33 to f34.
That explains it. The recent F34 update to the 5.11.16-300 kernel restored my default boot kernel to F34.
On 2021-04-30 3:12 a.m., Joachim Backes wrote:
I'm running kernel-5.11.17-200.fc33.x86_64 with my F33, and I tried to upgrade from F33 tp F34. I performed all adviced steps sucessfully, including the last download step "sudo dnf system-upgrade download --releasever=34".
Does that command tell you at the end that it's ready for you to reboot? What are the last few lines of the output?
But nothing special happens when calling the last step "sudo dnf system-upgrade reboot": The system is booted without any message into F33 again, and I dont know, why.
Anybody has an idea what to do for getting some important infos?
"dnf system-upgrade log" will give you a list of available upgrade logs. I don't know what the command to read a specific log is since I don't have any handy right now to test.
On 02/05/2021 07:00, Samuel Sieb wrote:
"dnf system-upgrade log" will give you a list of available upgrade logs. I don't know what the command to read a specific log is since I don't have any handy right now to test.
dnf system-upgrade log --number=X
-
Chris Murphy -
Ed Greshko -
Joachim Backes -
Qiyu Yan -
Richard Ryniker -
Samuel Sieb -
Thomas Mittelstaedt