A quick search digs up that the path is created by this: https://github.com/systemd/systemd/blob/09541e49ebd17b41482e447dd8194942f39788c0/src/udev/udev-builtin-path_id.c#L349 . This code in that region was added in https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a but doesn't account for the fact that there may be multiple targets (each serving up a different ATA port 1)... Prior to that it doesn't look there was anything to build ATA paths at all? Additionally if my analysis is correct then this affects HEAD systemd-udev too.
I guess it would be good to know what the paths looked like back in 12.04 (perhaps they were SCSI based?) and whether you get any paths of that style on a system like 14.04 or 16.04.
A quick search digs up that the path is created by this: /github. com/systemd/ systemd/ blob/09541e49eb d17b41482e447dd 8194942f39788c0 /src/udev/ udev-builtin- path_id. c#L349 . This code in that region was added in https:/ /github. com/systemd/ systemd/ commit/ ba86822db70d9ff d02ad78cd02b237 ff8c569c7a but doesn't account for the fact that there may be multiple targets (each serving up a different ATA port 1)... Prior to that it doesn't look there was anything to build ATA paths at all? Additionally if my analysis is correct then this affects HEAD systemd-udev too.
https:/
I guess it would be good to know what the paths looked like back in 12.04 (perhaps they were SCSI based?) and whether you get any paths of that style on a system like 14.04 or 16.04.