yes, I can do that. But I thought that mdadm should be able to assemble my raid50 without any help from my side. Let me rephrase the question. My raid50 system does not boot because .... - I miss something in mdadm configuration - mdadm cannot assemble (by itself) raid50 arrays (which is hard to believe) - there is a bug somewhere With best wishes, Alexander Zvyagin. On 17 April 2013 21:08, Tommy Apel <tommyapeldk@xxxxxxxxx> wrote: > unpack you initfs and make the changes to the init file and pack it again. > > /Tommy > > > 2013/4/17 Alexander Zvyagin <zvyagin.alexander@xxxxxxxxx> >> >> Hi, >> >> I have almost working RAID50 (two RAID5 forms RAID0) in my >> Linux-mint13. When booting the system always ends up in initramfs >> shell, saying it cannot find the "root". When I type "cat >> /proc/mdstat" I see that both RAID5 are available, but they did not >> form RAID0. So I do "mdadm -A --scan" to finish the raid creation. >> After that I can exit the initramfs shell and system finishes booting >> (and works later) without any problems. Of course initramfs image is >> in sync with root (/etc/mdadm/mdadm.conf file is the same in initramfs >> and rootfs). >> This is what my system is using: >> kernel 3.5.0-26-generic >> mdadm - v3.2.5 - 18th May 2012 >> >> To summarize, I have RAID50 which _almost_ works. It just needs to be >> pushed/kicked during the boot. Could you advise my how can I >> automatize the process, so I do not need to type "mdadm -A >> --scan;exit" every time I switch on my computer? >> >> Thanks a lot in advance, >> Alexander. > > -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
