What to do after Failed to start Load Kernel Modules





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







38















I tried to upgrade my system from Ubuntu 14.04. My laptop froze for a few hours. Not even the pointer did anything. So I switched off by pressing the power button for a few seconds.
This uncompleted installation is the origin of my problem.
When I reboot the system, grub appears and then, the following message:



[FAILED] Failed to start Load Kernel Modules
See 'systemctl status systemd-modules-load.service' for details


Plus some other lines that end with a final:



Failed to start Load Kernel Modules


image



When I open a command line by pressing CTRL+ALT+F1 I'm able to enter



sudo systemctl status systemd-modules-load.service


and I get the following output:



status systemd-modules-load.service


image



If I repeat the systemctl command, I get sometimes other process instead of 179, for example, 183.



Just in case it's needed,



sudo ls /lib/systemd/system/systemd-modules-load.service


gives me



/lib/system/systemd-modules-load

(written in green)

journalctl


outputs a lot of data. The red lines are the following ones:



First red line:



image



Second and third red line:



image



Fourth red line:



image



I really appreciate a little bit of help here. I don't know what to do next and I've searched the web finding nothing.










share|improve this question































    38















    I tried to upgrade my system from Ubuntu 14.04. My laptop froze for a few hours. Not even the pointer did anything. So I switched off by pressing the power button for a few seconds.
    This uncompleted installation is the origin of my problem.
    When I reboot the system, grub appears and then, the following message:



    [FAILED] Failed to start Load Kernel Modules
    See 'systemctl status systemd-modules-load.service' for details


    Plus some other lines that end with a final:



    Failed to start Load Kernel Modules


    image



    When I open a command line by pressing CTRL+ALT+F1 I'm able to enter



    sudo systemctl status systemd-modules-load.service


    and I get the following output:



    status systemd-modules-load.service


    image



    If I repeat the systemctl command, I get sometimes other process instead of 179, for example, 183.



    Just in case it's needed,



    sudo ls /lib/systemd/system/systemd-modules-load.service


    gives me



    /lib/system/systemd-modules-load

    (written in green)

    journalctl


    outputs a lot of data. The red lines are the following ones:



    First red line:



    image



    Second and third red line:



    image



    Fourth red line:



    image



    I really appreciate a little bit of help here. I don't know what to do next and I've searched the web finding nothing.










    share|improve this question



























      38












      38








      38


      11






      I tried to upgrade my system from Ubuntu 14.04. My laptop froze for a few hours. Not even the pointer did anything. So I switched off by pressing the power button for a few seconds.
      This uncompleted installation is the origin of my problem.
      When I reboot the system, grub appears and then, the following message:



      [FAILED] Failed to start Load Kernel Modules
      See 'systemctl status systemd-modules-load.service' for details


      Plus some other lines that end with a final:



      Failed to start Load Kernel Modules


      image



      When I open a command line by pressing CTRL+ALT+F1 I'm able to enter



      sudo systemctl status systemd-modules-load.service


      and I get the following output:



      status systemd-modules-load.service


      image



      If I repeat the systemctl command, I get sometimes other process instead of 179, for example, 183.



      Just in case it's needed,



      sudo ls /lib/systemd/system/systemd-modules-load.service


      gives me



      /lib/system/systemd-modules-load

      (written in green)

      journalctl


      outputs a lot of data. The red lines are the following ones:



      First red line:



      image



      Second and third red line:



      image



      Fourth red line:



      image



      I really appreciate a little bit of help here. I don't know what to do next and I've searched the web finding nothing.










      share|improve this question
















      I tried to upgrade my system from Ubuntu 14.04. My laptop froze for a few hours. Not even the pointer did anything. So I switched off by pressing the power button for a few seconds.
      This uncompleted installation is the origin of my problem.
      When I reboot the system, grub appears and then, the following message:



      [FAILED] Failed to start Load Kernel Modules
      See 'systemctl status systemd-modules-load.service' for details


      Plus some other lines that end with a final:



      Failed to start Load Kernel Modules


      image



      When I open a command line by pressing CTRL+ALT+F1 I'm able to enter



      sudo systemctl status systemd-modules-load.service


      and I get the following output:



      status systemd-modules-load.service


      image



      If I repeat the systemctl command, I get sometimes other process instead of 179, for example, 183.



      Just in case it's needed,



      sudo ls /lib/systemd/system/systemd-modules-load.service


      gives me



      /lib/system/systemd-modules-load

      (written in green)

      journalctl


      outputs a lot of data. The red lines are the following ones:



      First red line:



      image



      Second and third red line:



      image



      Fourth red line:



      image



      I really appreciate a little bit of help here. I don't know what to do next and I've searched the web finding nothing.







      boot command-line kernel services






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 22 '16 at 19:18









      Caleb Evans

      1518




      1518










      asked May 29 '16 at 22:48









      FranciscoFrancisco

      371137




      371137






















          7 Answers
          7






          active

          oldest

          votes


















          18














          I found exactly what I needed in a discussion in ubuntuforums.org. Specifically, I was looking for the command:



          dpkg --configure -a


          The linked article above mentions four commands that may help resolve this problem and notes that they may need to be repeated "in no specific order":



          apt-get update
          dpkg --configure -a
          apt-get dist-upgrade
          apt-get -f install





          share|improve this answer





















          • 2





            The linked article threw me off a bit, because its first command (apt-get update) didn't help. But your pointer to the article's second command (dpkg --configure -a) did the job. Now that my machine is back in action (and I'm not stuck on my phone), I see that the article advises that the commands may need to be repeated "in no specific order". In case that article disappears, the other two commands are apt-get dist-upgrade and apt-get -f install.

            – Steve
            Oct 25 '16 at 16:44











          • I'd just like to add that I'm working with Gem 5, and I'm trying to boot a disk image of Ubuntu 16.04.1/3 (server), and while it boots fine in QEMU, it gives me this error when running in full system mode in Gem 5. I'm sure that this solution has worked for others, but I wanted to add that it didn't fix it in my case.

            – Joshua Detwiler
            Dec 16 '17 at 0:17











          • the apt-get update` only really needs to come before the apt-get dist-upgrade. You should avoid running a dist-upgrade if you don't know what you are doing, especially if dpkg --configure -a already works for you. Similarly, use apt-get -f install as a last resort as it can severely break your system.

            – virtualxtc
            Aug 28 '18 at 21:32





















          2














          I had the impression something went wrong on an update / kernel update:



          Booted into recovery mode.





          • menu "root": manually revoked network



            ifconfig ethx <ip> netmask <mask> up
            echo "nameserver 8.8.8.8" > /etc/resolv.conf
            apt-get update


          • menu "dpkg": Repaired installation



          • back to menu "root": repair kernel initramfs



            update-initramfs -k all -u
            update-grub







          share|improve this answer


























          • +1 for the 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' line :)

            – Tom
            Apr 11 '18 at 17:27



















          1














          I just had this problem with an ubuntu 16.04 installation. When I looked into journalctl | grep modules from the recovery root shell, I saw that it was trying to load modules from the 16.10 (newer) kernel. It was left over data on my USB stick because I did not format it in-between writing images to it (from a mac using unetbootin).



          So a format of the USB stick, remake the bootable stick, and it was as good as gold.



          :)






          share|improve this answer































            1














            In my case this might have happen when an update to the installation was going on and the system switched off without fully updated.



            Press Ctrl+Alt+F1 (for command line interface)



            After that,



            sudo dpkg --configure -a
            sudo apt-get dist-upgrade
            sudo apt-get -f install (this command is optional, because the `dist-upgrade` command should have everything)


            At lastly,



            sudo init 6


            (restart the system)



            Now you will see Ubuntu 16.04 LTS without any error.



            Note: It will take 45 min to 60 min.






            share|improve this answer


























            • if your system is up to date, it won't take 45-60 min

              – virtualxtc
              Aug 28 '18 at 21:33



















            0














            Same problem to upgrade from 12 to 14 and 14 to 16. Without solution :-/



            I make same question without solution here:




            • http://www.ubuntu-es.org/node/190523

            • http://www.ubuntu-es.org/node/188881


            The solution for me: formating pc.






            share|improve this answer































              0














              For me it was a problem with my home partition, so running fsck /dev/sdb6 and answering all questions with yes solved it.



              The affected partition might not be sdb6 on your system. In that case you will have to adjust the device name from /dev/sdb6 to the name used by your partition. If you don't know the correct pathname then you may be able to find it by running mount or by inspecting the contents of /etc/fstab (which you can do with cat /etc/fstab).






              share|improve this answer

































                0














                I also got



                Failed to start Load Kernel Modules


                every time at startup.



                I did what Francisco suggested, but it didn't remove the error.



                What did work though was to comment out the line nouveau in my /etc/modules file, the nvidia driver.



                All my problems started when I switched driver so ofc it makes perfect sense. One thing that led me to it was the lines



                ... systemd-modules-load[279]: could not find module by name='off'
                ... Failed to insert 'off': No such file or directory


                in my /var/log/syslog. Btw, I'm running Ubuntu 18.04.






                share|improve this answer








                New contributor




                Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





















                  Your Answer








                  StackExchange.ready(function() {
                  var channelOptions = {
                  tags: "".split(" "),
                  id: "89"
                  };
                  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: true,
                  noModals: true,
                  showLowRepImageUploadWarning: true,
                  reputationToPostImages: 10,
                  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%2faskubuntu.com%2fquestions%2f779251%2fwhat-to-do-after-failed-to-start-load-kernel-modules%23new-answer', 'question_page');
                  }
                  );

                  Post as a guest















                  Required, but never shown

























                  7 Answers
                  7






                  active

                  oldest

                  votes








                  7 Answers
                  7






                  active

                  oldest

                  votes









                  active

                  oldest

                  votes






                  active

                  oldest

                  votes









                  18














                  I found exactly what I needed in a discussion in ubuntuforums.org. Specifically, I was looking for the command:



                  dpkg --configure -a


                  The linked article above mentions four commands that may help resolve this problem and notes that they may need to be repeated "in no specific order":



                  apt-get update
                  dpkg --configure -a
                  apt-get dist-upgrade
                  apt-get -f install





                  share|improve this answer





















                  • 2





                    The linked article threw me off a bit, because its first command (apt-get update) didn't help. But your pointer to the article's second command (dpkg --configure -a) did the job. Now that my machine is back in action (and I'm not stuck on my phone), I see that the article advises that the commands may need to be repeated "in no specific order". In case that article disappears, the other two commands are apt-get dist-upgrade and apt-get -f install.

                    – Steve
                    Oct 25 '16 at 16:44











                  • I'd just like to add that I'm working with Gem 5, and I'm trying to boot a disk image of Ubuntu 16.04.1/3 (server), and while it boots fine in QEMU, it gives me this error when running in full system mode in Gem 5. I'm sure that this solution has worked for others, but I wanted to add that it didn't fix it in my case.

                    – Joshua Detwiler
                    Dec 16 '17 at 0:17











                  • the apt-get update` only really needs to come before the apt-get dist-upgrade. You should avoid running a dist-upgrade if you don't know what you are doing, especially if dpkg --configure -a already works for you. Similarly, use apt-get -f install as a last resort as it can severely break your system.

                    – virtualxtc
                    Aug 28 '18 at 21:32


















                  18














                  I found exactly what I needed in a discussion in ubuntuforums.org. Specifically, I was looking for the command:



                  dpkg --configure -a


                  The linked article above mentions four commands that may help resolve this problem and notes that they may need to be repeated "in no specific order":



                  apt-get update
                  dpkg --configure -a
                  apt-get dist-upgrade
                  apt-get -f install





                  share|improve this answer





















                  • 2





                    The linked article threw me off a bit, because its first command (apt-get update) didn't help. But your pointer to the article's second command (dpkg --configure -a) did the job. Now that my machine is back in action (and I'm not stuck on my phone), I see that the article advises that the commands may need to be repeated "in no specific order". In case that article disappears, the other two commands are apt-get dist-upgrade and apt-get -f install.

                    – Steve
                    Oct 25 '16 at 16:44











                  • I'd just like to add that I'm working with Gem 5, and I'm trying to boot a disk image of Ubuntu 16.04.1/3 (server), and while it boots fine in QEMU, it gives me this error when running in full system mode in Gem 5. I'm sure that this solution has worked for others, but I wanted to add that it didn't fix it in my case.

                    – Joshua Detwiler
                    Dec 16 '17 at 0:17











                  • the apt-get update` only really needs to come before the apt-get dist-upgrade. You should avoid running a dist-upgrade if you don't know what you are doing, especially if dpkg --configure -a already works for you. Similarly, use apt-get -f install as a last resort as it can severely break your system.

                    – virtualxtc
                    Aug 28 '18 at 21:32
















                  18












                  18








                  18







                  I found exactly what I needed in a discussion in ubuntuforums.org. Specifically, I was looking for the command:



                  dpkg --configure -a


                  The linked article above mentions four commands that may help resolve this problem and notes that they may need to be repeated "in no specific order":



                  apt-get update
                  dpkg --configure -a
                  apt-get dist-upgrade
                  apt-get -f install





                  share|improve this answer















                  I found exactly what I needed in a discussion in ubuntuforums.org. Specifically, I was looking for the command:



                  dpkg --configure -a


                  The linked article above mentions four commands that may help resolve this problem and notes that they may need to be repeated "in no specific order":



                  apt-get update
                  dpkg --configure -a
                  apt-get dist-upgrade
                  apt-get -f install






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Oct 18 '18 at 19:00









                  Zanna

                  51.2k13139243




                  51.2k13139243










                  answered May 30 '16 at 16:55









                  FranciscoFrancisco

                  371137




                  371137








                  • 2





                    The linked article threw me off a bit, because its first command (apt-get update) didn't help. But your pointer to the article's second command (dpkg --configure -a) did the job. Now that my machine is back in action (and I'm not stuck on my phone), I see that the article advises that the commands may need to be repeated "in no specific order". In case that article disappears, the other two commands are apt-get dist-upgrade and apt-get -f install.

                    – Steve
                    Oct 25 '16 at 16:44











                  • I'd just like to add that I'm working with Gem 5, and I'm trying to boot a disk image of Ubuntu 16.04.1/3 (server), and while it boots fine in QEMU, it gives me this error when running in full system mode in Gem 5. I'm sure that this solution has worked for others, but I wanted to add that it didn't fix it in my case.

                    – Joshua Detwiler
                    Dec 16 '17 at 0:17











                  • the apt-get update` only really needs to come before the apt-get dist-upgrade. You should avoid running a dist-upgrade if you don't know what you are doing, especially if dpkg --configure -a already works for you. Similarly, use apt-get -f install as a last resort as it can severely break your system.

                    – virtualxtc
                    Aug 28 '18 at 21:32
















                  • 2





                    The linked article threw me off a bit, because its first command (apt-get update) didn't help. But your pointer to the article's second command (dpkg --configure -a) did the job. Now that my machine is back in action (and I'm not stuck on my phone), I see that the article advises that the commands may need to be repeated "in no specific order". In case that article disappears, the other two commands are apt-get dist-upgrade and apt-get -f install.

                    – Steve
                    Oct 25 '16 at 16:44











                  • I'd just like to add that I'm working with Gem 5, and I'm trying to boot a disk image of Ubuntu 16.04.1/3 (server), and while it boots fine in QEMU, it gives me this error when running in full system mode in Gem 5. I'm sure that this solution has worked for others, but I wanted to add that it didn't fix it in my case.

                    – Joshua Detwiler
                    Dec 16 '17 at 0:17











                  • the apt-get update` only really needs to come before the apt-get dist-upgrade. You should avoid running a dist-upgrade if you don't know what you are doing, especially if dpkg --configure -a already works for you. Similarly, use apt-get -f install as a last resort as it can severely break your system.

                    – virtualxtc
                    Aug 28 '18 at 21:32










                  2




                  2





                  The linked article threw me off a bit, because its first command (apt-get update) didn't help. But your pointer to the article's second command (dpkg --configure -a) did the job. Now that my machine is back in action (and I'm not stuck on my phone), I see that the article advises that the commands may need to be repeated "in no specific order". In case that article disappears, the other two commands are apt-get dist-upgrade and apt-get -f install.

                  – Steve
                  Oct 25 '16 at 16:44





                  The linked article threw me off a bit, because its first command (apt-get update) didn't help. But your pointer to the article's second command (dpkg --configure -a) did the job. Now that my machine is back in action (and I'm not stuck on my phone), I see that the article advises that the commands may need to be repeated "in no specific order". In case that article disappears, the other two commands are apt-get dist-upgrade and apt-get -f install.

                  – Steve
                  Oct 25 '16 at 16:44













                  I'd just like to add that I'm working with Gem 5, and I'm trying to boot a disk image of Ubuntu 16.04.1/3 (server), and while it boots fine in QEMU, it gives me this error when running in full system mode in Gem 5. I'm sure that this solution has worked for others, but I wanted to add that it didn't fix it in my case.

                  – Joshua Detwiler
                  Dec 16 '17 at 0:17





                  I'd just like to add that I'm working with Gem 5, and I'm trying to boot a disk image of Ubuntu 16.04.1/3 (server), and while it boots fine in QEMU, it gives me this error when running in full system mode in Gem 5. I'm sure that this solution has worked for others, but I wanted to add that it didn't fix it in my case.

                  – Joshua Detwiler
                  Dec 16 '17 at 0:17













                  the apt-get update` only really needs to come before the apt-get dist-upgrade. You should avoid running a dist-upgrade if you don't know what you are doing, especially if dpkg --configure -a already works for you. Similarly, use apt-get -f install as a last resort as it can severely break your system.

                  – virtualxtc
                  Aug 28 '18 at 21:32







                  the apt-get update` only really needs to come before the apt-get dist-upgrade. You should avoid running a dist-upgrade if you don't know what you are doing, especially if dpkg --configure -a already works for you. Similarly, use apt-get -f install as a last resort as it can severely break your system.

                  – virtualxtc
                  Aug 28 '18 at 21:32















                  2














                  I had the impression something went wrong on an update / kernel update:



                  Booted into recovery mode.





                  • menu "root": manually revoked network



                    ifconfig ethx <ip> netmask <mask> up
                    echo "nameserver 8.8.8.8" > /etc/resolv.conf
                    apt-get update


                  • menu "dpkg": Repaired installation



                  • back to menu "root": repair kernel initramfs



                    update-initramfs -k all -u
                    update-grub







                  share|improve this answer


























                  • +1 for the 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' line :)

                    – Tom
                    Apr 11 '18 at 17:27
















                  2














                  I had the impression something went wrong on an update / kernel update:



                  Booted into recovery mode.





                  • menu "root": manually revoked network



                    ifconfig ethx <ip> netmask <mask> up
                    echo "nameserver 8.8.8.8" > /etc/resolv.conf
                    apt-get update


                  • menu "dpkg": Repaired installation



                  • back to menu "root": repair kernel initramfs



                    update-initramfs -k all -u
                    update-grub







                  share|improve this answer


























                  • +1 for the 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' line :)

                    – Tom
                    Apr 11 '18 at 17:27














                  2












                  2








                  2







                  I had the impression something went wrong on an update / kernel update:



                  Booted into recovery mode.





                  • menu "root": manually revoked network



                    ifconfig ethx <ip> netmask <mask> up
                    echo "nameserver 8.8.8.8" > /etc/resolv.conf
                    apt-get update


                  • menu "dpkg": Repaired installation



                  • back to menu "root": repair kernel initramfs



                    update-initramfs -k all -u
                    update-grub







                  share|improve this answer















                  I had the impression something went wrong on an update / kernel update:



                  Booted into recovery mode.





                  • menu "root": manually revoked network



                    ifconfig ethx <ip> netmask <mask> up
                    echo "nameserver 8.8.8.8" > /etc/resolv.conf
                    apt-get update


                  • menu "dpkg": Repaired installation



                  • back to menu "root": repair kernel initramfs



                    update-initramfs -k all -u
                    update-grub








                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Apr 26 '18 at 10:58









                  David Foerster

                  28.6k1367113




                  28.6k1367113










                  answered Sep 22 '17 at 7:49









                  aposapos

                  46939




                  46939













                  • +1 for the 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' line :)

                    – Tom
                    Apr 11 '18 at 17:27



















                  • +1 for the 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' line :)

                    – Tom
                    Apr 11 '18 at 17:27

















                  +1 for the 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' line :)

                  – Tom
                  Apr 11 '18 at 17:27





                  +1 for the 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' line :)

                  – Tom
                  Apr 11 '18 at 17:27











                  1














                  I just had this problem with an ubuntu 16.04 installation. When I looked into journalctl | grep modules from the recovery root shell, I saw that it was trying to load modules from the 16.10 (newer) kernel. It was left over data on my USB stick because I did not format it in-between writing images to it (from a mac using unetbootin).



                  So a format of the USB stick, remake the bootable stick, and it was as good as gold.



                  :)






                  share|improve this answer




























                    1














                    I just had this problem with an ubuntu 16.04 installation. When I looked into journalctl | grep modules from the recovery root shell, I saw that it was trying to load modules from the 16.10 (newer) kernel. It was left over data on my USB stick because I did not format it in-between writing images to it (from a mac using unetbootin).



                    So a format of the USB stick, remake the bootable stick, and it was as good as gold.



                    :)






                    share|improve this answer


























                      1












                      1








                      1







                      I just had this problem with an ubuntu 16.04 installation. When I looked into journalctl | grep modules from the recovery root shell, I saw that it was trying to load modules from the 16.10 (newer) kernel. It was left over data on my USB stick because I did not format it in-between writing images to it (from a mac using unetbootin).



                      So a format of the USB stick, remake the bootable stick, and it was as good as gold.



                      :)






                      share|improve this answer













                      I just had this problem with an ubuntu 16.04 installation. When I looked into journalctl | grep modules from the recovery root shell, I saw that it was trying to load modules from the 16.10 (newer) kernel. It was left over data on my USB stick because I did not format it in-between writing images to it (from a mac using unetbootin).



                      So a format of the USB stick, remake the bootable stick, and it was as good as gold.



                      :)







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Nov 23 '16 at 4:20









                      Tim RichardsonTim Richardson

                      731415




                      731415























                          1














                          In my case this might have happen when an update to the installation was going on and the system switched off without fully updated.



                          Press Ctrl+Alt+F1 (for command line interface)



                          After that,



                          sudo dpkg --configure -a
                          sudo apt-get dist-upgrade
                          sudo apt-get -f install (this command is optional, because the `dist-upgrade` command should have everything)


                          At lastly,



                          sudo init 6


                          (restart the system)



                          Now you will see Ubuntu 16.04 LTS without any error.



                          Note: It will take 45 min to 60 min.






                          share|improve this answer


























                          • if your system is up to date, it won't take 45-60 min

                            – virtualxtc
                            Aug 28 '18 at 21:33
















                          1














                          In my case this might have happen when an update to the installation was going on and the system switched off without fully updated.



                          Press Ctrl+Alt+F1 (for command line interface)



                          After that,



                          sudo dpkg --configure -a
                          sudo apt-get dist-upgrade
                          sudo apt-get -f install (this command is optional, because the `dist-upgrade` command should have everything)


                          At lastly,



                          sudo init 6


                          (restart the system)



                          Now you will see Ubuntu 16.04 LTS without any error.



                          Note: It will take 45 min to 60 min.






                          share|improve this answer


























                          • if your system is up to date, it won't take 45-60 min

                            – virtualxtc
                            Aug 28 '18 at 21:33














                          1












                          1








                          1







                          In my case this might have happen when an update to the installation was going on and the system switched off without fully updated.



                          Press Ctrl+Alt+F1 (for command line interface)



                          After that,



                          sudo dpkg --configure -a
                          sudo apt-get dist-upgrade
                          sudo apt-get -f install (this command is optional, because the `dist-upgrade` command should have everything)


                          At lastly,



                          sudo init 6


                          (restart the system)



                          Now you will see Ubuntu 16.04 LTS without any error.



                          Note: It will take 45 min to 60 min.






                          share|improve this answer















                          In my case this might have happen when an update to the installation was going on and the system switched off without fully updated.



                          Press Ctrl+Alt+F1 (for command line interface)



                          After that,



                          sudo dpkg --configure -a
                          sudo apt-get dist-upgrade
                          sudo apt-get -f install (this command is optional, because the `dist-upgrade` command should have everything)


                          At lastly,



                          sudo init 6


                          (restart the system)



                          Now you will see Ubuntu 16.04 LTS without any error.



                          Note: It will take 45 min to 60 min.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited May 2 '18 at 10:49

























                          answered May 2 '18 at 6:22









                          Kiritkumar VananiKiritkumar Vanani

                          164




                          164













                          • if your system is up to date, it won't take 45-60 min

                            – virtualxtc
                            Aug 28 '18 at 21:33



















                          • if your system is up to date, it won't take 45-60 min

                            – virtualxtc
                            Aug 28 '18 at 21:33

















                          if your system is up to date, it won't take 45-60 min

                          – virtualxtc
                          Aug 28 '18 at 21:33





                          if your system is up to date, it won't take 45-60 min

                          – virtualxtc
                          Aug 28 '18 at 21:33











                          0














                          Same problem to upgrade from 12 to 14 and 14 to 16. Without solution :-/



                          I make same question without solution here:




                          • http://www.ubuntu-es.org/node/190523

                          • http://www.ubuntu-es.org/node/188881


                          The solution for me: formating pc.






                          share|improve this answer




























                            0














                            Same problem to upgrade from 12 to 14 and 14 to 16. Without solution :-/



                            I make same question without solution here:




                            • http://www.ubuntu-es.org/node/190523

                            • http://www.ubuntu-es.org/node/188881


                            The solution for me: formating pc.






                            share|improve this answer


























                              0












                              0








                              0







                              Same problem to upgrade from 12 to 14 and 14 to 16. Without solution :-/



                              I make same question without solution here:




                              • http://www.ubuntu-es.org/node/190523

                              • http://www.ubuntu-es.org/node/188881


                              The solution for me: formating pc.






                              share|improve this answer













                              Same problem to upgrade from 12 to 14 and 14 to 16. Without solution :-/



                              I make same question without solution here:




                              • http://www.ubuntu-es.org/node/190523

                              • http://www.ubuntu-es.org/node/188881


                              The solution for me: formating pc.







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Aug 27 '16 at 15:23









                              e-info128e-info128

                              1547




                              1547























                                  0














                                  For me it was a problem with my home partition, so running fsck /dev/sdb6 and answering all questions with yes solved it.



                                  The affected partition might not be sdb6 on your system. In that case you will have to adjust the device name from /dev/sdb6 to the name used by your partition. If you don't know the correct pathname then you may be able to find it by running mount or by inspecting the contents of /etc/fstab (which you can do with cat /etc/fstab).






                                  share|improve this answer






























                                    0














                                    For me it was a problem with my home partition, so running fsck /dev/sdb6 and answering all questions with yes solved it.



                                    The affected partition might not be sdb6 on your system. In that case you will have to adjust the device name from /dev/sdb6 to the name used by your partition. If you don't know the correct pathname then you may be able to find it by running mount or by inspecting the contents of /etc/fstab (which you can do with cat /etc/fstab).






                                    share|improve this answer




























                                      0












                                      0








                                      0







                                      For me it was a problem with my home partition, so running fsck /dev/sdb6 and answering all questions with yes solved it.



                                      The affected partition might not be sdb6 on your system. In that case you will have to adjust the device name from /dev/sdb6 to the name used by your partition. If you don't know the correct pathname then you may be able to find it by running mount or by inspecting the contents of /etc/fstab (which you can do with cat /etc/fstab).






                                      share|improve this answer















                                      For me it was a problem with my home partition, so running fsck /dev/sdb6 and answering all questions with yes solved it.



                                      The affected partition might not be sdb6 on your system. In that case you will have to adjust the device name from /dev/sdb6 to the name used by your partition. If you don't know the correct pathname then you may be able to find it by running mount or by inspecting the contents of /etc/fstab (which you can do with cat /etc/fstab).







                                      share|improve this answer














                                      share|improve this answer



                                      share|improve this answer








                                      edited Sep 19 '17 at 14:47









                                      Eliah Kagan

                                      83.1k22229369




                                      83.1k22229369










                                      answered Sep 19 '17 at 13:58









                                      DeepKlingDeepKling

                                      1




                                      1























                                          0














                                          I also got



                                          Failed to start Load Kernel Modules


                                          every time at startup.



                                          I did what Francisco suggested, but it didn't remove the error.



                                          What did work though was to comment out the line nouveau in my /etc/modules file, the nvidia driver.



                                          All my problems started when I switched driver so ofc it makes perfect sense. One thing that led me to it was the lines



                                          ... systemd-modules-load[279]: could not find module by name='off'
                                          ... Failed to insert 'off': No such file or directory


                                          in my /var/log/syslog. Btw, I'm running Ubuntu 18.04.






                                          share|improve this answer








                                          New contributor




                                          Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                          Check out our Code of Conduct.

























                                            0














                                            I also got



                                            Failed to start Load Kernel Modules


                                            every time at startup.



                                            I did what Francisco suggested, but it didn't remove the error.



                                            What did work though was to comment out the line nouveau in my /etc/modules file, the nvidia driver.



                                            All my problems started when I switched driver so ofc it makes perfect sense. One thing that led me to it was the lines



                                            ... systemd-modules-load[279]: could not find module by name='off'
                                            ... Failed to insert 'off': No such file or directory


                                            in my /var/log/syslog. Btw, I'm running Ubuntu 18.04.






                                            share|improve this answer








                                            New contributor




                                            Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                            Check out our Code of Conduct.























                                              0












                                              0








                                              0







                                              I also got



                                              Failed to start Load Kernel Modules


                                              every time at startup.



                                              I did what Francisco suggested, but it didn't remove the error.



                                              What did work though was to comment out the line nouveau in my /etc/modules file, the nvidia driver.



                                              All my problems started when I switched driver so ofc it makes perfect sense. One thing that led me to it was the lines



                                              ... systemd-modules-load[279]: could not find module by name='off'
                                              ... Failed to insert 'off': No such file or directory


                                              in my /var/log/syslog. Btw, I'm running Ubuntu 18.04.






                                              share|improve this answer








                                              New contributor




                                              Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                              Check out our Code of Conduct.










                                              I also got



                                              Failed to start Load Kernel Modules


                                              every time at startup.



                                              I did what Francisco suggested, but it didn't remove the error.



                                              What did work though was to comment out the line nouveau in my /etc/modules file, the nvidia driver.



                                              All my problems started when I switched driver so ofc it makes perfect sense. One thing that led me to it was the lines



                                              ... systemd-modules-load[279]: could not find module by name='off'
                                              ... Failed to insert 'off': No such file or directory


                                              in my /var/log/syslog. Btw, I'm running Ubuntu 18.04.







                                              share|improve this answer








                                              New contributor




                                              Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                              Check out our Code of Conduct.









                                              share|improve this answer



                                              share|improve this answer






                                              New contributor




                                              Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                              Check out our Code of Conduct.









                                              answered 6 hours ago









                                              MattiasMattias

                                              101




                                              101




                                              New contributor




                                              Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                              Check out our Code of Conduct.





                                              New contributor





                                              Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                              Check out our Code of Conduct.






                                              Mattias is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                              Check out our Code of Conduct.






























                                                  draft saved

                                                  draft discarded




















































                                                  Thanks for contributing an answer to Ask Ubuntu!


                                                  • 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%2faskubuntu.com%2fquestions%2f779251%2fwhat-to-do-after-failed-to-start-load-kernel-modules%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

                                                  GameSpot

                                                  connect to host localhost port 22: Connection refused

                                                  Getting a Wifi WPA2 wifi connection