12.01.2017 10:04, David C. Rankin пишет:
On 01/11/2017 03:35 PM, Istvan Gabor wrote:
Hi Andrei,
Was the new log file I sent this morning useful?
I have tried openSUSE 13.2 and it assembles the arrays correctly at boot. I haven't tried Leap 42.1 because I don't have it installed.
Thanks,
Istvan
Istvan,
I'll let Andrei decipher the udev messages, but I do have a thought. On Arch
I answered it off list (as I got them off list) - I do not see anything explaining this behavior. It looks like events related to disk are simply lost or udev for some reasons decides to not apply some rules. Unfortunately udev debug logging is both quite voluminous (so you are always in danger to lose some output) and rather non-informative, making it hard to associate particular log line with specific event.
at least, mdadm is added as a hook to the initcpio initramfs creation setup so
You (should) need it only if your boot/hibernate devices are on MD RAID. Otherwise there is no point to add them to initrd.
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org