Recover LUKS encrypted system after removing a seperate encrypted volume?
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
I had a full LUKS encrypted Debian install on a TB drive, and a encrypted volume on a 488GB drive. The 488GB drive was its own encrypted volume mounted at /home/user/projects Originally, when I booted up, it asked for two paraphrases, and I unlocked both to boot the system.
Recently, I needed to remove the 488GB drive, so I copied everything off of the 488Gb drive, and removed it.
Now the system enters in Emergency mode when giving the paraphrase for the encrypted main Disk. It does however seem to accept the paraphrase and load up the graphic drivers and other services, but ends up putting me in emergency mode ( which is really doesn't because it tells me my root account is locked, im assuming because I have the a root account disabled and I use 'sudo -i' )
Does anyone know what's going on here? How can I get my filesystem back? I assume it must be recoverable.
encryption luks disk-encryption
add a comment |
up vote
-1
down vote
favorite
I had a full LUKS encrypted Debian install on a TB drive, and a encrypted volume on a 488GB drive. The 488GB drive was its own encrypted volume mounted at /home/user/projects Originally, when I booted up, it asked for two paraphrases, and I unlocked both to boot the system.
Recently, I needed to remove the 488GB drive, so I copied everything off of the 488Gb drive, and removed it.
Now the system enters in Emergency mode when giving the paraphrase for the encrypted main Disk. It does however seem to accept the paraphrase and load up the graphic drivers and other services, but ends up putting me in emergency mode ( which is really doesn't because it tells me my root account is locked, im assuming because I have the a root account disabled and I use 'sudo -i' )
Does anyone know what's going on here? How can I get my filesystem back? I assume it must be recoverable.
encryption luks disk-encryption
2
Sounds like you need a LiveCD / rescue system and go from there. It may be as simple as removing any reference to the missing drive from /etc/fstab, crypttab, chroot and update the initramfs.
– frostschutz
Nov 30 at 8:31
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I had a full LUKS encrypted Debian install on a TB drive, and a encrypted volume on a 488GB drive. The 488GB drive was its own encrypted volume mounted at /home/user/projects Originally, when I booted up, it asked for two paraphrases, and I unlocked both to boot the system.
Recently, I needed to remove the 488GB drive, so I copied everything off of the 488Gb drive, and removed it.
Now the system enters in Emergency mode when giving the paraphrase for the encrypted main Disk. It does however seem to accept the paraphrase and load up the graphic drivers and other services, but ends up putting me in emergency mode ( which is really doesn't because it tells me my root account is locked, im assuming because I have the a root account disabled and I use 'sudo -i' )
Does anyone know what's going on here? How can I get my filesystem back? I assume it must be recoverable.
encryption luks disk-encryption
I had a full LUKS encrypted Debian install on a TB drive, and a encrypted volume on a 488GB drive. The 488GB drive was its own encrypted volume mounted at /home/user/projects Originally, when I booted up, it asked for two paraphrases, and I unlocked both to boot the system.
Recently, I needed to remove the 488GB drive, so I copied everything off of the 488Gb drive, and removed it.
Now the system enters in Emergency mode when giving the paraphrase for the encrypted main Disk. It does however seem to accept the paraphrase and load up the graphic drivers and other services, but ends up putting me in emergency mode ( which is really doesn't because it tells me my root account is locked, im assuming because I have the a root account disabled and I use 'sudo -i' )
Does anyone know what's going on here? How can I get my filesystem back? I assume it must be recoverable.
encryption luks disk-encryption
encryption luks disk-encryption
asked Nov 30 at 8:05
TrevorKS
1318
1318
2
Sounds like you need a LiveCD / rescue system and go from there. It may be as simple as removing any reference to the missing drive from /etc/fstab, crypttab, chroot and update the initramfs.
– frostschutz
Nov 30 at 8:31
add a comment |
2
Sounds like you need a LiveCD / rescue system and go from there. It may be as simple as removing any reference to the missing drive from /etc/fstab, crypttab, chroot and update the initramfs.
– frostschutz
Nov 30 at 8:31
2
2
Sounds like you need a LiveCD / rescue system and go from there. It may be as simple as removing any reference to the missing drive from /etc/fstab, crypttab, chroot and update the initramfs.
– frostschutz
Nov 30 at 8:31
Sounds like you need a LiveCD / rescue system and go from there. It may be as simple as removing any reference to the missing drive from /etc/fstab, crypttab, chroot and update the initramfs.
– frostschutz
Nov 30 at 8:31
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485088%2frecover-luks-encrypted-system-after-removing-a-seperate-encrypted-volume%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
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
2
Sounds like you need a LiveCD / rescue system and go from there. It may be as simple as removing any reference to the missing drive from /etc/fstab, crypttab, chroot and update the initramfs.
– frostschutz
Nov 30 at 8:31