This should be fixed in the precise release:
* Cryptsetup now properly checks if underlying device is in use and
disallows *luksFormat*, *luksOpen* and *create* commands on open
(e.g. already mapped or mounted) device.
Feel free to reopen the bug if this is still giving issues on Precise.
**
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888782
Title:
cryptsetup -c aes-xts-plain -s 512 luksFormat not working in Xubuntu
11.10
To manage notifications about this bug go to:
** Description changed:
Running cryptsetup -c aes-xts-plain -s 512 luksFormat /dev/sdb1 on an
external USB Storage (tried with HDD and USB Stick) in Xubuntu 11.10
(did not try out Ubuntu or Kubuntu) gives the following error
(encryption with aes is definitly working, whole system is
** Description changed:
- Running cryptsetup -c aes-xts-plain -s 512 luksFormat /dev/sdb1 on an
+ Running cryptsetup -c aes-xts-plain -s 512 luksFormat /dev/sdd1 on an
external USB Storage (tried with HDD and USB Stick) in Xubuntu 11.10
(did not try out Ubuntu or Kubuntu) gives the following
when playing around to get behind this error i found out what is causing
this:
If the partition that cryptsetup is trying to encrypt is currently mounted the
above error gets produced, if its not mounted it works.
The side-effect when doing this over a mounted partition is that the partition
