“Could not open moddep file '/lib/modules/3.XX-generic/modules.dep.bin'” when mounting using a loop












26















Running 14.04 in virtualbox 4.3.8



Unable to detect the guest additions.iso when i selected the guest additions.iso in the IDE Secondary Master.



No problem, so I used wget and downloaded the iso into the guest ubuntu headless.



when I attempt to load the iso from inside using these commands:



sudo mkdir /media/iso
sudo modprobe loop
sudo mount filename.iso /media/iso -t iso9660 -o loop


At the sudo modprobe loop, I got the following error:



modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'


Here are my lsb_release -a:



No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty


EDIT:



When I typed



ls /lib/modules/*/modules.dep.bin


I get back



/lib/modules/3.11.0-20-generic/modules.dep.bin  /lib/modules/3.13.0-24-generic/mo‌​dules.dep.bin /lib/modules/3.5.0-49-generic/modules.dep.bin









share|improve this question

























  • When I do this I just get 1 dep.bin: ls /lib/modules/*/modules.dep.bin /lib/modules/4.4.0-22-generic/modules.dep.bin But somehow he still says I have 4.2.0.25. How might this come?

    – kwoxer
    Jun 4 '16 at 19:02
















26















Running 14.04 in virtualbox 4.3.8



Unable to detect the guest additions.iso when i selected the guest additions.iso in the IDE Secondary Master.



No problem, so I used wget and downloaded the iso into the guest ubuntu headless.



when I attempt to load the iso from inside using these commands:



sudo mkdir /media/iso
sudo modprobe loop
sudo mount filename.iso /media/iso -t iso9660 -o loop


At the sudo modprobe loop, I got the following error:



modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'


Here are my lsb_release -a:



No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty


EDIT:



When I typed



ls /lib/modules/*/modules.dep.bin


I get back



/lib/modules/3.11.0-20-generic/modules.dep.bin  /lib/modules/3.13.0-24-generic/mo‌​dules.dep.bin /lib/modules/3.5.0-49-generic/modules.dep.bin









share|improve this question

























  • When I do this I just get 1 dep.bin: ls /lib/modules/*/modules.dep.bin /lib/modules/4.4.0-22-generic/modules.dep.bin But somehow he still says I have 4.2.0.25. How might this come?

    – kwoxer
    Jun 4 '16 at 19:02














26












26








26


10






Running 14.04 in virtualbox 4.3.8



Unable to detect the guest additions.iso when i selected the guest additions.iso in the IDE Secondary Master.



No problem, so I used wget and downloaded the iso into the guest ubuntu headless.



when I attempt to load the iso from inside using these commands:



sudo mkdir /media/iso
sudo modprobe loop
sudo mount filename.iso /media/iso -t iso9660 -o loop


At the sudo modprobe loop, I got the following error:



modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'


Here are my lsb_release -a:



No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty


EDIT:



When I typed



ls /lib/modules/*/modules.dep.bin


I get back



/lib/modules/3.11.0-20-generic/modules.dep.bin  /lib/modules/3.13.0-24-generic/mo‌​dules.dep.bin /lib/modules/3.5.0-49-generic/modules.dep.bin









share|improve this question
















Running 14.04 in virtualbox 4.3.8



Unable to detect the guest additions.iso when i selected the guest additions.iso in the IDE Secondary Master.



No problem, so I used wget and downloaded the iso into the guest ubuntu headless.



when I attempt to load the iso from inside using these commands:



sudo mkdir /media/iso
sudo modprobe loop
sudo mount filename.iso /media/iso -t iso9660 -o loop


At the sudo modprobe loop, I got the following error:



modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-24-generic/modules.dep.bin'


Here are my lsb_release -a:



No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty


EDIT:



When I typed



ls /lib/modules/*/modules.dep.bin


I get back



/lib/modules/3.11.0-20-generic/modules.dep.bin  /lib/modules/3.13.0-24-generic/mo‌​dules.dep.bin /lib/modules/3.5.0-49-generic/modules.dep.bin






modprobe






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 3 '14 at 8:03







Kim Stacks

















asked May 2 '14 at 3:50









Kim StacksKim Stacks

60611027




60611027













  • When I do this I just get 1 dep.bin: ls /lib/modules/*/modules.dep.bin /lib/modules/4.4.0-22-generic/modules.dep.bin But somehow he still says I have 4.2.0.25. How might this come?

    – kwoxer
    Jun 4 '16 at 19:02



















  • When I do this I just get 1 dep.bin: ls /lib/modules/*/modules.dep.bin /lib/modules/4.4.0-22-generic/modules.dep.bin But somehow he still says I have 4.2.0.25. How might this come?

    – kwoxer
    Jun 4 '16 at 19:02

















When I do this I just get 1 dep.bin: ls /lib/modules/*/modules.dep.bin /lib/modules/4.4.0-22-generic/modules.dep.bin But somehow he still says I have 4.2.0.25. How might this come?

– kwoxer
Jun 4 '16 at 19:02





When I do this I just get 1 dep.bin: ls /lib/modules/*/modules.dep.bin /lib/modules/4.4.0-22-generic/modules.dep.bin But somehow he still says I have 4.2.0.25. How might this come?

– kwoxer
Jun 4 '16 at 19:02










7 Answers
7






active

oldest

votes


















21














Thanks to Braiam comments, I have solved it using



sudo apt-get install --reinstall linux-image-3.13.0





share|improve this answer



















  • 1





    I had the same problem after the battery in my notebook failed during boot. mo‌​dules.dep.bin was empty. (computer shut off probably right during rebuild or something?) The mentioned reinstall solved the problem. Thanks! After further study I think it would probably suffice to run depmod to regenerate the file.

    – pabouk
    Oct 14 '14 at 14:11





















17














No need to reinstall linux image



sudo depmod


works fine for me. credit goes to @pabouk






share|improve this answer





















  • 8





    The I get: sudo depmod depmod: ERROR: could not open directory /lib/modules/4.2.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory

    – kwoxer
    Jun 4 '16 at 19:01











  • I have the same error as @kwoxer.

    – Vladimir Prudnikov
    Apr 4 '18 at 9:53











  • this worked for me, after notebook lost power, and rebooting it, /boot/efi could not be booted anymore, not even manually...

    – m.ardito
    Aug 11 '18 at 17:22











  • sudo depmod depmod: WARNING: could not open /lib/modules/4.9.0/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.9.0/modules.builtin: No such file or directory

    – Egbert S
    Dec 19 '18 at 0:05



















7














It may be system changes waiting for a reboot after updates. My installation was pointing to the wrong /lib/modules/<version>, but it worked itself out after a reboot.



#:/ $ sudo modinfo iptable_nat
libkmod: ERROR ../libkmod/libkmod.c:557 kmod_search_moddep: could not open moddep file '/lib/modules/4.1.18+/modules.dep.bin'
modinfo: ERROR: Module alias iptable_nat not found.





share|improve this answer


























  • I also has this issue: sudo modinfo iptable_nat libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/4.2.0-25-generic/modules.dep.bin' modinfo: ERROR: Module alias iptable_nat not found.

    – kwoxer
    Jun 4 '16 at 19:00











  • @kwoxer did you try rebooting?

    – sshow
    Jun 4 '16 at 20:42











  • Was able to solve it already : serverfault.com/questions/780980/…

    – kwoxer
    Jun 5 '16 at 5:13











  • Thankful for this answer. Saved me from reinstalling linux. :)

    – Zig
    Jan 3 '17 at 23:58











  • I am writing ansible role for iptables setup and experiencing the same issue.. after reboot all works... but I need to do it in a programmatic way, so no reboot allowed. Is there any way to make it work without reboot?

    – Drew
    Feb 23 '18 at 6:42



















4















# apt-get install --reinstall linux-image-`uname -r`


This will do the trick unless you want to upgrade your kernel.






share|improve this answer
























  • Same answer as Kim Stacks's earlier one.

    – Karl Richter
    Jul 26 '17 at 0:21



















0














Oddly, I'm experiencing this issue if I specify an ExecStart stanze in a systemd unit containing two commands connected with &&, e.g.



ExecStart=/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data


This might be incorrect, but then systemd would still need to fail with a helpful error message - like any program ever existing.



The command chain can be expressed with bash -c, e.g.



ExecStart=/bin/bash -c '/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data'


(mind the simple quotes '' instead of double quotes "").






share|improve this answer































    0














    Ok. I couldn’t believe it but I got the same error and after much troubleshooting, I’ve discovered that the /boot was NOT mounted during this kernel module rebuild.



    Once mounted, the problem went away for me.



    Turns out that I was a good “victim” of a good security practice (as outlined by CISecurity).






    share|improve this answer































      -1














      If you can't access the network you can do



      dpkg-reconfigure linux-image-$(uname -r)


      It worked for me






      share|improve this answer


























        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%2f459296%2fcould-not-open-moddep-file-lib-modules-3-xx-generic-modules-dep-bin-when-mo%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









        21














        Thanks to Braiam comments, I have solved it using



        sudo apt-get install --reinstall linux-image-3.13.0





        share|improve this answer



















        • 1





          I had the same problem after the battery in my notebook failed during boot. mo‌​dules.dep.bin was empty. (computer shut off probably right during rebuild or something?) The mentioned reinstall solved the problem. Thanks! After further study I think it would probably suffice to run depmod to regenerate the file.

          – pabouk
          Oct 14 '14 at 14:11


















        21














        Thanks to Braiam comments, I have solved it using



        sudo apt-get install --reinstall linux-image-3.13.0





        share|improve this answer



















        • 1





          I had the same problem after the battery in my notebook failed during boot. mo‌​dules.dep.bin was empty. (computer shut off probably right during rebuild or something?) The mentioned reinstall solved the problem. Thanks! After further study I think it would probably suffice to run depmod to regenerate the file.

          – pabouk
          Oct 14 '14 at 14:11
















        21












        21








        21







        Thanks to Braiam comments, I have solved it using



        sudo apt-get install --reinstall linux-image-3.13.0





        share|improve this answer













        Thanks to Braiam comments, I have solved it using



        sudo apt-get install --reinstall linux-image-3.13.0






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 3 '14 at 8:48









        Kim StacksKim Stacks

        60611027




        60611027








        • 1





          I had the same problem after the battery in my notebook failed during boot. mo‌​dules.dep.bin was empty. (computer shut off probably right during rebuild or something?) The mentioned reinstall solved the problem. Thanks! After further study I think it would probably suffice to run depmod to regenerate the file.

          – pabouk
          Oct 14 '14 at 14:11
















        • 1





          I had the same problem after the battery in my notebook failed during boot. mo‌​dules.dep.bin was empty. (computer shut off probably right during rebuild or something?) The mentioned reinstall solved the problem. Thanks! After further study I think it would probably suffice to run depmod to regenerate the file.

          – pabouk
          Oct 14 '14 at 14:11










        1




        1





        I had the same problem after the battery in my notebook failed during boot. mo‌​dules.dep.bin was empty. (computer shut off probably right during rebuild or something?) The mentioned reinstall solved the problem. Thanks! After further study I think it would probably suffice to run depmod to regenerate the file.

        – pabouk
        Oct 14 '14 at 14:11







        I had the same problem after the battery in my notebook failed during boot. mo‌​dules.dep.bin was empty. (computer shut off probably right during rebuild or something?) The mentioned reinstall solved the problem. Thanks! After further study I think it would probably suffice to run depmod to regenerate the file.

        – pabouk
        Oct 14 '14 at 14:11















        17














        No need to reinstall linux image



        sudo depmod


        works fine for me. credit goes to @pabouk






        share|improve this answer





















        • 8





          The I get: sudo depmod depmod: ERROR: could not open directory /lib/modules/4.2.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory

          – kwoxer
          Jun 4 '16 at 19:01











        • I have the same error as @kwoxer.

          – Vladimir Prudnikov
          Apr 4 '18 at 9:53











        • this worked for me, after notebook lost power, and rebooting it, /boot/efi could not be booted anymore, not even manually...

          – m.ardito
          Aug 11 '18 at 17:22











        • sudo depmod depmod: WARNING: could not open /lib/modules/4.9.0/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.9.0/modules.builtin: No such file or directory

          – Egbert S
          Dec 19 '18 at 0:05
















        17














        No need to reinstall linux image



        sudo depmod


        works fine for me. credit goes to @pabouk






        share|improve this answer





















        • 8





          The I get: sudo depmod depmod: ERROR: could not open directory /lib/modules/4.2.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory

          – kwoxer
          Jun 4 '16 at 19:01











        • I have the same error as @kwoxer.

          – Vladimir Prudnikov
          Apr 4 '18 at 9:53











        • this worked for me, after notebook lost power, and rebooting it, /boot/efi could not be booted anymore, not even manually...

          – m.ardito
          Aug 11 '18 at 17:22











        • sudo depmod depmod: WARNING: could not open /lib/modules/4.9.0/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.9.0/modules.builtin: No such file or directory

          – Egbert S
          Dec 19 '18 at 0:05














        17












        17








        17







        No need to reinstall linux image



        sudo depmod


        works fine for me. credit goes to @pabouk






        share|improve this answer















        No need to reinstall linux image



        sudo depmod


        works fine for me. credit goes to @pabouk







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 21 '15 at 10:39









        Tal

        1878




        1878










        answered Jan 26 '15 at 9:12









        GiriGiri

        4013616




        4013616








        • 8





          The I get: sudo depmod depmod: ERROR: could not open directory /lib/modules/4.2.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory

          – kwoxer
          Jun 4 '16 at 19:01











        • I have the same error as @kwoxer.

          – Vladimir Prudnikov
          Apr 4 '18 at 9:53











        • this worked for me, after notebook lost power, and rebooting it, /boot/efi could not be booted anymore, not even manually...

          – m.ardito
          Aug 11 '18 at 17:22











        • sudo depmod depmod: WARNING: could not open /lib/modules/4.9.0/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.9.0/modules.builtin: No such file or directory

          – Egbert S
          Dec 19 '18 at 0:05














        • 8





          The I get: sudo depmod depmod: ERROR: could not open directory /lib/modules/4.2.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory

          – kwoxer
          Jun 4 '16 at 19:01











        • I have the same error as @kwoxer.

          – Vladimir Prudnikov
          Apr 4 '18 at 9:53











        • this worked for me, after notebook lost power, and rebooting it, /boot/efi could not be booted anymore, not even manually...

          – m.ardito
          Aug 11 '18 at 17:22











        • sudo depmod depmod: WARNING: could not open /lib/modules/4.9.0/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.9.0/modules.builtin: No such file or directory

          – Egbert S
          Dec 19 '18 at 0:05








        8




        8





        The I get: sudo depmod depmod: ERROR: could not open directory /lib/modules/4.2.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory

        – kwoxer
        Jun 4 '16 at 19:01





        The I get: sudo depmod depmod: ERROR: could not open directory /lib/modules/4.2.0-25-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory

        – kwoxer
        Jun 4 '16 at 19:01













        I have the same error as @kwoxer.

        – Vladimir Prudnikov
        Apr 4 '18 at 9:53





        I have the same error as @kwoxer.

        – Vladimir Prudnikov
        Apr 4 '18 at 9:53













        this worked for me, after notebook lost power, and rebooting it, /boot/efi could not be booted anymore, not even manually...

        – m.ardito
        Aug 11 '18 at 17:22





        this worked for me, after notebook lost power, and rebooting it, /boot/efi could not be booted anymore, not even manually...

        – m.ardito
        Aug 11 '18 at 17:22













        sudo depmod depmod: WARNING: could not open /lib/modules/4.9.0/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.9.0/modules.builtin: No such file or directory

        – Egbert S
        Dec 19 '18 at 0:05





        sudo depmod depmod: WARNING: could not open /lib/modules/4.9.0/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/4.9.0/modules.builtin: No such file or directory

        – Egbert S
        Dec 19 '18 at 0:05











        7














        It may be system changes waiting for a reboot after updates. My installation was pointing to the wrong /lib/modules/<version>, but it worked itself out after a reboot.



        #:/ $ sudo modinfo iptable_nat
        libkmod: ERROR ../libkmod/libkmod.c:557 kmod_search_moddep: could not open moddep file '/lib/modules/4.1.18+/modules.dep.bin'
        modinfo: ERROR: Module alias iptable_nat not found.





        share|improve this answer


























        • I also has this issue: sudo modinfo iptable_nat libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/4.2.0-25-generic/modules.dep.bin' modinfo: ERROR: Module alias iptable_nat not found.

          – kwoxer
          Jun 4 '16 at 19:00











        • @kwoxer did you try rebooting?

          – sshow
          Jun 4 '16 at 20:42











        • Was able to solve it already : serverfault.com/questions/780980/…

          – kwoxer
          Jun 5 '16 at 5:13











        • Thankful for this answer. Saved me from reinstalling linux. :)

          – Zig
          Jan 3 '17 at 23:58











        • I am writing ansible role for iptables setup and experiencing the same issue.. after reboot all works... but I need to do it in a programmatic way, so no reboot allowed. Is there any way to make it work without reboot?

          – Drew
          Feb 23 '18 at 6:42
















        7














        It may be system changes waiting for a reboot after updates. My installation was pointing to the wrong /lib/modules/<version>, but it worked itself out after a reboot.



        #:/ $ sudo modinfo iptable_nat
        libkmod: ERROR ../libkmod/libkmod.c:557 kmod_search_moddep: could not open moddep file '/lib/modules/4.1.18+/modules.dep.bin'
        modinfo: ERROR: Module alias iptable_nat not found.





        share|improve this answer


























        • I also has this issue: sudo modinfo iptable_nat libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/4.2.0-25-generic/modules.dep.bin' modinfo: ERROR: Module alias iptable_nat not found.

          – kwoxer
          Jun 4 '16 at 19:00











        • @kwoxer did you try rebooting?

          – sshow
          Jun 4 '16 at 20:42











        • Was able to solve it already : serverfault.com/questions/780980/…

          – kwoxer
          Jun 5 '16 at 5:13











        • Thankful for this answer. Saved me from reinstalling linux. :)

          – Zig
          Jan 3 '17 at 23:58











        • I am writing ansible role for iptables setup and experiencing the same issue.. after reboot all works... but I need to do it in a programmatic way, so no reboot allowed. Is there any way to make it work without reboot?

          – Drew
          Feb 23 '18 at 6:42














        7












        7








        7







        It may be system changes waiting for a reboot after updates. My installation was pointing to the wrong /lib/modules/<version>, but it worked itself out after a reboot.



        #:/ $ sudo modinfo iptable_nat
        libkmod: ERROR ../libkmod/libkmod.c:557 kmod_search_moddep: could not open moddep file '/lib/modules/4.1.18+/modules.dep.bin'
        modinfo: ERROR: Module alias iptable_nat not found.





        share|improve this answer















        It may be system changes waiting for a reboot after updates. My installation was pointing to the wrong /lib/modules/<version>, but it worked itself out after a reboot.



        #:/ $ sudo modinfo iptable_nat
        libkmod: ERROR ../libkmod/libkmod.c:557 kmod_search_moddep: could not open moddep file '/lib/modules/4.1.18+/modules.dep.bin'
        modinfo: ERROR: Module alias iptable_nat not found.






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jun 4 '16 at 20:41

























        answered Mar 18 '16 at 3:30









        sshowsshow

        19114




        19114













        • I also has this issue: sudo modinfo iptable_nat libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/4.2.0-25-generic/modules.dep.bin' modinfo: ERROR: Module alias iptable_nat not found.

          – kwoxer
          Jun 4 '16 at 19:00











        • @kwoxer did you try rebooting?

          – sshow
          Jun 4 '16 at 20:42











        • Was able to solve it already : serverfault.com/questions/780980/…

          – kwoxer
          Jun 5 '16 at 5:13











        • Thankful for this answer. Saved me from reinstalling linux. :)

          – Zig
          Jan 3 '17 at 23:58











        • I am writing ansible role for iptables setup and experiencing the same issue.. after reboot all works... but I need to do it in a programmatic way, so no reboot allowed. Is there any way to make it work without reboot?

          – Drew
          Feb 23 '18 at 6:42



















        • I also has this issue: sudo modinfo iptable_nat libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/4.2.0-25-generic/modules.dep.bin' modinfo: ERROR: Module alias iptable_nat not found.

          – kwoxer
          Jun 4 '16 at 19:00











        • @kwoxer did you try rebooting?

          – sshow
          Jun 4 '16 at 20:42











        • Was able to solve it already : serverfault.com/questions/780980/…

          – kwoxer
          Jun 5 '16 at 5:13











        • Thankful for this answer. Saved me from reinstalling linux. :)

          – Zig
          Jan 3 '17 at 23:58











        • I am writing ansible role for iptables setup and experiencing the same issue.. after reboot all works... but I need to do it in a programmatic way, so no reboot allowed. Is there any way to make it work without reboot?

          – Drew
          Feb 23 '18 at 6:42

















        I also has this issue: sudo modinfo iptable_nat libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/4.2.0-25-generic/modules.dep.bin' modinfo: ERROR: Module alias iptable_nat not found.

        – kwoxer
        Jun 4 '16 at 19:00





        I also has this issue: sudo modinfo iptable_nat libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/4.2.0-25-generic/modules.dep.bin' modinfo: ERROR: Module alias iptable_nat not found.

        – kwoxer
        Jun 4 '16 at 19:00













        @kwoxer did you try rebooting?

        – sshow
        Jun 4 '16 at 20:42





        @kwoxer did you try rebooting?

        – sshow
        Jun 4 '16 at 20:42













        Was able to solve it already : serverfault.com/questions/780980/…

        – kwoxer
        Jun 5 '16 at 5:13





        Was able to solve it already : serverfault.com/questions/780980/…

        – kwoxer
        Jun 5 '16 at 5:13













        Thankful for this answer. Saved me from reinstalling linux. :)

        – Zig
        Jan 3 '17 at 23:58





        Thankful for this answer. Saved me from reinstalling linux. :)

        – Zig
        Jan 3 '17 at 23:58













        I am writing ansible role for iptables setup and experiencing the same issue.. after reboot all works... but I need to do it in a programmatic way, so no reboot allowed. Is there any way to make it work without reboot?

        – Drew
        Feb 23 '18 at 6:42





        I am writing ansible role for iptables setup and experiencing the same issue.. after reboot all works... but I need to do it in a programmatic way, so no reboot allowed. Is there any way to make it work without reboot?

        – Drew
        Feb 23 '18 at 6:42











        4















        # apt-get install --reinstall linux-image-`uname -r`


        This will do the trick unless you want to upgrade your kernel.






        share|improve this answer
























        • Same answer as Kim Stacks's earlier one.

          – Karl Richter
          Jul 26 '17 at 0:21
















        4















        # apt-get install --reinstall linux-image-`uname -r`


        This will do the trick unless you want to upgrade your kernel.






        share|improve this answer
























        • Same answer as Kim Stacks's earlier one.

          – Karl Richter
          Jul 26 '17 at 0:21














        4












        4








        4








        # apt-get install --reinstall linux-image-`uname -r`


        This will do the trick unless you want to upgrade your kernel.






        share|improve this answer














        # apt-get install --reinstall linux-image-`uname -r`


        This will do the trick unless you want to upgrade your kernel.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 17 '16 at 8:04









        Aanokpe RaiAanokpe Rai

        916




        916













        • Same answer as Kim Stacks's earlier one.

          – Karl Richter
          Jul 26 '17 at 0:21



















        • Same answer as Kim Stacks's earlier one.

          – Karl Richter
          Jul 26 '17 at 0:21

















        Same answer as Kim Stacks's earlier one.

        – Karl Richter
        Jul 26 '17 at 0:21





        Same answer as Kim Stacks's earlier one.

        – Karl Richter
        Jul 26 '17 at 0:21











        0














        Oddly, I'm experiencing this issue if I specify an ExecStart stanze in a systemd unit containing two commands connected with &&, e.g.



        ExecStart=/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data


        This might be incorrect, but then systemd would still need to fail with a helpful error message - like any program ever existing.



        The command chain can be expressed with bash -c, e.g.



        ExecStart=/bin/bash -c '/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data'


        (mind the simple quotes '' instead of double quotes "").






        share|improve this answer




























          0














          Oddly, I'm experiencing this issue if I specify an ExecStart stanze in a systemd unit containing two commands connected with &&, e.g.



          ExecStart=/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data


          This might be incorrect, but then systemd would still need to fail with a helpful error message - like any program ever existing.



          The command chain can be expressed with bash -c, e.g.



          ExecStart=/bin/bash -c '/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data'


          (mind the simple quotes '' instead of double quotes "").






          share|improve this answer


























            0












            0








            0







            Oddly, I'm experiencing this issue if I specify an ExecStart stanze in a systemd unit containing two commands connected with &&, e.g.



            ExecStart=/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data


            This might be incorrect, but then systemd would still need to fail with a helpful error message - like any program ever existing.



            The command chain can be expressed with bash -c, e.g.



            ExecStart=/bin/bash -c '/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data'


            (mind the simple quotes '' instead of double quotes "").






            share|improve this answer













            Oddly, I'm experiencing this issue if I specify an ExecStart stanze in a systemd unit containing two commands connected with &&, e.g.



            ExecStart=/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data


            This might be incorrect, but then systemd would still need to fail with a helpful error message - like any program ever existing.



            The command chain can be expressed with bash -c, e.g.



            ExecStart=/bin/bash -c '/sbin/modprobe zfs && /usr/local/sbin/zpool import -d /dev data'


            (mind the simple quotes '' instead of double quotes "").







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jul 26 '17 at 0:26









            Karl RichterKarl Richter

            2,49483569




            2,49483569























                0














                Ok. I couldn’t believe it but I got the same error and after much troubleshooting, I’ve discovered that the /boot was NOT mounted during this kernel module rebuild.



                Once mounted, the problem went away for me.



                Turns out that I was a good “victim” of a good security practice (as outlined by CISecurity).






                share|improve this answer




























                  0














                  Ok. I couldn’t believe it but I got the same error and after much troubleshooting, I’ve discovered that the /boot was NOT mounted during this kernel module rebuild.



                  Once mounted, the problem went away for me.



                  Turns out that I was a good “victim” of a good security practice (as outlined by CISecurity).






                  share|improve this answer


























                    0












                    0








                    0







                    Ok. I couldn’t believe it but I got the same error and after much troubleshooting, I’ve discovered that the /boot was NOT mounted during this kernel module rebuild.



                    Once mounted, the problem went away for me.



                    Turns out that I was a good “victim” of a good security practice (as outlined by CISecurity).






                    share|improve this answer













                    Ok. I couldn’t believe it but I got the same error and after much troubleshooting, I’ve discovered that the /boot was NOT mounted during this kernel module rebuild.



                    Once mounted, the problem went away for me.



                    Turns out that I was a good “victim” of a good security practice (as outlined by CISecurity).







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Feb 28 at 12:40









                    Egbert SEgbert S

                    1284




                    1284























                        -1














                        If you can't access the network you can do



                        dpkg-reconfigure linux-image-$(uname -r)


                        It worked for me






                        share|improve this answer






























                          -1














                          If you can't access the network you can do



                          dpkg-reconfigure linux-image-$(uname -r)


                          It worked for me






                          share|improve this answer




























                            -1












                            -1








                            -1







                            If you can't access the network you can do



                            dpkg-reconfigure linux-image-$(uname -r)


                            It worked for me






                            share|improve this answer















                            If you can't access the network you can do



                            dpkg-reconfigure linux-image-$(uname -r)


                            It worked for me







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Mar 15 '17 at 6:24









                            Zanna

                            51.2k13139242




                            51.2k13139242










                            answered Mar 14 '17 at 19:02









                            AlexAlex

                            1




                            1






























                                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%2f459296%2fcould-not-open-moddep-file-lib-modules-3-xx-generic-modules-dep-bin-when-mo%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

                                flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                                Mangá

                                 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕