Bug 1267792

Summary: LVMError: Process reported exit code 1280: device-mapper: resume ioctl on failed: Invalid argument Unable to resume fedora-home (253:1)
Product: [Fedora] Fedora Reporter: Ryan <rwk016>
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: 22CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b7ca9c64c189b4d90655edefccbef03c26a891bd69b197dd175a378587c0af20
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-01 13:49:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: anaconda-tb
File: anaconda.log
File: environ
File: journalctl
File: lsblk_output
File: nmcli_dev_list
File: os_info
File: program.log
File: storage.log
File: ifcfg.log none

Description Ryan 2015-10-01 04:02:14 UTC
Description of problem:
During installation anaconda fails with an unknown error.  I suspect its an issue with my SSD.  Can boot into Fedora Live fine but fails before I pick a language.

Version-Release number of selected component:

The following was filed automatically by anaconda:
anaconda 22.20.13-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/gi/overrides/BlockDev.py", line 384, in wrapped
    raise transform[1](msg)
  File "/usr/lib/python2.7/site-packages/blivet/devices/lvm.py", line 628, in _setup
    blockdev.lvm.lvactivate(self.vg.name, self._name)
  File "/usr/lib/python2.7/site-packages/blivet/devices/storage.py", line 430, in setup
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1509, in addLV
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1525, in handleVgLvs
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1589, in handleUdevLVMPVFormat
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1897, in handleUdevDeviceFormat
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1261, in addUdevDevice
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2193, in _populate
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2127, in populate
  File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 277, in reset
  File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1116, in storageInitialize
  File "/usr/lib64/python2.7/threading.py", line 766, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 244, in run
    threading.Thread.run(self, *args, **kwargs)
LVMError: Process reported exit code 1280:   device-mapper: resume ioctl on  failed: Invalid argument
  Unable to resume fedora-home (253:1)

Additional info:
cmdline:        /usr/bin/python2  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-22-3 ro rd.live.image quiet rhgb
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.0.4-301.fc22.x86_64
other involved packages: libblockdev-0.13-2.fc22.x86_64, python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch
product:        Fedora
release:        Fedora release 22 (Twenty Two)
type:           anaconda
version:        22

Comment 1 Ryan 2015-10-01 04:02:20 UTC
Created attachment 1078924 [details]
File: anaconda-tb

Comment 2 Ryan 2015-10-01 04:02:21 UTC
Created attachment 1078925 [details]
File: anaconda.log

Comment 3 Ryan 2015-10-01 04:02:22 UTC
Created attachment 1078926 [details]
File: environ

Comment 4 Ryan 2015-10-01 04:02:26 UTC
Created attachment 1078927 [details]
File: journalctl

Comment 5 Ryan 2015-10-01 04:02:27 UTC
Created attachment 1078928 [details]
File: lsblk_output

Comment 6 Ryan 2015-10-01 04:02:28 UTC
Created attachment 1078929 [details]
File: nmcli_dev_list

Comment 7 Ryan 2015-10-01 04:02:30 UTC
Created attachment 1078930 [details]
File: os_info

Comment 8 Ryan 2015-10-01 04:02:31 UTC
Created attachment 1078931 [details]
File: program.log

Comment 9 Ryan 2015-10-01 04:02:33 UTC
Created attachment 1078932 [details]
File: storage.log

Comment 10 Ryan 2015-10-01 04:02:34 UTC
Created attachment 1078933 [details]
File: ifcfg.log

Comment 11 David Shea 2015-10-01 13:49:36 UTC
The logs you attached are full of storage errors. See all of the lines with "SQUASHFS error: Unable to read page". This could be a kernel bug, but is more likely a hardware problem or corrupt boot media.