https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c66 --- Comment #66 from pgnet _ <pgnet.trash@gmail.com> 2009-02-26 10:27:14 MST --- re: the fail to assemble the raid array @ bott without prior edit/add of mdadm.conf, @ http://www.mail-archive.com/linux-raid@vger.kernel.org/msg10641.html "If you have your disk/controller and md drivers built into the kernel, AND marked the partitions as "linux raid autodetect", kernel may assemble them right at boot. But I don't remember if the kernel will even consider v.1 superblocks for its auto- assembly. In any way, don't rely on the kernel to do this work, in-kernel assembly code is very simplistic and works up to a moment when anything changes/breaks. It's almost the same code as was in old raidtools..." per above, i _have_ marked those partitions (/dev/sd{a,b}{1,2}) as "linux raid autodetect", w/ cfdisk. the comments above seem to imply that under 'sufficient' conditions, the kernel may (can? will?) assemble the array correctly at boot. and, it seems that's _without_ prior manual edit of mdadm.conf. if that's true (is it?), then the question is why, with the debug kernel in-place, are those arrays NOT getting assembled without the mdadm.conf manual edit? is the info above wrong, are mdadm or kernel assembly not working in-general, or is it something in the debug kernel's implementation? thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.