[dm-crypt] What does it mean ?not a valid LUKS device?? Can I start over and not destroy the drive?

Milan Broz gmazyland at gmail.com
Sat Jun 16 10:01:31 CEST 2012


On 06/15/2012 10:59 PM, Arno Wagner wrote:
> If you do not care about the data in the old LUKS container 
> (partition), you can just luksFormat the device. However
> you should be sure /dev/sda3 is not used in any other
> way (something did erase or damage the header after all, may 
> have been a filesystem, raid-superflock or other thing),
> and may damage your new header.

Exactly. Anaconda (the Fedora installer) sometimes wipes
devices during install, I would not be surprised that this can
happen even during upgrade.

(In install, it usually appends device to LVM, so be sure that
this device is really not in use or luksFormat break your system
even more.)

Usually you should do:
1) blkid -p <device> - check what is not on that disk
(partition table added, lvm, mdraid, fs... ?)

2) check if the device is not use - lsblk, pvs, lvs -o+devices ...

I am afraid that if device was wiped, no way to get you data back
(without LUKS header backup).

So, once you are sure, just reformat the drive. Maybe you will have
to setup UUID (check fstab/crypttab) - you can set UUID
on the device itself (see man cryptsetup luksUUID) or just
fix files mentioned above (if they contain UUID reference).

> As to grub.conf, Grub legacy uses menu.lst, and grub 2
> uses grub.cfg, so I am not really sure what you are talking 
> about.

Upgrade F15...F17 seems to switch grub->grub2
(I had to fix 3 borked systems after upgrade already so will not
better comment it anymore:-) Whatever, grub2-mkconfig is very
useful tool...
also see http://fedoraproject.org/wiki/Common_F17_bugs and other
pages, just search Google

Milan


More information about the dm-crypt mailing list