[SOLVED] boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ...
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 8 of 8
  1. #1
    Join Date
    Dec 2017
    Location
    USA
    Posts
    72
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ...

    This is on a Windows 10 / Fedora 34 dual boot machine which was recently (within the past month) upgraded to Fedora 34 from Fedora 33.

    Today, after a command-line update and reboot I get the following error message when attempting to boot to the latest kernel followed by a kernel panic

    Code:
    error: ../../grub-core/fs/fshelp.c:257:file'/initramfs-5.12.15-300.fc34.x86_64.img' not found.
    
    Press any key to continue
    and after pressing any key I get a screen full of text which can be viewed here https://imgur.com/dAcKc13

    There are three kernels listed

    Code:
    rpm -qa kernel
    kernel-5.12.13-300.fc34.x86_64
    kernel-5.12.14-300.fc34.x86_64
    kernel-5.12.15-300.fc34.x86_64
    kernel-5.12.15-300.fc34.x86_64 is the only one that won't boot. IE I successfully booted into Fedora 34 after choosing the previous kernels. The system also boots into Windows 10 no problem.


    The recent command line update 'might' have been interrupted - I couldn't get at the terminal window, it froze for some reason. After signing out and back in I ran

    Code:
    sudo dnf update
    again and got a message that there was nothing to do, etc.


    I found this article which might be on point: https://unix.stackexchange.com/quest...ny-key-to-cont

    I know how to boot from a live cd/flash drive but the rest is unfamiliar to me - i.e. mounting the problematic partitions and running any commands.

    Do i just reinstall the latest kernel? Is that possible?

    Thanks in advance.
    Last edited by gmach24; 15th July 2021 at 11:24 PM.

  2. #2
    Join Date
    May 2019
    Location
    Indonesia
    Posts
    202
    Mentioned
    5 Post(s)
    Tagged
    0 Thread(s)

    Re: boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ..

    I think your partition i ok, because the previous kernel are working as intended.
    Just try to reinstall the latest kernel.

  3. #3
    Join Date
    Aug 2009
    Posts
    9,444
    Mentioned
    18 Post(s)
    Tagged
    0 Thread(s)

    Re: boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ..

    You can tell it to reinstall the latest kernel by booting to a previous kernel, then running dnf.. You must boot to a previous kernel first, though. dnf does not allow reinstalling the currently running kernel.

    Code:
    sudo dnf reinstall kernel*
    Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

  4. #4
    Join Date
    Dec 2017
    Location
    USA
    Posts
    72
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ..

    Quote Originally Posted by DBelton
    You can tell it to reinstall the latest kernel by booting to a previous kernel, then running dnf.. You must boot to a previous kernel first, though. dnf does not allow reinstalling the currently running kernel.

    Code:
    sudo dnf reinstall kernel*
    I removed and then reinstalled kernel-5.12.15-300.fc34.x86_64 via command line. Rebooted and got the same error messages.

    I then updated the grub file via command line just to see. I still get the same error messages.

    Was I suppose to reboot the system after removing kernel-5.12.15-300.fc34.x86_64 and then update/reinstall it?

    Re: your "You must boot to a previous kernel first, though. dnf does not allow reinstalling the currently running kernel."

    Since the problem is I cannot boot to the latest kernel i.e. kernel-5.12.15-300.fc34.x86_64 this is not the problem.

    This is an update:

    I removed kernel-5.12.15-300.fc34.x86_64 and then upgraded grub. Checked which kernels are installed and it's the previous two i.e. 5.12.14 & 5.12.13.

    Rebooted and on the boot screen kernel-5.12.15-300.fc34.x86_64 is still top of the list.

    but

    Code:
    $ rpm -qa kernel
    kernel-5.12.13-300.fc34.x86_64
    kernel-5.12.14-300.fc34.x86_64
    I did

    Code:
    $ sudo grep menuentry /boot/grub2/grub.cfg
    
    if [ x"${feature_menuentry_id}" = xy ]; then
      menuentry_id_option="--id"
      menuentry_id_option=""
    export menuentry_id_option
    menuentry 'Windows 10 (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-01D7663F75254AB0' {
    menuentry 'Windows 10 (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-01D766414F2C4E10' {
    Don't know if that helps.
    Last edited by gmach24; 15th July 2021 at 10:46 PM.

  5. #5
    Join Date
    Dec 2017
    Location
    USA
    Posts
    72
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ..

    OK. I read this https://askbot.fedoraproject.org/en/...panic-on-boot/

    and then ran


    Code:
    $ rpm -q kernel-core
     
    kernel-core-5.12.13-300.fc34.x86_64
    kernel-core-5.12.14-300.fc34.x86_64
    kernel-core-5.12.15-300.fc34.x86_64
    So, I then ran

    Code:
    dnf remove kernel-core-5.12.15-300.fc34.x86_64
    which gave me

    Code:
    Dependencies resolved.
    ================================================================================
     Package                  Arch       Version                 Repository    Size
    ================================================================================
    Removing:
     kernel-core              x86_64     5.12.15-300.fc34        @updates      74 M
    Removing dependent packages:
     kernel-modules           x86_64     5.12.15-300.fc34        @updates      30 M
     kernel-modules-extra     x86_64     5.12.15-300.fc34        @updates     1.9 M
    
    Transaction Summary
    ================================================================================
    Remove  3 Packages
    
    Freed space: 106 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-modules-extra-5.12.15-300.fc34.x86_64           1/3 
      Running scriptlet: kernel-modules-extra-5.12.15-300.fc34.x86_64           1/3 
      Erasing          : kernel-modules-5.12.15-300.fc34.x86_64                 2/3 
      Running scriptlet: kernel-modules-5.12.15-300.fc34.x86_64                 2/3 
      Running scriptlet: kernel-core-5.12.15-300.fc34.x86_64                    3/3 
      Erasing          : kernel-core-5.12.15-300.fc34.x86_64                    3/3 
    warning: file /lib/modules/5.12.15-300.fc34.x86_64/updates: remove failed: No such file or directory
    
      Running scriptlet: kernel-core-5.12.15-300.fc34.x86_64                    3/3 
      Verifying        : kernel-core-5.12.15-300.fc34.x86_64                    1/3 
      Verifying        : kernel-modules-5.12.15-300.fc34.x86_64                 2/3 
      Verifying        : kernel-modules-extra-5.12.15-300.fc34.x86_64           3/3 
    
    Removed:
      kernel-core-5.12.15-300.fc34.x86_64                                           
      kernel-modules-5.12.15-300.fc34.x86_64                                        
      kernel-modules-extra-5.12.15-300.fc34.x86_64                                  
    
    Complete!
    After reboot there is no kernel-5.12.15-300.fc34.x86_64 on the boot screen and

    Code:
    rpm -q kernel-core
    kernel-core-5.12.13-300.fc34.x86_64
    kernel-core-5.12.14-300.fc34.x86_64
    So I think I removed all kernel-5.12.15-300.fc34.x86_64 related files.

    Now, what do I do? A simple dnf update? I know there are ways to exclude kernel updates while running dnf updates but I'm in over my head here.

    I read one Fedora user said his kernel panic issues resolved on a Win 10 dual-boot machine after he updated the BIOS.
    Last edited by gmach24; 15th July 2021 at 11:18 PM.

  6. #6
    Join Date
    Dec 2017
    Location
    USA
    Posts
    72
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ..

    Well - I took a chance and did

    Code:
    $ dnf update
    which reinstalled kernel-core-5.12.15-300.fc34.x86_64 and related files. A reboot occurred without problem - i.e. I can boot into the latest kernel without issue.

    I guess something happened during the original installation of kernel-core-5.12.14-300.fc34.x86_64 and related files and I had to remove ALL of those and reinstall - not just the kernel. As I said, this was all pretty much over my head.

    I'm going to mark this thread "solved".

  7. #7
    Join Date
    Dec 2017
    Location
    USA
    Posts
    72
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ..

    Quote Originally Posted by DBelton
    You can tell it to reinstall the latest kernel by booting to a previous kernel, then running dnf.. You must boot to a previous kernel first, though. dnf does not allow reinstalling the currently running kernel.

    Code:
    sudo dnf reinstall kernel*
    I realize now this probably would have worked without my going through all the stuff I did But, as I said, I was in over my head. Thanks, though. Sorry I didn't understand this sooner.

  8. #8
    Join Date
    Aug 2009
    Posts
    9,444
    Mentioned
    18 Post(s)
    Tagged
    0 Thread(s)

    Re: boot error after update Fedora 34 error: ../../grub-core/fs/fshelp.c:257:file ..

    I have occasionally had a glitch in a kernel update that got resolved by reinstalling the kernel myself. At first you think... Well, there is a problem with this kernel version... It's normal to think that if your machine has been running flawlessly and then starts having issues on a kernel update.

    Unless you actually see an error message during the update, you really don't think about it being an issue with the update itself rather than an issue with the kernel version.

    Edit:

    Just for future reference, you posted your /boot/grub2/grub.cfg above. The Fedora entries are now located in /boot/loader/entries since Fedora started using BLS.
    Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Similar Threads

  1. Fedora 9 Grub error Error 15 File not found
    By QuantumKnot in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 14th May 2008, 07:35 AM
  2. Boot-up error --- GRUB Loading stage2Read Error
    By xboomerx in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 19th November 2006, 05:42 PM
  3. Fedora core - Grub 15 error
    By masoroso in forum Installation, Upgrades and Live Media
    Replies: 0
    Last Post: 23rd March 2006, 12:33 PM
  4. Fedora Core 3; GRUB error 2
    By RoBoCoP in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 19th April 2005, 04:55 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •