modules.devname not found after updating process was cancelled












0















I can't boot into my Arch system after updating was canceled in the middle of it.
When I'm trying to boot it shows this message



Warning: /lib/modules/4.19.25-1-lts/modules.devname not found - ignoring starting version 239
mount: /new_root: unknown filesystem type 'ext4'.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]# _


When this message is shown I can't really type anything so I used live-usb.
My system has 3 partitions:





  1. boot (~500mb);


  2. swap (~16Gb) ;

  3. another one that contains all the data and is the biggest one, I'll call this partition home.


In live-usb I've mounted:





  1. home to /mnt


  2. boot to /mnt/boot


Then I did these steps:




  1. arch-chroot /mnt


  2. sudo pacman -S linux-lts (I used lts before)

  3. mkinitcpio -p linux-lts

  4. exit

  5. reboot


It didn't help.



One thing I noticed, after I arch-chroot'ed into the /mnt and typed uname -r, it showed me an older version that starts with 4.18. After I've performed steps 1, 2 and 3, I used uname -r again, and it still showed me the same old version 4.18..



What could be the source of this problem and how do I fix it?



UPDATE:
It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.










share|improve this question





























    0















    I can't boot into my Arch system after updating was canceled in the middle of it.
    When I'm trying to boot it shows this message



    Warning: /lib/modules/4.19.25-1-lts/modules.devname not found - ignoring starting version 239
    mount: /new_root: unknown filesystem type 'ext4'.
    You are now being dropped into an emergency shell.
    sh: can't access tty; job control turned off
    [rootfs ]# _


    When this message is shown I can't really type anything so I used live-usb.
    My system has 3 partitions:





    1. boot (~500mb);


    2. swap (~16Gb) ;

    3. another one that contains all the data and is the biggest one, I'll call this partition home.


    In live-usb I've mounted:





    1. home to /mnt


    2. boot to /mnt/boot


    Then I did these steps:




    1. arch-chroot /mnt


    2. sudo pacman -S linux-lts (I used lts before)

    3. mkinitcpio -p linux-lts

    4. exit

    5. reboot


    It didn't help.



    One thing I noticed, after I arch-chroot'ed into the /mnt and typed uname -r, it showed me an older version that starts with 4.18. After I've performed steps 1, 2 and 3, I used uname -r again, and it still showed me the same old version 4.18..



    What could be the source of this problem and how do I fix it?



    UPDATE:
    It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.










    share|improve this question



























      0












      0








      0








      I can't boot into my Arch system after updating was canceled in the middle of it.
      When I'm trying to boot it shows this message



      Warning: /lib/modules/4.19.25-1-lts/modules.devname not found - ignoring starting version 239
      mount: /new_root: unknown filesystem type 'ext4'.
      You are now being dropped into an emergency shell.
      sh: can't access tty; job control turned off
      [rootfs ]# _


      When this message is shown I can't really type anything so I used live-usb.
      My system has 3 partitions:





      1. boot (~500mb);


      2. swap (~16Gb) ;

      3. another one that contains all the data and is the biggest one, I'll call this partition home.


      In live-usb I've mounted:





      1. home to /mnt


      2. boot to /mnt/boot


      Then I did these steps:




      1. arch-chroot /mnt


      2. sudo pacman -S linux-lts (I used lts before)

      3. mkinitcpio -p linux-lts

      4. exit

      5. reboot


      It didn't help.



      One thing I noticed, after I arch-chroot'ed into the /mnt and typed uname -r, it showed me an older version that starts with 4.18. After I've performed steps 1, 2 and 3, I used uname -r again, and it still showed me the same old version 4.18..



      What could be the source of this problem and how do I fix it?



      UPDATE:
      It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.










      share|improve this question
















      I can't boot into my Arch system after updating was canceled in the middle of it.
      When I'm trying to boot it shows this message



      Warning: /lib/modules/4.19.25-1-lts/modules.devname not found - ignoring starting version 239
      mount: /new_root: unknown filesystem type 'ext4'.
      You are now being dropped into an emergency shell.
      sh: can't access tty; job control turned off
      [rootfs ]# _


      When this message is shown I can't really type anything so I used live-usb.
      My system has 3 partitions:





      1. boot (~500mb);


      2. swap (~16Gb) ;

      3. another one that contains all the data and is the biggest one, I'll call this partition home.


      In live-usb I've mounted:





      1. home to /mnt


      2. boot to /mnt/boot


      Then I did these steps:




      1. arch-chroot /mnt


      2. sudo pacman -S linux-lts (I used lts before)

      3. mkinitcpio -p linux-lts

      4. exit

      5. reboot


      It didn't help.



      One thing I noticed, after I arch-chroot'ed into the /mnt and typed uname -r, it showed me an older version that starts with 4.18. After I've performed steps 1, 2 and 3, I used uname -r again, and it still showed me the same old version 4.18..



      What could be the source of this problem and how do I fix it?



      UPDATE:
      It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.







      arch-linux boot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 4 at 14:49









      Jeff Schaller

      43.4k1160140




      43.4k1160140










      asked Feb 25 at 10:47









      Chaz AshleyChaz Ashley

      112




      112






















          1 Answer
          1






          active

          oldest

          votes


















          1














          I've solved it.
          It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.






          share|improve this answer























            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%2f502837%2fmodules-devname-not-found-after-updating-process-was-cancelled%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














            I've solved it.
            It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.






            share|improve this answer




























              1














              I've solved it.
              It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.






              share|improve this answer


























                1












                1








                1







                I've solved it.
                It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.






                share|improve this answer













                I've solved it.
                It happened to be that I was using custom initramfs and it wasn't updated. So I changed names of used initramfs back to initramfs-linux-lts.img (or something like that) in my grub.cfg file and system started to boot.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 25 at 12:22









                Chaz AshleyChaz Ashley

                112




                112






























                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502837%2fmodules-devname-not-found-after-updating-process-was-cancelled%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

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?