removing redudant kernal libraries after kernal reinstallation












0














I'm learning to administer a VPS which has an openVZ kernel (= go easy...). I thought I'd attempt to load a missing kernal module by reinstalling my kernel with:



sudo apt-get install -y linux-image-$(uname -r)


Not only did that fail to get the module I needed, my disk usage doubled. My VPS host admin loaded the module in the host kernel which solved that issue. But now I have 8+GB of redundant OS libraries for Ubuntu 18.04. How can i remove these redundant libraries? apt auto-remove didn't help.



Besides starting from scratch, would appreciate suggestions how one can reclaim the 8+GB of SSD space I carelessly lost!










share|improve this question













migrated from serverfault.com 2 days ago


This question came from our site for system and network administrators.




















    0














    I'm learning to administer a VPS which has an openVZ kernel (= go easy...). I thought I'd attempt to load a missing kernal module by reinstalling my kernel with:



    sudo apt-get install -y linux-image-$(uname -r)


    Not only did that fail to get the module I needed, my disk usage doubled. My VPS host admin loaded the module in the host kernel which solved that issue. But now I have 8+GB of redundant OS libraries for Ubuntu 18.04. How can i remove these redundant libraries? apt auto-remove didn't help.



    Besides starting from scratch, would appreciate suggestions how one can reclaim the 8+GB of SSD space I carelessly lost!










    share|improve this question













    migrated from serverfault.com 2 days ago


    This question came from our site for system and network administrators.


















      0












      0








      0







      I'm learning to administer a VPS which has an openVZ kernel (= go easy...). I thought I'd attempt to load a missing kernal module by reinstalling my kernel with:



      sudo apt-get install -y linux-image-$(uname -r)


      Not only did that fail to get the module I needed, my disk usage doubled. My VPS host admin loaded the module in the host kernel which solved that issue. But now I have 8+GB of redundant OS libraries for Ubuntu 18.04. How can i remove these redundant libraries? apt auto-remove didn't help.



      Besides starting from scratch, would appreciate suggestions how one can reclaim the 8+GB of SSD space I carelessly lost!










      share|improve this question













      I'm learning to administer a VPS which has an openVZ kernel (= go easy...). I thought I'd attempt to load a missing kernal module by reinstalling my kernel with:



      sudo apt-get install -y linux-image-$(uname -r)


      Not only did that fail to get the module I needed, my disk usage doubled. My VPS host admin loaded the module in the host kernel which solved that issue. But now I have 8+GB of redundant OS libraries for Ubuntu 18.04. How can i remove these redundant libraries? apt auto-remove didn't help.



      Besides starting from scratch, would appreciate suggestions how one can reclaim the 8+GB of SSD space I carelessly lost!







      ubuntu vps openvz linux-kernel






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 30 '18 at 22:53







      kbrand











      migrated from serverfault.com 2 days ago


      This question came from our site for system and network administrators.






      migrated from serverfault.com 2 days ago


      This question came from our site for system and network administrators.
























          1 Answer
          1






          active

          oldest

          votes


















          2














          You should be able to just uninstall the package, but before you do, please read the rest of the answer.



          If the command you provided in your question ran without an error message, you didn't reinstall your actual kernel but installed another one (that isn't used now).

          If you just run apt-get install on an already installed package you get the following output:



          linux-image-4.4.0-137-generic is already the newest version (4.4.0-137.163)


          and apt-get does nothing. Since it installed something on your server, it must be a package that wasn't installed before.



          So, to make absolutely sure you are not uninstalling your current kernel, run the following:



          $ dpkg -S /boot/vmlinuz-`uname -r`
          linux-image-4.4.0-137-generic: /boot/vmlinuz-4.4.0-137-generic


          This let's dpkg search for the package that contains the currently running kernel (based on the filename in /boot).



          In my case the package name is linux-image-4.4.0-137-generic, for your virtual server it most probably will be different.



          If this package name differs from the package you installed earlier, you can safely uninstall the unwanted package.



          sudo apt-get remove linux-image-$(uname -r)


          running sudo apt-get autoremove afterwards should take care of all dependencies.






          share|improve this answer





















            Your Answer








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

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

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


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492851%2fremoving-redudant-kernal-libraries-after-kernal-reinstallation%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown
























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            You should be able to just uninstall the package, but before you do, please read the rest of the answer.



            If the command you provided in your question ran without an error message, you didn't reinstall your actual kernel but installed another one (that isn't used now).

            If you just run apt-get install on an already installed package you get the following output:



            linux-image-4.4.0-137-generic is already the newest version (4.4.0-137.163)


            and apt-get does nothing. Since it installed something on your server, it must be a package that wasn't installed before.



            So, to make absolutely sure you are not uninstalling your current kernel, run the following:



            $ dpkg -S /boot/vmlinuz-`uname -r`
            linux-image-4.4.0-137-generic: /boot/vmlinuz-4.4.0-137-generic


            This let's dpkg search for the package that contains the currently running kernel (based on the filename in /boot).



            In my case the package name is linux-image-4.4.0-137-generic, for your virtual server it most probably will be different.



            If this package name differs from the package you installed earlier, you can safely uninstall the unwanted package.



            sudo apt-get remove linux-image-$(uname -r)


            running sudo apt-get autoremove afterwards should take care of all dependencies.






            share|improve this answer


























              2














              You should be able to just uninstall the package, but before you do, please read the rest of the answer.



              If the command you provided in your question ran without an error message, you didn't reinstall your actual kernel but installed another one (that isn't used now).

              If you just run apt-get install on an already installed package you get the following output:



              linux-image-4.4.0-137-generic is already the newest version (4.4.0-137.163)


              and apt-get does nothing. Since it installed something on your server, it must be a package that wasn't installed before.



              So, to make absolutely sure you are not uninstalling your current kernel, run the following:



              $ dpkg -S /boot/vmlinuz-`uname -r`
              linux-image-4.4.0-137-generic: /boot/vmlinuz-4.4.0-137-generic


              This let's dpkg search for the package that contains the currently running kernel (based on the filename in /boot).



              In my case the package name is linux-image-4.4.0-137-generic, for your virtual server it most probably will be different.



              If this package name differs from the package you installed earlier, you can safely uninstall the unwanted package.



              sudo apt-get remove linux-image-$(uname -r)


              running sudo apt-get autoremove afterwards should take care of all dependencies.






              share|improve this answer
























                2












                2








                2






                You should be able to just uninstall the package, but before you do, please read the rest of the answer.



                If the command you provided in your question ran without an error message, you didn't reinstall your actual kernel but installed another one (that isn't used now).

                If you just run apt-get install on an already installed package you get the following output:



                linux-image-4.4.0-137-generic is already the newest version (4.4.0-137.163)


                and apt-get does nothing. Since it installed something on your server, it must be a package that wasn't installed before.



                So, to make absolutely sure you are not uninstalling your current kernel, run the following:



                $ dpkg -S /boot/vmlinuz-`uname -r`
                linux-image-4.4.0-137-generic: /boot/vmlinuz-4.4.0-137-generic


                This let's dpkg search for the package that contains the currently running kernel (based on the filename in /boot).



                In my case the package name is linux-image-4.4.0-137-generic, for your virtual server it most probably will be different.



                If this package name differs from the package you installed earlier, you can safely uninstall the unwanted package.



                sudo apt-get remove linux-image-$(uname -r)


                running sudo apt-get autoremove afterwards should take care of all dependencies.






                share|improve this answer












                You should be able to just uninstall the package, but before you do, please read the rest of the answer.



                If the command you provided in your question ran without an error message, you didn't reinstall your actual kernel but installed another one (that isn't used now).

                If you just run apt-get install on an already installed package you get the following output:



                linux-image-4.4.0-137-generic is already the newest version (4.4.0-137.163)


                and apt-get does nothing. Since it installed something on your server, it must be a package that wasn't installed before.



                So, to make absolutely sure you are not uninstalling your current kernel, run the following:



                $ dpkg -S /boot/vmlinuz-`uname -r`
                linux-image-4.4.0-137-generic: /boot/vmlinuz-4.4.0-137-generic


                This let's dpkg search for the package that contains the currently running kernel (based on the filename in /boot).



                In my case the package name is linux-image-4.4.0-137-generic, for your virtual server it most probably will be different.



                If this package name differs from the package you installed earlier, you can safely uninstall the unwanted package.



                sudo apt-get remove linux-image-$(uname -r)


                running sudo apt-get autoremove afterwards should take care of all dependencies.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 2 days ago









                Gerald SchneiderGerald Schneider

                373314




                373314






























                    draft saved

                    draft discarded




















































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


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

                    But avoid



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

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


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





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


                    Please pay close attention to the following guidance:


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

                    But avoid



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

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


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




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492851%2fremoving-redudant-kernal-libraries-after-kernal-reinstallation%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

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

                    is 'sed' thread safe

                    How to make a Squid Proxy server?