-- Logs begin at Di 2015-09-01 18:53:16 CEST, end at Di 2015-09-01 19:14:47 CEST. --
Sep 01 18:53:16 hostname kernel: ACPI: RSDP 0x00000000000F6500 000014 (v00 GBT   )
Sep 01 18:53:16 hostname kernel: ACPI: RSDT 0x000000007FFF3040 000030 (v01 GBT    AWRDACPI 42302E31 AWRD 01010101)
Sep 01 18:53:16 hostname kernel: ACPI: FACP 0x000000007FFF30C0 000074 (v01 GBT    AWRDACPI 42302E31 AWRD 01010101)
Sep 01 18:53:16 hostname kernel: ACPI: DSDT 0x000000007FFF3180 003397 (v01 GBT    AWRDACPI 00001000 MSFT 0100000C)
Sep 01 18:53:16 hostname kernel: ACPI: FACS 0x000000007FFF0000 000040
Sep 01 18:53:16 hostname kernel: ACPI: MCFG 0x000000007FFF6640 00003C (v01 GBT    AWRDACPI 42302E31 AWRD 01010101)
Sep 01 18:53:16 hostname kernel: ACPI: APIC 0x000000007FFF6580 000068 (v01 GBT    AWRDACPI 42302E31 AWRD 01010101)
Sep 01 18:53:16 hostname kernel: ACPI: All ACPI Tables successfully acquired
Sep 01 18:53:16 hostname kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Sep 01 18:53:16 hostname kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20141107/hwxface-580)
Sep 01 18:53:16 hostname kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20141107/hwxface-580)
Sep 01 18:53:16 hostname kernel: pci 0000:00:1f.0: BAR 13: [io  0x0400-0x047f] has bogus alignment
Sep 01 18:53:16 hostname kernel: pci 0000:02:08.0: Firmware left e100 interrupts enabled; disabling
Sep 01 18:53:16 hostname kernel: PCCT header not found.
Sep 01 18:53:16 hostname kernel: ACPI PCC probe failed.
Sep 01 18:53:43 hostname org.freedesktop.systemd1[555]: ** (process:579): WARNING **: Could not connect to cgmanager: Could not connect: No such file or directory
Sep 01 18:53:43 hostname NetworkManager[557]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Sep 01 18:53:43 hostname NetworkManager[557]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Sep 01 18:53:43 hostname NetworkManager[557]: <warn> Error: failed to open /run/network/ifstate
Sep 01 18:53:43 hostname dhclient[584]: Can't create /run/sendsigs.omit.d/network-manager.dhclient-eth0.pid: No such file or directory
Sep 01 18:53:44 hostname dhclient[584]: Can't create /run/sendsigs.omit.d/network-manager.dhclient-eth0.pid: No such file or directory
Sep 01 18:53:44 hostname NetworkManager[557]: <warn> dnsmasq not available on the bus, can't update servers.
Sep 01 18:53:44 hostname NetworkManager[557]: <error> [1441126424.847523] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Sep 01 18:53:44 hostname NetworkManager[557]: <warn> DNS: plugin dnsmasq update failed
Sep 01 18:53:44 hostname dnsmasq[590]: kann die Prozessidentifikations-(PID)-Datei /run/sendsigs.omit.d/network-manager.dnsmasq.pid nicht öffnen: Datei oder Verzeichnis nicht gefunden
Sep 01 18:53:44 hostname dnsmasq[590]: Start fehlgeschlagen
Sep 01 18:53:45 hostname NetworkManager[557]: <warn> dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3)
Sep 01 18:53:45 hostname NetworkManager[557]: <warn> dnsmasq appeared on DBus: :1.5
Sep 01 18:53:45 hostname NetworkManager[557]: <warn> dnsmasq not available on the bus, can't update servers.
Sep 01 18:53:45 hostname NetworkManager[557]: <error> [1441126425.284441] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Sep 01 18:53:45 hostname NetworkManager[557]: <warn> DNS: plugin dnsmasq update failed
Sep 01 18:53:45 hostname dnsmasq[643]: kann die Prozessidentifikations-(PID)-Datei /run/sendsigs.omit.d/network-manager.dnsmasq.pid nicht öffnen: Datei oder Verzeichnis nicht gefunden
Sep 01 18:53:45 hostname dnsmasq[643]: Start fehlgeschlagen
Sep 01 18:53:45 hostname NetworkManager[557]: <warn> dnsmasq disappeared from the bus.
Sep 01 18:53:45 hostname NetworkManager[557]: <warn> dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3)
Sep 01 18:53:45 hostname org.freedesktop.systemd1[555]: ** (process:579): CRITICAL **: Unable to acquire bus name 'org.freedesktop.systemd1'.  Quitting.
Sep 01 18:53:45 hostname nm-dispatcher[635]: Disconnected from the system bus, exiting.
Sep 01 18:54:27 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 18:54:27 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 18:54:27 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 18:54:27 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 18:54:28 hostname kernel: XFS (sda2): Invalid superblock magic number
Sep 01 18:54:28 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 18:54:28 hostname kernel: MINIX-fs: unable to read superblock
Sep 01 18:54:28 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 18:54:28 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 18:54:28 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 18:54:28 hostname kernel: hfs: can't find a HFS filesystem on dev sda2
Sep 01 18:54:28 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 18:54:28 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 18:54:28 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 18:54:28 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 18:54:28 hostname kernel: XFS (sda6): Invalid superblock magic number
Sep 01 18:54:28 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 18:54:28 hostname kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda6.
Sep 01 18:54:28 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 18:54:28 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 18:54:28 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 18:54:28 hostname kernel: ufs: ufs_fill_super(): bad magic number
Sep 01 18:54:28 hostname kernel: hfs: can't find a HFS filesystem on dev sda6
Sep 01 19:07:40 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:07:40 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:07:40 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:07:40 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 19:07:40 hostname kernel: XFS (sda2): Invalid superblock magic number
Sep 01 19:07:40 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 19:07:40 hostname kernel: MINIX-fs: unable to read superblock
Sep 01 19:07:40 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 19:07:40 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 19:07:40 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 19:07:40 hostname kernel: hfs: can't find a HFS filesystem on dev sda2
Sep 01 19:07:40 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:07:40 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:07:40 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:07:40 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 19:07:40 hostname kernel: XFS (sda6): Invalid superblock magic number
Sep 01 19:07:40 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 19:07:40 hostname kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda6.
Sep 01 19:07:40 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 19:07:40 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 19:07:40 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 19:07:40 hostname kernel: ufs: ufs_fill_super(): bad magic number
Sep 01 19:07:40 hostname kernel: hfs: can't find a HFS filesystem on dev sda6
Sep 01 19:12:00 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:12:00 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:12:00 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:12:00 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 19:12:00 hostname kernel: XFS (sda2): Invalid superblock magic number
Sep 01 19:12:00 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 19:12:00 hostname kernel: MINIX-fs: unable to read superblock
Sep 01 19:12:00 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 19:12:00 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 19:12:01 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 19:12:01 hostname kernel: hfs: can't find a HFS filesystem on dev sda2
Sep 01 19:12:01 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:12:01 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:12:01 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:12:01 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 19:12:01 hostname kernel: XFS (sda6): Invalid superblock magic number
Sep 01 19:12:01 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 19:12:01 hostname kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda6.
Sep 01 19:12:01 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 19:12:01 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 19:12:01 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 19:12:01 hostname kernel: ufs: ufs_fill_super(): bad magic number
Sep 01 19:12:01 hostname kernel: hfs: can't find a HFS filesystem on dev sda6
Sep 01 19:12:28 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:12:28 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:12:28 hostname kernel: EXT4-fs (sda2): unable to read superblock
Sep 01 19:12:28 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 19:12:28 hostname kernel: XFS (sda2): Invalid superblock magic number
Sep 01 19:12:28 hostname kernel: FAT-fs (sda2): invalid media value (0x00)
Sep 01 19:12:28 hostname kernel: MINIX-fs: unable to read superblock
Sep 01 19:12:28 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 19:12:28 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 19:12:28 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 19:12:28 hostname kernel: hfs: can't find a HFS filesystem on dev sda2
Sep 01 19:12:28 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:12:28 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:12:28 hostname kernel: EXT4-fs (sda6): VFS: Can't find ext4 filesystem
Sep 01 19:12:28 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 19:12:28 hostname kernel: XFS (sda6): Invalid superblock magic number
Sep 01 19:12:28 hostname kernel: FAT-fs (sda6): bogus number of reserved sectors
Sep 01 19:12:28 hostname kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda6.
Sep 01 19:12:28 hostname kernel: hfsplus: unable to find HFS+ superblock
Sep 01 19:12:28 hostname kernel: qnx4: no qnx4 filesystem (no root dir).
Sep 01 19:12:28 hostname kernel: ufs: You didn't specify the type of your ufs filesystem
                                          
                                          mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
                                          
                                          >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Sep 01 19:12:28 hostname kernel: ufs: ufs_fill_super(): bad magic number
Sep 01 19:12:28 hostname kernel: hfs: can't find a HFS filesystem on dev sda6
Sep 01 19:12:50 hostname systemd-tmpfiles[29452]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Sep 01 19:12:51 hostname systemd[1]: Socket service cups.service already active, refusing.
Sep 01 19:12:51 hostname systemd[1]: Failed to listen on CUPS Scheduler.
Sep 01 19:12:51 hostname kernel: cgroup: new mount options do not match the existing superblock, will be ignored
Sep 01 19:12:51 hostname systemd-tmpfiles[29687]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Sep 01 19:12:51 hostname NetworkManager[29648]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Sep 01 19:12:51 hostname NetworkManager[29648]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Sep 01 19:12:52 hostname NetworkManager[29648]: <warn> dnsmasq not available on the bus, can't update servers.
Sep 01 19:12:52 hostname NetworkManager[29648]: <error> [1441127572.817063] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Sep 01 19:12:52 hostname NetworkManager[29648]: <warn> DNS: plugin dnsmasq update failed
Sep 01 19:12:52 hostname dnsmasq[29842]: Warnung: keine vorgelagerten (Upstream) Server konfiguriert
Sep 01 19:12:52 hostname NetworkManager[29648]: <warn> dnsmasq appeared on DBus: :1.11
Sep 01 19:12:53 hostname ModemManager[29664]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:08.0': not supported by any plugin
Sep 01 19:12:57 hostname org.a11y.Bus[30017]: Activating service name='org.a11y.atspi.Registry'
Sep 01 19:12:57 hostname org.a11y.Bus[30017]: Successfully activated service 'org.a11y.atspi.Registry'
Sep 01 19:13:01 hostname gnome-session[30160]: WARNING: Could not parse desktop file vino-server.desktop or it references a not found TryExec binary
Sep 01 19:13:09 hostname pulseaudio[30336]: [pulseaudio] source.c: Default and alternate sample rates are the same.
Sep 01 19:13:09 hostname pulseaudio[30336]: [alsa-source-USB Audio] alsa-source.c: ALSA weckte uns auf, um neue Daten vom Gerät zu lesen, doch es gab nichts zum Lesen!
Sep 01 19:13:09 hostname pulseaudio[30336]: [alsa-source-USB Audio] alsa-source.c: Dies ist höchstwahrscheinlich ein Fehler im ALSA-Treiber 'snd_usb_audio'. Bitte melden Sie diesen Fehler den ALSA-Entwicklern.
Sep 01 19:13:09 hostname pulseaudio[30336]: [alsa-source-USB Audio] alsa-source.c: Wir wurden durch das POLLIN-Set geweckt, allerdings lieferte ein anschliessender snd_pcm_avail() den Wert 0 oder einen anderen Wert < min_avail.
Sep 01 19:13:10 hostname pulseaudio[30396]: [pulseaudio] pid.c: Daemon already running.
Sep 01 19:13:10 hostname pulseaudio[30398]: [pulseaudio] pid.c: Daemon already running.
Sep 01 19:13:24 hostname org.gnome.ScreenSaver[30017]: ** Message: Lost the name, shutting down.
Sep 01 19:13:32 hostname org.gnome.zeitgeist.Engine[30017]: ** (zeitgeist-datahub:30615): WARNING **: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!