On 2023-05-30 15:56, mh@mike.franken.de wrote:
On Freitag, 26. Mai 2023 16:15:42 CEST Carlos E. R. wrote:
I get this in the /var/log/warn logfile:
2023-05-26T16:00:03.721677+02:00 Elesar systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.swap: Cannot add dependency job, ignoring: Unit dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.swap not found. 2023-05-26T16:00:03.736908+02:00 Elesar systemd[1]: message repeated 11 times: [ dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.swap: Cannot add dependency job, ignoring: Unit dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.swap not found.]
Strange things: the message is not in /var/log/messages nor in journalctl output.
[...]
What could be producing that message?
I had the same or a similar problem, that drove me crazy for months. It turned out, that I had a stale systemd mount unit file in /etc/systemd/ system. I could not find out, who/what created it, but it contained not existing drive paths. Perhaps you have also such a file sowmewhere in the numerous systemd directories?
No. I was being confused because the end of the path was ...part1.swap, and I could not find any such path. Turns out that there is a /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part1 that happens to be a swap partition, and systemd creates a service file with name ending in ...part1.swap. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)