FS#66477 - [cryptsetup][json-c] luksFormat persistent error "Cannot not wipe header on device"
Attached to Project:
Arch Linux
Opened by Stefan Haller (fgrsnau) - Thursday, 30 April 2020, 10:12 GMT
Last edited by Christian Hesse (eworm) - Thursday, 30 April 2020, 13:28 GMT
Opened by Stefan Haller (fgrsnau) - Thursday, 30 April 2020, 10:12 GMT
Last edited by Christian Hesse (eworm) - Thursday, 30 April 2020, 13:28 GMT
|
Details
I am unable to run `cryptsetup luksFormat` on an up-to-date
Arch Linux machine. I tested it on a second machine and also
while running the linux and linux-lts kernels. Opening
existing encrypted devices is working fine for me.
Unfortunately, the --verbose flag is not very helpful in
this case.
Additional info: * cryptsetup 2.3.1-2 Steps to reproduce: 1. touch /tmp/test 2. fallocate -l 500M /tmp/test 3. cryptsetup luksFormat -v /tmp/test 4. Enter "YES" + passphrase "test" twice. Output: # cryptsetup luksFormat -v /tmp/test WARNING! ======== This will overwrite data on /tmp/test irrevocably. Are you sure? (Type 'yes' in capital letters): YES Enter passphrase for /tmp/test: Verify passphrase: Cannot wipe header on device /tmp/test. Command failed with code -1 (wrong or missing parameters). |
This task depends upon
Closed by Christian Hesse (eworm)
Thursday, 30 April 2020, 13:28 GMT
Reason for closing: Fixed
Additional comments about closing: cryptsetup 2.3.1-3
Thursday, 30 April 2020, 13:28 GMT
Reason for closing: Fixed
Additional comments about closing: cryptsetup 2.3.1-3
https://gitlab.com/cryptsetup/cryptsetup/-/issues/556
Can you try this command: cryptsetup --type luks1 luksFormat /tmp/test
If this doesn't get fixed today, tomorrow's ISO will bring a nasty surprise for those wanting to install Arch.