Why does booting from Debian on usb with lvm fail until usb is plugged out and in again?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Background: I decided to “dual boot†an encrypted Fedora and Debian system.
I installed fedora first on a the usb drive. Created a boot partition (call it sdb1 for reference) and then an encrypted partition (sdb2) (managed through cryptsetup and volume groups), with encrypted root and home and swap. Fedora boots without problem through legacy-grub (non-uefi boot).
I created an extended partition with sdb5 as the boot partition for Debian and sdb6 as the encrypted partition with the same structure as I had for fedora.
During installation Debian was not able to install a kernel (probably because I wrote the install disk to a usb using unetboot). No problem, I chrooted into Debian and installed a kernel: linux-image-rt-amd64. Ran update-initramfs.
Configured grub to treat sdb1 as essentially the primary boot partition, but when I want to boot Debian I just load the Debian grub configuration file (I run configfile (hd0, msdos5)/grub/grub.cfg).
The Debian configuration file loads and then I can “boot†into Debian. By that I mean it runs the initrd I created.
Problem: if I just try to boot Debian, there is two prominent errors that are repeated multiple times. First there is a usb error -71. Then there is multiple errors about lvmetad. If I do not do anything, the system eventually fails to boot and drops to a busy box shell.
However, if I unplug my usb drive after seeing the errors and then plug it back in, I am prompted to enter the password to unlock my encrypted partition and Debian boots normally. I have tried so many things to fix this, but I just cannot figure it out. Is there anything I can do so I do not need to unplug my USB drive?
disk-encryption lvm initrd
asked Jun 14 at 16:02
Viktor
1012
migrated from superuser.com Jun 15 at 17:16
This question came from our site for computer enthusiasts and power users.
add a comment |Â
up vote
0
down vote
favorite
Background: I decided to “dual boot†an encrypted Fedora and Debian system.
I installed fedora first on a the usb drive. Created a boot partition (call it sdb1 for reference) and then an encrypted partition (sdb2) (managed through cryptsetup and volume groups), with encrypted root and home and swap. Fedora boots without problem through legacy-grub (non-uefi boot).
I created an extended partition with sdb5 as the boot partition for Debian and sdb6 as the encrypted partition with the same structure as I had for fedora.
During installation Debian was not able to install a kernel (probably because I wrote the install disk to a usb using unetboot). No problem, I chrooted into Debian and installed a kernel: linux-image-rt-amd64. Ran update-initramfs.
Configured grub to treat sdb1 as essentially the primary boot partition, but when I want to boot Debian I just load the Debian grub configuration file (I run configfile (hd0, msdos5)/grub/grub.cfg).
The Debian configuration file loads and then I can “boot†into Debian. By that I mean it runs the initrd I created.
Problem: if I just try to boot Debian, there is two prominent errors that are repeated multiple times. First there is a usb error -71. Then there is multiple errors about lvmetad. If I do not do anything, the system eventually fails to boot and drops to a busy box shell.
However, if I unplug my usb drive after seeing the errors and then plug it back in, I am prompted to enter the password to unlock my encrypted partition and Debian boots normally. I have tried so many things to fix this, but I just cannot figure it out. Is there anything I can do so I do not need to unplug my USB drive?
disk-encryption lvm initrd
asked Jun 14 at 16:02
Viktor
1012
migrated from superuser.com Jun 15 at 17:16
This question came from our site for computer enthusiasts and power users.
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Background: I decided to “dual boot†an encrypted Fedora and Debian system.
I installed fedora first on a the usb drive. Created a boot partition (call it sdb1 for reference) and then an encrypted partition (sdb2) (managed through cryptsetup and volume groups), with encrypted root and home and swap. Fedora boots without problem through legacy-grub (non-uefi boot).
I created an extended partition with sdb5 as the boot partition for Debian and sdb6 as the encrypted partition with the same structure as I had for fedora.
During installation Debian was not able to install a kernel (probably because I wrote the install disk to a usb using unetboot). No problem, I chrooted into Debian and installed a kernel: linux-image-rt-amd64. Ran update-initramfs.
Configured grub to treat sdb1 as essentially the primary boot partition, but when I want to boot Debian I just load the Debian grub configuration file (I run configfile (hd0, msdos5)/grub/grub.cfg).
The Debian configuration file loads and then I can “boot†into Debian. By that I mean it runs the initrd I created.
Problem: if I just try to boot Debian, there is two prominent errors that are repeated multiple times. First there is a usb error -71. Then there is multiple errors about lvmetad. If I do not do anything, the system eventually fails to boot and drops to a busy box shell.
However, if I unplug my usb drive after seeing the errors and then plug it back in, I am prompted to enter the password to unlock my encrypted partition and Debian boots normally. I have tried so many things to fix this, but I just cannot figure it out. Is there anything I can do so I do not need to unplug my USB drive?
disk-encryption lvm initrd
asked Jun 14 at 16:02
Viktor
1012
Background: I decided to “dual boot†an encrypted Fedora and Debian system.
I installed fedora first on a the usb drive. Created a boot partition (call it sdb1 for reference) and then an encrypted partition (sdb2) (managed through cryptsetup and volume groups), with encrypted root and home and swap. Fedora boots without problem through legacy-grub (non-uefi boot).
I created an extended partition with sdb5 as the boot partition for Debian and sdb6 as the encrypted partition with the same structure as I had for fedora.
During installation Debian was not able to install a kernel (probably because I wrote the install disk to a usb using unetboot). No problem, I chrooted into Debian and installed a kernel: linux-image-rt-amd64. Ran update-initramfs.
Configured grub to treat sdb1 as essentially the primary boot partition, but when I want to boot Debian I just load the Debian grub configuration file (I run configfile (hd0, msdos5)/grub/grub.cfg).
The Debian configuration file loads and then I can “boot†into Debian. By that I mean it runs the initrd I created.
Problem: if I just try to boot Debian, there is two prominent errors that are repeated multiple times. First there is a usb error -71. Then there is multiple errors about lvmetad. If I do not do anything, the system eventually fails to boot and drops to a busy box shell.
However, if I unplug my usb drive after seeing the errors and then plug it back in, I am prompted to enter the password to unlock my encrypted partition and Debian boots normally. I have tried so many things to fix this, but I just cannot figure it out. Is there anything I can do so I do not need to unplug my USB drive?
disk-encryption lvm initrd
asked Jun 14 at 16:02
Viktor
1012
asked Jun 14 at 16:02
Viktor
1012
asked Jun 14 at 16:02
Viktor
1012
asked Jun 14 at 16:02
Viktor
1012
1012
migrated from superuser.com Jun 15 at 17:16
This question came from our site for computer enthusiasts and power users.
migrated from superuser.com Jun 15 at 17:16
This question came from our site for computer enthusiasts and power users.
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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%2funix.stackexchange.com%2fquestions%2f450048%2fwhy-does-booting-from-debian-on-usb-with-lvm-fail-until-usb-is-plugged-out-and-i%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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');
);
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');
);
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