Hi I am trying to upgrade to Fedora 35 but once upgrade finished and restarted still it pointing to f34 and I am not able to find error logs why it didn’t showing f35 , Any help would be appreciated. Please let me know if need more inforation
1 Like
sudo grubby --info=ALL
[sudo] password for user:
index=0
kernel="/boot/vmlinuz-5.14.18-200.fc34.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.14.18-200.fc34.x86_64.img"
title="Fedora (5.14.18-200.fc34.x86_64) 34 (Workstation Edition)"
id="502b4e4fe98b4ee29885f6d47364ec86-5.14.18-200.fc34.x86_64"
index=1
kernel="/boot/vmlinuz-5.14.17-201.fc34.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.14.17-201.fc34.x86_64.img"
title="Fedora (5.14.17-201.fc34.x86_64) 34 (Workstation Edition)"
id="502b4e4fe98b4ee29885f6d47364ec86-5.14.17-201.fc34.x86_64"
index=2
kernel="/boot/vmlinuz-5.14.16-201.fc34.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.14.16-201.fc34.x86_64.img"
title="Fedora (5.14.16-201.fc34.x86_64) 34 (Workstation Edition)"
id="502b4e4fe98b4ee29885f6d47364ec86-5.14.16-201.fc34.x86_64"
grub2-editenv: error: invalid environment block.
index=3
kernel="/boot/vmlinuz-0-rescue-502b4e4fe98b4ee29885f6d47364ec86"
args="$kernelopts"
initrd="/boot/initramfs-0-rescue-502b4e4fe98b4ee29885f6d47364ec86.img"
title="Fedora (0-rescue-502b4e4fe98b4ee29885f6d47364ec86) 31 (Thirty One)"
id="502b4e4fe98b4ee29885f6d47364ec86-0-rescue"
The update didn’t complete in this case. Did it go all the way to 100% when you rebooted?
2 Likes
Yes it does I tried both ways command line using dnf and also software update center .
Can you please retry, and this time hit space or esc while it’s updating so you get verbose information? It’s possible that it errors out, but that it isn’t clear from the progress bar.
Hi,
The newer kernel on Fedora 35 are 5.14.18 and it’s same with your latest kernel on Fedora 34 before update.
There should be a chance that you’re already on Fedora 35. Please check on /etc/os-release or on Gnome settings if you’re using Gnome.
Edit:
I have rawhide version but still using kernel 5.14.18 from Fedora 34 (and it’s ok as long as all working fine) since latest kernel on rawhide repos doesn’t work well on my laptop.
Next time if newer and stable kernel available, when you do upgrade, you should get newer kernel with fc35 version.
GNOME version - 40.5
syaramada@surya007 ~> cat /etc/os-release
NAME=Fedora
VERSION=“34 (Workstation Edition)”
ID=fedora
VERSION_ID=34
VERSION_CODENAME=“”
PLATFORM_ID=“platform:f34”
PRETTY_NAME=“Fedora 34 (Workstation Edition)”
ANSI_COLOR=“0;38;2;60;110;180”
LOGO=fedora-logo-icon
CPE_NAME=“cpe:/o:fedoraproject:fedora:34”
HOME_URL=“https://fedoraproject.org/”
DOCUMENTATION_URL=“System Administrator’s Guide :: Fedora Docs”
SUPPORT_URL=“Communicating and getting help - Fedora Project Wiki”
BUG_REPORT_URL=“https://bugzilla.redhat.com/”
REDHAT_BUGZILLA_PRODUCT=“Fedora”
REDHAT_BUGZILLA_PRODUCT_VERSION=34
REDHAT_SUPPORT_PRODUCT=“Fedora”
REDHAT_SUPPORT_PRODUCT_VERSION=34
PRIVACY_POLICY_URL=“Privacy Statement for the Fedora Project :: Fedora Docs”
VARIANT=“Workstation Edition”
VARIANT_ID=workstation
1 Like
My bad. You’re still on Fedora 34.
I’m interesting with part
index=3
kernel="/boot/vmlinuz-0-rescue-502b4e4fe98b4ee29885f6d47364ec86"
args="$kernelopts"
initrd="/boot/initramfs-0-rescue-502b4e4fe98b4ee29885f6d47364ec86.img"
title="Fedora (0-rescue-502b4e4fe98b4ee29885f6d47364ec86) 31 (Thirty One)"
id="502b4e4fe98b4ee29885f6d47364ec86-0-rescue"
The rescue boot still on Fedora 31. It’s interesting since on my case when I’m upgrading from Fedora 34 to Rawhide recently, the rescue boot are also upgraded to Fedora Rawhide (I’m also didn’t notice that the Fedora version also mentioned on the title= on your case).
Here my grubby info that still using Fedora 34 /boot/vmlinuz-5.14.18-200.fc34.x86_64 and Fedora 35 /boot/vmlinuz-5.14.20-300.fc35.x86_64 (manual install) but all already mention Rawhide on title=.
index=0
kernel="/boot/vmlinuz-5.14.20-300.fc35.x86_64"
args="ro rootflags=subvol=@ quiet modprobe.blacklist=pcspkr"
root="UUID=80bb5921-6d0b-4f02-be56-e8c800b7b215"
initrd="/boot/initramfs-5.14.20-300.fc35.x86_64.img"
title="Fedora Linux (5.14.20-300.fc35.x86_64) 36 (Rawhide Prerelease)"
id="7f27ecce41514d00b3fc25de5005ec7f-5.14.20-300.fc35.x86_64"
index=1
kernel="/boot/vmlinuz-5.14.18-200.fc34.x86_64"
args="ro rootflags=subvol=@ quiet modprobe.blacklist=pcspkr"
root="UUID=80bb5921-6d0b-4f02-be56-e8c800b7b215"
initrd="/boot/initramfs-5.14.18-200.fc34.x86_64.img"
title="Fedora Linux (5.14.18-200.fc34.x86_64) 36 (Rawhide Prerelease)"
id="7f27ecce41514d00b3fc25de5005ec7f-5.14.18-200.fc34.x86_64"
index=2
kernel="/boot/vmlinuz-0-rescue-7f27ecce41514d00b3fc25de5005ec7f"
args="ro rootflags=subvol=@ quiet modprobe.blacklist=pcspkr"
root="UUID=80bb5921-6d0b-4f02-be56-e8c800b7b215"
initrd="/boot/initramfs-0-rescue-7f27ecce41514d00b3fc25de5005ec7f.img"
title="Fedora Linux (0-rescue-7f27ecce41514d00b3fc25de5005ec7f) 36 (Rawhide Prerelease)"
id="7f27ecce41514d00b3fc25de5005ec7f-0-rescue"
I’m out of idea. May be with mentioning the the rescue boot still on Fedora 31 on your case could give clue to others to give help to you.
1 Like
Have we tried this yet?
Can we also have the full output of:
sudo dnf system-upgrade download --releasever=35
to see what’s in the transaction?
1 Like
@ankursinha I tired start those two failed services but still those are not able to run them , are those services preventing F35 upgrade ? I do make a video whole upgrade process but looks like this blog only accepts photos and not videos .
Please let me know if any more information would help to resolve this issue that would be great help
Really Appreciated…
2 Likes
Hi @ankursinha,
From the kernel arg, it show the resume parameter. Since from his grubby also mention Fedora 31 on rescue boot, maybe it also have physical swap.
Is there any chance that during the boot, the system actually try to resume from hibernation but also try to upgrade the system to Fedora 35?
Is this when you reboot to upgrade? It does show an error, so the upgrade is not going through successfully from the looks of it.
We’ll need to look into this error. I don’t think we’ve come across this one before 
Can you go through your journal logs to see what else it says for this failed upgrade boot?
It shouldn’t do both unless there’s something quite wrong with the system, but I can’t tell just yet.
Hi, I got the same result when trying to upgrade a f33 → f34. I suspect it’s the combination of using lvm partitioning and a uefi bios booting in ‘bios mode’ ak csm or legacy mode. Somehow the bootlaoder isn’t updated correctly in this case. I didn’t find a solution and left that system @f33. Now I have to upgrade it to f35 so I’ll follow this thread with interest!
Please let me know if required any more details that could help find root cause and able to upgrade to F35
@ankursinha Please let me know above logs helpful or any more logs that will help to resolve this issue when you got some time
Hi, maybe before you troubleshooting further about upgrading to F35, it would be wise if fixing current problem with your F34.
From your first post there mentioning grub2-editenv: error: invalid environment block.. From Red Hat Bugzilla – Bug 1714533 looks like you have corrupted /boot/grub2/grubenv file.
Your can regenerate it again with:
sudo grub2-editenv /boot/grub2/grubenv create
It will make blank new fresh grubenv file in directory /boot/grub2.
After that, please run sudo grubby --info=ALL to check if the error message already gone.
1 Like