On 26.05.2023 20:30, Carlos E. R. wrote:

On 2023-05-26 18:46, Andrei Borzenkov wrote:

...

On 26.05.2023 17:15, 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.

And there is no such device, and no similar entry at all in fstab.

There is no way to tell it because you did not show which device as which label.

How would I? There is no such device to show. The only information I have is the log entry in /var/log/warn.

Using quote ">" to avoid line wrap in Thunderbird:

...

Elesar:~ # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS fd0 2:0 1 4K 0 disk sda 8:0 0 931.5G 0 disk └─sda1 8:1 0 931.5G 0 part └─cr_laman 254:2 0 931.5G 0 crypt /data/Lamán sdb 8:16 0 232.9G 0 disk ├─sdb1 8:17 0 24G 0 part [SWAP] ├─sdb2 8:18 0 15M 0 part ├─sdb3 8:19 0 15G 0 part / ├─sdb4 8:20 0 100G 0 part │ ├─cr_cripta 254:0 0 100G 0 crypt │ └─cr_ata-Samsung_SSD_850_EVO_250GB_...-part4 254:1 0 100G 0 crypt /home └─sdb5 8:21 0 25G 0 part /usr sr0 11:0 1 1024M 0 rom Elesar:~ #

(boot devide is sdb1)

There is only one swap partition:

Elesar:~ # l /dev/disk/by-* | grep -i swap lrwxrwxrwx 1 root root 10 May 26 16:18 ssd-swap -> ../../sdb1

Here is your device.

lrwxrwxrwx 1 root root 10 May 26 16:18 ssd-swap -> ../../sdb1 Elesar:~ #

/dev/disk/by-label: lrwxrwxrwx 1 root root 10 May 26 16:18 ssd-swap -> ../../sdb1

/dev/disk/by-partlabel: lrwxrwxrwx 1 root root 10 May 26 16:18 ssd-swap -> ../../sdb1

...

...

...

cer@Elesar:~> l /dev/disk/by-path/*part1* lrwxrwxrwx 1 root root 10 May 26 15:58 /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 May 26 15:00 /dev/disk/by-path/pci-0000:00:1f.2-ata-1.1-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 May 26 15:00 /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part1 -> ../../sdb1

Educated guess - systemd is confused by two different device paths to the same device.

A device that doesn't exist anywhere. The log entry is "...part1.swap", and the "swap" word doesn't appear on the command output.

I have no idea what "command output" you mean, but ...swap is not "a device", it is swap unit which is (must be) named according to swap device name. And you most certainly have swap on the /dev/sdb1 which is also /dev/disk/by-path/pci-0000:00:1f.2-ata-1.1-part1 and /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part1.

The log entry appeared after I run a yast online update, and prior to rebooting. So maybe it was triggered by some rpm script.

On Fri, 26 May 2023 19:30:38 +0200, "Carlos E. R." wrote:

...

Elesar:~ # lsblk NAME                                           MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS [...]

That did not show the labels which are used in your fstab.  I suggest:     lsblk -o +FSTYPE,LABEL -- Robert Webb

On 2023-05-27 00:16, Robert Webb via openSUSE Users wrote:

On Fri, 26 May 2023 19:30:38 +0200, "Carlos E. R." <> wrote:

...

...

Elesar:~ # lsblk NAME                                           MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS [...]

That did not show the labels which are used in your fstab.  I suggest:     lsblk -o +FSTYPE,LABEL

Intentionally. Labels were not involved in the error message, just paths. When I do want details, I use: lsblk --output \ NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)

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)