Backtrace attached. The exception happened during the formatting of the discs. This is an Intel Entry Server board S875WP1-E with an on-board Promise RAID controller. I have 2 SATA discs attached to the Promise controller as a RAID 1 array. Two additional discs are connected to the PATA ports. The PATA discs were configured as a software RAID 1 on top of which I asked the installer to create a logical volume using LVM. The partition on the PATA discs was mounted as /home. The system boots from the RAID 1 configured on the SATA discs on the Promise controller. The exception occurred during the initial install of FC7. Installing just on the SATA discs disconnecting the two additional PATA discs works fine. Experimenting with disc configuration leads me to believe that the problem has something to do with the mix of devices and the way they are configured (software RAID 1 with LVM) on the PATA discs.
Created attachment 156033 [details] Python backtrace captured to floppy
There are lots of errors like the following in your exception information. This could be due to a problem with a driver, hardware, cabling, etc. Reassigning to kernel for now. <5>SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB) <5>sdc: Write Protect is off <7>sdc: Mode Sense: 00 3a 00 00 <5>SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA <5>SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB) <5>sdc: Write Protect is off <7>sdc: Mode Sense: 00 3a 00 00
Hello Martin, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem has gone away then please close this bug or I'll do so in a few days if there is no additional information lodged. Cheers Chris
As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug.