Bug 744045 - Exception: device-mapper: reload ioctl failed: Argument invalide
Summary: Exception: device-mapper: reload ioctl failed: Argument invalide
Keywords:
Status: CLOSED DUPLICATE of bug 533703
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:82f4a33b05bce8f16...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 20:02 UTC by roms2k
Modified: 2011-10-11 13:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-11 13:30:09 UTC
Type: ---


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (157.75 KB, text/plain)
2011-10-06 20:02 UTC, roms2k
no flags Details

Description roms2k 2011-10-06 20:02:38 UTC
The following was filed automatically by anaconda:
anaconda 15.31 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/pyanaconda/storage/devicetree.py", line 1453, in handleUdevDMRaidMemberFormat
    rs.activate(mknod=True)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1581, in handleUdevDeviceFormat
    self.handleUdevDMRaidMemberFormat(info, device)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1020, in addUdevDevice
    self.handleUdevDeviceFormat(info, device)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1797, in _populate
    self.addUdevDevice(dev)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1755, in populate
    self._populate()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 435, in reset
    self.devicetree.populate()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 116, in storageInitialize
    storage.reset()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext
    self.moveStep()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked
    self.anaconda.dispatch.gotoNext()
Exception: device-mapper: reload ioctl failed: Argument invalide

Comment 1 roms2k 2011-10-06 20:02:44 UTC
Created attachment 526789 [details]
Attached traceback automatically from anaconda.

Comment 2 roms2k 2011-10-06 20:07:25 UTC
This error occured while trying to install Fedora 15 x64 on a raid 5 disc system.

The motherboard is a ASUS P5N-d and the raid bios is a NVIDIA chip.

Comment 3 roms2k 2011-10-06 22:20:42 UTC
The raid is maid of 3 1.5Tb Western Digital.
Windows 7 is already installed on it with the 2Tb limit on NTFS.

The goal of it is to install Fedora on dual boot.

Comment 4 David Lehman 2011-10-06 22:58:19 UTC
The last two lines in your system log indicate that your raid array uses level 45 and that support for that level is absent:

 device-mapper: table: 253:0: raid45: unknown target type
 device-mapper: ioctl: error adding target to table

As an aside, if you want to create filesystems that start at or beyond 2TB I hope you used a GPT disklabel (aka partition table) since older msdos/mbr disklabels do not allow partitions to start beyond 2TB.

I'm inclined to close this bug, but I want to first verify that we do not support nvidia raid45.

Comment 5 Chris Lumens 2011-10-11 13:30:09 UTC
This appears to be the same root cause as bug 533703 (searching for "fedora raid45 nvidia" on google points there, even) but it gives no indication as to whether it was ever fixed or not.  It may be worth prodding the owner of that one on its status.

*** This bug has been marked as a duplicate of bug 533703 ***


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