Install of Hardy Heron Alpha-4 corrupted fakeraid

[Justin]

I installed Hardy Heron Alpha-4 using manual partitioning on an IDE drive attached directly to my GA-P35-DS4 (rev. 2.0) mainboard. Upon reboot, I found that my HighPoint RocketRAID 100 array had been corrupted. The array contained my Windows install which I had hoped to optionally boot. Guess I'll be reinstalling. :-)

The manual partitioning configured four primary partitions: 1) /boot as ext2, 2) / as ext3, 3) swap, and 4) /media/sda4 as fat32.

As a side request, I've seen little to no support for mounting, formating, and using fakeraid partitions in major Linux distributions. I don't think I'd be the only one who would like to use my RAID controller for something like an XFS partition for MythTV or other DVR storage. I've been able to boot from the array, but not use it.

[Danny Wood (danwood76)]

You need to install dmraid and tell it to ignore RAID partitions to install it in a RAID system.

[Justin (justin-redhat-bugs)]

Description of problem:
After booting the Fedora 9 Beta (x86_64) install DVD, selecting English, and
selecting US keyboard, the Anaconda installer fails to recognize my disks and
halts. I have 2 IDE disks attached to my High Point RocketRAID 100 PCI card
in a RAID 0 configuration. I have had mixed luck with other distributions
recognizing the disks whether configured in RAID 0 or not, but none so far has
successfully allowed read and write. Other noteable components include a GA-
P35-DS4 (rev. 2) mainboard, a Q6600 processor, and a DVD burner on the
mainboard's IDE channel.

Version-Release number of selected component (if applicable):
Behavior noticed in Alpha's and Beta of Fedora 9

How reproducible:
Always

Steps to Reproduce:
1. Boot from Fedora 9 Beta (x86_64) install DVD
2. Select English, US keyboard
3. Observe failure when attempting to detect disks

Actual results:
Unable to proceed with installation

Expected results:
1. Successful installation with High Point RocketRAID 100 in system
2. Successful installation onto High Point RocketRAID 100 disk
3. Successful installation onto High Point RocketRAID 100 RAID array

Additional info:

[Justin (justin-e-palmer)]

The problem still exists as my RAID array was again destroyed. I am forced to reconstruct the array in the controller's BIOS after install. Would you be able to tell me how to install dmraid during OS installation? I don't recall seeing a way to do this.

Neither Ubuntu nor Mythbuntu create a correct /boot/grub/menu.lst. I have to replace "hd2" with "hd0". Apparently the disks appear differently to the installer than to a normal boot sequence.

Neither Ubuntu nor Mythbuntu mount the array. Even after installing dmraid on Mythbuntu, I don't see a /dev/mapper directory. I see the devices "hde" and "hdg", but no attempts to mount (e.g. anything in /etc/fstab).

[Gerry (gerry-redhat-bugs)]

I have not been able to successfully load any Fedora distribution since FC6 on
any of my systems that have onboard or card HighPoint controllers. I have about
a dozen systems that have HighPoint controllers and all of them are stuck at FC6.

[Bug (bug-redhat-bugs)]

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Danny Wood (danwood76)]

You have to load the live CD and simply install it through synaptic.
Then discover your RAID with sudo dmraid -ay and your good to go.

[Michael Nagel (nailor)]

thanks for reporting, but is this still up-to-date?

[Justin (justin-e-palmer)]

I believe the same problem occured in the beta release. I don't think I've tried the final release, but there's only so much reinstalling I have time for. My work-around has been to unplug the RAID card during installation.

I may try using dmraid after installation, but others have reported problems after Fedora Core 6 which may be common to all or many Linux distributions.

https://bugzilla.redhat.com/show_bug.cgi?id=439113

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 '9'.

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 9'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 9 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

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

[Gerry (gerry-redhat-bugs)]

Please move this bug to F11. It is still an issue.

[kernel-janitor (kernel-janitor)]

Hi justin-e-palmer,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 188983

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. 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 '11'.

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 11'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 11 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

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

[Bug (bug-redhat-bugs)]

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.