Bug 1046436

Summary: CryptoError: luks_close failed for luks-f0625123-6cf8-47a3-8223-1566d56504f8
Product: [Fedora] Fedora Reporter: Ronen Hod <rhod>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, g.kaviyarasu, jonathan, knoel, rhod, sschaefer, vanmeeuwen+fedora, venger.b.love
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a8e9dfb45e567409009b08e5d1196ca02b927a19d6dd093b94d1a60eac0aaf4c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-09 16:11:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: packaging.log none

Description Ronen Hod 2013-12-25 09:46:33 UTC
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

Comment 1 Ronen Hod 2013-12-25 09:46:41 UTC
Created attachment 841437 [details]
File: anaconda-tb

Comment 2 Ronen Hod 2013-12-25 09:46:44 UTC
Created attachment 841438 [details]
File: anaconda.log

Comment 3 Ronen Hod 2013-12-25 09:46:47 UTC
Created attachment 841439 [details]
File: environ

Comment 4 Ronen Hod 2013-12-25 09:46:49 UTC
Created attachment 841440 [details]
File: lsblk_output

Comment 5 Ronen Hod 2013-12-25 09:46:53 UTC
Created attachment 841441 [details]
File: nmcli_dev_list

Comment 6 Ronen Hod 2013-12-25 09:46:56 UTC
Created attachment 841442 [details]
File: os_info

Comment 7 Ronen Hod 2013-12-25 09:46:58 UTC
Created attachment 841443 [details]
File: program.log

Comment 8 Ronen Hod 2013-12-25 09:47:06 UTC
Created attachment 841444 [details]
File: storage.log

Comment 9 Ronen Hod 2013-12-25 09:47:11 UTC
Created attachment 841445 [details]
File: syslog

Comment 10 Ronen Hod 2013-12-25 09:47:13 UTC
Created attachment 841446 [details]
File: packaging.log

Comment 11 David Shea 2014-12-09 15:17:18 UTC
*** Bug 1113646 has been marked as a duplicate of this bug. ***

Comment 12 David Shea 2014-12-09 15:19:02 UTC
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?

Comment 13 Ronen Hod 2014-12-09 16:10:32 UTC
(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.