How can I avoid my boot and kernel partitions getting out of sync?












0














I apparently screwed up my Arch Linux system by inadvertently updating the kernel, but not the boot partition. So, for example:



pacman -Q linux  -> results in 4.20.arch1-1
uname -a -> results in 4.19.4-arch1-1-ARCH


I am not sure exactly how this could be. If I look in my /boot directory, it has the three files initramfs-linux-fallback.img, initramfs-linux.img and vmlinuz-linux and the first two of these were recently updated and the last is dated when I installed the system several weeks ago. So, what exactly is out of sync? My vmlinuz-linux is out of sync with my kernel in the root partition?



The result of this is that the kernel is no longer finding my network device for some reason. I am not sure how this happened, the only command that I did that seems relevant was:



sudo pacman -Syu


I thought this command was only supposed to update the package database, not change the kernel.



In any case, my problem now is how to resync the boot partition so that it matches the kernel, or at least make things so that the network device module is being found and loaded, which apparently it is not any more.



My system is set up to boot directly from the motherboard (no intermediate boot loader). However, when I give this command:



# efibootmgr --verbose


I get the result "command not found". Do I need to be in the live boot environment to use this command? How can untangle this mess and get my system synchronized again? Also, how can I avoid this happening in the future? I mean I plan to add a lot of packages, and it will be problematic if the system is updating the kernel and messing up my system every time I add a new package.










share|improve this question





























    0














    I apparently screwed up my Arch Linux system by inadvertently updating the kernel, but not the boot partition. So, for example:



    pacman -Q linux  -> results in 4.20.arch1-1
    uname -a -> results in 4.19.4-arch1-1-ARCH


    I am not sure exactly how this could be. If I look in my /boot directory, it has the three files initramfs-linux-fallback.img, initramfs-linux.img and vmlinuz-linux and the first two of these were recently updated and the last is dated when I installed the system several weeks ago. So, what exactly is out of sync? My vmlinuz-linux is out of sync with my kernel in the root partition?



    The result of this is that the kernel is no longer finding my network device for some reason. I am not sure how this happened, the only command that I did that seems relevant was:



    sudo pacman -Syu


    I thought this command was only supposed to update the package database, not change the kernel.



    In any case, my problem now is how to resync the boot partition so that it matches the kernel, or at least make things so that the network device module is being found and loaded, which apparently it is not any more.



    My system is set up to boot directly from the motherboard (no intermediate boot loader). However, when I give this command:



    # efibootmgr --verbose


    I get the result "command not found". Do I need to be in the live boot environment to use this command? How can untangle this mess and get my system synchronized again? Also, how can I avoid this happening in the future? I mean I plan to add a lot of packages, and it will be problematic if the system is updating the kernel and messing up my system every time I add a new package.










    share|improve this question



























      0












      0








      0







      I apparently screwed up my Arch Linux system by inadvertently updating the kernel, but not the boot partition. So, for example:



      pacman -Q linux  -> results in 4.20.arch1-1
      uname -a -> results in 4.19.4-arch1-1-ARCH


      I am not sure exactly how this could be. If I look in my /boot directory, it has the three files initramfs-linux-fallback.img, initramfs-linux.img and vmlinuz-linux and the first two of these were recently updated and the last is dated when I installed the system several weeks ago. So, what exactly is out of sync? My vmlinuz-linux is out of sync with my kernel in the root partition?



      The result of this is that the kernel is no longer finding my network device for some reason. I am not sure how this happened, the only command that I did that seems relevant was:



      sudo pacman -Syu


      I thought this command was only supposed to update the package database, not change the kernel.



      In any case, my problem now is how to resync the boot partition so that it matches the kernel, or at least make things so that the network device module is being found and loaded, which apparently it is not any more.



      My system is set up to boot directly from the motherboard (no intermediate boot loader). However, when I give this command:



      # efibootmgr --verbose


      I get the result "command not found". Do I need to be in the live boot environment to use this command? How can untangle this mess and get my system synchronized again? Also, how can I avoid this happening in the future? I mean I plan to add a lot of packages, and it will be problematic if the system is updating the kernel and messing up my system every time I add a new package.










      share|improve this question















      I apparently screwed up my Arch Linux system by inadvertently updating the kernel, but not the boot partition. So, for example:



      pacman -Q linux  -> results in 4.20.arch1-1
      uname -a -> results in 4.19.4-arch1-1-ARCH


      I am not sure exactly how this could be. If I look in my /boot directory, it has the three files initramfs-linux-fallback.img, initramfs-linux.img and vmlinuz-linux and the first two of these were recently updated and the last is dated when I installed the system several weeks ago. So, what exactly is out of sync? My vmlinuz-linux is out of sync with my kernel in the root partition?



      The result of this is that the kernel is no longer finding my network device for some reason. I am not sure how this happened, the only command that I did that seems relevant was:



      sudo pacman -Syu


      I thought this command was only supposed to update the package database, not change the kernel.



      In any case, my problem now is how to resync the boot partition so that it matches the kernel, or at least make things so that the network device module is being found and loaded, which apparently it is not any more.



      My system is set up to boot directly from the motherboard (no intermediate boot loader). However, when I give this command:



      # efibootmgr --verbose


      I get the result "command not found". Do I need to be in the live boot environment to use this command? How can untangle this mess and get my system synchronized again? Also, how can I avoid this happening in the future? I mean I plan to add a lot of packages, and it will be problematic if the system is updating the kernel and messing up my system every time I add a new package.







      arch-linux kernel boot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 9 mins ago







      Tyler Durden

















      asked 45 mins ago









      Tyler DurdenTyler Durden

      1,57041950




      1,57041950






















          1 Answer
          1






          active

          oldest

          votes


















          -1














          There are too many issues to address here, but this won't fit into a comment, so I'll post it here until the question is deleted.




          1. Your /boot was not mounted during the upgrade, so your running kernel has no access to the modules it requires.


          2. efibootmgr is showing "command not found" because, surprise!, you haven't installed it.


          3. Your /boot wasn't mounted for the upgrade because, again this must come as a shock, you don't have /boot in your /etc/fstab (or if you do, it is incorrect).



          You prevent this from happening by actually having a clue about what you are doing, whereas your current slew of questions under archlinux shows exactly the opposite.






          share|improve this answer





















          • I came to this forum looking for help. I am sorry I am not as expert as you are. If I wanted to get told how stupid and ignorant I am, I could have just had dinner with my parents instead.
            – Tyler Durden
            18 mins ago











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493118%2fhow-can-i-avoid-my-boot-and-kernel-partitions-getting-out-of-sync%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          -1














          There are too many issues to address here, but this won't fit into a comment, so I'll post it here until the question is deleted.




          1. Your /boot was not mounted during the upgrade, so your running kernel has no access to the modules it requires.


          2. efibootmgr is showing "command not found" because, surprise!, you haven't installed it.


          3. Your /boot wasn't mounted for the upgrade because, again this must come as a shock, you don't have /boot in your /etc/fstab (or if you do, it is incorrect).



          You prevent this from happening by actually having a clue about what you are doing, whereas your current slew of questions under archlinux shows exactly the opposite.






          share|improve this answer





















          • I came to this forum looking for help. I am sorry I am not as expert as you are. If I wanted to get told how stupid and ignorant I am, I could have just had dinner with my parents instead.
            – Tyler Durden
            18 mins ago
















          -1














          There are too many issues to address here, but this won't fit into a comment, so I'll post it here until the question is deleted.




          1. Your /boot was not mounted during the upgrade, so your running kernel has no access to the modules it requires.


          2. efibootmgr is showing "command not found" because, surprise!, you haven't installed it.


          3. Your /boot wasn't mounted for the upgrade because, again this must come as a shock, you don't have /boot in your /etc/fstab (or if you do, it is incorrect).



          You prevent this from happening by actually having a clue about what you are doing, whereas your current slew of questions under archlinux shows exactly the opposite.






          share|improve this answer





















          • I came to this forum looking for help. I am sorry I am not as expert as you are. If I wanted to get told how stupid and ignorant I am, I could have just had dinner with my parents instead.
            – Tyler Durden
            18 mins ago














          -1












          -1








          -1






          There are too many issues to address here, but this won't fit into a comment, so I'll post it here until the question is deleted.




          1. Your /boot was not mounted during the upgrade, so your running kernel has no access to the modules it requires.


          2. efibootmgr is showing "command not found" because, surprise!, you haven't installed it.


          3. Your /boot wasn't mounted for the upgrade because, again this must come as a shock, you don't have /boot in your /etc/fstab (or if you do, it is incorrect).



          You prevent this from happening by actually having a clue about what you are doing, whereas your current slew of questions under archlinux shows exactly the opposite.






          share|improve this answer












          There are too many issues to address here, but this won't fit into a comment, so I'll post it here until the question is deleted.




          1. Your /boot was not mounted during the upgrade, so your running kernel has no access to the modules it requires.


          2. efibootmgr is showing "command not found" because, surprise!, you haven't installed it.


          3. Your /boot wasn't mounted for the upgrade because, again this must come as a shock, you don't have /boot in your /etc/fstab (or if you do, it is incorrect).



          You prevent this from happening by actually having a clue about what you are doing, whereas your current slew of questions under archlinux shows exactly the opposite.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 34 mins ago









          jasonwryanjasonwryan

          49.3k14134184




          49.3k14134184












          • I came to this forum looking for help. I am sorry I am not as expert as you are. If I wanted to get told how stupid and ignorant I am, I could have just had dinner with my parents instead.
            – Tyler Durden
            18 mins ago


















          • I came to this forum looking for help. I am sorry I am not as expert as you are. If I wanted to get told how stupid and ignorant I am, I could have just had dinner with my parents instead.
            – Tyler Durden
            18 mins ago
















          I came to this forum looking for help. I am sorry I am not as expert as you are. If I wanted to get told how stupid and ignorant I am, I could have just had dinner with my parents instead.
          – Tyler Durden
          18 mins ago




          I came to this forum looking for help. I am sorry I am not as expert as you are. If I wanted to get told how stupid and ignorant I am, I could have just had dinner with my parents instead.
          – Tyler Durden
          18 mins ago


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493118%2fhow-can-i-avoid-my-boot-and-kernel-partitions-getting-out-of-sync%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Entries order in /etc/network/interfaces

          新発田市

          Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)