FC5 weird raid issues

[dragoran]

Jarod Wilson wrote:
> On Sunday 26 March 2006 01:51, dragoran wrote:
>   
>> Gilboa Davara wrote:
>>     
>>> On Fri, 2006-03-24 at 17:53 +0100, dragoran wrote:
>>>       
>>>> I have tryed to upgrade from FC4 -> FC5 using anaconda but it did not
>>>> detect my FC4 installation which is installed on /dev/md0.
>>>> It tryes to add a non raid partition to the array and ignores the raid
>>>> partition. This causes the initalisation of md0 to fail.
>>>> Is this a kernel or anaconda bug?
>>>> Bug report:
>>>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186312
>>>> (no reply ...)
>>>> So I backuped my data dan tryed a reinstall and it detected the md0
>>>> array in diskdruid but showed "foreign" as filesystem..
>>>> did edit and set mount point to / and filesystem ext3
>>>> but it failed formating it with a messages saying that it failed and
>>>> that I should press enter to reboot the system.
>>>> What happend? How could such things happen with a *final* release? Raid
>>>> support seems broken and nobody has noticed.
>>>> I always updated my system from RH9->FC1->FC2->FC3->FC4 (then
>>>> reinstalled FC4 because of i386->x86_64) but it seems that upgrade is no
>>>> more possible to FC5 :(
>>>>         
>>> I'd suggest you switch to console once Anaconda loads and mount the MD0
>>> by hand.
>>> It should give you a way to circumvent the bug.
>>>
>>> Gilboa
>>>       
>> I just deleted the raid and recreated it and now it seems to work fine.
>> (running FC5 with md raid now).
>> But the bug still needs to be fixed.
>> But I don't like to reinstall FC6 when its out upgrade from raid should
>> work as it did before FC5.
>>     
>
> I assure you upgrades from FC4 to FC5 on systems with md software raids were 
> tested and all worked without issue. It isn't that raid support is broken and 
> nobody noticed. Not sure why the failure in your particular case, but I've 
> done several upgrades myself without incident. Without being able to 
> reproduce the problem, fixing whatever went wrong on your system may prove 
> difficult, if not impossible.
>
>   
At least I have provided any possible infos that might help fixing the bug.