How to fix a not booting ubuntu setup with encrypted root disk?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
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 chroot
ing 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
add a comment |Â
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 chroot
ing 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
add a comment |Â
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 chroot
ing 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
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 chroot
ing 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
boot luks btrfs cryptsetup
asked Feb 25 at 15:43
matt3o
143110
143110
add a comment |Â
add a comment |Â
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:
- 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! - This entry should be referred to in the
/etc/fstab
with/dev/mapper/root
. Check
that the UUIDs are correctly set up - 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 - Run
update-grub
to fix any remaining grub issues - Now check the
/boot/grub/grub.cfg
. Go search for the firstmenuentry
which is the one that will be booted.
Thesearch
part should contain the UUID of the boot partition (unencrypted!).
Thelinux
part should have something saying thatroot=/dev/mapper/root
or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume) - 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!
add a comment |Â
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:
- 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! - This entry should be referred to in the
/etc/fstab
with/dev/mapper/root
. Check
that the UUIDs are correctly set up - 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 - Run
update-grub
to fix any remaining grub issues - Now check the
/boot/grub/grub.cfg
. Go search for the firstmenuentry
which is the one that will be booted.
Thesearch
part should contain the UUID of the boot partition (unencrypted!).
Thelinux
part should have something saying thatroot=/dev/mapper/root
or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume) - 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!
add a comment |Â
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:
- 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! - This entry should be referred to in the
/etc/fstab
with/dev/mapper/root
. Check
that the UUIDs are correctly set up - 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 - Run
update-grub
to fix any remaining grub issues - Now check the
/boot/grub/grub.cfg
. Go search for the firstmenuentry
which is the one that will be booted.
Thesearch
part should contain the UUID of the boot partition (unencrypted!).
Thelinux
part should have something saying thatroot=/dev/mapper/root
or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume) - 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!
add a comment |Â
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:
- 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! - This entry should be referred to in the
/etc/fstab
with/dev/mapper/root
. Check
that the UUIDs are correctly set up - 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 - Run
update-grub
to fix any remaining grub issues - Now check the
/boot/grub/grub.cfg
. Go search for the firstmenuentry
which is the one that will be booted.
Thesearch
part should contain the UUID of the boot partition (unencrypted!).
Thelinux
part should have something saying thatroot=/dev/mapper/root
or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume) - 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!
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:
- 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! - This entry should be referred to in the
/etc/fstab
with/dev/mapper/root
. Check
that the UUIDs are correctly set up - 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 - Run
update-grub
to fix any remaining grub issues - Now check the
/boot/grub/grub.cfg
. Go search for the firstmenuentry
which is the one that will be booted.
Thesearch
part should contain the UUID of the boot partition (unencrypted!).
Thelinux
part should have something saying thatroot=/dev/mapper/root
or pointing to the UUID of the unencrypted volume (in my setup the btrfs volume) - 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!
answered Feb 25 at 15:43
matt3o
143110
143110
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password