How to remove unpinned boot entry showing on Silverblue?

Ask Fedora
,
1

I’ve been using Fedora for quite some time but just switched over to Silverblue on version 35. When I installed Silverblue it created a boot entry for Fedora 34 as well as for the current version of 35.

When I upgraded to 36, I assumed the 34 entry would be removed and replaced by one for 35. That didn’t happen. :slight_smile:

I have version 35 pinned along with the regular entries for 36, but that entry for version 34 is still there. When I look at rpm-ostree status, it does not show as pinned. How do I remove that entry so that I’m left with only version 35 and 36 now?

3

Can you show us the output of rpm-ostree status -v?

4

In hopes of not confusing @fooze666, but this is not true for Silverblue/Kinoite. By default there are only 2 deployments - the currently booted one and the previous (rollback) deployment. Additional deployments can be pinned manually. There are no kernel choices in GRUB, just deployment.

This is not a valid rpm-ostree command.

rpm-ostree remove is not a valid command, the command would be rpm-ostree uninstall .... This actually would not work in Silverblue, since the kernel is part of the base install. You’d have to do rpm-ostree override remove .... But don’t do that with the kernel. There are no kernel choices at boot as mentioned earlier; if you remove the kernel, the deployment will be unbootable.

5

This happens in normal fedora system so replacing just dnf with rpm-os should work. If that does not i have deleted that post for further confusion.

6

I’m attaching a picture of my Grub boot screen. There are 4 entries:

Fedora 36 that I am using
Fedora 36 default rollback deployment
Fedora 35 deployment that I pinned on purpose
Fedora 34 that I have never used.

Notice in the picture that the last entry just says Fedora 34 and not Fedora Linux 34 like the others…

I never used Silverblue version 34. I wiped my drive and installed 35 fresh. The F34 entry was there after the initial installation.

Following is the full output of ‘rpm-ostree status’:

State: idle
Deployments:
● fedora:fedora/36/x86_64/silverblue
                   Version: 36.20220523.0 (2022-05-23T00:43:57Z)
                BaseCommit: 30487f8aac075c10fbee025662d2dbaba305ba0534ca8482c4fb29108b634e45
              GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4
       RemovedBasePackages: firefox 100.0.1-1.fc36
           LayeredPackages: borgbackup gnome-tweaks jetbrains-mono-fonts openssl

  fedora:fedora/36/x86_64/silverblue
                   Version: 36.20220522.0 (2022-05-22T00:44:21Z)
                BaseCommit: 2c2f9a0b13f0e65407ae4616e5d5095acacd8e9c911c73443fc4764a7c7168cd
              GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4
       RemovedBasePackages: firefox 100.0.1-1.fc36
           LayeredPackages: borgbackup gnome-tweaks jetbrains-mono-fonts openssl

  fedora:fedora/35/x86_64/silverblue
                   Version: 35.20220517.0 (2022-05-17T00:55:34Z)
                BaseCommit: 91a86e047f400aa9f11bac91e226927c1279a0a25171df1020dbe41d435df6ab
              GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
       RemovedBasePackages: firefox 100.0-4.fc35
           LayeredPackages: borgbackup gnome-tweaks jetbrains-mono-fonts openssl
                    Pinned: yes

e825687ecea44d20237b13af8015e1193f8956b2.jpeg
e825687ecea44d20237b13af8015e1193f8956b2.jpeg1600×900 75.2 KB

8

That’s very odd. What did you have installed on the drive before wiping and installing Silverblue 35? Do you have any other drives attached?

What is the contents of /boot/loader/entries?

9

It was basically the same thing. I had Fedora Workstation (not Silverblue) with Windows dual boot.

Before I installed Silverblue, though, I used a live USB to nuke the partitions on my drive and start fresh. I wanted to give more space to Fedora and less to Windows.