F40 dual-boot problem, was Re: What is Castor ? Att.Jonathan Billings.

On 08/05/2024 21:57, Samuel Sieb wrote: On 5/8/24 1:13 PM, John Pilkington wrote: On 08/05/2024 20:13, Samuel Sieb wrote: On 5/8/24 10:50 AM, John Pilkington wrote: The harware was working well, before my recent upgrades from f38, briefly to f39 and now to f40.  Then I was using the rpmfusion

Re: imminent /boot problem. [SOLVED (for a while!)]

home user composed on 2024-02-25 21:17 (UTC-0700): > On 2/24/24 11:49 PM, Tim via users wrote: I'm curious how you installed it in the first place, then? >> home user: >>> That was about 11 years ago, so my memory of that is foggy and >>> incomplete. >>> I installed windows-7 first, proba

Re: imminent /boot problem. [SOLVED (for a while!)]

On 2/25/24 4:52 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 7:39 PM home user mailto:mattis...@comcast.net>> wrote: [...] I wrestled for many days this past fall trying to make a working LiveUSB.  Couldn't get it to work.  I was able to establish that neither the sticks

Re: imminent /boot problem. [SOLVED (for a while!)]

On 2/24/24 11:49 PM, Tim via users wrote: Tim: I'm curious how you installed it in the first place, then? home user: That was about 11 years ago, so my memory of that is foggy and incomplete. I installed windows-7 first, probably from a CD purchased from a local (near Washington, D.C) s

Re: imminent /boot problem.

On Sun, Feb 25, 2024 at 1:29 PM Tim via users wrote: > I'd like to run the few WiFi controlled lights I have locally, all this > cloud stuff goes against the grain, I loathe things controlled by > mobile phones, even though I am doing that. For that reason all the > main lighting has no smarts.

Re: imminent /boot problem.

On Sun, Feb 25, 2024 at 11:29 AM Tim via users < users@lists.fedoraproject.org> wrote: > > I'd like to run the few WiFi controlled lights I have locally (The rest of this has nothing directly to do with Fedora) I do this with Phillips Hue lights and Home Assistant. The Hue integration in Home A

Re: imminent /boot problem.

Tim: >> I still have one ancient motherboard that cannot boot from USB >> sticks. Go Canes: > Once upon a time you could use "plop boot manager" to boot off of USB > devices if the motherboard didn't provide support. Of course this > meant that you had to have something that could boot plop, but

Re: imminent /boot problem.

On Sun, Feb 25, 2024 at 1:49 AM Tim via users wrote: > I still have one ancient motherboard that cannot boot from USB sticks. > It's only options for USB booting are USB floppy and USB zip drives, > neither of which like USB anything else. It's also an extremely > useless motherboard, small RAM s

Re: imminent /boot problem.

On Thu, Feb 22, 2024 at 7:39 PM home user wrote: > [...] > I wrestled for many days this past fall trying to make a working LiveUSB. > Couldn't > get it to work. I was able to establish that neither the sticks nor the > ports were the problem. > > I find that upgrading Fedora more than a few tim

Re: imminent /boot problem.

On 2/24/24 22:50, Tim via users wrote: Samuel Sieb (re: lost & found directory): That directory is also special. There might be consequences for recreating it. I don't know if it's accessed by name or inode. I would imagine there'd have to be reserved space in the partition so it doesn't oth

Re: imminent /boot problem.

Samuel Sieb (re: lost & found directory): > That directory is also special. There might be consequences for > recreating it. I don't know if it's accessed by name or inode. I would imagine there'd have to be reserved space in the partition so it doesn't otherwise fill up 100% making it impossib

Re: imminent /boot problem.

Tim: >> I'm curious how you installed it in the first place, then? home user: > That was about 11 years ago, so my memory of that is foggy and > incomplete. > > I installed windows-7 first, probably from a CD purchased from a > local (near Washington, D.C) store. > > Then using either a CD b

Re: imminent /boot problem.

On 2/24/24 7:10 PM, Tim via users wrote: On Sat, 2024-02-24 at 13:58 -0700, home user wrote: No other computer. No live boot. Tried making one multiple times with multiple sticks and multiple ports. Even a local youngish professional programmer (specializing in embedded and micro) could not fi

Re: imminent /boot problem.

On Sat, 2024-02-24 at 13:58 -0700, home user wrote: > No other computer. > No live boot. Tried making one multiple times with multiple sticks > and multiple ports. Even a local youngish professional programmer > (specializing in embedded and micro) could not figure it out. I'm curious how you in

Re: imminent /boot problem. [SOLVED (for a while!)]

On 2/22/24 11:21 AM, home user wrote: (f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remaining. Examine   Ignore -- Seeing

Re: imminent /boot problem.

On 2/24/24 1:34 PM, Samuel Sieb wrote: On 2/24/24 12:16, home user wrote: On 2/23/24 2:34 PM, Jon LaBadie wrote: On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>> w

Re: imminent /boot problem.

you could delete it. it is create the next fsck run -- ___ 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-o

Re: imminent /boot problem.

On 2/23/24 3:31 PM, Felix Miata wrote: Samuel Sieb composed on 2024-02-23 16:48 (UTC-0500): home user wrote: -bash.4[~]: fdisk -l Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM006-2DM1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical)

Re: imminent /boot problem.

On 2/23/24 2:51 PM, Samuel Sieb wrote: On 2/23/24 11:19, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>> wrote: Is there anything in your /boot/lost+found? /boot/lost+found/: total 20 drwx--. 2 r

Re: imminent /boot problem.

On 2/23/24 2:48 PM, Samuel Sieb wrote: On 2/23/24 10:44, home user wrote: -bash.4[~]: fdisk -l Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM006-2DM1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (mini

Re: imminent /boot problem.

On 2/24/24 12:16, home user wrote: On 2/23/24 2:34 PM, Jon LaBadie wrote: On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user > wrote: Is there anything in your /b

Re: imminent /boot problem.

On 2/23/24 2:34 PM, Jon LaBadie wrote: On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>> wrote: Is there anything in your /boot/lost+found? /boot/lost+found/:

Re: imminent /boot problem.

Samuel Sieb composed on 2024-02-23 16:48 (UTC-0500): > home user wrote: >> -bash.4[~]: fdisk -l >> Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors >> Disk model: ST2000DM006-2DM1 >> Units: sectors of 1 * 512 = 512 bytes >> Sector size (logical/physical): 512 bytes / 4096 bytes >>

Re: imminent /boot problem.

On 2/23/24 11:19, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user > wrote: Is there anything in your /boot/lost+found? /boot/lost+found/: total 20 drwx--. 2 root root 12288 Mar 17  2013 . dr-xr-xr-

Re: imminent /boot problem.

On 2/23/24 10:44, home user wrote: -bash.4[~]: fdisk -l Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM006-2DM1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Di

Re: imminent /boot problem.

On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote: On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>> wrote: Is there anything in your /boot/lost+found? /boot/lost+found/: total 20 drwx--. 2 root root 12288 M

Re: imminent /boot problem.

On 2/23/24 5:44 AM, George N. White III wrote: On Thu, Feb 22, 2024 at 2:22 PM home user mailto:mattis...@comcast.net>> wrote: Is there anything in your /boot/lost+found? /boot/lost+found/: total 20 drwx--. 2 root root 12288 Mar 17 2013 . dr-xr-xr-x. 6 root root 5120 Feb 22 20:21 ..

Re: imminent /boot problem.

On 2/22/24 9:27 PM, Felix Miata wrote: Output from: cat /etc/fstab -bash.1[~]: cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Mar 17 20:21:35 2013 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/

Re: imminent /boot problem.

On Thu, Feb 22, 2024 at 2:22 PM home user wrote: > (f-38; gnome) > Good morning, > > While doing my weekly "dnf upgrade" a little while ago, I got the > following pop-up at the top of the screen" > -- > Low Disk Space on"boot" > The volume "boot" has only 20.9 MB disk space remaining. > > Exa

Re: imminent /boot problem.

home user composed on 2024-02-22 21:06 (UTC-0700): > Felix Miata wrote: ... >> Does your overall configuration necessitate having boot on its own >> partition? If >> not, and you have plenty of freespace on /, you could remount your /boot/ >> filesystem elsewhere, remove that filesystem from fsta

Re: imminent /boot problem.

On 2/22/24 4:46 PM, Felix Miata wrote: home user composed on 2024-02-22 16:30 (UTC-0700): Is my only real choice to cut back from 2 old kernels to 1 old kernel? Maybe not. Most people don't need to run more than one kernel at a time, or retain more than one as emergency fallback. Does your

Re: imminent /boot problem.

On 2/22/24 8:46 PM, Samuel Sieb wrote: On 2/22/24 19:32, home user wrote: Sorry, I misinterpreted it.  You're keeping 2 *old* kernels and I read it as keeping 2 kernels *total*. Well, I'm not the best of writers! If you change the installonly_limit=3 to 2 in /etc/dnf/dnf.conf then it wil

Re: imminent /boot problem.

On 2/22/24 19:32, home user wrote: On 2/22/24 4:56 PM, Samuel Sieb wrote: On 2/22/24 10:21, home user wrote: While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space

Re: imminent /boot problem.

On 2/22/24 4:56 PM, Samuel Sieb wrote: On 2/22/24 10:21, home user wrote: While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remaining. I'm only keeping 2 old

Re: imminent /boot problem.

On 2/22/24 10:21, home user wrote: While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remaining. I'm only keeping 2 old kernels now.  I did not do anything to s

Re: imminent /boot problem.

home user composed on 2024-02-22 16:30 (UTC-0700): > Is my only real choice to cut back from 2 old kernels to 1 old kernel? Maybe not. Most people don't need to run more than one kernel at a time, or retain more than one as emergency fallback. Does your overall configuration necessitate having

Re: imminent /boot problem.

On 2/22/24 4:02 PM, Joe Zeff wrote: On 02/22/2024 03:46 PM, home user wrote: It's dual boot: Fedora-38 and windows-7. I seriously doubt that the /boot partition can be made larger, but I'm no sys.admin. and I could be wrong. Dual boot doesn't matter.  /boot is only used by Linux, and general

Re: imminent /boot problem.

On 2/22/24 1:01 PM, Jeffrey Walton wrote: On Thu, Feb 22, 2024 at 2:33 PM Mike Wright wrote: On 2/22/24 10:21, home user wrote: (f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"bo

Re: imminent /boot problem.

On 02/22/2024 03:46 PM, home user wrote: It's dual boot: Fedora-38 and windows-7. I seriously doubt that the /boot partition can be made larger, but I'm no sys.admin. and I could be wrong. Dual boot doesn't matter. /boot is only used by Linux, and generally isn't ever mounted when you're us

Re: imminent /boot problem.

On 2/22/24 2:50 PM, Samuel Sieb wrote: On 2/22/24 10:21, home user wrote: (f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remain

Re: imminent /boot problem.

On 2/22/24 10:21, home user wrote: (f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remaining. How big is your boot partition?

Re: imminent /boot problem.

On 2/22/24 12:58 PM, Jeffrey Walton wrote: On Thu, Feb 22, 2024 at 1:22 PM home user wrote: (f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9

Re: imminent /boot problem.

On Thu, Feb 22, 2024 at 2:33 PM Mike Wright wrote: > > On 2/22/24 10:21, home user wrote: > > (f-38; gnome) > > Good morning, > > > > While doing my weekly "dnf upgrade" a little while ago, I got the > > following pop-up at the top of the screen" > > -- > > Low Disk Space on"boot" > > The volu

Re: imminent /boot problem.

On Thu, Feb 22, 2024 at 1:22 PM home user wrote: > > (f-38; gnome) > Good morning, > > While doing my weekly "dnf upgrade" a little while ago, I got the following > pop-up at the top of the screen" > -- > Low Disk Space on"boot" > The volume "boot" has only 20.9 MB disk space remaining. > > E

Re: imminent /boot problem.

On 2/22/24 10:21, home user wrote: (f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remaining. Examine   Ignore -- Seeing th

imminent /boot problem.

(f-38; gnome) Good morning, While doing my weekly "dnf upgrade" a little while ago, I got the following pop-up at the top of the screen" -- Low Disk Space on"boot" The volume "boot" has only 20.9 MB disk space remaining. Examine   Ignore -- Seeing that a new kernel needs... over 74,000,

Re: follow-up - Re: /boot problem. [SOLVED]

On 6/2/23 10:27 AM, stan via users wrote: On Fri, 2 Jun 2023 07:03:52 -0400 Go Canes wrote: On Fri, Jun 2, 2023 at 12:21 AM home user wrote: One more kernel update is needed to make sure the weekly patches does not keep too many kernels, and that the rescue kernel is updated. I don't belie

Re: follow-up - Re: /boot problem. [SOLVED]

On Fri, 2 Jun 2023 07:03:52 -0400 Go Canes wrote: > On Fri, Jun 2, 2023 at 12:21 AM home user > wrote: > > One more kernel update is needed to make sure the weekly patches > > does not keep too many kernels, and that the rescue kernel is > > updated. > > I don't believe the rescue kernel gets

Re: follow-up - Re: /boot problem. [SOLVED]

On Fri, Jun 2, 2023 at 12:21 AM home user wrote: > One more kernel update is needed to make sure the weekly patches does not > keep too many kernels, and that the rescue kernel is updated. I don't believe the rescue kernel gets updated automatically. _

follow-up - Re: /boot problem. [SOLVED]

On 5/18/23 4:21 PM, home user wrote: (f37 stand-alone dual-boot workstation) During this afternoon's patching (via dnf), a warning GUI popped up saying /boot is full.  It offered me the option to move /boot files to trash, but no option to delete anything.  I tried moving the rescue file to tr

Re: /boot problem. [SOLVED]

On Tue, 2023-05-23 at 18:08 +0930, Tim via users wrote: > Although re-installing something is rarely the solution.  It really > only makes sense if you know you've lost some of the packages files. Which you can check using 'rpm -V ' poc ___ users mailin

Re: /boot problem. [SOLVED]

On Mon, 2023-05-22 at 15:04 -0600, home user wrote: > The only ways an "upgrade over the top" should happen is if there's > something wrong in dnf or the kernels undergo serious growth. At > least I now know one thing to look for if this does happen. Actually, what I was referring to was when you

Re: /boot problem. [SOLVED]

On 5/22/23 2:49 PM, Tim via users wrote: Tom Horsley: I don't know if it already appeared somewhere in this thread, but I think there is a DNF option you can set in the dnf.conf file to limit the number of old kernels it will keep around. That might help prevent a recurrence. home user: Yes,

Re: /boot problem. [SOLVED]

Tom Horsley: >> I don't know if it already appeared somewhere in this thread, but I >> think there is a DNF option you can set in the dnf.conf file to >> limit the number of old kernels it will keep around. That might >> help prevent a recurrence. home user: > Yes, I set that back to 3 during this

Re: /boot problem. [SOLVED]

On 5/22/23 12:17 PM, Tom Horsley wrote: On Mon, 22 May 2023 12:02:19 -0600 home user wrote: If the problem happens again, I'll open a new thread. I don't know if it already appeared somewhere in this thread, but I think there is a DNF option you can set in the dnf.conf file to limit the numbe

Re: /boot problem. [SOLVED]

On Mon, 22 May 2023 12:02:19 -0600 home user wrote: > If the problem happens again, I'll open a new thread. I don't know if it already appeared somewhere in this thread, but I think there is a DNF option you can set in the dnf.conf file to limit the number of old kernels it will keep around. That

Re: kernel growth (was: /boot problem.)

On 5/19/23 4:38 AM, Felix Miata wrote: 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

Re: /boot problem. [SOLVED]

On 5/18/23 4:21 PM, home user wrote: (f37 stand-alone dual-boot workstation) During this afternoon's patching (via dnf), a warning GUI popped up saying /boot is full.  It offered me the option to move /boot files to trash, but no option to delete anything.  I tried moving the rescue file to tr

Re: /boot problem.

On 5/22/23 8:38 AM, stan via users wrote: On Sun, 21 May 2023 19:28:14 +0200 Lukas Middendorf wrote: Thanks for comments. [... snip ...] There is quite some potential for mistakes that will break the boot process. Yes, there sure is. Given this new addition, I would not recommend this unles

Re: /boot problem.

On 5/22/23 8:01 AM, stan via users wrote: On Sun, 21 May 2023 21:02:19 -0600 home user wrote: question does come to mind from my first reading: What you say about using CDs will work with DVDs too, right? Yes, I actually have a dvd burner that can handle CDs as well. Make sure that you tick

Re: /boot problem.

On 5/21/23 11:56 PM, Samuel Sieb wrote: On 5/21/23 20:02, home user wrote: I notice that the themes/starfield subdirectory has quite a few (31) files, all from July 06, 2017, a few quite big.  But should not assume that being old means they're no longer needed. My question: Is anything in this

Re: /boot problem.

On 5/21/23 10:20 PM, Mike Wright wrote: On 5/21/23 20:02, home user wrote: On 5/18/23 4:21 PM, home user wrote: [... snip ...] There are two more /boot subdirectories I want to look at: /boot/grub2/i386-pc/ /boot/grub2/themes/starfield/ I did an "ls -lRt" on /boot/grub2/ and put the output (a

Re: /boot problem.

On Sun, 21 May 2023 19:28:14 +0200 Lukas Middendorf wrote: Thanks for comments. > On 21/05/2023 18:05, stan via users wrote: > > 1. Caveat: This is a complex procedure, and from your past posts of > > your skill level, maybe too risky for you to do. > > There is lots of room in / for /boot. Rig

Re: /boot problem.

On Sun, 21 May 2023 21:02:19 -0600 home user wrote: > question does come to mind from my first reading: What you say about > using CDs will work with DVDs too, right? Yes, I actually have a dvd burner that can handle CDs as well. Make sure that you tick the box that validates the burn after it

Re: /boot problem.

On 5/21/23 20:02, home user wrote: I notice that the themes/starfield subdirectory has quite a few (31) files, all from July 06, 2017, a few quite big.  But should not assume that being old means they're no longer needed. My question: Is anything in this directory still needed.  I'd like to eit

Re: /boot problem.

On 5/21/23 20:02, home user wrote: On 5/18/23 4:21 PM, home user wrote: [... snip ...] There are two more /boot subdirectories I want to look at: /boot/grub2/i386-pc/ /boot/grub2/themes/starfield/ I did an "ls -lRt" on /boot/grub2/ and put the output (as a text file) onto the google drive her

Re: /boot problem.

On 5/18/23 4:21 PM, home user wrote: [... snip ...] There are two more /boot subdirectories I want to look at: /boot/grub2/i386-pc/ /boot/grub2/themes/starfield/ I did an "ls -lRt" on /boot/grub2/ and put the output (as a text file) onto the google drive here: "https://drive.google.com/file/d/

Re: /boot problem.

On 21/05/2023 18:05, stan via users wrote: 1. Caveat: This is a complex procedure, and from your past posts of your skill level, maybe too risky for you to do. There is lots of room in / for /boot. Right now you are using a separate /boot, but there is a way to use a /boot under the root partiti

Re: /boot problem.

Ignore this post if you are happy with the current resolution to your issue. On Sat, 20 May 2023 18:17:56 -0600 home user wrote: > On 5/20/23 3:03 PM, Patrick O'Callaghan wrote: > > On Sun, 2023-05-21 at 04:12 +0930, Tim via users wrote: > >> On Sat, 2023-05-20 at 17:07 +0100, Patrick O'Callag

Re: /boot problem.

On 5/19/23 5:46 AM, Jeffrey Walton wrote: 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 tmpfs

Re: /boot problem.

On 5/20/23 8:48 PM, Samuel Sieb wrote: On 5/20/23 19:36, home user wrote: On 5/18/23 4:21 PM, home user wrote: (f37 stand-alone dual-boot workstation) (not replying to anyone else's post) - -bash.12[boot]: ls -a . symvers-6.2.10-200.fc37.x86_64.gz ..   

Re: /boot problem.

On 5/19/23 4:40 AM, Lukas Middendorf wrote: On 19/05/2023 03:24, home user wrote: On 5/18/23 6:30 PM, Felix Miata wrote: 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 neede

Re: /boot problem.

On 5/20/23 19:36, home user wrote: On 5/18/23 4:21 PM, home user wrote: (f37 stand-alone dual-boot workstation) (not replying to anyone else's post) - -bash.12[boot]: ls -a . symvers-6.2.10-200.fc37.x86_64.gz ..    symvers

Re: /boot problem.

On 5/18/23 4:21 PM, home user wrote: (f37 stand-alone dual-boot workstation) (not replying to anyone else's post) - -bash.12[boot]: ls -a . symvers-6.2.10-200.fc37.x86_64.gz ..symvers-6.2.12-200.fc37.x86_64.gz config-6.

Re: /boot problem.

On 5/20/23 19:09, home user wrote: On 5/20/23 7:54 PM, home user wrote: On 5/20/23 7:51 PM, Samuel Sieb wrote: On 5/20/23 18:44, home user wrote:  From what I see in the Fedora doc, is this my next step: "grub2-mkconfig -o /boot/grub2/grub.cfg"? If no, what?  ...or  is grub menu clean-up done?

Re: /boot problem.

On 5/18/23 6:30 PM, Felix Miata wrote: home user composed on 2023-05-18 16:21 (UTC-0600): What size is the filesystem on which /boot/ lives? Separate partition? BTRFS? I don't recall answering this. size = 485348 separate partition: yes (based on Disks display) BTRFS: no; it's Ext4.

Re: /boot problem.

On 5/20/23 7:54 PM, home user wrote: On 5/20/23 7:51 PM, Samuel Sieb wrote: On 5/20/23 18:44, home user wrote:  From what I see in the Fedora doc, is this my next step: "grub2-mkconfig -o /boot/grub2/grub.cfg"? If no, what?  ...or  is grub menu clean-up done? That is how to do it, but unless

Re: /boot problem.

Sorry I should write 'sudo dnf reinstall kernel kernel-*' On Sat, 2023-05-20 at 19:53 -0600, home user wrote: > On 5/20/23 7:25 PM, Igor Bezrodnik wrote: > > Can you try to do just reinstall kernel like 'sudo dnf kernel > > kernel-*' > > ? > I looked at the man page for dnf.  There is no "kernel"

Re: /boot problem.

On 5/20/23 7:51 PM, Samuel Sieb wrote: On 5/20/23 18:44, home user wrote:  From what I see in the Fedora doc, is this my next step: "grub2-mkconfig -o /boot/grub2/grub.cfg"? If no, what?  ...or  is grub menu clean-up done? That is how to do it, but unless there's still something in the menu yo

Re: /boot problem.

On 5/20/23 7:25 PM, Igor Bezrodnik wrote: Can you try to do just reinstall kernel like 'sudo dnf kernel kernel-*' ? I looked at the man page for dnf. There is no "kernel" command for dnf. [... snip ...] ___ users mailing list -- users@lists.fedorapr

Re: /boot problem.

On 5/20/23 18:44, home user wrote: From what I see in the Fedora doc, is this my next step: "grub2-mkconfig -o /boot/grub2/grub.cfg"? If no, what?  ...or  is grub menu clean-up done? That is how to do it, but unless there's still something in the menu you don't want, you're done. ___

Re: /boot problem.

On 5/20/23 7:32 PM, Samuel Sieb wrote: On 5/20/23 18:17, home user wrote: On 5/20/23 7:07 PM, Samuel Sieb wrote: On 5/20/23 18:01, home user wrote: On 5/20/23 6:53 PM, Samuel Sieb wrote: On 5/20/23 17:17, home user wrote: [... snip ...] How do I get the grub menu corrected? Assuming the

Re: /boot problem.

On 5/20/23 18:17, home user wrote: On 5/20/23 7:07 PM, Samuel Sieb wrote: On 5/20/23 18:01, home user wrote: On 5/20/23 6:53 PM, Samuel Sieb wrote: On 5/20/23 17:17, home user wrote: [... snip ...] How do I get the grub menu corrected? Assuming the BLS conversion happened, look in /boot/

Re: /boot problem.

On Sun, 2023-05-21 at 11:25 +1000, Igor Bezrodnik wrote: > Can you try to do just reinstall kernel like 'sudo dnf install kernel > kernel-*' > On Sat, 2023-05-20 at 19:17 -0600, home user wrote: > > On 5/20/23 7:07 PM, Samuel Sieb wrote: > > > On 5/20/23 18:01, home user wrote: > > > > On 5/20/23 6

Re: /boot problem.

Can you try to do just reinstall kernel like 'sudo dnf kernel kernel-*' On Sat, 2023-05-20 at 19:17 -0600, home user wrote: > On 5/20/23 7:07 PM, Samuel Sieb wrote: > > On 5/20/23 18:01, home user wrote: > > > On 5/20/23 6:53 PM, Samuel Sieb wrote: > > > > On 5/20/23 17:17, home user wrote: > [...

Re: /boot problem.

On 5/20/23 7:07 PM, Samuel Sieb wrote: On 5/20/23 18:01, home user wrote: On 5/20/23 6:53 PM, Samuel Sieb wrote: On 5/20/23 17:17, home user wrote: [... snip ...] How do I get the grub menu corrected? Assuming the BLS conversion happened, look in /boot/loader/entries/ and remove any entr

Re: /boot problem.

On 5/20/23 18:01, home user wrote: On 5/20/23 6:53 PM, Samuel Sieb wrote: On 5/20/23 17:17, home user wrote: I am seriously considering enlarging /boot.  But I anticipate that would take even more help from this list than this current problem. So we're back to where this left off You do

Re: /boot problem.

On 5/20/23 6:53 PM, Samuel Sieb wrote: On 5/20/23 17:17, home user wrote: I am seriously considering enlarging /boot.  But I anticipate that would take even more help from this list than this current problem.  So we're back to where this left off You don't want to be messing around with

Re: /boot problem.

On 5/20/23 17:17, home user wrote: I am seriously considering enlarging /boot.  But I anticipate that would take even more help from this list than this current problem.  So we're back to where this left off You don't want to be messing around with changing partition sizes if you don't ha

Re: /boot problem.

On 5/20/23 3:03 PM, Patrick O'Callaghan wrote: On Sun, 2023-05-21 at 04:12 +0930, Tim via users wrote: On Sat, 2023-05-20 at 17:07 +0100, Patrick O'Callaghan wrote: Apologies if you've already considered this, but I wonder why you don't just do a fresh install of F38 (or F37). It would have bee

Re: /boot problem.

On Sun, 2023-05-21 at 04:12 +0930, Tim via users wrote: > On Sat, 2023-05-20 at 17:07 +0100, Patrick O'Callaghan wrote: > > Apologies if you've already considered this, but I wonder why you > > don't > > just do a fresh install of F38 (or F37). It would have been much > > quicker than all the futzi

Re: /boot problem.

On Sat, 2023-05-20 at 17:07 +0100, Patrick O'Callaghan wrote: > Apologies if you've already considered this, but I wonder why you don't > just do a fresh install of F38 (or F37). It would have been much > quicker than all the futzing around you've had to do, and you could > have seized the opportun

Re: /boot problem.

On Sat, 2023-05-20 at 09:16 -0600, home user wrote: > So as was pointed out by more than one poster, some grub clean-up is > needed.  How do I do that? Apologies if you've already considered this, but I wonder why you don't just do a fresh install of F38 (or F37). It would have been much quicker t

Re: /boot problem.

Last night, when I shut down the workstation for the night, it took quite a while (minutes); it was running akmod. I had done no installs and no upgrades since the previous boot (earlier in the day). I had only done dnf removes and rm commands. Why was akmod run during that shutdown?! On 5/

Re: /boot problem.

> > 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 20

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,

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

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/ex

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

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.fc3

  1   2   >