You are not logged in.

Pages: 1 2

Topic closed

#1 2015-04-26 14:18:20

nstgc
Member
Registered: 2014-03-17
Posts: 393

[S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

$ dmesg -l err
[    6.330201] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache2
[    6.332384] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache1
[    6.334041] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache1
[    6.730564] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache3
[    6.732213] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache3
[    6.997304] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[    6.999960] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[    7.003235] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[    7.005881] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[    7.194594] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[    7.197369] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[    7.207859] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[    7.210477] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[    7.240459] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[    7.243114] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[    8.062829] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
[    8.065328] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4

I've been getting this since I upgraded systemd last week. I tried fixing some of these by removing partitions with the same label that I wasn't using, which worked. The reason I have so many partitions with the same label is due to btrfs. Each partition that makes up a volume in btrfs has the same label. Apparently systemd doesn't like this.

Everything on my system seems to be working fine, however I would like to stop these errors since they are annoying/scary, but without having to reduce all my volumes to single.

[edit=solution] The recent systemd upgrade to 221 seems to have fixed this issue.

Last edited by nstgc (2015-06-26 00:43:51)

Offline

#2 2015-04-26 17:46:33

dront78
Member
From: Moscow
Registered: 2010-11-24
Posts: 47

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

same here on laptop with sda1..9 partitions

[   13.269998] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda8
[   14.066665] Adding 4194300k swap on /dev/sda7.  Priority:-1 extents:1 across:4194300k FS
[   14.629998] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
[   14.643331] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda9

# /etc/fstab: static file system information
#
# <file system>    <dir>    <type>    <options>    <dump>    <pass>
UUID=5f8c742d-2dc1-4b44-a058-4ab3ee0958e3               /             ext4          rw,relatime,data=ordered    0 1

UUID=b906dc5b-2755-4a64-bdd5-c264684d0fab               /boot         ext2          rw,relatime,stripe=4    0 2

# UUID=4959-05E7
/dev/sda5               /boot/efi     vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

UUID=585c2004-338f-4d51-9aa3-60fefd10fa4b               /home         ext4          rw,relatime,data=ordered    0 2

Offline

#3 2015-04-26 17:50:09

dront78
Member
From: Moscow
Registered: 2010-11-24
Posts: 47

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

probably can be related to partition name length or label info

sudo hwinfo --partition
18: None 00.0: 11300 Partition                                  
  [Created at block.414]
  Unique ID: bdUI.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda1
  Device Files: /dev/sda1, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part1, /dev/disk/by-id/wwn-0x3672424430888570880x-part1, /dev/disk/by-label/Восстановить, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/eaf4409d-b63b-4ce2-9aff-52995cd8c8d8, /dev/disk/by-uuid/BAD05F43D05F0553
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

19: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 2pkM.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda2
  Device Files: /dev/sda2, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part2, /dev/disk/by-id/wwn-0x3672424430888570880x-part2, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/993e7d46-fe14-423b-b9d5-33a9c3154a5f, /dev/disk/by-uuid/F861-03AC
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

20: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: W__Q.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda3
  Device Files: /dev/sda3, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part3, /dev/disk/by-id/wwn-0x3672424430888570880x-part3, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/a0d73074-d1c8-484b-bc46-8d3d4884fe6e
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

21: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: z9FV.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda4
  Device Files: /dev/sda4, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part4, /dev/disk/by-id/wwn-0x3672424430888570880x-part4, /dev/disk/by-label/SYSTEM, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/53783aca-73a9-4b60-bf9a-1b31fa71ee3b, /dev/disk/by-uuid/A012754C12752904
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

22: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: QLVZ.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda5
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda5
  Device Files: /dev/sda5, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part5, /dev/disk/by-id/wwn-0x3672424430888570880x-part5, /dev/disk/by-partlabel/EFI\x20System, /dev/disk/by-partuuid/db6a1b94-9521-46dd-8e60-a907a879b72b, /dev/disk/by-uuid/4959-05E7
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

23: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: tWld.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda6
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda6
  Device Files: /dev/sda6, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part6, /dev/disk/by-id/wwn-0x3672424430888570880x-part6, /dev/disk/by-partlabel/Linux\x20filesystem, /dev/disk/by-partuuid/a1c1f957-98ad-49d0-b11c-74f95370c5b8, /dev/disk/by-uuid/b906dc5b-2755-4a64-bdd5-c264684d0fab
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

24: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: Zzw6.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda7
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda7
  Device Files: /dev/sda7, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part7, /dev/disk/by-id/wwn-0x3672424430888570880x-part7, /dev/disk/by-partlabel/Linux\x20swap, /dev/disk/by-partuuid/e5b7681d-2d17-4a94-9ae1-0937cb64c8b4, /dev/disk/by-uuid/fe74f17a-dc27-4dd4-9b25-4c28c9f42127
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

25: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 09BB.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda8
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda8
  Device Files: /dev/sda8, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part8, /dev/disk/by-id/wwn-0x3672424430888570880x-part8, /dev/disk/by-partlabel/Linux\x20filesystem, /dev/disk/by-partuuid/2655add6-acb4-4514-814c-033269ec8c25, /dev/disk/by-uuid/5f8c742d-2dc1-4b44-a058-4ab3ee0958e3
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

26: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: TKRF.SE1wIdpsiiC
  Parent ID: 3OOL.ADuNngwJXg4
  SysFS ID: /class/block/sda/sda9
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda9
  Device Files: /dev/sda9, /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_62BGP18UT-part9, /dev/disk/by-id/wwn-0x3672424430888570880x-part9, /dev/disk/by-partlabel/Linux\x20filesystem, /dev/disk/by-partuuid/59d2e8c4-a073-4ec5-9276-70dc55fb17de, /dev/disk/by-uuid/585c2004-338f-4d51-9aa3-60fefd10fa4b
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (Disk)

Moderator edit:  Added BBCode code tags around program output

Last edited by ewaller (2015-04-26 18:48:39)

Offline

#4 2015-04-26 18:28:30

3igHankCh0w
Member
From: Fort Worth, Texas
Registered: 2012-08-22
Posts: 20

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I would like to add that I am also receiving similar error messages, but with ext4 partitions, and a gpt bios partition. This is on a fresh install, that did not appear until after I ran "sudo systemctl enable netctl-auto@wlan0.service". I have not had problems booting, or running, and the other strange thing is the effected partition changes after a reboot, or shutdown. I know others are having similar issues, as I have been scouring the web since this occurred, but with little success. It appears to effect raids, lvms, as mentioned here btrfs, and my ext4 file system equally. I hope this of some help, as I too would welcome a solution.

The cats have hacked into my network and are taking control!

Offline

#5 2015-04-27 06:39:32

3igHankCh0w
Member
From: Fort Worth, Texas
Registered: 2012-08-22
Posts: 20

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I would like to pass on that I have fixed the problem I was having, it appears that a wireless profile I had created for netctl was the cause, but I don't understand why. I had created a profile using wireless-wpa from the examples for my home network, I was having trouble logging into my network, so I removed the profile I had created, and used wifi-menu to create another. The new profile works, and I no longer have the problem with duplicate devices. I checked both profiles, the one created by wifi-menu, and the one I created from the examples, and they are identical, so I don't understand where the problem was. I also used the examle wireless-wpa to create a profile for my work wifi, and it worked without a problem. I hope this is of help to someone, and thanks to nstgc for the original post.

The cats have hacked into my network and are taking control!

Offline

#6 2015-04-27 13:23:51

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I'm running with a wired-only set up. I'll have to wait for the weekend to look into the wireless angle, however I doubt that is the cause for me.

Following dront78's example below is the output of "# hwinfo --partitions"

75: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: bdUI.SE1wIdpsiiC
  Parent ID: 3OOL.7ppt9e3ai+9
  SysFS ID: /class/block/sda/sda1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda1
  Device Files: /dev/sda1, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part1, /dev/disk/by-id/wwn-0x6829766019904589826x-part1, /dev/disk/by-partuuid/77f1354c-3b20-454d-ba60-9dbab9bc8640, /dev/disk/by-uuid/ff387510-d0ad-498f-8d1b-576b26ed103e
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #74 (Disk)

76: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 2pkM.SE1wIdpsiiC
  Parent ID: 3OOL.7ppt9e3ai+9
  SysFS ID: /class/block/sda/sda2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda2
  Device Files: /dev/sda2, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part2, /dev/disk/by-id/wwn-0x6829766019904589826x-part2, /dev/disk/by-partuuid/44596381-4cfe-4a2d-8e7b-f6427cc089d0
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #74 (Disk)

77: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: W__Q.SE1wIdpsiiC
  Parent ID: 3OOL.7ppt9e3ai+9
  SysFS ID: /class/block/sda/sda3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda3
  Device Files: /dev/sda3, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part3, /dev/disk/by-id/wwn-0x6829766019904589826x-part3, /dev/disk/by-partuuid/c9b404ec-f407-4081-a69c-9b10360d4cf7
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #74 (Disk)

78: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: z9FV.SE1wIdpsiiC
  Parent ID: 3OOL.7ppt9e3ai+9
  SysFS ID: /class/block/sda/sda4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda4
  Device Files: /dev/sda4, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part4, /dev/disk/by-id/wwn-0x6829766019904589826x-part4, /dev/disk/by-partuuid/69c0972d-51ed-429c-acea-6e1afd7ebb1f
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #74 (Disk)

80: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: h4pj.SE1wIdpsiiC
  Parent ID: WZeP.bTSLTpVNGx8
  SysFS ID: /class/block/sdb/sdb1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdb1
  Device Files: /dev/sdb1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part1, /dev/disk/by-id/wwn-0x17950130428369588225x-part1, /dev/disk/by-uuid/2c0f1039-2d4b-4f75-8fa4-529d19cd18fc
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #79 (Disk)

81: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 8G3o.SE1wIdpsiiC
  Parent ID: WZeP.bTSLTpVNGx8
  SysFS ID: /class/block/sdb/sdb2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdb2
  Device Files: /dev/sdb2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part2, /dev/disk/by-id/wwn-0x17950130428369588225x-part2, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #79 (Disk)

82: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: bRJs.SE1wIdpsiiC
  Parent ID: WZeP.bTSLTpVNGx8
  SysFS ID: /class/block/sdb/sdb3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdb3
  Device Files: /dev/sdb3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part3, /dev/disk/by-id/wwn-0x17950130428369588225x-part3, /dev/disk/by-label/old-raid1, /dev/disk/by-uuid/dfa989d8-edac-4c7e-b6fc-45237e6a0ebc
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #79 (Disk)

83: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 2dZw.SE1wIdpsiiC
  Parent ID: WZeP.bTSLTpVNGx8
  SysFS ID: /class/block/sdb/sdb4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdb4
  Device Files: /dev/sdb4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part4, /dev/disk/by-id/wwn-0x17950130428369588225x-part4, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #79 (Disk)

85: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: mX79.SE1wIdpsiiC
  Parent ID: _kuT.rgQvtxWxfg6
  SysFS ID: /class/block/sdc/sdc1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdc1
  Device Files: /dev/sdc1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part1, /dev/disk/by-id/wwn-0x4611505914592251905x-part1, /dev/disk/by-uuid/80780835-de4b-462c-b7f0-2b389d3e2c2f
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #84 (Disk)

86: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: DjND.SE1wIdpsiiC
  Parent ID: _kuT.rgQvtxWxfg6
  SysFS ID: /class/block/sdc/sdc2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdc2
  Device Files: /dev/sdc2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part2, /dev/disk/by-id/wwn-0x4611505914592251905x-part2, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #84 (Disk)

87: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: gudH.SE1wIdpsiiC
  Parent ID: _kuT.rgQvtxWxfg6
  SysFS ID: /class/block/sdc/sdc3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdc3
  Device Files: /dev/sdc3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part3, /dev/disk/by-id/wwn-0x4611505914592251905x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #84 (Disk)

88: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 74uL.SE1wIdpsiiC
  Parent ID: _kuT.rgQvtxWxfg6
  SysFS ID: /class/block/sdc/sdc4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdc4
  Device Files: /dev/sdc4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part4, /dev/disk/by-id/wwn-0x4611505914592251905x-part4, /dev/disk/by-label/old-aroot, /dev/disk/by-uuid/b396dd50-e3f1-4b74-8cac-7d8d79a75386
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #84 (Disk)

90: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: r_Ra.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd1
  Device Files: /dev/sdd1, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part1, /dev/disk/by-id/wwn-0x14865109125905272832x-part1, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/f3e9ce24-988d-40ef-bd5c-6313c808bef2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

91: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: IAie.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd2
  Device Files: /dev/sdd2, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part2, /dev/disk/by-id/wwn-0x14865109125905272832x-part2, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/f3344931-99c3-11e4-8601-806e6f6e6963, /dev/disk/by-uuid/30F403F0F403B75E
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

92: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: lLyi.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd3
  Device Files: /dev/sdd3, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part3, /dev/disk/by-id/wwn-0x14865109125905272832x-part3, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/ffbaa0cc-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/0DE5-0CB0
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

93: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: CXCn.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd4
  Device Files: /dev/sdd4, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part4, /dev/disk/by-id/wwn-0x14865109125905272832x-part4, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/ffbaa0b6-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/FE2648382647EFE7
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

94: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: fiSr.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd5
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd5
  Device Files: /dev/sdd5, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part5, /dev/disk/by-id/wwn-0x14865109125905272832x-part5, /dev/disk/by-label/flbck, /dev/disk/by-partuuid/bd84f197-066e-4b9e-bf9b-b0b3a4090cde, /dev/disk/by-uuid/832bcc8d-836e-4b4e-8d9c-0a19f5bcf7dd
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

95: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 6uiv.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd6
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd6
  Device Files: /dev/sdd6, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part6, /dev/disk/by-id/wwn-0x14865109125905272832x-part6, /dev/disk/by-partuuid/8f77bc79-ba57-462e-8beb-d09db5c77490
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

96: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: oKuO.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd7
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd7
  Device Files: /dev/sdd7, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part7, /dev/disk/by-id/wwn-0x14865109125905272832x-part7, /dev/disk/by-partuuid/7ca3eb27-d198-4915-9c71-e96fa7a34d8b, /dev/disk/by-uuid/fd43f1bd-9f52-41b7-badc-4ab7881473ee
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

97: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: GW8T.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd8
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd8
  Device Files: /dev/sdd8, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part8, /dev/disk/by-id/wwn-0x14865109125905272832x-part8, /dev/disk/by-partuuid/550f9e19-c0ec-4474-9e98-84c727854158
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

98: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: cPdt.SE1wIdpsiiC
  Parent ID: Rw8Y.lfY9_MpZuK1
  SysFS ID: /class/block/sdd/sdd10
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdd10
  Device Files: /dev/sdd10, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part10, /dev/disk/by-id/wwn-0x14865109125905272832x-part10, /dev/disk/by-label/bckup, /dev/disk/by-partuuid/de7eaa1e-66b0-4058-ad71-d0f8ea470b2f, /dev/disk/by-uuid/723d7788-8514-4777-8e07-e0faa48c9a83
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #89 (Disk)

100: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: wRm+.SE1wIdpsiiC
  Parent ID: u5Pc.jfv0tLKpnVA
  SysFS ID: /class/block/sde/sde1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sde1
  Device Files: /dev/sde1, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part1, /dev/disk/by-id/wwn-0x9832618751734861824x-part1, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #99 (Disk)

101: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: Nd04.SE1wIdpsiiC
  Parent ID: u5Pc.jfv0tLKpnVA
  SysFS ID: /class/block/sde/sde2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sde2
  Device Files: /dev/sde2, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part2, /dev/disk/by-id/wwn-0x9832618751734861824x-part2, /dev/disk/by-uuid/aa19d2cf-e59d-4277-a5e6-d0078ede6d3b
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #99 (Disk)

102: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: qoG8.SE1wIdpsiiC
  Parent ID: u5Pc.jfv0tLKpnVA
  SysFS ID: /class/block/sde/sde3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sde3
  Device Files: /dev/sde3, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part3, /dev/disk/by-id/wwn-0x9832618751734861824x-part3, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #99 (Disk)

103: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: H_WC.SE1wIdpsiiC
  Parent ID: u5Pc.jfv0tLKpnVA
  SysFS ID: /class/block/sde/sde4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sde4
  Device Files: /dev/sde4, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part4, /dev/disk/by-id/wwn-0x9832618751734861824x-part4
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #99 (Disk)

105: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: +u4R.SE1wIdpsiiC
  Parent ID: LHfg.eZsVjjzwg10
  SysFS ID: /class/block/sdf/sdf1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdf1
  Device Files: /dev/sdf1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part1, /dev/disk/by-id/wwn-0x8355873293896667137x-part1, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #104 (Disk)

106: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: S4LV.SE1wIdpsiiC
  Parent ID: LHfg.eZsVjjzwg10
  SysFS ID: /class/block/sdf/sdf2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdf2
  Device Files: /dev/sdf2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part2, /dev/disk/by-id/wwn-0x8355873293896667137x-part2, /dev/disk/by-uuid/96fa47c5-061d-4849-8582-7186cc1695d2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #104 (Disk)

107: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: vFbZ.SE1wIdpsiiC
  Parent ID: LHfg.eZsVjjzwg10
  SysFS ID: /class/block/sdf/sdf3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdf3
  Device Files: /dev/sdf3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part3, /dev/disk/by-id/wwn-0x8355873293896667137x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #104 (Disk)

108: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: NRrd.SE1wIdpsiiC
  Parent ID: LHfg.eZsVjjzwg10
  SysFS ID: /class/block/sdf/sdf4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sdf4
  Device Files: /dev/sdf4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part4, /dev/disk/by-id/wwn-0x8355873293896667137x-part4, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #104 (Disk)

i don't have time to look at this in detail this morning, but I will this afternoon.

Thank you for all the replies. Have any of you found this to actually be damaging?

[edit] In an effort to not be completely lazy, and because I was curious, I did check a bit into netctl. Running "$ netctl list" returned exactly nothing. I have no profiles.

[edit2]

I just ran "$ dmesg -l err" on my laptop and I'm not getting any errors.

Last edited by nstgc (2015-04-27 15:09:46)

Offline

#7 2015-04-28 07:00:36

Immobile
Member
Registered: 2015-02-07
Posts: 8

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I'm not sure what the issue with netctl is, but, like nstgc, I also have the same error messages on boot (and might have the same problem):

relevant portion of dmesg -l err:

[   11.674243] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
[   12.149338] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda8
[   12.182607] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda9
[   12.344037] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5

Indeed, looking at gparted, I do have 3 partitions with the "Name" field set to Linux Filesystem and 3 partitions set to Basic Data Partition; looking at hwinfo, this field seems to correspond to the device file in /dev/disk/by-partlabel:

22: None 00.0: 11300 Partition                                  
  [Created at block.414]
  Unique ID: bdUI.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda1
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda1
  Device Files: /dev/sda1, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part1, /dev/disk/by-id/wwn-0x5126384891044777984x-part1, /dev/disk/by-label/WINRE, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/bfc6c2a0-3681-4de3-92e1-041ecb8cbc25, /dev/disk/by-uuid/404EF0084EEFF516
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

23: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 2pkM.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda2
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda2
  Device Files: /dev/sda2, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part2, /dev/disk/by-id/wwn-0x5126384891044777984x-part2, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/6902ea91-7b72-4e4b-8a5c-66c0cc9ee479, /dev/disk/by-uuid/2A72-0B28
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

24: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: W__Q.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda3
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda3
  Device Files: /dev/sda3, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part3, /dev/disk/by-id/wwn-0x5126384891044777984x-part3, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/6d960232-8d33-486b-b4b6-79de914d9f77
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

25: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: z9FV.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda4
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda4
  Device Files: /dev/sda4, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part4, /dev/disk/by-id/wwn-0x5126384891044777984x-part4, /dev/disk/by-label/Windows, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/5f7879f4-a62e-4d20-b7ce-d02b66782882, /dev/disk/by-uuid/8EB693EFB693D655
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

26: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: QLVZ.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda5
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda5
  Device Files: /dev/sda5, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part5, /dev/disk/by-id/wwn-0x5126384891044777984x-part5, /dev/disk/by-label/RECOVERY, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/79642f3a-449f-4e49-b407-bb6bd19b0a6c, /dev/disk/by-uuid/E6A8EE9EA8EE6C8D
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

27: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: tWld.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda6
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda6
  Device Files: /dev/sda6, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part6, /dev/disk/by-id/wwn-0x5126384891044777984x-part6, /dev/disk/by-partlabel/Linux\x20filesystem, /dev/disk/by-partuuid/65022e4d-1919-451a-86e3-d546d1dc9dec, /dev/disk/by-uuid/c72bc918-e034-4953-9662-34c9b48a74a2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

28: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: Zzw6.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda7
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda7
  Device Files: /dev/sda7, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part7, /dev/disk/by-id/wwn-0x5126384891044777984x-part7, /dev/disk/by-partlabel/Linux\x20swap, /dev/disk/by-partuuid/85cbaac2-745b-442b-b359-773b421f0989, /dev/disk/by-uuid/9a8780a2-9649-4ea9-9ca6-d429e06c8887
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

29: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: 09BB.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda8
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda8
  Device Files: /dev/sda8, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part8, /dev/disk/by-id/wwn-0x5126384891044777984x-part8, /dev/disk/by-partlabel/Linux\x20filesystem, /dev/disk/by-partuuid/7f40e3d3-3735-48a3-bc17-b4726e5a56dc, /dev/disk/by-uuid/61369972-e67e-410e-a20b-ad35b976217e
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

30: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: TKRF.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda9
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda9
  Device Files: /dev/sda9, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part9, /dev/disk/by-id/wwn-0x5126384891044777984x-part9, /dev/disk/by-label/Experimental, /dev/disk/by-partlabel/Linux\x20filesystem, /dev/disk/by-partuuid/4b552a14-8dbd-451c-83d6-a8491f1734b4, /dev/disk/by-uuid/9409b433-7026-4af0-83e4-140f37cd1998
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

31: None 00.0: 11300 Partition
  [Created at block.414]
  Unique ID: n50z.SE1wIdpsiiC
  Parent ID: 3OOL.GVrgNTRDKE0
  SysFS ID: /class/block/sda/sda10
  Hardware Class: partition
  Model: "Partition"
  Device File: /dev/sda10
  Device Files: /dev/sda10, /dev/disk/by-id/ata-HGST_HTS541010A9E680_JA1009C0JN05WK-part10, /dev/disk/by-id/wwn-0x5126384891044777984x-part10, /dev/disk/by-label/Stuff, /dev/disk/by-partlabel/Microsoft\x20basic\x20data, /dev/disk/by-partuuid/2ed92959-d369-4116-8d0a-0a62c588edbe, /dev/disk/by-uuid/162CBBF32CBBCBCD
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (Disk)

The wiki page on Persistent Block Device Naming seems to suggest that GPT partition labels must be unique, is this the cause of these errors? (I only started seeing them yesterday)

I do not know if this is even reasonable, though. The 3 Linux Filesystem labelled partitions were all labelled by default by gdisk or gparted or something when I first created them, and the 3 Basic Data Partitions are all ntfs partitions which came pre-labelled with Windows with the OEM install. If the partlabels must be unique, there is going to be a conflict any time someone dual boots with Windows, I think.

Offline

#8 2015-04-28 14:19:15

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

All the errors I'm getting are for partitions on drives with MBR. I do have one drive with GPT, but that one no longer is reporting issues.

Offline

#9 2015-04-29 07:42:51

estan
Member
Registered: 2011-03-11
Posts: 13

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I'm getting a single message:

apr 29 09:12:50 pyret systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb2 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1

sdb is my SSD which has a GPT table, and sda is my HDD which I believe uses the legacy MBR scheme.

Like @Immobile I also suspect the duplicate name "Linux filesystem" is the issue. But I also think it's a strange requirement.

Has anyone tried changing the name of one of the partitions to see if it helps? If so, what configurations will I have to update afterwards?

Offline

#10 2015-04-29 11:41:08

ksu
Member
Registered: 2015-02-26
Posts: 55

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I had the same error a couple of days ago, and in my case the cause was that my drive was used in a RAID array years ago. Somehow the RAID flag was still set on that drive, giving the "appeared twice with different sysfs paths" error message. Additionally, I wasn't able to mount this drive because of this. I created a thread about this here: https://bbs.archlinux.org/viewtopic.php?id=196598
On Kubuntu though I didn't get this error (or maybe I did and I just didn't notice) and I could also mount the drive just fine. But on Arch dmesg was showing this error and it was impossible to mount.

Offline

#11 2015-04-29 22:14:52

3igHankCh0w
Member
From: Fort Worth, Texas
Registered: 2012-08-22
Posts: 20

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

Well after several days without a problem, I am now getting the same error as before.

[    4.837870] Bluetooth: hci0 hardware error 0x37
[    9.026795] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda2 and /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda6
[    9.270115] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda2 and /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda1
[    9.903416] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda2 and /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda10
[   10.106776] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda2 and /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda5
[   10.416763] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda2 and /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda9

The Bluetooth error I always get, but the others about devices with duplicate paths only started to appear after a fresh install, my other laptop does not throw these errors, so I am at a loss. I am using a disk with gpt and a gpt bios boot partition. I should also add that I used dd command to write zeros to disk before installing. I hope this info is of help.

Last edited by 3igHankCh0w (2015-04-29 22:17:12)

The cats have hacked into my network and are taking control!

Offline

#12 2015-04-30 14:42:18

brix
Member
Registered: 2014-05-26
Posts: 69

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

Like  @Immobile and @estan I suspect  it may be identical partition names that trigger the issue. I see only one message 

systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device \
appeared twice with different sysfs paths \
/sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda3 \
and \
/sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda5

and the partitions involved seem to have only a name in common

sda3: 
   name      Basic data partition 
   formatted FAT32 
   label     LRS_ESP
   size      1000 MiB
   flag      hidden
   UUID      IC84-FF9A

sda5:
   name      Basic data partition 
   formatted ntfs 
   label     Windows8_OS
   size      30 GiB
   flag      msftdata
   UUID      5AF88ABF0888EC7

However, another with the same name seems not to be noticed

sda1:
   name      Basic data partition 
   formatted ntfs 
   label     WINRE_DRV
   size      1000 MiB
   flag      hidden,diag
   UUID      2CA7887A87850F6

so identical names may not be the issue -- unless only the last two identical names (by partition device number)  can be fitted into the warning.

Unsurprisingly I'm experiencing no problems as the partitions involved are never mounted except when booting into Windows.

Enough is more.

Offline

#13 2015-04-30 15:48:51

paneless
Member
Registered: 2013-02-21
Posts: 27

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

The same message "Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device \ appeared twice with different sysfs paths \ " was appearing here also. I am using a Gpt partitioned disk and have just changed the partition names via cgdisk 'm' command from Linux filesystem to Rootfs and Home and the message has gone.

Last edited by paneless (2015-05-03 11:53:58)

Offline

#14 2015-05-02 09:31:11

b_adele
Member
From: Montpellier, France
Registered: 2012-02-03
Posts: 15
Website

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I confirm, if you label your HDD partition with e2label tool, the error disappear and you can mount the HDD.

It seem another problem, if the USB disk is present in the /etc/fstab i receive this error, you must remove the USB disk on the /etc/fstab and reboot the computer.

Please confirm if this solution works for you

Last edited by b_adele (2015-05-03 18:22:46)

Offline

#15 2015-05-03 18:23:25

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I don't know if it's related, however I've been having some issues since upgrading to Linux 4.0. https://bbs.archlinux.org/viewtopic.php?id=196960

b_adele wrote:

I confirm, if you label your HDD partition with e2label tool, the error disappear and you can mount the HDD

The problem is that every partition in a btrfs volume has the same label.

Offline

#16 2015-05-03 18:56:12

b_adele
Member
From: Montpellier, France
Registered: 2012-02-03
Posts: 15
Website

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

The problem is that every partition in a btrfs volume has the same label.

I don't understand this regression feature ! smile

Ok for the same label, but in the btrfs the partitions have the same uuid ?

Offline

#17 2015-05-04 08:29:03

3igHankCh0w
Member
From: Fort Worth, Texas
Registered: 2012-08-22
Posts: 20

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I used System Rescue CD, booted it up, and then used gparted, all partitions were labeled Linux File System, I gave each partition a different label, and no longer have a problem. I would add that I am using ext4, and not btrfs.

The cats have hacked into my network and are taking control!

Offline

#18 2015-05-05 16:17:49

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

b_adele wrote:

The problem is that every partition in a btrfs volume has the same label.

I don't understand this regression feature ! smile

Ok for the same label, but in the btrfs the partitions have the same uuid ?

Yes. Every member of a btrfs volume has the same UUID. At least on my system. Once the semester is over and things settle down, I'll see about getting onto the IRC and figuring out if something can be done. These errors seem to be benign, but that doesn't mean they will stay that way.

[edit] For example:

$ sudo blkid |grep 3873
/dev/sdb2: LABEL="aroot" UUID="3873d8ba-9472-4d92-ab0d-e94574bd0eae" UUID_SUB="cdd62d1a-c0ae-4e19-ac6d-cc6973f607b1" TYPE="btrfs" PARTUUID="bed43306-02"
/dev/sde1: LABEL="aroot" UUID="3873d8ba-9472-4d92-ab0d-e94574bd0eae" UUID_SUB="85308e59-62ba-4675-8167-f5d2fb7f1cbf" TYPE="btrfs" PARTUUID="e5bf7f39-01"
/dev/sdf4: LABEL="aroot" UUID="3873d8ba-9472-4d92-ab0d-e94574bd0eae" UUID_SUB="df84655d-c186-4198-a360-782fa4ad97f2" TYPE="btrfs" PARTUUID="10e2bec1-04"

Last edited by nstgc (2015-05-05 16:20:54)

Offline

#19 2015-05-08 05:13:47

stbinan
Member
Registered: 2013-11-18
Posts: 8

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

In my case, $ sudo blkid also shows PARTLABEL. I need to also change all the PARTLABELs to eliminate the errors. And "e2label" isn't able to change label for partition with format like swap or fat32, while "gparted" works.

Last edited by stbinan (2015-05-08 05:14:33)

Offline

#20 2015-05-22 22:25:42

Quanttek
Member
Registered: 2015-01-10
Posts: 22

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I have the same problem as OP, though in my case I have a raid,  where I can't just change the labels.

Offline

#21 2015-06-08 09:58:12

greyltc
Member
Registered: 2015-04-15
Posts: 5

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

Quanttek wrote:

I have the same problem as OP, though in my case I have a raid,  where I can't just change the labels.

Same thing for me. Anyone know how to fix this?

Offline

#22 2015-06-09 11:55:29

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

I just moved, but once things settle, and I can get an internet connection to my desktop, I'll work on this.

Offline

#23 2015-06-23 21:05:37

dakt
Member
From: Croatia
Registered: 2010-10-04
Posts: 67

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

Same here:

[    9.378340] systemd[1]: Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda/sda3 and /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda/sda4

Last edited by dakt (2015-06-23 21:06:02)

Offline

#24 2015-06-26 00:43:14

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

The recent systemd upgrade to 221 seems to have fixed this issue.

Offline

#25 2015-06-27 08:56:42

severach
Member
Registered: 2015-05-23
Posts: 198

Re: [S] Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff

It's not all fixed yet. I get it on my GPT partitions for zfs and btrfs. GPT mdraid partitions don't cause any warnings. Here we see the reason for the warning on these btrfs partitions. 

$ sgdisk -p /dev/sda
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 43292AF9-FF60-4921-85ED-40A847FE8B90
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048      5860533134   2.7 TiB     8300  urbackup

$ sgdisk -p /dev/sdb
...
Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048      5860533134   2.7 TiB     8300  urbackup

]$ ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 10 Jun 27 03:15 urbackup -> ../../sda1

Both of these drives will try to enumerate as /dev/disk/by-partlabel/urbackup which annoys systemd. I can solve this with the same fix I used for zfs by giving each partition label a unique name. gdisk can be used by hand or sgdisk by command line:

sgdisk -c1:"urbackup1" /dev/sda
sgdisk -c1:"urbackup2" /dev/sdb

Edit /etc/fstab and /dev/mdadm.conf /etc/mdadm.conf as necessary.

There's 101 ways to mess this up so don't do this remotely or you'll be making a midnight run to fix the server.

Last edited by severach (2015-06-29 06:59:31)

Offline

Pages: 1 2

Topic closed

Board footer

Powered by FluxBB