RetroFed Forum

Welcome to the nostalgia-filled piefed instance of yesteryear.

Open Registration with Application questionnaire.

If you have a question or comment you can post in !meta@retrofed.com or message @DosDude@retrofed.com or @Die4Ever@retrofed.com

In case of downtime and/or emergency, we will post updates on @DosDude@mastodon.social

Some rules we try to uphold:

Be civil. Bigotry is not welcome. This includes (but is not limited to): transphobia, queerphobia, racism, ageism and ableism. We do not promote hate.
Communities need to be Retro or Retro-adjacent.
Please don't upload pornographic content. (use an external image host for that)

dudesss@lemmy.ca Joined: 2025-03-27

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.

Welcome to the nostalgia-filled piefed instance of yesteryear.

Open Registration with Application questionnaire.

If you have a question or comment you can post in !meta@retrofed.com or message @DosDude@retrofed.com or @Die4Ever@retrofed.com

In case of downtime and/or emergency, we will post updates on @DosDude@mastodon.social

Some rules we try to uphold:

Be civil. Bigotry is not welcome. This includes (but is not limited to): transphobia, queerphobia, racism, ageism and ableism. We do not promote hate.
Communities need to be Retro or Retro-adjacent.
Please don't upload pornographic content. (use an external image host for that)