Re: systemd messages relating to non-existent devices

[Kushal Kumaran <kushal@locationd.net>]

Richard Hector <richard@walnut.gen.nz> writes:

> Hi all,
>
> I'm getting messages like this in my logs:
>
> Aug  6 13:16:18 akl-host3 systemd[1]: dev-xvda9.device: Job
> dev-xvda9.device/start timed out.
> Aug  6 13:16:18 akl-host3 systemd[1]: Timed out waiting for device
> dev-xvda9.device.
> Aug  6 13:16:18 akl-host3 systemd[1]: Dependency failed for /dev/xvda9.
> Aug  6 13:16:18 akl-host3 systemd[1]: dev-xvda9.swap: Job
> dev-xvda9.swap/start failed with result 'dependency'.
> Aug  6 13:16:18 akl-host3 systemd[1]: dev-xvda9.device: Job
> dev-xvda9.device/start failed with result 'timeout'.
>
> /dev/xvda9 used to be my swap device, but no longer exists due to VPS
> weirdness (it's now on xvdi). I've changed my /etc/fstab to suit.
>
> Why does systemd keep trying to do stuff with it?
>
> I have the same issue with former LVM volumes on other systems as well.
>
> I suspect a reboot might fix it, but where is systemd keeping this info
> around, and why, and how can I stop it?
>

Run systemctl daemon-reload to regenerate the systemd mount units from
changed fstab file.

-- 
regards,
kushal