04.07.2016 21:32, Chris Murphy пишет: > I have a system where I get an indefinite > > "A start job is running for dev-vda2.device (xmin ys / no limit)" > > Is there a boot parameter to use to change the no limit to have a > limit? rd.timeout does nothing.
It should. Use rd.break and examine unit configuration (systemctl show dev-vda2.device) as well as /run/systemd/system/dev-vda1.device.d. dracut is using infinite timeout by default indeed. > When I use rd.break=pre-mount and use > blkid, /dev/vda2 is there and can be mounted with the same mount > options as specified with rootflags= on the command line. So I'm not > sure why it's hanging indefinitely. I figure with > systemd.log_level=debug and rd.debug and maybe rd.udev.debug I should > be able to figure out why this is failing to mount. > In all cases I can remember this was caused by lack of CONFIG_FHANDLE support in kernel. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
