Bug 798765 - CryptoError: luks_format failed for '/dev/sda3'
Summary: CryptoError: luks_format failed for '/dev/sda3'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f4710dfea46cfbdcc671dd036bf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 19:44 UTC by Paul Alesius
Modified: 2013-07-31 23:53 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-31 23:53:23 UTC
Type: ---


Attachments (Terms of Use)
File: anaconda-tb-EyCsVe (360.58 KB, text/plain)
2012-02-29 19:44 UTC, Paul Alesius
no flags Details

Description Paul Alesius 2012-02-29 19:44:34 UTC
libreport version: 2.0.8
cmdline:        /usr/bin/python  /sbin/anaconda --graphical --selinux --lang sv_SE.UTF-8 --keymap sv-latin1
executable:     /sbin/anaconda
exnFileName:    /tmp/anaconda-tb-EyCsVe
hashmarkername: anaconda
kernel:         3.3.0-0.rc3.git7.2.fc17.x86_64
other involved packages: 
product:        Fedora
reason:         CryptoError: luks_format failed for '/dev/sda3'
release:        Cannot get release name.
time:           ons 29 feb 2012 22:30:08
version:        17-Alpha

anaconda-tb-EyCsVe: Text file, 369229 bytes

description:
:The following was filed automatically by anaconda:
:anaconda 17.11 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/crypto.py", line 100, in luks_format
:    raise CryptoError("luks_format failed for '%s'" % device)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/luks.py", line 207, in create
:    key_size=self.key_size)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 433, in execute
:    options=self.device.formatArgs)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 319, in processActions
:    action.execute(intf=self.intf)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 375, in doIt
:    self.devicetree.processActions()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 122, in turnOnFilesystems
:    anaconda.storage.doIt()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 383, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 247, in go_forward
:    self.dispatch()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1200, in nextClicked
:    self.anaconda.dispatch.go_forward()
:CryptoError: luks_format failed for '/dev/sda3'

environ:
:LC_NUMERIC=C
:live_dir=/boot/livecd/LiveOS/
:LANGKEY=sv
:LVM_SUPPRESS_FD_WARNINGS=1
:GCONF_GLOBAL_LOCKS=1
:PATH=/tmp/product:/tmp/updates:/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin:/sbin:/usr/sbin
:PIXMAPPATH=/tmp/updates/pixmaps/:/tmp/updates/:/tmp/product/pixmaps/:/tmp/product/:pixmaps/:/usr/share/anaconda/pixmaps/:/usr/share/pixmaps/:/usr/share/anaconda/:/usr/share/python-meh/:/usr/share/icons/Fedora/48x48/apps/
:HOME=/tmp
:DISPLAY=:1
:LANG=sv_SE.UTF-8
:TERM=linux
:TZ=Europe/Stockholm
:XAUTHORITY=/root/.Xauthority
:GLADEPATH=/tmp/updates/:/tmp/updates/data/ui/:ui/:/usr/share/anaconda/ui/:/usr/share/python-meh/
:SHLVL=0
:LIBUSER_CONF=/tmp/libuser.U_gU9T
:LD_LIBRARY_PATH=/tmp/product:/tmp/updates
:GNOME_DISABLE_CRASH_DIALOG=1
:PYTHONPATH=/tmp/product:/tmp/updates:/tmp/updates
:LINGUAS=Swedish
:BOOT_IMAGE=/boot/livecd/isolinux/vmlinuz
:LC_COLLATE=C
:PWD=/
:MALLOC_PERTURB_=MALLOC_PERTURB_=60
:MALLOC_CHECK_=2

Comment 1 Paul Alesius 2012-02-29 19:44:38 UTC
Created attachment 566626 [details]
File: anaconda-tb-EyCsVe

Comment 2 Jesse Keating 2012-07-18 23:30:21 UTC
I don't see anything interesting in the logs.  Are you able to duplicate the problem with F17 final?

Comment 3 Christian Jann 2012-08-02 11:35:56 UTC
Hi,

I'm able to triple the problem with F17 final, this has happened on two of my systems which I reinstalled from F15 and F16 today and yesterday.

This happens when I skip entering the old luks passwords when anaconda asks for them.

I'm using a custom partition layout without lvm and some existing partitions which I don't modify.

I wanted to reformat some old luks partitions (/,/home, swap) and encrypt them again without using the same password and anaconda crashed when formating the first luks partition.

At what height is someone officially considered KDE Partition Manager or GParted is not necessary on Fedora live CDs, so I had to search for another distribution to manually format my disks to ext4 so that anaconda can encrypt them again.

--
chris

Comment 4 Jesse Keating 2012-08-02 20:26:08 UTC
(In reply to comment #3)
> Hi,
> 
> I'm able to triple the problem with F17 final, this has happened on two of
> my systems which I reinstalled from F15 and F16 today and yesterday.
> 
> This happens when I skip entering the old luks passwords when anaconda asks
> for them.
> 
> I'm using a custom partition layout without lvm and some existing partitions
> which I don't modify.
> 
> I wanted to reformat some old luks partitions (/,/home, swap) and encrypt
> them again without using the same password and anaconda crashed when
> formating the first luks partition.

Thanks for the reproduction steps, that will help.

> 
> At what height is someone officially considered KDE Partition Manager or
> GParted is not necessary on Fedora live CDs, so I had to search for another
> distribution to manually format my disks to ext4 so that anaconda can
> encrypt them again.

Not all that concerned, given you can install additional software into our live environment.  If you need something not on the live media, just fire up the software installer (PackageKit) or use yum from the command line.

Comment 5 collura 2012-08-21 23:00:34 UTC
eek, reproduced comment#3

( *eyeroll*, ironically only because the preupgrade failed  
and i got tired of messing with it lol :') )

Comment 6 Fedora End Of Life 2013-07-03 22:11:33 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2013-07-31 23:53:28 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.