Bug 798360 - Exception: device-mapper: resume ioctl failed: Invalid argument
Exception: device-mapper: resume ioctl failed: Invalid argument
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-02-28 13:04 EST by Gary Stainburn
Modified: 2013-02-13 03:46 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 03:46:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: anaconda-tb-ZhWufv (144.49 KB, text/plain)
2012-02-28 13:04 EST, Gary Stainburn
no flags Details

  None (edit)
Description Gary Stainburn 2012-02-28 13:04:13 EST
libreport version: 2.0.6
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-7.fc16.x86_64
product:        Fedora
reason:         Exception: device-mapper: resume ioctl failed: Invalid argument
time:           Tue Feb 28 18:04:00 2012
version:        16

anaconda-tb-ZhWufv: Text file, 147957 bytes

:The following was filed automatically by anaconda:
:anaconda 16.25 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/block/__init__.py", line 33, in dm_log
:    raise Exception, message
:  File "/usr/lib64/python2.7/site-packages/block/device.py", line 710, in get_map
:    self._RaidSet__map = _dm.map(name=self.name, table=self.rs.dmTable)
:  File "/usr/lib64/python2.7/site-packages/block/device.py", line 828, in activate
:    self.map.dev.mknod(self.prefix+self.name)
:  File "/usr/lib64/python2.7/site-packages/block/device.py", line 820, in activate
:    member.activate(degradedOk=degradedOk, mknod=mknod, mkparts=False)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1509, in handleUdevDMRaidMemberFormat
:    rs.activate(mknod=True)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1636, in handleUdevDeviceFormat
:    self.handleUdevDMRaidMemberFormat(info, device)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1054, in addUdevDevice
:    self.handleUdevDeviceFormat(info, device)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1866, in _populate
:    self.addUdevDevice(dev)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1823, in populate
:    self._populate(progressWindow)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 476, in reset
:    cleanupOnly=cleanupOnly)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 117, in storageInitialize
:    storage.reset()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward
:    self.dispatch()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked
:    self.anaconda.dispatch.go_forward()
:Exception: device-mapper: resume ioctl failed: Invalid argument
Comment 1 Gary Stainburn 2012-02-28 13:04:22 EST
Created attachment 566367 [details]
File: anaconda-tb-ZhWufv
Comment 2 Gary Stainburn 2012-02-28 13:10:28 EST
The hardware setup consists of a StarTech PCISATA4R1 card with 4x500GB drives configured as RAID10.
Anaconda sees it and shows it as an option to install onto but then crashes when I choose next.

screen shots are available at

Comment 3 Jesse Keating 2012-07-18 19:39:18 EDT
Does this hardware work with F17?
Comment 4 Fedora End Of Life 2013-01-16 05:13:32 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
Comment 5 Fedora End Of Life 2013-02-13 03:46:48 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.