Re: /boot problem.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/18/23 22:03, Samuel Sieb wrote:
On 5/18/23 20:36, Tim via users wrote:
On Thu, 2023-05-18 at 20:15 -0600, home user wrote:
What's the correct, best-practice way to remove the oldest kernel?

To remove a kernel, make sure that you're not currently using it.  Then
it's simply rpm --erase or dnf erase kernel-(with the full version
numbers).

On my system these are installed:

$ rpm -q kernel
kernel-6.1.18-100.fc36.x86_64
kernel-6.2.8-100.fc36.x86_64
kernel-6.2.14-100.fc36.x86_64

The oldest is kernel-6.1.18-100.fc36.x86_64, so I could

rpm --erase kernel-6.1.18-100.fc36.x86_64

That will only remove the empty package and you don't want to use rpm to do it anyway.  The best option is to "dnf remove kernel-core-..." which will also remove the related packages.

Thank-you Samuel and Tim.

ok.
Here we go...

1.
During boot-up, I wrote down what the grub menu contained:
Fedora Linux (6.2.15-200.fc37.x86_64 37
Fedora Linux (6.2.14-200.fc37.x86_64 37
Fedora Linux (6.2.12-200.fc37.x86_64 37
Fedora Linux (6.2.10-200.fc37.x86_64 37
Fedora Linux (6.2.9-200.fc37.x86_64 37
[rescue kernel, f30]
[memtest entry]
[2 windows-7 entries]

Hmmm.... 5 kernels, not 4.  That's suspicious.

2.
bash.2[~]: rpm -q kernel
kernel-6.2.8-100.fc36.x86_64
kernel-6.2.9-200.fc37.x86_64
kernel-6.2.14-200.fc37.x86_64
kernel-6.2.15-200.fc37.x86_64
bash.3[~]:

Hmmm.... This output does not match what's in the grub menu. That's suspicious.

3. Though I'm uncomfortable with what I saw in the grub menu and the rpm -q output, I'm gonna try the removals anyway, starting with the 6.2.8-100.
----------
bash.4[~]: dnf remove kernel-core-6.2.8-100.fc36.x86_64
Dependencies resolved.
======================================================================================================================================================
Package Architecture Version Repository Size
======================================================================================================================================================
Removing:
kernel-core x86_64 6.2.8-100.fc36 @@System 64 M
Removing dependent packages:
kernel x86_64 6.2.8-100.fc36 @@System 0 kernel-modules x86_64 6.2.8-100.fc36 @@System 61 M kernel-modules-core x86_64 6.2.8-100.fc36 @@System 36 M

Transaction Summary
======================================================================================================================================================
Remove  4 Packages

Freed space: 160 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :
  1/1
  Erasing          : kernel-6.2.8-100.fc36.x86_64
  1/4
  Running scriptlet: kernel-6.2.8-100.fc36.x86_64
  1/4
  Erasing          : kernel-modules-6.2.8-100.fc36.x86_64
  2/4
  Running scriptlet: kernel-modules-6.2.8-100.fc36.x86_64
  2/4
depmod: WARNING: could not open modules.order at /lib/modules/6.2.8-100.fc36.x86_64: No such file or directory depmod: WARNING: could not open modules.builtin at /lib/modules/6.2.8-100.fc36.x86_64: No such file or directory depmod: WARNING: could not open modules.builtin.modinfo at /lib/modules/6.2.8-100.fc36.x86_64: No such file or directory

  Erasing          : kernel-modules-core-6.2.8-100.fc36.x86_64
  3/4
warning: file 6.2.8-100.fc36.x86_64: remove failed: No such file or directory
warning: file weak-updates: remove failed: No such file or directory
warning: file vdso: remove failed: No such file or directory
warning: file updates: remove failed: No such file or directory
warning: file systemtap: remove failed: No such file or directory
warning: file source: remove failed: No such file or directory
warning: file modules.order: remove failed: No such file or directory
warning: file modules.networking: remove failed: No such file or directory
warning: file modules.modesetting: remove failed: No such file or directory
warning: file modules.drm: remove failed: No such file or directory
warning: file modules.builtin.modinfo: remove failed: No such file or directory
warning: file modules.builtin: remove failed: No such file or directory
warning: file modules.block: remove failed: No such file or directory
warning: file kernel: remove failed: No such file or directory
warning: file build: remove failed: No such file or directory

  Running scriptlet: kernel-modules-core-6.2.8-100.fc36.x86_64
  3/4
  Running scriptlet: kernel-core-6.2.8-100.fc36.x86_64
  4/4
  Erasing          : kernel-core-6.2.8-100.fc36.x86_64
  4/4
warning: file COPYING-6.2.8-100.fc36: remove failed: No such file or directory
warning: file vmlinuz: remove failed: No such file or directory
warning: file symvers.gz: remove failed: No such file or directory
warning: file config: remove failed: No such file or directory
warning: file System.map: remove failed: No such file or directory
warning: file .vmlinuz.hmac: remove failed: No such file or directory

  Running scriptlet: kernel-core-6.2.8-100.fc36.x86_64
  4/4
  Verifying        : kernel-6.2.8-100.fc36.x86_64
  1/4
  Verifying        : kernel-core-6.2.8-100.fc36.x86_64
  2/4
  Verifying        : kernel-modules-6.2.8-100.fc36.x86_64
  3/4
  Verifying        : kernel-modules-core-6.2.8-100.fc36.x86_64
  4/4

Removed:
kernel-6.2.8-100.fc36.x86_64 kernel-core-6.2.8-100.fc36.x86_64 kernel-modules-6.2.8-100.fc36.x86_64 kernel-modules-core-6.2.8-100.fc36.x86_64

Complete!
bash.5[~]:
----------
Well, it finished, but it looks "dirty" to me.
I'm going ahead with the removal of 6.2.9....
----------
bash.5[~]: dnf remove kernel-core-6.2.9-100.fc36.x86_64
No match for argument: kernel-core-6.2.9-100.fc36.x86_64
No packages marked for removal.
Dependencies resolved.
Nothing to do.
Complete!
bash.6[~]:
----------
I did not expect that!
One more...  on to 6.2.10....
----------
No match for argument: kernel-core-6.2.10-100.fc36.x86_64
No packages marked for removal.
Dependencies resolved.
Nothing to do.
Complete!
bash.7[~]:
----------
The rpm command now shows:
bash.7[~]: rpm -q kernel
kernel-6.2.9-200.fc37.x86_64
kernel-6.2.14-200.fc37.x86_64
kernel-6.2.15-200.fc37.x86_64
bash.8[~]:
----------
I'm gonna save this as a draft, and reboot to see what's now in the grub menu.
==========
The grub menu is UNchanged; it still has entries for 6.2.9 and 6.2.10.
The rpm -q output is also still showing 6.2.9, and NO 6.2.12.
What additional steps are needed to get this core problem fully and correctly resolved?

I'm not ignoring the other posts in this thread. I'll come back to those after this core issue is properly resolved.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux