MD raid device (big) problem

[Olivier Cortes]

Jeff Bailey a écrit :
>>i will boot on the hoary live, chroot, dist-upgrade and try to rebuild 
>>the initrd and reboot.
>>
>>do you have any more advice ? I can't get to find the "definitive" 
>>information in the bugtraker on how to solve the problem...
> 
> 
> The problem is that initrd-tools doesn't have information on a running
> system to figure out how the raid array should be put together (which
> devices, which drivers).
> 
>>From the rescue CD, if you use mdadm to load the raid, chroot to it and
> rebuild the initrd, it should be fine.

I'm afraid it isn't...
When I booted Hoary RC live CD, the raid was automatically detected.
i chrooted in the /dev/md0 mounted in /raid, mounted /proc, mounted 
/dev/ -o bind (from outside the chroot).

i mkinitrd'ed 2.6.10-5-686, umounted, rebooted, and the same error showed.

   Post-Hoary I plan to make it
> possible to override the raid generation bits (so that you can forcable
> tell it which drivers, etc.).  Note that you will need to make sure that
> the 'evms' package is updated to 2.5.1-1ubuntu4.

it is. i updated and apt-get install evms, it installed exactly the 
version 2.5.1-1ubuntu4.

> Can you please note in the bug report
> https://bugzilla.ubuntu.com/show_bug.cgi?id=5421
> if this solves your problem?  The fix worked on all my test systems, but
> it's nice to be sure.

perhaps i missed something, or there is a problem with the 686 version 
of the kernel ?

Olivier