[systemd-devel] mount failed during system start but after "systemctl daemon-reload" everything works

[Lennart Poettering]

On Fri, 18.04.14 10:32, Oliver (oliver at business-security.de) wrote:

> Hello.
> Could anyone tell me a reason why a mount (regardless of via fstab
> or "mountpoint.mount" unit file) during system boot leads to a
> timeout because of device timeout and after i do a "systemctl
> daemon-reload" the mount is successful?
> 
> Detailed information:
> My system is a Linuxfromscratch 7.5 (so no "real" distribution -
> everything is self-compiled) and it runs as a paravirtualized Xen
> DomU. Therefore the block devices are /dev/xvda1 and /dev/xvdb1.
> The first is the root fs and mount and remount are okay. Then the
> second block device should mount and it timed out with "Dependency
> failed" and "dev-xvdb1.device/start timed out"
> When I run "udevadm info /dev/xvdb1" everything seems to be okay,
> but any try of mount this via systemd failes. When I mount manually
> via "mount /dev/xvdb1 /mountpoint" it's fine. Then "systemctl status
> mountpoint.mount" says "active".
> Manually unmount is okay and after this a mount via systemd failes again.
> If I do, and only if I do "systemctl daemon-reload" and then
> "systemctl start mountpoint.mount" it works.
> 
> I'm a beginner with a systemd based system and do not know much
> about the internals. What could lead to this behaviour? Is it
> possible that I do anything wrong?
> Please help. I'm very frustrated. If you need more Input, please tell me.

systemd's .device units rely on the "systemd" tag to be on the udev
device, as well as DEVICE_READY=1 being absent of it. I have no idea how
xen sets up block device nodes, but what is essential that this used to
inform systemd when the devices are ready to be mounted. 

Lennart

-- 
Lennart Poettering, Red Hat