| Summary: | Exception: device-mapper: reload ioctl failed: Invalid argument | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Henry Danis <henry> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | agk, anaconda-maint-list, daniel, gansalmon, g.kaviyarasu, heinzm, itamar, jbrassow, jonathan, kernel-maint, madhu.chinakonda, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:54d40645d6cbce757c5dc626f21a7bb10f943ba740606bec926c3c20be980c25 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-02-13 08:46:04 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Henry Danis
2012-02-04 19:08:28 UTC
Created attachment 559423 [details]
File: anaconda-tb-cFNYQA
Can you describe how you hit this? I see this in the log: 13:52:46,808 WARNING kernel:[ 18.599900] composite sync not supported 13:52:46,981 WARNING kernel:[ 18.772667] composite sync not supported 13:52:49,349 WARNING kernel:[ 21.140188] composite sync not supported 13:52:56,885 ERR kernel:[ 28.676332] device-mapper: table: 253:1: raid45: unknown target type 13:52:56,885 WARNING kernel:[ 28.676337] device-mapper: ioctl: error adding target to table I had a USB 2.0 to Dual SATA JBOD External Hard Drive Enclosure attached to the system. The disks where setup as a software mirrored RAID using the Disk Utility in another Fedora system (I believe 15). At one point I attached it to this system and left it there. When I went to install a new operating system (Fedora 16) on this system it would crash when loading the partitioning tool in Anaconda. I removed the external enclosure and I was able to install the system normally. See comment 2 and 3 for the only details of what exactly failed and the hardware involved. I believe this was encountered when I tried to install Fedora 16 over a Fedora 10 (or 14) image that had RAID 1 for the Boot and Root / partitions. While I know this isn't supported in Fedora 16, it was supported or at least allowed in previous releases. To get around this, I had to use a Fedora 10 DVD and do a partial install and wipe the disk formatting to remove RAID for core partitions. RAID 5 seems okay for /home. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. dm "raid45" is not upstream, but is present in some versions of RHEL for use by the "dmraid" package. It won't be going upstream or into Fedora. (We're using a dm wrapper around md instead.) 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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. |