Bug 877645

Summary: CryptoError: luks_open failed for /dev/sda3 (luks-19d8c6e9-bd27-4e23-9e6c-2dd362643bee) with errno -1
Product: [Fedora] Fedora Reporter: arv <antony.vennard+rhbug>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8d5cd17040edf17afe4ff9becd449be06a96b024fb9d86e7e4a7dfcc5e08be02
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-21 10:52:28 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-4n1h9C none

Description arv 2012-11-17 15:46:52 UTC
libreport version: 2.0.10
cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/loop3 --lang en_US.UTF-8
executable:     /sbin/anaconda
exnFileName:    /tmp/anaconda-tb-4n1h9C
hashmarkername: anaconda
kernel:         3.3.4-5.fc17.x86_64
other involved packages: 
product:        Fedora
release:        Fedora release 17 (Beefy Miracle)
time:           Sat 17 Nov 2012 03:45:29 PM GMT
version:        17

anaconda-tb-4n1h9C: Text file, 790875 bytes

description:
:The following was filed automatically by anaconda:
:anaconda 17.29 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/crypto.py", line 116, in luks_open
:    raise CryptoError("luks_open failed for %s (%s) with errno %d" % (device, name, rc))
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/luks.py", line 174, in setup
:    key_file=self._key_file)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 850, in setupParents
:    _format.setup()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 780, in _preCreate
:    self.setupParents()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 789, in create
:    self._preCreate()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 241, in execute
:    self.device.create(intf=intf)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 320, 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 1201, in nextClicked
:    self.anaconda.dispatch.go_forward()
:CryptoError: luks_open failed for /dev/sda3 (luks-19d8c6e9-bd27-4e23-9e6c-2dd362643bee) with errno -1

environ:
:LC_NUMERIC=C
:LIBUSER_CONF=/tmp/libuser.VY8vJn
:LVM_SUPPRESS_FD_WARNINGS=1
:LOGNAME=root
:USER=root
:GCONF_GLOBAL_LOCKS=1
:PATH=/sbin:/usr/sbin:/usr/sbin:/usr/bin:/sbin:/bin:/root/bin:/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=:0
:ANACONDA_PRODUCTNAME=Fedora
:LANG=en_US.UTF-8
:TERM=dumb
:SHELL=/bin/bash
:TZ=Europe/London
:XAUTHORITY=/root/.xauth8O08S5
:GLADEPATH=/tmp/updates/:/tmp/updates/data/ui/:ui/:/usr/share/anaconda/ui/:/usr/share/python-meh/
:SHLVL=1
:GNOME_DISABLE_CRASH_DIALOG=1
:ANACONDA_PRODUCTVERSION=17
:ANACONDA_BUGURL=https://bugzilla.redhat.com/bugzilla/
:USERHELPER_UID=1000
:ANACONDA_ISFINAL=true
:_=/sbin/anaconda
:PWD=/home/liveuser
:DESKTOP_STARTUP_ID=userhelper/Starting Install to Hard Drive/1662-0-localhost.localdomain_TIME0

Comment 1 arv 2012-11-17 15:47:16 UTC
Created attachment 646834 [details]
File: anaconda-tb-4n1h9C

Comment 2 arv 2012-11-17 15:52:10 UTC
Additional information for this bugreport:

Installing via EFI booted live CD or DVD produces this error. Installing to Samsung SSD 830 Series, blank disk, initialized GPT. An existing Marvell "fake" raid with encrypted LUKS is present at time of install. So that the UIDs make sense:

ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx. 1 root root 10 Nov 17 15:41 02B2-88C5 -> ../../sda1
lrwxrwxrwx. 1 root root 10 Nov 17 15:41 19d8c6e9-bd27-4e23-9e6c-2dd362643bee -> ../../sda3
lrwxrwxrwx. 1 root root 10 Nov 17 15:41 25a0f699-0241-40e7-b0ea-b74785cf87bb -> ../../dm-2
lrwxrwxrwx. 1 root root 10 Nov 17 15:39 acc84e47-e326-409d-9e78-5d5a1498d0eb -> ../../sdb1
lrwxrwxrwx. 1 root root 10 Nov 17 15:40 b39d6418-8f98-4350-a48a-e70b0dd203f9 -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Nov 17 15:41 c7594194-4c10-459b-9d6a-c82f9172173a -> ../../sda4
lrwxrwxrwx. 1 root root 10 Nov 17 15:41 d7dd1773-fdcc-4bcf-8ad2-ee42fe91b869 -> ../../sda2

Comment 3 Chris Lumens 2012-11-19 14:54:26 UTC
Is this reproducible with F18?

Comment 4 arv 2012-11-21 10:52:28 UTC
I may have reported this too hastily.

Some experimental results:

 * Same issue with F18 and F16.
 * Does not matter if I use LVM or not.
 * Plugging this disk into another booting F17 install reports ata17: COMRESET errors on a frequent basis.
 * Plugging a different disk into the same SATA port works.

I believe, therefore, that something is wrong with this disk. I'm going to close this so as to not waste your time investigating what I now believe is a hardware issue - and I'll re-open if the manufacturer reports that the disk is fine (smartctl reports no issues, but I'm not convinced I believe that).