Wols Lists wrote:
On 23/10/17 18:50, Andrei Borzenkov wrote:
23.10.2017 20:16, Peter Suetterlin пишет:
So to sum up again:
If you want any useful help show full log (journal -b). If you can reproduce this problem, boot without "quiet" on kernel command line, it will give more verbose and hopefully more useful log.
What version of mdadm? What version of udev?
As I wrote, Leap 42.2. So mdadm - v3.4 - 28th January 2016 and udev-228-25.9.1
Another possible problem is that mdadm is correctly assembling the array, and because udev is notified by the array appearing in /dev (the events are asynchronous), udev/systemd is getting confused over whether the array exists, or is degraded, or what. Doesn't sound that likely, but it's plausible.
This is what I suspect is happening. The log part (which I unfortunately posted out-of-time-order) says md properly started the raid w/o issues. systemd also sees the partition (around line 1185 in the boot log http://www.royac.iac.es/~pit/Stuff/boot.log.xz): Oct 23 07:44:13 royac6 systemd[1]: Found device /dev/disk/by-uuid/133b616a-1100-4278-86a7-9eb677783e9b. and mounts it afterwards. But for some reason systemd thinks it is missing disks and is degraded, and I have no idea why :(( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org