Re: [opensuse] How to start mdadm service in openSUSE Leap 42.2?
On Thu, 12 Jan 2017 20:24:44 +0300, Andrei Borzenkov wrote:
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.
------------------------ On Tue, 10 Jan 2017 11:36:03 +0300, Andrei Borzenkov wrote:
On Mon, Jan 9, 2017 at 11:20 PM, Istvan Gabor <suseuser04@gmail.hu> wrote:
Unfortunately, udev logs while being quite voluminous are of little help. Stab in the dark - could you try disabling smartd service?
One more try - could you add "systemd.log_target=kmsg systemd.log_level=debug log_buf_len=16M" instead of udev.log-priority. Some output is definitely missing here.
Andrei, The systemd log message file (journalctl-b-170111a.txt )wasn't useful either? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (1)
-
Istvan Gabor