Ubuntu Server 18.04 LVM out of space with improper default partitioning












1















I installed Ubuntu Server 18.04 with the LVM option and left the default partition setup. Now my main drive only has 4GB in a 1TB hard drive. How can I fix this without starting from scratch?



Results of df -h :



df -h (image snapshot)










share|improve this question





























    1















    I installed Ubuntu Server 18.04 with the LVM option and left the default partition setup. Now my main drive only has 4GB in a 1TB hard drive. How can I fix this without starting from scratch?



    Results of df -h :



    df -h (image snapshot)










    share|improve this question



























      1












      1








      1








      I installed Ubuntu Server 18.04 with the LVM option and left the default partition setup. Now my main drive only has 4GB in a 1TB hard drive. How can I fix this without starting from scratch?



      Results of df -h :



      df -h (image snapshot)










      share|improve this question
















      I installed Ubuntu Server 18.04 with the LVM option and left the default partition setup. Now my main drive only has 4GB in a 1TB hard drive. How can I fix this without starting from scratch?



      Results of df -h :



      df -h (image snapshot)







      partitioning 18.04 lvm






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 5 at 2:26







      GEC

















      asked Jan 4 at 3:22









      GECGEC

      112




      112






















          3 Answers
          3






          active

          oldest

          votes


















          0














          Consider installing KVPM to get yourself a GUI and a better understanding on your situation/layout. Within the program you can do a lot of very powerful things.






          share|improve this answer
























          • Thank you. I get the following error when running kvpm: qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.

            – GEC
            Jan 5 at 0:31













          • this may help.

            – MeSo2
            Jan 5 at 0:38











          • I am not using ipython, I have a monitor connected to the server and was looking at it when I got the error.

            – GEC
            Jan 5 at 0:49













          • I dont have a GUI installed, does KVPM need me to install one or does it have one itself?

            – GEC
            Jan 5 at 1:05











          • GUI (Graphic User Interface) is what KVPM provides. I suggest to boot from a USB sick that has Ubuntu on it and install KVPM onto the stick, and run it from the stick. It may help you get a better understanding what is going on with your hard drive. Did you do an Update or a fresh install?

            – MeSo2
            Jan 5 at 1:47





















          0














          It appears that you need to extend your Logical Volume.



          It can be a bit tricky but if you understand that there are 3 parts, it'll be much easier.




          • Physical Volume (PV) => The physical space on a drive.


          • Volume Group (VG) => An abstracted amount of drive space that can be split between multiple drives/devices.


          • Logical Volume (LV) => The space that ubuntu "sees"



          You'll need to extend your VG all the way across your 1TB Drive (or extend however much you want), then extend the Logical Volume group to take up that space.



          Technet has a nice writeup that (if you follow carefully) you'll be able to follow and extend your drive.






          share|improve this answer































            0














            Had the exact same problem with a fresh install of Ubuntu Server 18.04.1.



            What I had to do was:



            # We need to resize the logical volume to use all the available space of the volume group
            $ lvm
            lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
            lvm> exit

            # And then, we need to resize the file system to use the new available space in the logical volume
            $ resize2fs /dev/ubuntu-vg/ubuntu-lv
            resize2fs 1.44.1 (24-Mar-2018)
            Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
            old_desc_blocks = 1, new_desc_blocks = 58
            The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 120784896 (4k) blocks long.

            # Finally, you can check that you now have available space:
            $ df -h
            Filesystem Size Used Avail Use% Mounted on
            udev 3.9G 0 3.9G 0% /dev
            tmpfs 786M 1.2M 785M 1% /run
            /dev/mapper/ubuntu--vg-ubuntu--lv 454G 3.8G 432G 1% /


            If you didn't customize the LVM settings, the names for the volume group and logical volume should be the same as mine (ubuntu-vg and ubuntu-lv respectively).



            If your partition is completely full, you could get a no space left error when trying to resize the logical volume like:



            lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
            /etc/lvm/archive/.lvm_computer: write error failed: No space left on device


            The easier way to fix this is by removing apt cache (it will get regenerated next time you do apt update), which should give you more than enough space to complete the operation:



            $ rm -rf /var/cache/apt/*




            share























              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%2f1106795%2fubuntu-server-18-04-lvm-out-of-space-with-improper-default-partitioning%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              Consider installing KVPM to get yourself a GUI and a better understanding on your situation/layout. Within the program you can do a lot of very powerful things.






              share|improve this answer
























              • Thank you. I get the following error when running kvpm: qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.

                – GEC
                Jan 5 at 0:31













              • this may help.

                – MeSo2
                Jan 5 at 0:38











              • I am not using ipython, I have a monitor connected to the server and was looking at it when I got the error.

                – GEC
                Jan 5 at 0:49













              • I dont have a GUI installed, does KVPM need me to install one or does it have one itself?

                – GEC
                Jan 5 at 1:05











              • GUI (Graphic User Interface) is what KVPM provides. I suggest to boot from a USB sick that has Ubuntu on it and install KVPM onto the stick, and run it from the stick. It may help you get a better understanding what is going on with your hard drive. Did you do an Update or a fresh install?

                – MeSo2
                Jan 5 at 1:47


















              0














              Consider installing KVPM to get yourself a GUI and a better understanding on your situation/layout. Within the program you can do a lot of very powerful things.






              share|improve this answer
























              • Thank you. I get the following error when running kvpm: qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.

                – GEC
                Jan 5 at 0:31













              • this may help.

                – MeSo2
                Jan 5 at 0:38











              • I am not using ipython, I have a monitor connected to the server and was looking at it when I got the error.

                – GEC
                Jan 5 at 0:49













              • I dont have a GUI installed, does KVPM need me to install one or does it have one itself?

                – GEC
                Jan 5 at 1:05











              • GUI (Graphic User Interface) is what KVPM provides. I suggest to boot from a USB sick that has Ubuntu on it and install KVPM onto the stick, and run it from the stick. It may help you get a better understanding what is going on with your hard drive. Did you do an Update or a fresh install?

                – MeSo2
                Jan 5 at 1:47
















              0












              0








              0







              Consider installing KVPM to get yourself a GUI and a better understanding on your situation/layout. Within the program you can do a lot of very powerful things.






              share|improve this answer













              Consider installing KVPM to get yourself a GUI and a better understanding on your situation/layout. Within the program you can do a lot of very powerful things.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jan 4 at 5:29









              MeSo2MeSo2

              68113




              68113













              • Thank you. I get the following error when running kvpm: qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.

                – GEC
                Jan 5 at 0:31













              • this may help.

                – MeSo2
                Jan 5 at 0:38











              • I am not using ipython, I have a monitor connected to the server and was looking at it when I got the error.

                – GEC
                Jan 5 at 0:49













              • I dont have a GUI installed, does KVPM need me to install one or does it have one itself?

                – GEC
                Jan 5 at 1:05











              • GUI (Graphic User Interface) is what KVPM provides. I suggest to boot from a USB sick that has Ubuntu on it and install KVPM onto the stick, and run it from the stick. It may help you get a better understanding what is going on with your hard drive. Did you do an Update or a fresh install?

                – MeSo2
                Jan 5 at 1:47





















              • Thank you. I get the following error when running kvpm: qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.

                – GEC
                Jan 5 at 0:31













              • this may help.

                – MeSo2
                Jan 5 at 0:38











              • I am not using ipython, I have a monitor connected to the server and was looking at it when I got the error.

                – GEC
                Jan 5 at 0:49













              • I dont have a GUI installed, does KVPM need me to install one or does it have one itself?

                – GEC
                Jan 5 at 1:05











              • GUI (Graphic User Interface) is what KVPM provides. I suggest to boot from a USB sick that has Ubuntu on it and install KVPM onto the stick, and run it from the stick. It may help you get a better understanding what is going on with your hard drive. Did you do an Update or a fresh install?

                – MeSo2
                Jan 5 at 1:47



















              Thank you. I get the following error when running kvpm: qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.

              – GEC
              Jan 5 at 0:31







              Thank you. I get the following error when running kvpm: qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.

              – GEC
              Jan 5 at 0:31















              this may help.

              – MeSo2
              Jan 5 at 0:38





              this may help.

              – MeSo2
              Jan 5 at 0:38













              I am not using ipython, I have a monitor connected to the server and was looking at it when I got the error.

              – GEC
              Jan 5 at 0:49







              I am not using ipython, I have a monitor connected to the server and was looking at it when I got the error.

              – GEC
              Jan 5 at 0:49















              I dont have a GUI installed, does KVPM need me to install one or does it have one itself?

              – GEC
              Jan 5 at 1:05





              I dont have a GUI installed, does KVPM need me to install one or does it have one itself?

              – GEC
              Jan 5 at 1:05













              GUI (Graphic User Interface) is what KVPM provides. I suggest to boot from a USB sick that has Ubuntu on it and install KVPM onto the stick, and run it from the stick. It may help you get a better understanding what is going on with your hard drive. Did you do an Update or a fresh install?

              – MeSo2
              Jan 5 at 1:47







              GUI (Graphic User Interface) is what KVPM provides. I suggest to boot from a USB sick that has Ubuntu on it and install KVPM onto the stick, and run it from the stick. It may help you get a better understanding what is going on with your hard drive. Did you do an Update or a fresh install?

              – MeSo2
              Jan 5 at 1:47















              0














              It appears that you need to extend your Logical Volume.



              It can be a bit tricky but if you understand that there are 3 parts, it'll be much easier.




              • Physical Volume (PV) => The physical space on a drive.


              • Volume Group (VG) => An abstracted amount of drive space that can be split between multiple drives/devices.


              • Logical Volume (LV) => The space that ubuntu "sees"



              You'll need to extend your VG all the way across your 1TB Drive (or extend however much you want), then extend the Logical Volume group to take up that space.



              Technet has a nice writeup that (if you follow carefully) you'll be able to follow and extend your drive.






              share|improve this answer




























                0














                It appears that you need to extend your Logical Volume.



                It can be a bit tricky but if you understand that there are 3 parts, it'll be much easier.




                • Physical Volume (PV) => The physical space on a drive.


                • Volume Group (VG) => An abstracted amount of drive space that can be split between multiple drives/devices.


                • Logical Volume (LV) => The space that ubuntu "sees"



                You'll need to extend your VG all the way across your 1TB Drive (or extend however much you want), then extend the Logical Volume group to take up that space.



                Technet has a nice writeup that (if you follow carefully) you'll be able to follow and extend your drive.






                share|improve this answer


























                  0












                  0








                  0







                  It appears that you need to extend your Logical Volume.



                  It can be a bit tricky but if you understand that there are 3 parts, it'll be much easier.




                  • Physical Volume (PV) => The physical space on a drive.


                  • Volume Group (VG) => An abstracted amount of drive space that can be split between multiple drives/devices.


                  • Logical Volume (LV) => The space that ubuntu "sees"



                  You'll need to extend your VG all the way across your 1TB Drive (or extend however much you want), then extend the Logical Volume group to take up that space.



                  Technet has a nice writeup that (if you follow carefully) you'll be able to follow and extend your drive.






                  share|improve this answer













                  It appears that you need to extend your Logical Volume.



                  It can be a bit tricky but if you understand that there are 3 parts, it'll be much easier.




                  • Physical Volume (PV) => The physical space on a drive.


                  • Volume Group (VG) => An abstracted amount of drive space that can be split between multiple drives/devices.


                  • Logical Volume (LV) => The space that ubuntu "sees"



                  You'll need to extend your VG all the way across your 1TB Drive (or extend however much you want), then extend the Logical Volume group to take up that space.



                  Technet has a nice writeup that (if you follow carefully) you'll be able to follow and extend your drive.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 5 at 2:47









                  AndyAndy

                  1011




                  1011























                      0














                      Had the exact same problem with a fresh install of Ubuntu Server 18.04.1.



                      What I had to do was:



                      # We need to resize the logical volume to use all the available space of the volume group
                      $ lvm
                      lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                      lvm> exit

                      # And then, we need to resize the file system to use the new available space in the logical volume
                      $ resize2fs /dev/ubuntu-vg/ubuntu-lv
                      resize2fs 1.44.1 (24-Mar-2018)
                      Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
                      old_desc_blocks = 1, new_desc_blocks = 58
                      The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 120784896 (4k) blocks long.

                      # Finally, you can check that you now have available space:
                      $ df -h
                      Filesystem Size Used Avail Use% Mounted on
                      udev 3.9G 0 3.9G 0% /dev
                      tmpfs 786M 1.2M 785M 1% /run
                      /dev/mapper/ubuntu--vg-ubuntu--lv 454G 3.8G 432G 1% /


                      If you didn't customize the LVM settings, the names for the volume group and logical volume should be the same as mine (ubuntu-vg and ubuntu-lv respectively).



                      If your partition is completely full, you could get a no space left error when trying to resize the logical volume like:



                      lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                      /etc/lvm/archive/.lvm_computer: write error failed: No space left on device


                      The easier way to fix this is by removing apt cache (it will get regenerated next time you do apt update), which should give you more than enough space to complete the operation:



                      $ rm -rf /var/cache/apt/*




                      share




























                        0














                        Had the exact same problem with a fresh install of Ubuntu Server 18.04.1.



                        What I had to do was:



                        # We need to resize the logical volume to use all the available space of the volume group
                        $ lvm
                        lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                        lvm> exit

                        # And then, we need to resize the file system to use the new available space in the logical volume
                        $ resize2fs /dev/ubuntu-vg/ubuntu-lv
                        resize2fs 1.44.1 (24-Mar-2018)
                        Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
                        old_desc_blocks = 1, new_desc_blocks = 58
                        The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 120784896 (4k) blocks long.

                        # Finally, you can check that you now have available space:
                        $ df -h
                        Filesystem Size Used Avail Use% Mounted on
                        udev 3.9G 0 3.9G 0% /dev
                        tmpfs 786M 1.2M 785M 1% /run
                        /dev/mapper/ubuntu--vg-ubuntu--lv 454G 3.8G 432G 1% /


                        If you didn't customize the LVM settings, the names for the volume group and logical volume should be the same as mine (ubuntu-vg and ubuntu-lv respectively).



                        If your partition is completely full, you could get a no space left error when trying to resize the logical volume like:



                        lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                        /etc/lvm/archive/.lvm_computer: write error failed: No space left on device


                        The easier way to fix this is by removing apt cache (it will get regenerated next time you do apt update), which should give you more than enough space to complete the operation:



                        $ rm -rf /var/cache/apt/*




                        share


























                          0












                          0








                          0







                          Had the exact same problem with a fresh install of Ubuntu Server 18.04.1.



                          What I had to do was:



                          # We need to resize the logical volume to use all the available space of the volume group
                          $ lvm
                          lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                          lvm> exit

                          # And then, we need to resize the file system to use the new available space in the logical volume
                          $ resize2fs /dev/ubuntu-vg/ubuntu-lv
                          resize2fs 1.44.1 (24-Mar-2018)
                          Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
                          old_desc_blocks = 1, new_desc_blocks = 58
                          The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 120784896 (4k) blocks long.

                          # Finally, you can check that you now have available space:
                          $ df -h
                          Filesystem Size Used Avail Use% Mounted on
                          udev 3.9G 0 3.9G 0% /dev
                          tmpfs 786M 1.2M 785M 1% /run
                          /dev/mapper/ubuntu--vg-ubuntu--lv 454G 3.8G 432G 1% /


                          If you didn't customize the LVM settings, the names for the volume group and logical volume should be the same as mine (ubuntu-vg and ubuntu-lv respectively).



                          If your partition is completely full, you could get a no space left error when trying to resize the logical volume like:



                          lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                          /etc/lvm/archive/.lvm_computer: write error failed: No space left on device


                          The easier way to fix this is by removing apt cache (it will get regenerated next time you do apt update), which should give you more than enough space to complete the operation:



                          $ rm -rf /var/cache/apt/*




                          share













                          Had the exact same problem with a fresh install of Ubuntu Server 18.04.1.



                          What I had to do was:



                          # We need to resize the logical volume to use all the available space of the volume group
                          $ lvm
                          lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                          lvm> exit

                          # And then, we need to resize the file system to use the new available space in the logical volume
                          $ resize2fs /dev/ubuntu-vg/ubuntu-lv
                          resize2fs 1.44.1 (24-Mar-2018)
                          Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
                          old_desc_blocks = 1, new_desc_blocks = 58
                          The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 120784896 (4k) blocks long.

                          # Finally, you can check that you now have available space:
                          $ df -h
                          Filesystem Size Used Avail Use% Mounted on
                          udev 3.9G 0 3.9G 0% /dev
                          tmpfs 786M 1.2M 785M 1% /run
                          /dev/mapper/ubuntu--vg-ubuntu--lv 454G 3.8G 432G 1% /


                          If you didn't customize the LVM settings, the names for the volume group and logical volume should be the same as mine (ubuntu-vg and ubuntu-lv respectively).



                          If your partition is completely full, you could get a no space left error when trying to resize the logical volume like:



                          lvm> lvextend -l 100%FREE /dev/ubuntu-vg/ubuntu-lv
                          /etc/lvm/archive/.lvm_computer: write error failed: No space left on device


                          The easier way to fix this is by removing apt cache (it will get regenerated next time you do apt update), which should give you more than enough space to complete the operation:



                          $ rm -rf /var/cache/apt/*





                          share











                          share


                          share










                          answered 5 mins ago









                          yorchyorch

                          12615




                          12615






























                              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%2f1106795%2fubuntu-server-18-04-lvm-out-of-space-with-improper-default-partitioning%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