How to fix a not booting ubuntu setup with encrypted root disk?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












Ubuntu is not booting but printing weird things, either



  • /run/lvm/lvmetad.socket: connect failed: No such file or directory

  • or /sbin/cryptsetup not found

then falls back to busybox after a few minutes (sometimes..).



The error appeared after moving onto a new hard disk where I had to delete an encrypted partition. After chrooting into the root partition and running udpate-initramfs -u the error mentioned here popped up:



cryptsetup: WARNING: could not determine root device from /etc/fstab



My setup: I followed the setup proposed here. Now I have a / btrfs volume inside LUKS with an unencrypted /boot partition. All this running on EFI with secure boot disabled.










share|improve this question

























    up vote
    0
    down vote

    favorite












    Ubuntu is not booting but printing weird things, either



    • /run/lvm/lvmetad.socket: connect failed: No such file or directory

    • or /sbin/cryptsetup not found

    then falls back to busybox after a few minutes (sometimes..).



    The error appeared after moving onto a new hard disk where I had to delete an encrypted partition. After chrooting into the root partition and running udpate-initramfs -u the error mentioned here popped up:



    cryptsetup: WARNING: could not determine root device from /etc/fstab



    My setup: I followed the setup proposed here. Now I have a / btrfs volume inside LUKS with an unencrypted /boot partition. All this running on EFI with secure boot disabled.










    share|improve this question























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Ubuntu is not booting but printing weird things, either



      • /run/lvm/lvmetad.socket: connect failed: No such file or directory

      • or /sbin/cryptsetup not found

      then falls back to busybox after a few minutes (sometimes..).



      The error appeared after moving onto a new hard disk where I had to delete an encrypted partition. After chrooting into the root partition and running udpate-initramfs -u the error mentioned here popped up:



      cryptsetup: WARNING: could not determine root device from /etc/fstab



      My setup: I followed the setup proposed here. Now I have a / btrfs volume inside LUKS with an unencrypted /boot partition. All this running on EFI with secure boot disabled.










      share|improve this question













      Ubuntu is not booting but printing weird things, either



      • /run/lvm/lvmetad.socket: connect failed: No such file or directory

      • or /sbin/cryptsetup not found

      then falls back to busybox after a few minutes (sometimes..).



      The error appeared after moving onto a new hard disk where I had to delete an encrypted partition. After chrooting into the root partition and running udpate-initramfs -u the error mentioned here popped up:



      cryptsetup: WARNING: could not determine root device from /etc/fstab



      My setup: I followed the setup proposed here. Now I have a / btrfs volume inside LUKS with an unencrypted /boot partition. All this running on EFI with secure boot disabled.







      boot luks btrfs cryptsetup






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 25 at 15:43









      matt3o

      143110




      143110




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          All the default hacks and fixes are putting you on a good track, however none of them was complete. This was the solution in my case:



          1. Make sure the /etc/crypttab file is set up correctly. All entries have to refer to existing partitions. There should be
            at least one entry named "root", this is the root / entry. This was
            crucial for me - and nobody mentioned it so far!

          2. This entry should be referred to in the /etc/fstab with /dev/mapper/root. Check
            that the UUIDs are correctly set up

          3. Now run update-initramfs -u
            which udpates only your most recent kernel. If a cryptsetup warning
            pops up, you failed on the previous steps. Review all files and try
            figure out the problem

          4. Run update-grub to fix any remaining grub issues

          5. Now check the /boot/grub/grub.cfg. Go search for the first menuentry which is the one that will be booted.
            The search
            part should contain the UUID of the boot partition (unencrypted!).
            The linux part should have something saying that
            root=/dev/mapper/root or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume)

          6. Try to boot. If the lvm errors still pop up, silence them as mentioned in this answer

          One last advice: Care for any little warning popping up. Usually they are meaningless, in this case they are very important.



          Good luck!






          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',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            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%2f1009646%2fhow-to-fix-a-not-booting-ubuntu-setup-with-encrypted-root-disk%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote



            accepted










            All the default hacks and fixes are putting you on a good track, however none of them was complete. This was the solution in my case:



            1. Make sure the /etc/crypttab file is set up correctly. All entries have to refer to existing partitions. There should be
              at least one entry named "root", this is the root / entry. This was
              crucial for me - and nobody mentioned it so far!

            2. This entry should be referred to in the /etc/fstab with /dev/mapper/root. Check
              that the UUIDs are correctly set up

            3. Now run update-initramfs -u
              which udpates only your most recent kernel. If a cryptsetup warning
              pops up, you failed on the previous steps. Review all files and try
              figure out the problem

            4. Run update-grub to fix any remaining grub issues

            5. Now check the /boot/grub/grub.cfg. Go search for the first menuentry which is the one that will be booted.
              The search
              part should contain the UUID of the boot partition (unencrypted!).
              The linux part should have something saying that
              root=/dev/mapper/root or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume)

            6. Try to boot. If the lvm errors still pop up, silence them as mentioned in this answer

            One last advice: Care for any little warning popping up. Usually they are meaningless, in this case they are very important.



            Good luck!






            share|improve this answer
























              up vote
              0
              down vote



              accepted










              All the default hacks and fixes are putting you on a good track, however none of them was complete. This was the solution in my case:



              1. Make sure the /etc/crypttab file is set up correctly. All entries have to refer to existing partitions. There should be
                at least one entry named "root", this is the root / entry. This was
                crucial for me - and nobody mentioned it so far!

              2. This entry should be referred to in the /etc/fstab with /dev/mapper/root. Check
                that the UUIDs are correctly set up

              3. Now run update-initramfs -u
                which udpates only your most recent kernel. If a cryptsetup warning
                pops up, you failed on the previous steps. Review all files and try
                figure out the problem

              4. Run update-grub to fix any remaining grub issues

              5. Now check the /boot/grub/grub.cfg. Go search for the first menuentry which is the one that will be booted.
                The search
                part should contain the UUID of the boot partition (unencrypted!).
                The linux part should have something saying that
                root=/dev/mapper/root or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume)

              6. Try to boot. If the lvm errors still pop up, silence them as mentioned in this answer

              One last advice: Care for any little warning popping up. Usually they are meaningless, in this case they are very important.



              Good luck!






              share|improve this answer






















                up vote
                0
                down vote



                accepted







                up vote
                0
                down vote



                accepted






                All the default hacks and fixes are putting you on a good track, however none of them was complete. This was the solution in my case:



                1. Make sure the /etc/crypttab file is set up correctly. All entries have to refer to existing partitions. There should be
                  at least one entry named "root", this is the root / entry. This was
                  crucial for me - and nobody mentioned it so far!

                2. This entry should be referred to in the /etc/fstab with /dev/mapper/root. Check
                  that the UUIDs are correctly set up

                3. Now run update-initramfs -u
                  which udpates only your most recent kernel. If a cryptsetup warning
                  pops up, you failed on the previous steps. Review all files and try
                  figure out the problem

                4. Run update-grub to fix any remaining grub issues

                5. Now check the /boot/grub/grub.cfg. Go search for the first menuentry which is the one that will be booted.
                  The search
                  part should contain the UUID of the boot partition (unencrypted!).
                  The linux part should have something saying that
                  root=/dev/mapper/root or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume)

                6. Try to boot. If the lvm errors still pop up, silence them as mentioned in this answer

                One last advice: Care for any little warning popping up. Usually they are meaningless, in this case they are very important.



                Good luck!






                share|improve this answer












                All the default hacks and fixes are putting you on a good track, however none of them was complete. This was the solution in my case:



                1. Make sure the /etc/crypttab file is set up correctly. All entries have to refer to existing partitions. There should be
                  at least one entry named "root", this is the root / entry. This was
                  crucial for me - and nobody mentioned it so far!

                2. This entry should be referred to in the /etc/fstab with /dev/mapper/root. Check
                  that the UUIDs are correctly set up

                3. Now run update-initramfs -u
                  which udpates only your most recent kernel. If a cryptsetup warning
                  pops up, you failed on the previous steps. Review all files and try
                  figure out the problem

                4. Run update-grub to fix any remaining grub issues

                5. Now check the /boot/grub/grub.cfg. Go search for the first menuentry which is the one that will be booted.
                  The search
                  part should contain the UUID of the boot partition (unencrypted!).
                  The linux part should have something saying that
                  root=/dev/mapper/root or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume)

                6. Try to boot. If the lvm errors still pop up, silence them as mentioned in this answer

                One last advice: Care for any little warning popping up. Usually they are meaningless, in this case they are very important.



                Good luck!







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 25 at 15:43









                matt3o

                143110




                143110



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009646%2fhow-to-fix-a-not-booting-ubuntu-setup-with-encrypted-root-disk%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491