this post was submitted on 05 Jul 2025
17 points (94.7% liked)

Arch Linux

8901 readers
3 users here now

The beloved lightweight distro

founded 5 years ago
MODERATORS
k_o_t@lemmy.ml
17
Unable to Boot into ArchLinux Today (lemmy.ca)
submitted 1 week ago by dudesss@lemmy.ca to c/archlinux@lemmy.ml
11 comments fedilink hide all child comments
 

Today, after decrypting my encrypted drive, the system failed to boot into it.

I forget what the error said. It maybe said that it could not fine new_root or something.

I tried something like the following, by I don't know what it does.

cryptsetup reencrypt --decrypt --header new_file device_path

I'm not sure what it does and what the --header part does. It was taking too long, so interrupted with a reboot. Now its saying their device is not a valid LUKS device.

you are viewing a single comment's thread
view the rest of the comments
[–] HelloRoot@lemy.lol 17 points 1 week ago* (last edited 1 week ago) (2 children)

I think you might have fucked your data.

  1. when you get an error like on your boot, take a screenshot, write it down, search online, ask for help with the exact error online

  2. when you don't know what a command does, don't run it

Afaik the command tried to re-encrypt your drive. If you canceled it, well now you have a drive in some undetermined state and since it was reencrypting it your data is now mumho jumbo.

[–] MentalEdge@sopuli.xyz 6 points 1 week ago* (last edited 1 week ago)

The --decrypt option is used to remove LUKS encryption entirely and turn the partition into a normal storage volume.

Interrupting that process is still likely to have irreparably damaged the volume, making it impossible to recover.

[–] MyNameIsRichard@lemmy.ml 6 points 1 week ago

Still, you've got backups, haven't you?