On Thu, 12 Jan 2017 20:17:49 +0100, Carlos E. R. wrote:
On 2017-01-12 18:01, Istvan Gabor wrote:
On Thu, 12 Jan 2017 13:06:49 +0100, Carlos E. R. wrote:
On 2017-01-12 10:03, Istvan Gabor wrote:
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.
if fstab doesn't mention the array, how would the system know it has to set up the array? Maybe that would trigger initram creation.
fstab only describes which partitions to mount and where. Partition/volume/device recognition doesn't require fstab entry.
Or array mounts, too:
/dev/md0 /data/raid xfs defaults,nofail,relatime 1 3
Maybe I misunderstood you :-?
raid arrays are partition volumes too. In mdraid system they are designated as /dev/md* devices. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org