-- Logs begin at jeu. 2017-09-14 17:16:08 CEST, end at jeu. 2017-09-14 17:30:12 CEST. -- sept. 14 17:16:08 hostname kernel: ACPI: RSDP 0x000000007A68A000 000024 (v02 DELL ) sept. 14 17:16:08 hostname kernel: ACPI: XSDT 0x000000007A68A0C0 000104 (v01 DELL CBX3 01072009 AMI 00010013) sept. 14 17:16:08 hostname kernel: ACPI: FACP 0x000000007A6ADA90 00010C (v05 DELL CBX3 01072009 AMI 00010013) sept. 14 17:16:08 hostname kernel: ACPI: DSDT 0x000000007A68A258 023833 (v02 DELL CBX3 01072009 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: FACS 0x000000007AFF2F80 000040 sept. 14 17:16:08 hostname kernel: ACPI: APIC 0x000000007A6ADBA0 000084 (v03 DELL CBX3 01072009 AMI 00010013) sept. 14 17:16:08 hostname kernel: ACPI: FPDT 0x000000007A6ADC28 000044 (v01 DELL CBX3 01072009 AMI 00010013) sept. 14 17:16:08 hostname kernel: ACPI: FIDT 0x000000007A6ADC70 00009C (v01 DELL CBX3 01072009 AMI 00010013) sept. 14 17:16:08 hostname kernel: ACPI: MCFG 0x000000007A6ADD10 00003C (v01 DELL CBX3 01072009 MSFT 00000097) sept. 14 17:16:08 hostname kernel: ACPI: HPET 0x000000007A6ADD50 000038 (v01 DELL CBX3 01072009 AMI. 0005000B) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6ADD88 000322 (v01 SataRe SataTabl 00001000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: BOOT 0x000000007A6AE0B0 000028 (v01 DELL CBX3 01072009 AMI 00010013) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6AE0D8 0012DC (v02 SaSsdt SaSsdt 00003000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: HPET 0x000000007A6AF3B8 000038 (v01 INTEL KBL-ULT 00000001 MSFT 0000005F) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6AF3F0 0006B5 (v02 INTEL xh_OEMBD 00000000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: UEFI 0x000000007A6AFAA8 000042 (v01 00000000 00000000) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6AFAF0 000EDE (v02 CpuRef CpuSsdt 00003000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: LPIT 0x000000007A6B09D0 000094 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F) sept. 14 17:16:08 hostname kernel: ACPI: WSMT 0x000000007A6B0A68 000028 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6B0A90 00029F (v02 INTEL sensrhub 00000000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6B0D30 003002 (v02 INTEL PtidDevc 00001000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: DBGP 0x000000007A6B3D38 000034 (v01 INTEL 00000002 MSFT 0000005F) sept. 14 17:16:08 hostname kernel: ACPI: DBG2 0x000000007A6B3D70 000054 (v00 INTEL 00000002 MSFT 0000005F) sept. 14 17:16:08 hostname kernel: ACPI: MSDM 0x000000007A6B3DC8 000055 (v03 DELL CBX3 06222004 AMI 00010013) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6B3E20 005700 (v02 DptfTa DptfTabl 00001000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: SLIC 0x000000007A6B9520 000176 (v03 DELL CBX3 01072009 MSFT 00010013) sept. 14 17:16:08 hostname kernel: [81B blob data] sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6B96D0 000281 (v02 SgRef SgUlt 00001000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6B9958 000699 (v02 SgRef SgPch 00001000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: DMAR 0x000000007A6B9FF8 0000F0 (v01 INTEL KBL 00000001 INTL 00000001) sept. 14 17:16:08 hostname kernel: ACPI: TPM2 0x000000007A6BA0E8 000034 (v03 Tpm2Tabl 00000001 AMI 00000000) sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0x000000007A6BA120 000F88 (v01 AmdRef AmdTabl 00001000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: 11 ACPI AML tables successfully acquired and loaded sept. 14 17:16:08 hostname kernel: sept. 14 17:16:08 hostname kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' sept. 14 17:16:08 hostname kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) sept. 14 17:16:08 hostname kernel: PCCT header not found. sept. 14 17:16:08 hostname kernel: ACPI: Executed 33 blocks of module-level executable AML code sept. 14 17:16:08 hostname kernel: ACPI: Dynamic OEM Table Load: sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0xFFFF94B0AC625000 0006F6 (v02 PmRef Cpu0Ist 00003000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code sept. 14 17:16:08 hostname kernel: ACPI: Dynamic OEM Table Load: sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0xFFFF94B0AC72B000 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code sept. 14 17:16:08 hostname kernel: ACPI: Dynamic OEM Table Load: sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0xFFFF94B0AC623800 00065C (v02 PmRef ApIst 00003000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code sept. 14 17:16:08 hostname kernel: ACPI: Dynamic OEM Table Load: sept. 14 17:16:08 hostname kernel: ACPI: SSDT 0xFFFF94B0AC706400 00018A (v02 PmRef ApCst 00003000 INTL 20160422) sept. 14 17:16:08 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code sept. 14 17:16:08 hostname kernel: ACPI: Enabled 5 GPEs in block 00 to 7F sept. 14 17:16:08 hostname kernel: i8042: Warning: Keylock active sept. 14 17:16:08 hostname kernel: intel_pmc_core: probe of 0000:00:1f.2 failed with error -22 sept. 14 17:16:08 hostname kernel: ATPX version 1, functions 0x00000033 sept. 14 17:16:08 hostname kernel: ATPX Hybrid Graphics sept. 14 17:16:08 hostname kernel: CRAT table not found sept. 14 17:16:08 hostname kernel: i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed with error -2 sept. 14 17:16:08 hostname kernel: sd 2:0:0:0: [sdc] No Caching mode page found sept. 14 17:16:08 hostname kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through sept. 14 17:16:08 hostname kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff] sept. 14 17:16:08 hostname kernel: tpm_crb: probe of MSFT0101:00 failed with error -16 sept. 14 17:16:08 hostname kernel: ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20160422/nsprepkg-130) sept. 14 17:16:08 hostname systemd-tmpfiles[1272]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. sept. 14 17:16:08 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized! sept. 14 17:16:08 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 3 was not initialized! sept. 14 17:16:08 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized! sept. 14 17:16:08 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized! sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00000081/00002000 sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: [ 0] Receiver Error (First) sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: [ 7] Bad DLLP sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00002041/00002000 sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: [ 0] Receiver Error sept. 14 17:16:09 hostname kernel: pcieport 0000:00:1c.4: [ 6] Bad TLP sept. 14 17:16:09 hostname kernel: ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2 sept. 14 17:16:09 hostname kernel: ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2 sept. 14 17:16:09 hostname kernel: ath10k_pci 0000:02:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0042,subsystem-vendor=1028,subsystem-device=1810 from ath10k/QCA9377/hw1.0/board-2.bin sept. 14 17:16:10 hostname NetworkManager[1425]: [1505402170.2282] SettingsPlugin-Ofono: file doesn't exist: /var/lib/ofono sept. 14 17:16:10 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:10 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:10 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:10 hostname bluetoothd[1858]: Failed to obtain handles for "Service Changed" characteristic sept. 14 17:16:10 hostname bluetoothd[1858]: Not enough free handles to register service sept. 14 17:16:10 hostname bluetoothd[1858]: Error adding Link Loss service sept. 14 17:16:10 hostname bluetoothd[1858]: Not enough free handles to register service sept. 14 17:16:10 hostname bluetoothd[1858]: Not enough free handles to register service sept. 14 17:16:10 hostname bluetoothd[1858]: Not enough free handles to register service sept. 14 17:16:10 hostname bluetoothd[1858]: Current Time Service could not be registered sept. 14 17:16:10 hostname bluetoothd[1858]: gatt-time-server: Input/output error (5) sept. 14 17:16:10 hostname bluetoothd[1858]: Not enough free handles to register service sept. 14 17:16:10 hostname bluetoothd[1858]: Not enough free handles to register service sept. 14 17:16:10 hostname bluetoothd[1858]: Sap driver initialization failed. sept. 14 17:16:10 hostname bluetoothd[1858]: sap-server: Operation not permitted (1) sept. 14 17:16:10 hostname NetworkManager[1425]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed sept. 14 17:16:10 hostname systemd-udevd[1220]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. sept. 14 17:16:10 hostname NetworkManager[1425]: [1505402170.7342] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files sept. 14 17:16:11 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) sept. 14 17:16:11 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00000081/00002000 sept. 14 17:16:11 hostname kernel: pcieport 0000:00:1c.4: [ 0] Receiver Error sept. 14 17:16:11 hostname kernel: pcieport 0000:00:1c.4: [ 7] Bad DLLP sept. 14 17:16:11 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) sept. 14 17:16:11 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00000001/00002000 sept. 14 17:16:11 hostname kernel: pcieport 0000:00:1c.4: [ 0] Receiver Error sept. 14 17:16:13 hostname wpa_supplicant[1878]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none sept. 14 17:16:13 hostname wpa_supplicant[1878]: dbus: Failed to construct signal sept. 14 17:16:13 hostname wpa_supplicant[1878]: Could not read interface p2p-dev-wlp2s0 flags: No such device sept. 14 17:16:13 hostname org.a11y.Bus[1900]: Activating service name='org.a11y.atspi.Registry' sept. 14 17:16:13 hostname org.a11y.Bus[1900]: ** (process:1944): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files sept. 14 17:16:13 hostname org.a11y.Bus[1900]: Successfully activated service 'org.a11y.atspi.Registry' sept. 14 17:16:14 hostname org.gnome.ScreenSaver[1900]: Gtk-Message: Failed to load module "overlay-scrollbar" sept. 14 17:16:14 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:14 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:14 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:14 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:14 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:14 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:14 hostname org.gnome.ScreenSaver[1900]: ** (gnome-screensaver:2028): WARNING **: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files sept. 14 17:16:14 hostname pulseaudio[2004]: [pulseaudio] authkey.c: Failed to open cookie file '/home/hostname/.config/pulse/cookie': No such file or directory sept. 14 17:16:14 hostname pulseaudio[2004]: [pulseaudio] authkey.c: Failed to load authentication key '/home/hostname/.config/pulse/cookie': No such file or directory sept. 14 17:16:14 hostname pulseaudio[2004]: [pulseaudio] authkey.c: Failed to open cookie file '/home/hostname/.pulse-cookie': No such file or directory sept. 14 17:16:14 hostname pulseaudio[2004]: [pulseaudio] authkey.c: Failed to load authentication key '/home/hostname/.pulse-cookie': No such file or directory sept. 14 17:16:14 hostname pulseaudio[2004]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files sept. 14 17:16:14 hostname pulseaudio[2097]: [pulseaudio] pid.c: Daemon already running. sept. 14 17:16:18 hostname org.freedesktop.Notifications[1900]: Gtk-Message: Failed to load module "overlay-scrollbar" sept. 14 17:16:18 hostname org.freedesktop.Notifications[1900]: ** (notify-osd:3319): WARNING **: dnd_is_idle_inhibited(): got error "The name org.gnome.SessionManager was not provided by any .service files" sept. 14 17:16:32 hostname org.freedesktop.secrets[1900]: ** Message: couldn't access control socket: /run/user/999/keyring/control: No such file or directory sept. 14 17:16:37 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:16:37 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:16:37 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:16:40 hostname dnsmasq[3506]: warning: no upstream servers configured sept. 14 17:16:40 hostname org.freedesktop.Notifications[1900]: ** (notify-osd:3319): WARNING **: dnd_is_idle_inhibited(): got error "The name org.gnome.SessionManager was not provided by any .service files" sept. 14 17:16:40 hostname NetworkManager[1425]: [1505402200.6745] (pid 3497) unhandled DHCP event for interface wlp2s0 sept. 14 17:16:42 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:42 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:42 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:42 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:42 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:42 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:42 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:42 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:43 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:43 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:43 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:43 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:43 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:43 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:43 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:43 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:56 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:56 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:56 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:56 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:56 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:56 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:56 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:56 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:56 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:56 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:56 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:56 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:56 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:56 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:57 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:57 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:57 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:57 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:57 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:57 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:16:57 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:16:57 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:20:43 hostname kernel: aufs may_rename_srcdir:453:appstreamcli[18353]: renaming dir who has child(ren) on multiple branches, is not supported sept. 14 17:20:46 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:46 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:46 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:46 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:46 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:46 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:49 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:49 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:49 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:50 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:50 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:50 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:52 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:52 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:52 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:55 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:55 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:55 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:56 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:56 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:56 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:58 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:58 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:58 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:20:59 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:20:59 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:20:59 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:01 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:01 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:01 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:01 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:01 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:01 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:02 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:02 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:02 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:03 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:03 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:03 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:05 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:05 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:05 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:06 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:06 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:06 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:09 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:10 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:10 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:10 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:11 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:11 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:11 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:12 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:12 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:12 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:13 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:15 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:15 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:15 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:17 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:17 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:17 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:17 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:17 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:17 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:20 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:20 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:20 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:22 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:22 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:22 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:23 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:23 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:23 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:24 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:24 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:24 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:25 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:26 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:30 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:30 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:30 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:30 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:30 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:30 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:31 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:31 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:31 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:32 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:33 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:33 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:33 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:34 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:34 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:34 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:35 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:35 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:35 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:36 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:36 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:36 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:38 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:38 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:38 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:39 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:39 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00003000/00002000 sept. 14 17:21:39 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:39 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:21:39 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:21:39 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:21:58 hostname /plugininstall.py[18396]: log-output -t ubiquity umount /target/cdrom sept. 14 17:22:00 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:00 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:00 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:01 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:01 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:01 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:01 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:01 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:01 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:02 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00003000/00002000 sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:03 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:04 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:04 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:04 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:05 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:29 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:29 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:29 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:30 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:30 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:30 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:31 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:31 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:31 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:32 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:32 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:32 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00003000/00002000 sept. 14 17:22:33 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:34 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:34 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:34 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:22:34 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:22:34 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:22:34 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:23:17 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:17 hostname kernel: FAT-fs (sda1): Filesystem has been set read-only sept. 14 17:23:17 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:17 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:17 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:25 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:25 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:25 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:25 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:25 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:25 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:46 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:47 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:51 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:52 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:52 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:52 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:52 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:54 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:23:54 hostname kernel: FAT-fs (sda1): error, fat_get_cluster: invalid cluster chain (i_pos 0) sept. 14 17:25:16 hostname kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) sept. 14 17:25:16 hostname kernel: pcieport 0000:00:1c.4: device [8086:9d14] error status/mask=00001000/00002000 sept. 14 17:25:16 hostname kernel: pcieport 0000:00:1c.4: [12] Replay Timer Timeout sept. 14 17:30:07 hostname /plugininstall.py[18396]: Exception during installation: sept. 14 17:30:07 hostname /plugininstall.py[18396]: Traceback (most recent call last): sept. 14 17:30:07 hostname /plugininstall.py[18396]: File "/usr/share/ubiquity/plugininstall.py", line 1778, in sept. 14 17:30:07 hostname /plugininstall.py[18396]: install.run() sept. 14 17:30:07 hostname /plugininstall.py[18396]: File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper sept. 14 17:30:07 hostname /plugininstall.py[18396]: func(self) sept. 14 17:30:07 hostname /plugininstall.py[18396]: File "/usr/share/ubiquity/plugininstall.py", line 241, in run sept. 14 17:30:07 hostname /plugininstall.py[18396]: self.configure_bootloader() sept. 14 17:30:07 hostname /plugininstall.py[18396]: File "/usr/share/ubiquity/plugininstall.py", line 1035, in configure_bootloader sept. 14 17:30:07 hostname /plugininstall.py[18396]: "GrubInstaller failed with code %d" % ret) sept. 14 17:30:07 hostname /plugininstall.py[18396]: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1 sept. 14 17:30:07 hostname /plugininstall.py[18396]: sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1892]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc2 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device: Dev dev-disk-by\x2dlabel-Ubuntu\x5cx2016.04.2\x5cx20LTS\x5cx20amd64.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1 sept. 14 17:30:08 hostname systemd[1]: dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device: Dev dev-disk-by\x2duuid-2017\x2d02\x2d15\x2d21\x2d44\x2d13\x2d00.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc and /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0/block/sdc/sdc1