Re: /boot problem.
> On 19 May 2023, at 02:29, home user wrote: > > On 5/18/23 6:30 PM, Felix Miata wrote: >> home user composed on 2023-05-18 16:21 (UTC-0600): > [... snip ...] > > Added information: > This workstation is 10 years old; Fedora was installed on it in spring 2013. > >> How many kernels are installed, more than two? If yes, uninstall the oldest. > > 4 kernels. > I vaguely recall late last year being advised by this list to expand this > from 3 to 4 or 5. I did that, to 4, but I don't remember how. > Q1: How do I change that back to 3 permanently? > Q2: How do I uninstall the oldest kernel? > >> Listing output from >>tree /boot >> might suggest something is there that doesn't belong. > > I put the output of "tree /boot" on the google drive here: > "https://drive.google.com/file/d/1MlfEduVC62KVLnnBJMXbmUd0_zkhDnHF/view?usp=sharing";. > I do not know what does not belong. You have grub and grub2. You can remove /boot/grub i think You have an init fs for a 3.11 kernel that you do not need. Barry > >> What size is the filesystem on which /boot/ lives? Separate partition? BTRFS? > > Does this answer those questions?... > - > bash.7[~]: df > Filesystem 1K-blocks Used Available Use% Mounted on > devtmpfs40960 4096 0% /dev > tmpfs81540120 8154012 0% /dev/shm > tmpfs3261608 1696 3259912 1% /run > /dev/sda6 51422028 27967968 20816236 58% / > tmpfs8154012 88 8153924 1% /tmp > /dev/sda3 485348 379984 75668 84% /boot > /dev/sda7 947550748 19685980 879705128 3% /home > tmpfs1630800 3900 1626900 1% /run/user/1001 > bash.8[~]: > - > I will respond to Lukas and Tim shortly. > > Thanks, > Bill. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kernel growth (was: /boot problem.)
home user composed on 2023-05-18 20:25 (UTC-0600): > The boot partition has been big enough for over 10 years, including the time > I've had 4 kernels + 1 rescue kernel (since late last year). I'm puzzled > about how the /boot partition is now too small. Has the kernel grown > significantly? In 10 years, very, very much. Fedora's splitting of kernels into multiple packages complicates assessment of changes in size, but here is some raw data showing the general trend from: ls -hgGrS kernel-*4.rpm -rw-rw-r-- 1 79K Jan 19 2018 kernel-4.14.14-300.fc27.x86_64.rpm -rw-rw-r-- 1 23M Jan 19 2018 kernel-core-4.14.14-300.fc27.x86_64.rpm -rw-rw-r-- 1 27M Jan 19 2018 kernel-modules-4.14.14-300.fc27.x86_64.rpm -rw-rw-r-- 1 107K May 15 2019 kernel-5.0.16-100.fc28.x86_64.rpm -rw-rw-r-- 1 23M May 15 2019 kernel-core-5.0.16-100.fc28.i686.rpm -rw-rw-r-- 1 29M May 15 2019 kernel-modules-5.0.16-100.fc28.x86_64.rpm -rw-r--r-- 1 19K Nov 15 2019 kernel-5.3.11-100.fc29.x86_64.rpm -rw-r--r-- 1 29M Nov 15 2019 kernel-modules-5.3.11-100.fc29.x86_64.rpm -rw-r--r-- 1 31M Nov 15 2019 kernel-core-5.3.11-100.fc29.x86_64.rpm -rw-r--r-- 1 26K Jun 12 2020 kernel-5.6.13-100.fc30.x86_64.rpm -rw-r--r-- 1 29M Jun 12 2020 kernel-modules-5.6.13-100.fc30.x86_64.rpm -rw-r--r-- 1 33M Jun 12 2020 kernel-core-5.6.13-100.fc30.x86_64.rpm -rw-r--r-- 1 45K Oct 17 2020 kernel-5.8.15-101.fc31.x86_64.rpm -rw-r--r-- 1 30M Oct 17 2020 kernel-modules-5.8.15-101.fc31.x86_64.rpm -rw-r--r-- 1 34M Oct 17 2020 kernel-core-5.8.15-101.fc31.x86_64.rpm -rw-r--r-- 1 154K Aug 8 2021 kernel-5.11.22-100.fc32.x86_64.rpm -rw-r--r-- 1 31M Aug 8 2021 kernel-modules-5.11.22-100.fc32.x86_64.rpm -rw-r--r-- 1 34M Aug 8 2021 kernel-core-5.11.22-100.fc32.x86_64.rpm -rw-rw-r-- 1 32M Nov 13 2021 kernel-modules-5.14.18-100.fc33.x86_64.rpm -rw-rw-r-- 1 35M Nov 13 2021 kernel-core-5.14.18-100.fc33.x86_64.rpm -rw-rw-r-- 1 47M May 30 2022 kernel-core-5.17.12-100.fc34.x86_64.rpm -rw-rw-r-- 1 54M May 30 2022 kernel-modules-5.17.12-100.fc34.x86_64.rpm -rw-r--r-- 1 116K Dec 8 17:21 kernel-6.0.12-100.fc35.x86_64.rpm -rw-r--r-- 1 52M Dec 8 17:21 kernel-core-6.0.12-100.fc35.x86_64.rpm -rw-r--r-- 1 62M Dec 8 17:21 kernel-modules-6.0.12-100.fc35.x86_64.rpm -rw-rw-r-- 1 116K Jan 7 18:00 kernel-6.0.18-300.fc37.x86_64.rpm -rw-rw-r-- 1 121K Feb 26 11:20 kernel-6.1.14-200.fc37.x86_64.rpm -rw-rw-r-- 1 130K May 11 18:55 kernel-6.2.15-200.fc37.x86_64.rpm -rw-rw-r-- 1 264K Oct 21 2022 kernel-5.19.16-301.fc37.x86_64.rpm -rw-rw-r-- 1 16M May 11 18:56 kernel-core-6.2.15-200.fc37.x86_64.rpm -rw-rw-r-- 1 31M May 11 18:56 kernel-modules-core-6.2.15-200.fc37.x86_64.rpm -rw-r--r-- 1 49M Oct 24 2022 kernel-core-5.19.17-300.fc37.x86_64.rpm -rw-rw-r-- 1 49M Jan 7 18:00 kernel-core-6.0.18-300.fc37.x86_64.rpm -rw-rw-r-- 1 49M Feb 26 11:21 kernel-core-6.1.14-200.fc37.x86_64.rpm -rw-rw-r-- 1 55M May 11 18:56 kernel-modules-6.2.15-200.fc37.x86_64.rpm -rw-rw-r-- 1 55M Apr 26 21:11 kernel-modules-6.2.13-200.fc37.x86_64.rpm -rw-r--r-- 1 55M May 1 08:11 kernel-modules-6.2.14-200.fc37.x86_64.rpm -rw-r--r-- 1 58M Oct 24 2022 kernel-modules-5.19.17-300.fc37.x86_64.rpm -rw-rw-r-- 1 59M Jan 7 18:00 kernel-modules-6.0.18-300.fc37.x86_64.rpm -rw-rw-r-- 1 59M Feb 26 11:21 kernel-modules-6.1.14-200.fc37.x86_64.rpm These are from an old Athlon that I stopped using Fedora on several years ago that you could compare to your current installed kernels: # ls -hgGrS initr*g vmlin*E -rwxr-xr-x 1 6.3M Mar 31 2017 vmlinuz-4.10.8-200.fc25.i686+PAE* -rwxr-xr-x 1 6.8M May 22 2018 vmlinuz-4.16.11-100.fc26.i686+PAE* -rw--- 1 11M Apr 4 2017 initramfs-4.10.8-200.fc25.i686+PAE.img -rw--- 1 12M Sep 18 2018 initramfs-4.16.11-100.fc26.i686+PAE.img # ls -hgGrS initr*g vmlin*[E,6] -rwxr-xr-x 1 6.9M Sep 10 2018 vmlinuz-4.18.7-200.fc28.i686* -rwxr-xr-x 1 7.1M Sep 13 2018 vmlinuz-4.18.7-100.fc27.i686+PAE* -rwxr-xr-x 1 7.1M May 14 2019 vmlinuz-5.0.16-100.fc28.i686* -rw--- 1 13M Sep 18 2018 initramfs-4.18.7-100.fc27.i686+PAE.img -rw--- 1 14M Sep 18 2018 initramfs-4.18.7-200.fc28.i686.img -rw--- 1 14M Aug 4 2019 initramfs-5.0.16-100.fc28.i686.img Rather easier to see I collected a few months ago from Tumbleweed 20230331 64bit: /usr/lib/modules # du -d1 (sorted) 73196 ./5.4.14-2-default # 9052400 vmlinuz in /boot 73956 ./5.5.13-1-default # 9142512 vmlinuz in /boot 75524 ./5.6.14-1-default # 9311888 vmlinuz in /boot 75920 ./5.7.11-1-default # 10050K vmlinuz in /boot 77236 ./5.8.15-1-default # 10171K vmlinuz in /boot 76356 ./5.9.14-1-default # 10253K vmlinuz in /boot 77292 ./5.10.16-1-default # 10529K vmlinuz in /boot 95748 ./5.11.16-1-default # 10616K vmlinuz in /boot 96612 ./5.12.13-1-default # 10762K vmlinuz in /boot 98440 ./5.13.12-1-default # 10724K vmlinuz in /boot 123952 ./5.14.14-3-default # 10884K vmlinuz; removal freed 163.9 MiB 163272 ./5.15.12-1-default # 1
Re: /boot problem.
On 19/05/2023 03:24, home user wrote:
On 5/18/23 6:30 PM, Felix Miata wrote:
I put the output of "tree /boot" on the google drive here:
"https://drive.google.com/file/d/1MlfEduVC62KVLnnBJMXbmUd0_zkhDnHF/view?usp=sharing";.
I do not know what does not belong.
I have not seen initrd-plymouth.img and {initramfs,vmlinuz}-fedup
previously, but I guess they are leftovers from some earlier system
upgrade. I don't think they are needed any more, especially if they are
older than about a year. You likely can simply remove those (together
with the initramfs for the old fc19 kernel).
Also looks like you have three installations of grub on your /boot.
One in /boot/grub, one in /boot/grub/locale (which is totally out of
place) and one in /boot/grub2. You only need one of them. The currently
used path should be /boot/grub2. You should verify that the files in
/boot/grub and /boot/grub/locale are indeed older than /boot/grub2 and
then you can delete /boot/grub. Or better rename the directory to
something else and if your system still boots properly, then remove it.
If not, use some live system from USB and rename it back.
Since /boot/efi does not seem to be on a separate partition, I'm
assuming you are not using UEFI but booting in legacy BIOS mode. You
then likely also don't need the content of /boot/efi. But since there is
enough other stuff to remove and it will come back in the future with
some package updates if you simply delete the files, I would leave that
for last.
If you really are booting in legacy BIOS mode and also want to get rid
of the files in /boot/efi, you would have to remove the packages
grub2-efi-x64 and shim-x64 (which are protected from removal by files in
/etc/dnf/protected.d).
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
On Thu, May 18, 2023 at 9:29 PM home user wrote: > [...] > - > bash.7[~]: df > Filesystem 1K-blocks Used Available Use% Mounted on > devtmpfs40960 4096 0% /dev > tmpfs81540120 8154012 0% /dev/shm > tmpfs3261608 1696 3259912 1% /run > /dev/sda6 51422028 27967968 20816236 58% / > tmpfs8154012 88 8153924 1% /tmp > /dev/sda3 485348 379984 75668 84% /boot > /dev/sda7 947550748 19685980 879705128 3% /home > tmpfs1630800 3900 1626900 1% /run/user/1001 > bash.8[~]: > - > I will respond to Lukas and Tim shortly. If you don't need the extra kernels, then see https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-clean-up-old-kernels . Jeff ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
For comparison here is the sizes of /boot and the folders inside it on my file server. $ du -sh /boot/* 252K/boot/config-6.2.11-300.fc38.x86_64 252K/boot/config-6.2.13-300.fc38.x86_64 252K/boot/config-6.2.14-300.fc38.x86_64 7.1M/boot/efi 2.4M/boot/grub2 80M /boot/initramfs-0-rescue-23861aed63d748da85011d84ee28e601.img 28M /boot/initramfs-6.2.11-300.fc38.x86_64.img 28M /boot/initramfs-6.2.13-300.fc38.x86_64.img 28M /boot/initramfs-6.2.14-300.fc38.x86_64.img 24K /boot/loader 16K /boot/lost+found 0 /boot/symvers-6.2.11-300.fc38.x86_64.gz 0 /boot/symvers-6.2.13-300.fc38.x86_64.gz 0 /boot/symvers-6.2.14-300.fc38.x86_64.gz 8.1M/boot/System.map-6.2.11-300.fc38.x86_64 8.1M/boot/System.map-6.2.13-300.fc38.x86_64 8.1M/boot/System.map-6.2.14-300.fc38.x86_64 11M /boot/vmlinuz-0-rescue-23861aed63d748da85011d84ee28e601 14M /boot/vmlinuz-6.2.11-300.fc38.x86_64 14M /boot/vmlinuz-6.2.13-300.fc38.x86_64 14M /boot/vmlinuz-6.2.14-300.fc38.x86_64 $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sda3 974M 240M 667M 27% /boot As you can see I have 3 kernels only. I doubt your space issue is the number of kernels unless you have a very old install that predates the 1GiB /boot days. Barry ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
On Fri, 2023-05-19 at 14:03 +0100, Barry Scott wrote: > For comparison here is the sizes of /boot and the folders inside it > on my file server. > > $ du -sh /boot/* > 252K/boot/config-6.2.11-300.fc38.x86_64 > 252K/boot/config-6.2.13-300.fc38.x86_64 > 252K/boot/config-6.2.14-300.fc38.x86_64 > 7.1M/boot/efi > 2.4M/boot/grub2 > 80M /boot/initramfs-0-rescue-23861aed63d748da85011d84ee28e601.img > 28M /boot/initramfs-6.2.11-300.fc38.x86_64.img > 28M /boot/initramfs-6.2.13-300.fc38.x86_64.img > 28M /boot/initramfs-6.2.14-300.fc38.x86_64.img > 24K /boot/loader > 16K /boot/lost+found > 0 /boot/symvers-6.2.11-300.fc38.x86_64.gz > 0 /boot/symvers-6.2.13-300.fc38.x86_64.gz > 0 /boot/symvers-6.2.14-300.fc38.x86_64.gz > 8.1M/boot/System.map-6.2.11-300.fc38.x86_64 > 8.1M/boot/System.map-6.2.13-300.fc38.x86_64 > 8.1M/boot/System.map-6.2.14-300.fc38.x86_64 > 11M /boot/vmlinuz-0-rescue-23861aed63d748da85011d84ee28e601 > 14M /boot/vmlinuz-6.2.11-300.fc38.x86_64 > 14M /boot/vmlinuz-6.2.13-300.fc38.x86_64 > 14M /boot/vmlinuz-6.2.14-300.fc38.x86_64 > > $ df -h /boot > Filesystem Size Used Avail Use% Mounted on > /dev/sda3 974M 240M 667M 27% /boot > > As you can see I have 3 kernels only. > > I doubt your space issue is the number of kernels unless you have > a very old install that predates the 1GiB /boot days. His earlier post shows: /dev/sda3 485348 379984 75668 84% /boot So that's presumably a 500GB /boot. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F37->F38: Printed pages are reversed
Hi, after smooth upgrade from Fedora 37 to Fedora 38 every printed page on my HP LaserJet P2055dn is reversed. How to flip the printout around the vertical axis? And what happend to my cups config? Kind regards, Frank ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
> On 19 May 2023, at 14:13, Patrick O'Callaghan wrote: > > On Fri, 2023-05-19 at 14:03 +0100, Barry Scott wrote: >> For comparison here is the sizes of /boot and the folders inside it >> on my file server. >> >> $ du -sh /boot/* >> 252K/boot/config-6.2.11-300.fc38.x86_64 >> 252K/boot/config-6.2.13-300.fc38.x86_64 >> 252K/boot/config-6.2.14-300.fc38.x86_64 >> 7.1M/boot/efi >> 2.4M/boot/grub2 >> 80M /boot/initramfs-0-rescue-23861aed63d748da85011d84ee28e601.img >> 28M /boot/initramfs-6.2.11-300.fc38.x86_64.img >> 28M /boot/initramfs-6.2.13-300.fc38.x86_64.img >> 28M /boot/initramfs-6.2.14-300.fc38.x86_64.img >> 24K /boot/loader >> 16K /boot/lost+found >> 0 /boot/symvers-6.2.11-300.fc38.x86_64.gz >> 0 /boot/symvers-6.2.13-300.fc38.x86_64.gz >> 0 /boot/symvers-6.2.14-300.fc38.x86_64.gz >> 8.1M/boot/System.map-6.2.11-300.fc38.x86_64 >> 8.1M/boot/System.map-6.2.13-300.fc38.x86_64 >> 8.1M/boot/System.map-6.2.14-300.fc38.x86_64 >> 11M /boot/vmlinuz-0-rescue-23861aed63d748da85011d84ee28e601 >> 14M /boot/vmlinuz-6.2.11-300.fc38.x86_64 >> 14M /boot/vmlinuz-6.2.13-300.fc38.x86_64 >> 14M /boot/vmlinuz-6.2.14-300.fc38.x86_64 >> >> $ df -h /boot >> Filesystem Size Used Avail Use% Mounted on >> /dev/sda3 974M 240M 667M 27% /boot >> >> As you can see I have 3 kernels only. >> >> I doubt your space issue is the number of kernels unless you have >> a very old install that predates the 1GiB /boot days. > > His earlier post shows: > /dev/sda3 485348 379984 75668 84% /boot > > So that's presumably a 500GB /boot. The presence of /boot/grub hints at disk original setup a long time ago. But 500GiB is still far bigger then the 240MiB that I'm using for F38 and 3 kernels. Barry > > poc > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
SÖLVED: F37->F38: Printed pages are reversed
On Fri, 19 May 2023 15:42:26 +0200 Frank Elsner via users wrote: > Hi, > > after smooth upgrade from Fedora 37 to Fedora 38 every printed page on my HP > LaserJet P2055dn > is reversed. > > How to flip the printout around the vertical axis? And what happend to my > cups config? Don't know what happended. Problem solved by using driver HP LaserJet p2055 pcl3, hpcups 3.22.10 --Frank ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
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. == PackageArchitecture Version Repository Size == Removing: kernel-corex86_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-corex86_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 f
Re: /boot problem.
Have you checked for excessive space used in sub-directories of /boot? Here: % doas du -sm /boot/efi /boot/extlinux /boot/loader /boot/lost+found /boot/grub2 19 /boot/efi 2 /boot/extlinux 1 /boot/loader 1 /boot/lost+found 3 /boot/grub2 -- George N. White III ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
On Fri, May 19, 2023 at 1:58 PM home user wrote: > 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[~]: > -- > 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 Note that "rpm -q" is showing "-200.fc37" but you are trying to remove "-100.fc36"- copy/paste/recall error? > No match for argument: kernel-core-6.2.10-100.fc36.x86_64 Because 6.2.10-100 isn't installed according to the rpm database. That is a leftover grub menu entry that will require clean-up. (Also note that if it did exist in the rpm database, you would have run into the same fc36 vs fc37 error.) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
On 5/19/23 12:30, Go Canes wrote: On Fri, May 19, 2023 at 1:58 PM home user wrote: 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[~]: -- 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 Note that "rpm -q" is showing "-200.fc37" but you are trying to remove "-100.fc36"- copy/paste/recall error? No match for argument: kernel-core-6.2.10-100.fc36.x86_64 Because 6.2.10-100 isn't installed according to the rpm database. That is a leftover grub menu entry that will require clean-up. (Also note that if it did exist in the rpm database, you would have run into the same fc36 vs fc37 error.) oops. good eye! you're right. Thank-you. I was careless when using the history feature. trying again... -- bash.3[~]: 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.4[~]: dnf remove kernel-core-6.2.9-200.fc37.x86_64 Dependencies resolved. == PackageArchitecture Version Repository Size == Removing: kernel-corex86_64 6.2.9-200.fc37 @updates 64 M Removing dependent packages: kernel x86_64 6.2.9-200.fc37 @updates 0 kernel-modules x86_64 6.2.9-200.fc37 @updates 61 M kernel-modules-corex86_64 6.2.9-200.fc37 @updates 36 M kmod-nvidia-470xx-6.2.9-200.fc37.x86_64x86_64 3:470.182.03-1.fc37 @@commandline 24 M Transaction Summary == Remove 5 Packages Freed space: 184 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.9-200.fc37.x86_64 1/5 Running scriptlet: kernel-6.2.9-200.fc37.x86_64 1/5 Erasing : kernel-modules-6.2.9-200.fc37.x86_64 2/5 Running scriptlet: kernel-modules-6.2.9-200.fc37.x86_64 2/5 Erasing : kmod-nvidia-470xx-6.2.9-200.fc37.x86_64-3:470.182.03-1.fc37.x86_64 3/5 Running scriptlet: kmod-nvidia-470xx-6.2.9-200.fc37.x86_64-3:470.182.03-1.fc37.x86_64 3/5 Erasing : kernel-modules-core-6.2.9-200.fc37.x86_64 4/5 Running scriptlet: kernel-modules-core-6.2.9-200.fc37.x86_64 4/5 Running scriptlet: kernel-core-6.2.9-200.fc37.x86_64 5/5 Erasing : kernel-core-6.2.9-200.fc37.x86_64 5/5 Running scriptlet: kernel-core-6.2.9-200.fc37.x86_64 5/5 Verifying: kernel-6.2.9-200.fc37.x86_64 1/5 Verifying: kernel-core-6.2.9-200.fc37.x86_64 2/5 Verifying: kernel-modules-6.2.9-200.fc37.x86_64 3/5 Verifying: kernel-modules-core-6.2.9-200.fc37.x86_64 4/5 Verifying: kmod-nvidia-470xx-6.2.9-200.fc37.x86_64-3:470.182.03-1.fc37.x86_64 5/5 Removed: kernel-6.2.9-200.fc37.x86_64 kernel-core-6.2.9-200.fc37.x86_64 kernel-modules-6.2.9-200.fc37.x86_64 kernel-modules-core-6.2.9-200.fc37.x86_64 kmod-nvidia-470xx-6.2.9-200.fc37.x86_64-3:470.182.03-1.fc37.x86_64 Complete! bash.5[~]: dnf remove kernel-core-6.2.10-200.fc37.x86_64 No match for argument: kernel-core-6.2.10-200.fc37.x86_64 No packages marked for removal. Dependencies resolved. Nothing to do. Complete! bash.6[~]: rpm -q kernel kernel-6.2.14-200.fc37.x86_64 kernel-6.2.15-200.fc37.x86_64 bash.7[~]: -- saving a draft of this message and then rebooting... == bash.1[~]: rpm -q kernel kernel-6.2.14-200.fc37.x86_64 kernel-6.2.15-200.fc37.x86_64 bash.2[~]: -- The grub menu no longer shows 6.2.9. It still shows 6.2.10. The grub menu shows a 6.2.12, but the rpm -q does not. Improvement, but still a mismatch. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lis
Re: /boot problem.
On 5/19/23 12:16 PM, George N. White III wrote: Have you checked for excessive space used in sub-directories of /boot? Here: % doas du -sm /boot/efi /boot/extlinux /boot/loader /boot/lost+found /boot/grub2 19 /boot/efi 2 /boot/extlinux 1 /boot/loader 1 /boot/lost+found 3 /boot/grub2 doas? no such command. How about this: - -bash.7[~]: cd /boot -bash.8[boot]: du -m 1 ./lost+found 3 ./grub2/fonts 1 ./grub2/themes/system 3 ./grub2/themes/starfield 3 ./grub2/themes 3 ./grub2/i386-pc 5 ./grub2/locale 12 ./grub2 6 ./efi/EFI/fedora 1 ./efi/EFI/BOOT 7 ./efi/EFI 7 ./efi 2 ./grub/fonts 3 ./grub/i386-pc 2 ./grub/locale/fonts 3 ./grub/locale/i386-pc 4 ./grub/locale 8 ./grub 1 ./loader/entries 1 ./loader 317 . -bash.9[boot]: - ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
> On 19 May 2023, at 20:22, home user wrote: > > On 5/19/23 12:16 PM, George N. White III wrote: >> Have you checked for excessive space used in sub-directories of /boot? Here: >> % doas du -sm /boot/efi /boot/extlinux /boot/loader /boot/lost+found >> /boot/grub2 >> 19 /boot/efi >> 2 /boot/extlinux >> 1 /boot/loader >> 1 /boot/lost+found >> 3 /boot/grub2 > > doas? > no such command. > > How about this: > - > -bash.7[~]: cd /boot > -bash.8[boot]: du -m > 1 ./lost+found > 3 ./grub2/fonts > 1 ./grub2/themes/system > 3 ./grub2/themes/starfield > 3 ./grub2/themes > 3 ./grub2/i386-pc > 5 ./grub2/locale > 12./grub2 > 6 ./efi/EFI/fedora > 1 ./efi/EFI/BOOT > 7 ./efi/EFI > 7 ./efi > 2 ./grub/fonts > 3 ./grub/i386-pc > 2 ./grub/locale/fonts > 3 ./grub/locale/i386-pc > 4 ./grub/locale > 8 ./grub > 1 ./loader/entries > 1 ./loader > 317 . 317 - that is very big. What is that 317M consistening of? Try this command to see what is going on: du -sh /boot/* And you do not need /boot/grub you are using /boot/grub2 now not /boot/grub. Barry > -bash.9[boot]: > - > > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: /boot problem.
(responding to 3 posts by Barry) On 5/19/23 2:55 PM, Barry Scott wrote: [... snip ...] 317 - that is very big. What is that 317M consistening of? Try this command to see what is going on: du -sh /boot/* And you do not need /boot/grub you are using /boot/grub2 now not /boot/grub. Barry -bash.9[boot]: - I used rm -rf to remove /boot/grub. I also removed initramfs-3.10.7-200.fc19.x86_64.img. - -bash.32[~]: du -sh /boot/* 251K/boot/config-6.2.10-200.fc37.x86_64 251K/boot/config-6.2.12-200.fc37.x86_64 251K/boot/config-6.2.14-200.fc37.x86_64 251K/boot/config-6.2.15-200.fc37.x86_64 7.0M/boot/efi 149K/boot/elf-memtest86+-5.31 12M /boot/grub2 33M /boot/initramfs-6.2.10-200.fc37.x86_64.img 33M /boot/initramfs-6.2.12-200.fc37.x86_64.img 33M /boot/initramfs-6.2.14-200.fc37.x86_64.img 33M /boot/initramfs-6.2.15-200.fc37.x86_64.img 41M /boot/initramfs-fedup.img 549K/boot/initrd-plymouth.img 14K /boot/loader 13K /boot/lost+found 148K/boot/memtest86+-5.31 1.0K/boot/symvers-6.2.10-200.fc37.x86_64.gz 1.0K/boot/symvers-6.2.12-200.fc37.x86_64.gz 1.0K/boot/symvers-6.2.14-200.fc37.x86_64.gz 1.0K/boot/symvers-6.2.15-200.fc37.x86_64.gz 8.1M/boot/System.map-6.2.10-200.fc37.x86_64 8.1M/boot/System.map-6.2.12-200.fc37.x86_64 8.1M/boot/System.map-6.2.14-200.fc37.x86_64 8.1M/boot/System.map-6.2.15-200.fc37.x86_64 11M /boot/vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38 14M /boot/vmlinuz-6.2.10-200.fc37.x86_64 14M /boot/vmlinuz-6.2.12-200.fc37.x86_64 14M /boot/vmlinuz-6.2.14-200.fc37.x86_64 14M /boot/vmlinuz-6.2.15-200.fc37.x86_64 5.7M/boot/vmlinuz-fedup -bash.33[~]: - That brings the du -m down from 317 to 294. I've noticed a bunch of "hidden" files in /boot. Here's an ls -lrta output for /boot - -bash.38[boot]: ls -lrta total 281371 drwx--. 2 root root12288 Mar 17 2013 lost+found -rw-r--r--. 1 root root 5897400 May 21 2015 vmlinuz-fedup -rw-r--r--. 1 root root 42314752 Sep 22 2015 initramfs-fedup.img -rw-r--r--. 1 root root 166 Mar 10 2016 .vmlinuz.hmac-4.4.5-300.fc23.x86_64 -rw-r--r--. 1 root root 166 Mar 16 2016 .vmlinuz.hmac-4.4.6-300.fc23.x86_64 -rw-r--r--. 1 root root 166 Mar 30 2016 .vmlinuz.hmac-4.4.6-301.fc23.x86_64 -rw-r--r--. 1 root root 166 Apr 12 2016 .vmlinuz.hmac-4.4.7-300.fc23.x86_64 -rw-r--r--. 1 root root 166 Apr 20 2016 .vmlinuz.hmac-4.4.8-300.fc23.x86_64 -rw-r--r--. 1 root root 166 May 4 2016 .vmlinuz.hmac-4.4.9-300.fc23.x86_64 -rw-r--r--. 1 root root 166 Jun 1 2016 .vmlinuz.hmac-4.5.6-200.fc23.x86_64 -rw-r--r--. 1 root root 166 Jun 8 2016 .vmlinuz.hmac-4.5.7-200.fc23.x86_64 -rw-r--r--. 1 root root 166 Jun 28 2016 .vmlinuz.hmac-4.5.7-202.fc23.x86_64 -rw-r--r--. 1 root root 166 Jul 12 2016 .vmlinuz.hmac-4.6.4-201.fc23.x86_64 -rw-r--r--. 1 root root 166 Jul 27 2016 .vmlinuz.hmac-4.6.5-200.fc23.x86_64 -rw-r--r--. 1 root root 166 Aug 10 2016 .vmlinuz.hmac-4.6.6-200.fc23.x86_64 -rw-r--r--. 1 root root 166 Aug 17 2016 .vmlinuz.hmac-4.6.7-200.fc23.x86_64 -rw-r--r--. 1 root root 560654 Oct 21 2016 initrd-plymouth.img drwxr-xr-x. 3 root root 1024 Oct 11 2018 loader -rwxr-xr-x. 1 root root 10494664 Mar 19 2020 vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38 drwx--. 3 root root 1024 Jul 20 2022 efi -rw-r--r--. 1 root root 149856 Jul 21 2022 memtest86+-5.31 -rw-r--r--. 1 root root 151452 Jul 21 2022 elf-memtest86+-5.31 dr-xr-xr-x. 22 root root 4096 Apr 6 12:55 .. -rw-r--r--. 1 root root 161 Apr 6 17:57 .vmlinuz-6.2.10-200.fc37.x86_64.hmac -rw---. 1 root root 8433889 Apr 6 18:00 System.map-6.2.10-200.fc37.x86_64 -rw-r--r--. 1 root root 255930 Apr 6 18:00 config-6.2.10-200.fc37.x86_64 -rwxr-xr-x. 1 root root 14231432 Apr 6 18:00 vmlinuz-6.2.10-200.fc37.x86_64 lrwxrwxrwx. 1 root root 46 Apr 20 13:08 symvers-6.2.10-200.fc37.x86_64.gz -> /lib/modules/6.2.10-200.fc37.x86_64/symvers.gz -rw---. 1 root root 34271148 Apr 20 13:09 initramfs-6.2.10-200.fc37.x86_64.img -rw-r--r--. 1 root root 161 Apr 20 17:54 .vmlinuz-6.2.12-200.fc37.x86_64.hmac -rw---. 1 root root 8435408 Apr 20 17:56 System.map-6.2.12-200.fc37.x86_64 -rwxr-xr-x. 1 root root 14222920 Apr 20 17:56 vmlinuz-6.2.12-200.fc37.x86_64 -rw-r--r--. 1 root root 255930 Apr 20 17:56 config-6.2.12-200.fc37.x86_64 lrwxrwxrwx. 1 root root 46 Apr 27 12:28 symvers-6.2.12-200.fc37.x86_64.gz -> /lib/modules/6.2.12-200.fc37.x86_64/symvers.gz -rw---. 1 root root 34167039 Apr 27 12:29 initramfs-6.2.12-200.fc37.x86_64.img -rw-r--r--. 1 root root 161 Apr 30 19:29 .vmlinuz-6.2.14-200.fc37.x86_64.hmac -rw---. 1 root root 8435991 Apr 30 19:32 System.map-6.2.14-200.fc37.x86_64 -rw-r--r--. 1 root root 255899 Apr 30 19:32 config-6.2.14-200.fc37.x86_64 -rwxr-xr-x. 1 root root 14226184 Apr 30 19:32 vmlinuz-
Re: /boot problem.
On Fri, May 19, 2023 at 3:05 PM home user wrote: > bash.1[~]: rpm -q kernel > kernel-6.2.14-200.fc37.x86_64 > kernel-6.2.15-200.fc37.x86_64 > bash.2[~]: > -- > The grub menu no longer shows 6.2.9. It still shows 6.2.10. > The grub menu shows a 6.2.12, but the rpm -q does not. Basically, there are 3 areas that need to be cleaned-up: 1) remove old kernels using preferred tools (i.e. "dnf remove") - this is done 2) clean up grub menu entries referencing non-existent kernels - I'm not much help with grub - sorry! 3) remove any leftover kernel bits that may still be lurking in the file system - something like "ls -R /boot" and note any files that appear to be for old kernels. You may also have kernel modules for obsolete kernels present elsewhere (I'm sure someone else can give proper advice for locating these) 4) optional - once you have everything else cleaned-up there is a command you can run to regenerate the rescue kernel if desired. I think this may happen automatically the next time a kernel is installed Side note on rescue kernel - after the clean-up if you don't feel you have the space to keep a rescue kernel lying around, you can always use a Fedora install iso or a live image instead. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
