Description of problem: Version-Release number of selected component: anaconda-20.25.6-1 The following was filed automatically by anaconda: anaconda 20.25.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicelibs/crypto.py", line 124, in luks_close raise CryptoError("luks_close failed for %s" % name) File "/usr/lib/python2.7/site-packages/blivet/formats/luks.py", line 183, in teardown crypto.luks_close(self.mapName) File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 743, in _preTeardown self.originalFormat.teardown() File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 758, in teardown if not self._preTeardown(recursive=recursive): File "/usr/lib64/python2.7/site-packages/pyanaconda/rescue.py", line 251, in _unlock_devices device.teardown(recursive=True) File "/usr/lib64/python2.7/site-packages/pyanaconda/rescue.py", line 311, in doRescue _unlock_devices(intf, sto) File "/sbin/anaconda", line 1036, in <module> rescue.doRescue(anaconda.intf, anaconda.rescue_mount, ksdata) CryptoError: luks_close failed for luks-f0625123-6cf8-47a3-8223-1566d56504f8 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Beta\x20x86_64 rescue quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.6-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20-Beta
Created attachment 841437 [details] File: anaconda-tb
Created attachment 841438 [details] File: anaconda.log
Created attachment 841439 [details] File: environ
Created attachment 841440 [details] File: lsblk_output
Created attachment 841441 [details] File: nmcli_dev_list
Created attachment 841442 [details] File: os_info
Created attachment 841443 [details] File: program.log
Created attachment 841444 [details] File: storage.log
Created attachment 841445 [details] File: syslog
Created attachment 841446 [details] File: packaging.log
*** Bug 1113646 has been marked as a duplicate of this bug. ***
Is this still reproducible in Fedora 21? Can you provide steps to reproduce the problem? The cryptsetup deactivate call is returning EBUSY. Could anything else be using the partitions you are configuring?
(In reply to David Shea from comment #12) > Is this still reproducible in Fedora 21? Can you provide steps to reproduce > the problem? > > The cryptsetup deactivate call is returning EBUSY. Could anything else be > using the partitions you are configuring? I lost track of it. My disk was corrupted, and I lost everything. I stopped using Luks. My conclusion was that you guys need to push the user hard (almost enforce) to keep a backup of the headers and metadata. It was too easy for me, the innocent user not to backup it, and I lost all my data. Sorry, I cannot be of help. Ronen.