22.10.2015 19:56, Andrei Borzenkov пишет:
22.10.2015 19:28, Per Jessen пишет:
Istvan Gabor wrote:
A different assemble "pattern". And it goes like this from boot to boot. Why is this? How to fix this? Is this hardware of software issue?
I've never seen that before - I am assuming those arrays were all correctly assembled before you rebooted?
Not always assembled, but always synched. For example if every arrays are in sync and I reboot the computer, sometimes only one of the devices gets assembled into the array. If the array is not touched (mounted), after another reboot the same array sometimes gets assembled correctly.
Very odd.
Not really. Device discovery is non-deterministic, both in timings and order. Current TW and 13.2 use assembly initiated from udev and timers to wait for complete array. If enough array pieces are available but not all, it will assemble it in degraded mode after timeer is expired.
I do not know how 12.2 did it, but if it naively tried to activate array as soon as it saw it, this is exactly what is expected.
Hmm ... looking at 12.2 boot.md, this is exactly what it did: # firstly finish any incremental assembly that has started. $mdadm_BIN -IRs Try adding some delay before this line, something like "sleep 60". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org