finally I found the problem.
there was old record in persistent-net.rules. When I removed it,
udev-settle service exits normally. I thing this is another bug. Because
such thing (change of network card) should not brake system because of
old record.
old contents of /etc/udev/rules.d/70-persistent-net.rules:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x107c (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1b:xx:xx:xx:xx", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x10de:0x0373 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:30:xx:xx:xx:xx", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x10de:0x0373 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:30:xx:xx:xx:xx", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
Miloslav
Am 17.01.2016 um 20:18 schrieb Miloslav Semler:
Finally,
I found that if I shorten timeout of systemd-udev-settle.service from
180s to 60s, systems boot to normal mode (althrough this udev service
rise an error).
So please fix timeouts in this package to 60sec otherwise udev mount of
lvm drive can fail.
I don't see how this would be a proper fix.
So far we don't know what the underlying problem is and how to reproduce
it, which is a prerequisite for fixing it.
