Joachim Otahal wrote:
quoted text
> Michael Evans schrieb:
>> On Sun, Mar 28, 2010 at 7:32 PM, Joachim Otahal<Jou@gmx.net>  wrote:
>>   
>>> Joachim Otahal schrieb:
>>>     
>>>> free says: swap active, mdstat says:
>>>> md2 : active (auto-read-only) raid1 sda2[1] sdb2[0]
>>>>       979840 blocks [2/2] [UU]
>>>>        
>>> minor correction: the output right after creating the raid + issuing a
>>> mkswap is
>>> md2 : active raid1 sda2[1] sdb2[0]
>>>       979840 blocks [2/2] [UU]
>>>       [=======>.............]  resync = 37.9% (372480/979840) 
>>> finish=0.1min
>>> speed=93120K/sec
>>>
>>> and a few second later:
>>> md2 : active raid1 sda2[1] sdb2[0]
>>>       979840 blocks [2/2] [UU]
>>>
>>> mdadm.conf updated, but md2 still not there after reboot.
>>>
>>> Joachim
>>>
>>> -- 
>>> To unsubscribe from this list: send the line "unsubscribe 
>>> linux-raid" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>>      
>> Trigger the regeneration of your initrd/initramfs image.  It's
>> probably got an mdadm.conf that lacks your second device.
>>
>>    
> Strike, thank you.
>
> Joachim Otahal

My thought was that you didn't change the partition type to 
"raid-autostart" so the array got started by the kernel (0.90 meta 
needed). I suspect that would have fixed it as well.

-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html