Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

During an upgrade from Fedora 15 to 17, I installed into an existing LUKS encrypted partition. I'm sure I borked the boot loader options, because the new system boots to GRUB. When I attempt to fix the problems from the boot cd and run cryptsetup luksOpen /dev/sda3 cryptLVM, I get that error.

I read about header problems and the cryptsetup man page lists a "metadata repair" option for "benign" problems. I don't know what the trouble is and looking for the simplest answer. And yeah, I backed up (^_^)

share|improve this question
Actaully its a seven year old laptop! woot! It takes me a year to fix an installation on the desktop every time I upgrade. Last time I skipped and went from Fedora 11 to 15 when fedora forums started ragging on me for EOL. Im seriously thinking of CentOS and a 10 year support so I don't have to do this every 6 mo. – xtian Jun 15 '12 at 0:08
Its like this. Linux just wants to, beggs, and cajoles the user to do more then they are capable of doing. LUKS is a whole new thing for me. I gripe, but I do enjoy Linux, only installation is not my favorite... – xtian Jun 15 '12 at 0:12
It's a lot better than it was 10 or 15 years ago. – LawrenceC Jun 15 '12 at 1:47

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.