On Thu, 12 Jan 2017 01:04:14 -0600, David C. Rankin wrote:
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
David, thank you.
I'll let Andrei decipher the udev messages, but I do have a thought. On Arch at least, mdadm is added as a hook to the initcpio initramfs creation setup so 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.
Your supposition is correct. My initram and yast does not have the arrays. When I install a new system I set up only the minimal requirements for it. I install only one partition, the root (/), and don't set up separate partitions. My fstab has only this root partition and a swap partition.
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)
If the intram/initrd requires to have the mdadm arrays it also means that I have to recreate initram when I set up a new array or remove an array. Doesn't sound good. I can try to activate my arrays and make a new initrd. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org