Still on 37 after rebase to 38

Ask Fedora Ask in English
,
1

I followed the How to rebase to Fedora Silverblue 38 Beta – Fedora Community Blog
and 38 is not in the Grub menu. What to do?

1 Like
2

Please post output of rpm-ostree status

3

I followed the How to rebase to Fedora Silverblue 38 Beta – Fedora Community Blog
and when I restarted the Grub menu only lists the previous 37 images.

There was no error messages, so I assume the rebase was successful.

rpm-ostree status only lists the two 37 images.

Can anyone help me troubleshoot it?

4

I followed the How to rebase to Fedora Silverblue 38 Beta – Fedora Community Blog
and when I restarted the Grub menu only lists the previous 37 images.

There was no error messages, so I assume the rebase was successful.

rpm-ostree status only lists the two 37 images.

Can anyone help me troubleshoot it?

6

Here is what I get after rebasing to 38

$ rpm-ostree status
State: busy
Transaction: upgrade (download only)
Initiator: caller :1.121
Deployments:
● fedora:fedora/37/x86_64/silverblue
Version: 37.20230402.0 (2023-04-02T00:45:25Z)
BaseCommit: d04408862c3f2401aaa076e178e75d2e55c584d5643e0ae334fab527ddad070e
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: bridge-utils cabextract distrobox edk2-ovmf glances guestfs-tools htop libguestfs-tools libvirt libvirt-devel neofetch
qemu-kvm tldr virt-install virt-top

fedora:fedora/37/x86_64/silverblue
Version: 37.20230402.0 (2023-04-02T00:45:25Z)
BaseCommit: d04408862c3f2401aaa076e178e75d2e55c584d5643e0ae334fab527ddad070e
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: bridge-utils cabextract distrobox edk2-ovmf glances guestfs-tools htop libguestfs-tools libvirt libvirt-devel neofetch
qemu-kvm tldr virt-install virt-top
LocalPackages: megasync-4.8.1-1.1.x86_64 nautilus-megasync-5.1.0-1.1.x86_64
Pinned: yes

7

Can you post the journal log for rpm-ostreed.service?

8

rpm-ostree status
State: idle
Deployments:
● fedora:fedora/37/x86_64/silverblue
Version: 37.20230402.0 (2023-04-02T00:45:25Z)
BaseCommit: d04408862c3f2401aaa076e178e75d2e55c584d5643e0ae334fab527ddad070e
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: bridge-utils cabextract distrobox edk2-ovmf glances guestfs-tools htop libguestfs-tools libvirt libvirt-devel neofetch
qemu-kvm tldr virt-install virt-top

fedora:fedora/37/x86_64/silverblue
Version: 37.20230402.0 (2023-04-02T00:45:25Z)
BaseCommit: d04408862c3f2401aaa076e178e75d2e55c584d5643e0ae334fab527ddad070e
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: bridge-utils cabextract distrobox edk2-ovmf glances guestfs-tools htop libguestfs-tools libvirt libvirt-devel neofetch
qemu-kvm tldr virt-install virt-top
LocalPackages: megasync-4.8.1-1.1.x86_64 nautilus-megasync-5.1.0-1.1.x86_64
Pinned: yes

9

Would you please confirm if you can further update from 2023-04-02T00:45:25Z?

Please do post your journal log as suggested by Timothee.

Last time when my update failed to deploy, is when rebooting the system, before system reboots, the updates failed to deploy (due to too many btrfs subvols present) .

So to find out what happends during the rebooting process will help.

2 Likes
10

ok, ChatGPT walked me through how to get it to boot into 38.
Most of my goto Gnome extensions are still incompatible, so it’s back to 37 for me.

11

So, what was the issue?

12

Not sure I understand the process, but this is what worked;

ostree remote refs fedora

Found the fedora:fedora/38/x86_64/silverblue branch.

Pinned it:

sudo ostree admin pin fedora:fedora/38/x86_64/silverblue/[commit ID]

fedora [commit ID]
   Version: 38.20230331.0 (2022-03-31T00:05:23Z)
   Pinned: yes
   Origin: fedora

fedora:fedora/38/x86_64/silverblue       50ed88a1f37e26b6478f1cc99f9cc46b21c482bb25e8b0c0d321dc28f61f8ea5

Rebooted and selected 38 from the Grub menu.