-- Logs begin at Sun 2017-02-26 03:03:39 IST, end at Sun 2017-02-26 03:06:11 IST. -- Feb 26 08:10:30 hostname kernel: ACPI: RSDP 0x000000007A58A000 000024 (v02 DELL ) Feb 26 08:10:30 hostname kernel: ACPI: XSDT 0x000000007A58A0C0 000104 (v01 DELL CBX3 01072009 AMI 00010013) Feb 26 08:10:30 hostname kernel: ACPI: FACP 0x000000007A5ADA90 00010C (v05 DELL CBX3 01072009 AMI 00010013) Feb 26 08:10:30 hostname kernel: ACPI: DSDT 0x000000007A58A258 023833 (v02 DELL CBX3 01072009 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: FACS 0x000000007AEF2F80 000040 Feb 26 08:10:30 hostname kernel: ACPI: APIC 0x000000007A5ADBA0 000084 (v03 DELL CBX3 01072009 AMI 00010013) Feb 26 08:10:30 hostname kernel: ACPI: FPDT 0x000000007A5ADC28 000044 (v01 DELL CBX3 01072009 AMI 00010013) Feb 26 08:10:30 hostname kernel: ACPI: FIDT 0x000000007A5ADC70 00009C (v01 DELL CBX3 01072009 AMI 00010013) Feb 26 08:10:30 hostname kernel: ACPI: MCFG 0x000000007A5ADD10 00003C (v01 DELL CBX3 01072009 MSFT 00000097) Feb 26 08:10:30 hostname kernel: ACPI: HPET 0x000000007A5ADD50 000038 (v01 DELL CBX3 01072009 AMI. 0005000B) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5ADD88 000322 (v01 SataRe SataTabl 00001000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: BOOT 0x000000007A5AE0B0 000028 (v01 DELL CBX3 01072009 AMI 00010013) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5AE0D8 0012DC (v02 SaSsdt SaSsdt 00003000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: HPET 0x000000007A5AF3B8 000038 (v01 INTEL KBL-ULT 00000001 MSFT 0000005F) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5AF3F0 0006B5 (v02 INTEL xh_OEMBD 00000000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: UEFI 0x000000007A5AFAA8 000042 (v01 00000000 00000000) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5AFAF0 000EDE (v02 CpuRef CpuSsdt 00003000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: LPIT 0x000000007A5B09D0 000094 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F) Feb 26 08:10:30 hostname kernel: ACPI: WSMT 0x000000007A5B0A68 000028 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5B0A90 00029F (v02 INTEL sensrhub 00000000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5B0D30 003002 (v02 INTEL PtidDevc 00001000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: DBGP 0x000000007A5B3D38 000034 (v01 INTEL 00000002 MSFT 0000005F) Feb 26 08:10:30 hostname kernel: ACPI: DBG2 0x000000007A5B3D70 000054 (v00 INTEL 00000002 MSFT 0000005F) Feb 26 08:10:30 hostname kernel: ACPI: MSDM 0x000000007A5B3DC8 000055 (v03 DELL CBX3 06222004 AMI 00010013) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5B3E20 005700 (v02 DptfTa DptfTabl 00001000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: SLIC 0x000000007A5B9520 000176 (v03 DELL CBX3 01072009 MSFT 00010013) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5B9698 000281 (v02 SgRef SgUlt 00001000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5B9920 000699 (v02 SgRef SgPch 00001000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: DMAR 0x000000007A5B9FC0 0000F0 (v01 INTEL KBL 00000001 INTL 00000001) Feb 26 08:10:30 hostname kernel: ACPI: TPM2 0x000000007A5BA0B0 000034 (v03 Tpm2Tabl 00000001 AMI 00000000) Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0x000000007A5BA0E8 000F88 (v01 AmdRef AmdTabl 00001000 INTL 20160422) Feb 26 08:10:30 hostname kernel: [81B blob data] Feb 26 08:10:30 hostname kernel: tboot: non-0 tboot_addr but it is not of type E820_RESERVED Feb 26 08:10:30 hostname kernel: ACPI: 11 ACPI AML tables successfully acquired and loaded Feb 26 08:10:30 hostname kernel: Feb 26 08:10:30 hostname kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Feb 26 08:10:30 hostname kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) Feb 26 08:10:30 hostname kernel: PCCT header not found. Feb 26 08:10:30 hostname kernel: ACPI: Executed 33 blocks of module-level executable AML code Feb 26 08:10:30 hostname kernel: ACPI: Dynamic OEM Table Load: Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0xFFFF9302B9B41000 0006B4 (v02 PmRef Cpu0Ist 00003000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code Feb 26 08:10:30 hostname kernel: ACPI: Dynamic OEM Table Load: Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0xFFFF9302B9456800 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code Feb 26 08:10:30 hostname kernel: ACPI: Dynamic OEM Table Load: Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0xFFFF9302B9B40000 00065C (v02 PmRef ApIst 00003000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code Feb 26 08:10:30 hostname kernel: ACPI: Dynamic OEM Table Load: Feb 26 08:10:30 hostname kernel: ACPI: SSDT 0xFFFF9302B9451400 00018A (v02 PmRef ApCst 00003000 INTL 20160422) Feb 26 08:10:30 hostname kernel: ACPI: Executed 1 blocks of module-level executable AML code Feb 26 08:10:30 hostname kernel: ACPI: Enabled 5 GPEs in block 00 to 7F Feb 26 08:10:30 hostname kernel: i8042: Warning: Keylock active Feb 26 08:10:30 hostname kernel: intel_pmc_core: probe of 0000:00:1f.2 failed with error -22 Feb 26 08:10:30 hostname kernel: ATPX version 1, functions 0x00000033 Feb 26 08:10:30 hostname kernel: ATPX Hybrid Graphics Feb 26 08:10:30 hostname kernel: CRAT table not found Feb 26 08:10:30 hostname kernel: scsi host2: runtime PM trying to activate child device host2 but parent (2-1:1.0) is not active Feb 26 08:10:30 hostname kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff] Feb 26 08:10:30 hostname kernel: tpm_crb: probe of MSFT0101:00 failed with error -16 Feb 26 08:10:30 hostname kernel: ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20160422/nsprepkg-130) Feb 26 08:10:30 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized! Feb 26 08:10:30 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 7 was not initialized! Feb 26 08:10:30 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized! Feb 26 08:10:30 hostname kernel: uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized! Feb 26 08:10:30 hostname kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2 Feb 26 08:10:30 hostname kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2 Feb 26 08:10:30 hostname kernel: iwlwifi 0000:02:00.0: Unsupported splx structure Feb 26 08:10:30 hostname systemd-tmpfiles[1387]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Feb 26 08:10:31 hostname systemd-udevd[1216]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. Feb 26 08:10:31 hostname kernel: cgroup: new mount options do not match the existing superblock, will be ignored Feb 26 08:10:32 hostname NetworkManager[1631]: [1488076832.0668] SettingsPlugin-Ofono: file doesn't exist: /var/lib/ofono Feb 26 08:10:32 hostname NetworkManager[1631]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Feb 26 08:10:32 hostname NetworkManager[1631]: [1488076832.5439] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Feb 26 08:10:32 hostname wpa_supplicant[1793]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none Feb 26 08:10:32 hostname wpa_supplicant[1793]: dbus: Failed to construct signal Feb 26 08:10:32 hostname wpa_supplicant[1793]: Could not read interface p2p-dev-wlp2s0 flags: No such device Feb 26 08:10:34 hostname content-hub-pee[1849]: Error parsing manifest for package 'com.hostname.gallery': com.hostname.gallery does not exist in any database for user hostname Feb 26 08:10:34 hostname content-hub-pee[1849]: Unable to get snap information for 'com.hostname.gallery': Status code is: 404 Feb 26 08:10:34 hostname content-hub-pee[1849]: Error parsing manifest for package 'com.hostname.gallery': com.hostname.gallery does not exist in any database for user hostname Feb 26 08:10:34 hostname content-hub-pee[1849]: Unable to get snap information for 'com.hostname.gallery': Status code is: 404 Feb 26 08:10:35 hostname click[1826]: hooks.vala:1216: User-level hook push-helper failed: Hook command '/usr/lib/hostname-push-client/click-hook-wrapper' failed: Child process exited with code 1 Feb 26 08:10:35 hostname systemd[1803]: Failed to start Run Click user-level hooks. Feb 26 08:10:35 hostname systemd[1803]: click-user-hooks.service: Failed with result 'exit-code'. Feb 26 08:10:35 hostname at-spi-bus-laun[1965]: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Feb 26 08:10:36 hostname org.gnome.ScreenSaver[1829]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Feb 26 08:10:36 hostname org.gnome.ScreenSaver[1829]: Unable to init server: Could not connect: Connection refused Feb 26 08:10:36 hostname gnome-screensav[2072]: Cannot open display: Feb 26 08:10:36 hostname bluetoothd[2053]: Failed to obtain handles for "Service Changed" characteristic Feb 26 08:10:36 hostname bluetoothd[2053]: Sap driver initialization failed. Feb 26 08:10:36 hostname bluetoothd[2053]: sap-server: Operation not permitted (1) Feb 26 08:10:36 hostname pulseaudio[2070]: [pulseaudio] authkey.c: Failed to open cookie file '/home/hostname/.config/pulse/cookie': No such file or directory Feb 26 08:10:36 hostname pulseaudio[2070]: [pulseaudio] authkey.c: Failed to load authentication key '/home/hostname/.config/pulse/cookie': No such file or directory Feb 26 08:10:36 hostname pulseaudio[2070]: [pulseaudio] authkey.c: Failed to open cookie file '/home/hostname/.pulse-cookie': No such file or directory Feb 26 08:10:36 hostname pulseaudio[2070]: [pulseaudio] authkey.c: Failed to load authentication key '/home/hostname/.pulse-cookie': No such file or directory Feb 26 08:10:36 hostname pulseaudio[2070]: [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 Feb 26 08:10:36 hostname pulseaudio[2148]: [pulseaudio] pid.c: Daemon already running. Feb 26 08:10:40 hostname unknown[2426]: cannot open display: Feb 26 08:10:40 hostname unknown[2428]: cannot open display: Feb 26 08:10:40 hostname org.freedesktop.Notifications[1829]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Feb 26 08:10:40 hostname org.freedesktop.Notifications[1829]: Unable to init server: Could not connect: Connection refused Feb 26 08:10:40 hostname org.freedesktop.Notifications[1829]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Feb 26 08:10:40 hostname org.freedesktop.Notifications[1829]: Unable to init server: Could not connect: Connection refused Feb 26 08:11:25 hostname org.freedesktop.secrets[1829]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used Feb 26 08:11:26 hostname dnsmasq[4607]: warning: no upstream servers configured Feb 26 08:11:26 hostname unknown[4648]: cannot open display: Feb 26 08:11:26 hostname org.freedesktop.Notifications[1829]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Feb 26 08:11:26 hostname org.freedesktop.Notifications[1829]: Unable to init server: Could not connect: Connection refused Feb 26 02:42:53 hostname kernel: EXT4-fs (sda2): VFS: Can't find ext4 filesystem Feb 26 02:42:53 hostname kernel: EXT4-fs (sda2): VFS: Can't find ext4 filesystem Feb 26 02:42:53 hostname kernel: EXT4-fs (sda2): VFS: Can't find ext4 filesystem Feb 26 02:42:53 hostname kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda2 Feb 26 02:42:53 hostname kernel: FAT-fs (sda2): bogus number of reserved sectors Feb 26 02:42:53 hostname kernel: XFS (sda2): Invalid superblock magic number Feb 26 02:42:53 hostname kernel: FAT-fs (sda2): bogus number of reserved sectors Feb 26 02:42:53 hostname kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda2. Feb 26 02:42:53 hostname kernel: hfsplus: unable to find HFS+ superblock Feb 26 02:42:53 hostname kernel: qnx4: no qnx4 filesystem (no root dir). Feb 26 02:42:53 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 Feb 26 02:42:53 hostname kernel: ufs: ufs_fill_super(): bad magic number Feb 26 02:42:53 hostname kernel: hfs: can't find a HFS filesystem on dev sda2 Feb 26 02:52:28 hostname NetworkManager[1631]: [1488057748.2165] sup-iface[0x559ca2eadb80,wlp2s0]: connection disconnected (reason -3) Feb 26 02:52:29 hostname org.freedesktop.Notifications[1829]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Feb 26 02:52:29 hostname org.freedesktop.Notifications[1829]: Unable to init server: Could not connect: Connection refused Feb 26 02:52:29 hostname notify-osd[27853]: cannot open display: Feb 26 02:55:12 hostname systemd-tmpfiles[3454]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Feb 26 03:00:43 hostname kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Feb 26 03:02:43 hostname /plugininstall.py[13787]: log-output -t ubiquity umount /target/cdrom Feb 26 03:03:40 hostname systemd-resolved[1742]: Using degraded feature set (UDP) for DNS server 127.0.1.1. Feb 26 03:03:40 hostname org.freedesktop.Notifications[1829]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Feb 26 03:03:40 hostname org.freedesktop.Notifications[1829]: Unable to init server: Could not connect: Connection refused Feb 26 03:03:40 hostname notify-osd[24322]: cannot open display: Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x010482a0) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): Filesystem has been set read-only Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x010482a0) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2b0b3782) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2b0b3782) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x4735b955) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x4735b955) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xc8f8ac24) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xc8f8ac24) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x75bca001) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x75bca001) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x073a90f9) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x073a90f9) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x5cc157f6) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x5cc157f6) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x78b9b139) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x78b9b139) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x30313035) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x30313035) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x305a0930) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x305a0930) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x6e691031) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x6e691031) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x656b7473) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x656b7473) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xa61ae3aa) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xa61ae3aa) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x76516383) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x76516383) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x140442f7) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x140442f7) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xa448300d) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xa448300d) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x31386664) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x31386664) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x0aff6aa8) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x0aff6aa8) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2e39065d) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2e39065d) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x632e0306) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x632e0306) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x60368430) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x60368430) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x11301308) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x11301308) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x32333338) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x32333338) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x72dd3cfc) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x72dd3cfc) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2bb01aab) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2bb01aab) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2040f233) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2040f233) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x02030306) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x02030306) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x304d8647) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x304d8647) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x1340814c) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x1340814c) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x35db0f60) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x35db0f60) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x42e92ea6) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x42e92ea6) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xe30e260a) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0xe30e260a) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x7d440e18) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x7d440e18) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x01018181) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x01018181) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x61577467) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x61577467) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x4eba0e25) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x4eba0e25) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x0d3e2020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x0d3e2020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x200a2020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x200a2020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x65763d6e) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x65763d6e) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x3d725257) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x3d725257) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2f202020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2f202020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x74727265) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x74727265) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x54530a0d) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x54530a0d) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x63736f69) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x63736f69) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x20202020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x20202020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x3d725257) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x3d725257) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2f202020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x2f202020) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x74305942) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x74305942) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x49744e2f) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x49744e2f) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x65424e6e) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x65424e6e) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x42706d71) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x42706d71) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x71344c6b) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x71344c6b) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x3755456f) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x3755456f) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x56466369) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x56466369) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x70776e77) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x70776e77) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x37554c37) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x37554c37) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x43316534) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x43316534) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x7038345a) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x7038345a) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x7572326e) Feb 26 03:04:54 hostname kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x7572326e) Feb 26 03:04:55 hostname kernel: EXT4-fs (sda2): VFS: Can't find ext4 filesystem Feb 26 03:04:55 hostname kernel: EXT4-fs (sda2): VFS: Can't find ext4 filesystem Feb 26 03:04:55 hostname kernel: EXT4-fs (sda2): VFS: Can't find ext4 filesystem Feb 26 03:04:55 hostname kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda2 Feb 26 03:04:55 hostname kernel: FAT-fs (sda2): bogus number of reserved sectors Feb 26 03:04:55 hostname kernel: XFS (sda2): Invalid superblock magic number Feb 26 03:04:55 hostname kernel: FAT-fs (sda2): bogus number of reserved sectors Feb 26 03:04:55 hostname kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda2. Feb 26 03:04:55 hostname kernel: hfsplus: unable to find HFS+ superblock Feb 26 03:04:55 hostname kernel: qnx4: no qnx4 filesystem (no root dir). Feb 26 03:04:55 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 Feb 26 03:04:55 hostname kernel: ufs: ufs_fill_super(): bad magic number Feb 26 03:04:55 hostname kernel: hfs: can't find a HFS filesystem on dev sda2 Feb 26 03:05:39 hostname /plugininstall.py[13787]: Exception during installation: Feb 26 03:05:39 hostname /plugininstall.py[13787]: Traceback (most recent call last): Feb 26 03:05:39 hostname /plugininstall.py[13787]: File "/usr/share/ubiquity/plugininstall.py", line 1710, in Feb 26 03:05:39 hostname /plugininstall.py[13787]: install.run() Feb 26 03:05:39 hostname /plugininstall.py[13787]: File "/usr/share/ubiquity/plugininstall.py", line 60, in wrapper Feb 26 03:05:39 hostname /plugininstall.py[13787]: func(self) Feb 26 03:05:39 hostname /plugininstall.py[13787]: File "/usr/share/ubiquity/plugininstall.py", line 223, in run Feb 26 03:05:39 hostname /plugininstall.py[13787]: self.configure_bootloader() Feb 26 03:05:39 hostname /plugininstall.py[13787]: File "/usr/share/ubiquity/plugininstall.py", line 967, in configure_bootloader Feb 26 03:05:39 hostname /plugininstall.py[13787]: "GrubInstaller failed with code %d" % ret) Feb 26 03:05:39 hostname /plugininstall.py[13787]: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1 Feb 26 03:05:39 hostname /plugininstall.py[13787]: