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.

  • MentalEdge@sopuli.xyz
    link
    fedilink
    arrow-up
    9
    ·
    2 days ago

    Interrupting hard drive operations is REALLY dangerous.

    Add to that the sensitivities of encrypted volumes, and I’m 90% sure your data is gone. Hope you had backups.

    You’ll probably have to re-install.