On 12/01/17 17:24, Andrei Borzenkov wrote:
that mdadm is present in your boot image. If OpenSuSE requires something
similar, then when you moved arrays to your server, perhaps mdadm is missing from your image since it wasn't present when YAST created your setup. Like I said, this is just a 'thought' since I haven't waded into linux-raid on 42.2 yet and do not know what the underlying udev (should be Upray) involvement in activation and assembly is on this release. It just seems like you would need the kernel-level support active before udev could do its magic (maybe udev can do it all now -- I'll let Andrei fill in the details -- I don't know)
It actually works fine with three disks and stops working when the fourth disk is added.
Currently I'm afraid I'm out of ideas how to debug it. At least, without being able to reproduce it or having access to this problem configuration.
Raid 0.9 can have problems accurately identifying disks - I thought this was fixed in 1.0 (the problem doesn't apply to 1.1 and 1.2). You're not getting any errors or warnings about superblocks, are you? What version of mdadm are you using? mdadm 4.0 has just been released - it might well pay to upgrade. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org