crytptestup only works within the specified target device, no effect oytside of it. Hence your other partitions will be unaffected, baring some strange set-ups. 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. It may be a good thing to check the partition is not maunted and you could also check ehat kind of header is in it, e.g. with hd or by trying to mount it. 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. Arno On Fri, Jun 15, 2012 at 04:18:18PM +0000, neon_ bikini wrote: > > > > > > > > > > > > > > > > > > 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 and there is no sign of > grub.conf. > > > > > > When I attempt to fix the > problems from the boot cd and run cryptsetup luksOpen /dev/sda3 > cryptLVM, I get ?not a valid LUKS device?. > > > > > Can I simply reformat Luks? What are my concerns right now if I don't need to save data? > > > > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- One of the painful things about our time is that those who feel certainty are stupid, and those with any imagination and understanding are filled with doubt and indecision. -- Bertrand Russell _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
