I recently installed LM on my hard disk and was amazed at how quickly it booted - seconds. That was the 1st time, but after the 2nd or 3rd time the boot slowed to minutes.
Any suggestions?
What’s the output from:
dmesg | grep -i "error\|warn\|fail"
and
cat /etc/fstab
and
sudo blkid
and
cat /etc/initramfs-tools/conf.d/resume
and
systemd-analyze blame | more
and
systemd-analyze critical-chain
peter@peter-Lenovo-G510:~$ dmesg | grep -i "error\|warn\|fail"
[ 0.000000] ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x2B9E (20170831/psloop-247)
[ 0.136397] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[ 2.340030] pci 0000:00:1a.0: EHCI: BIOS handoff failed (BIOS bug?) 01010001
[ 4.340029] pci 0000:00:1d.0: EHCI: BIOS handoff failed (BIOS bug?) 01010001
[ 5.428190] RAS: Correctable Errors collector initialized.
[ 5.894969] ACPI Error: [AR02] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[ 5.894980] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0._PRT, AE_NOT_FOUND (20170831/psparse-550)
[ 6.048180] radeon 0000:01:00.0: failed VCE resume (-110).
[ 10.497041] random: 7 urandom warning(s) missed due to ratelimiting
[ 15.505321] EXT4-fs (sda9): re-mounted. Opts: errors=remount-ro
[ 27.856793] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20170831/utaddress-247)
[ 27.856813] ACPI Warning: SystemIO range 0x0000000000000840-0x000000000000084F conflicts with OpRegion 0x0000000000000800-0x0000000000000BFF (\GPR) (20170831/utaddress-247)
[ 27.856818] ACPI Warning: SystemIO range 0x0000000000000840-0x000000000000084F conflicts with OpRegion 0x0000000000000800-0x000000000000085F (\_SB.PCI0.PEG0.PEGP.GPIO) (20170831/utaddress-247)
[ 27.856823] ACPI Warning: SystemIO range 0x0000000000000830-0x000000000000083F conflicts with OpRegion 0x0000000000000800-0x0000000000000BFF (\GPR) (20170831/utaddress-247)
[ 27.856827] ACPI Warning: SystemIO range 0x0000000000000830-0x000000000000083F conflicts with OpRegion 0x0000000000000800-0x000000000000085F (\_SB.PCI0.PEG0.PEGP.GPIO) (20170831/utaddress-247)
[ 27.856831] ACPI Warning: SystemIO range 0x0000000000000800-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x0000000000000BFF (\GPR) (20170831/utaddress-247)
[ 27.856835] ACPI Warning: SystemIO range 0x0000000000000800-0x000000000000082F conflicts with OpRegion 0x0000000000000810-0x0000000000000813 (\IO_D) (20170831/utaddress-247)
[ 27.856839] ACPI Warning: SystemIO range 0x0000000000000800-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000085F (\_SB.PCI0.PEG0.PEGP.GPIO) (20170831/utaddress-247)
[ 28.382435] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 29.512804] radeon 0000:01:00.0: failed VCE resume (-110).
[ 47.519922] radeon 0000:01:00.0: failed VCE resume (-110).
[ 3671.760154] ERROR @wl_notify_scan_status :
[ 3671.760155] wlp8s0 Scan_results error (-22)
[ 3672.175525] radeon 0000:01:00.0: failed VCE resume (-110).
[ 3674.149047] mce: [Hardware Error]: Machine check events logged
[ 3674.327468] radeon 0000:01:00.0: failed VCE resume (-110).
[ 4510.323785] radeon 0000:01:00.0: failed VCE resume (-110).
[ 7008.893210] radeon 0000:01:00.0: failed VCE resume (-110).
peter@peter-Lenovo-G510:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda9 during installation
UUID=1190273a-e2ff-4ed1-a8b5-881c64b8b93a / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda2 during installation
UUID=928F-0273 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda10 during installation
UUID=a007ec6b-6585-4d42-913b-bcd8840b9656 /home ext4 defaults 0 2
/swapfile none swap sw 0 0
# UUID=D6E5-7E83 /media/ntfs ntfs rw,nosuid,nodev,noatime,allow_other 0 0
peter@peter-Lenovo-G510:~$ sudo blkid
[sudo] password for peter:
/dev/sda1: LABEL="WINRE_DRV" UUID="A8088CA4088C735C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="7db720a7-bd6c-42d3-afb6-89b502d8f824"
/dev/sda2: LABEL="SYSTEM_DRV" UUID="928F-0273" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="8f7aa258-d05c-4e2d-a69f-c291690fc5bc"
/dev/sda3: LABEL="LRS_ESP" UUID="3C8F-43EE" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="be4f8915-aeca-44c1-abf2-22fea6478249"
/dev/sda5: LABEL="Windows8_OS" UUID="5E7E2C417E2C1475" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="7a2b89fa-6e22-4520-9fc7-64827ef542c9"
/dev/sda6: UUID="248A79AE8A797D5C" TYPE="ntfs" PARTUUID="6c567377-f550-4917-86ff-87da0734b6e6"
/dev/sda7: LABEL="LENOVO" UUID="14F299DAF299C102" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a646b38a-5c18-453a-9350-e87cbc9df7da"
/dev/sda8: LABEL="PBR_DRV" UUID="907495157494FEE2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="0af496ed-74ae-4110-974d-c2464d1a3724"
/dev/sda9: UUID="1190273a-e2ff-4ed1-a8b5-881c64b8b93a" TYPE="ext4" PARTUUID="1b9ffaee-e3cf-4438-a094-4dc514931853"
/dev/sda10: UUID="a007ec6b-6585-4d42-913b-bcd8840b9656" TYPE="ext4" PARTUUID="2ef008c0-c3e3-428f-b21f-74a27d6f75b4"
/dev/sda4: PARTLABEL="Microsoft reserved partition" PARTUUID="ea95cc33-3d4f-4768-a1c3-bec1822bbb98"
/dev/mapper/veracrypt1: UUID="D6E5-7E83" TYPE="vfat"
/dev/sdb1: LABEL="Timeshift" UUID="082a14c7-ba1e-43dc-9963-1e6c9492b0ce" TYPE="ext4" PARTUUID="5bf7dc68-01"
peter@peter-Lenovo-G510:~$ cat /etc/initramfs-tools/conf.d/resume
cat: /etc/initramfs-tools/conf.d/resume: No such file or directory
peter@peter-Lenovo-G510:~$ systemd-analyze blame | more
16.784s systemd-journal-flush.service
14.434s dev-sda9.device
12.549s lvm2-monitor.service
10.770s ufw.service
10.449s systemd-modules-load.service
10.183s keyboard-setup.service
9.875s systemd-tmpfiles-setup-dev.service
9.802s swapfile.swap
3.353s networkd-dispatcher.service
2.933s systemd-fsck@dev-disk-by\x2duuid-a007ec6b\x2d6585\x2d4d42\x2d91
3b\x2dbcd8840b9656.service
2.629s ubuntu-system-adjustments.service
2.539s udisks2.service
2.363s NetworkManager.service
2.204s systemd-fsck@dev-disk-by\x2duuid-928F\x2d0273.service
1.765s accounts-daemon.service
1.730s ModemManager.service
1.477s thermald.service
1.441s tlp.service
1.421s dns-clean.service
1.328s grub-common.service
1.153s systemd-udevd.service
1.113s systemd-sysctl.service
peter@peter-Lenovo-G510:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @24.944s
??multi-user.target @24.943s
??getty.target @24.943s
??getty@tty1.service @24.943s
??system-getty.slice @24.942s
??setvtrgb.service @24.887s +55ms
??systemd-user-sessions.service @24.658s +3ms
??network.target @24.645s
??NetworkManager.service @22.281s +2.363s
??dbus.service @21.341s
??basic.target @21.333s
??sockets.target @21.333s
??acpid.socket @21.333s
??sysinit.target @21.293s
??systemd-update-utmp.service @21.195s +97ms
??systemd-tmpfiles-setup.service @20.860s +230ms
??local-fs.target @20.857s
??boot-efi.mount @20.526s +330ms
??systemd-fsck@dev-disk-by\x2duuid-928F\x2d027
??dev-disk-by\x2duuid-928F\x2d0273.device @1
Okay can you run:
dmesg > ~/Desktop/dmesg.txt
you’ll then find a file called dmesg.txt on your desktop.
Can you host that file somewhere like
http://www.tinyupload.com/
and post a link to it
Thanks Mark.
You can download it from here http://s000.tinyupload.com/?file_id=04079914648351734883
What’s the output from
sudo dmsetup info /dev/dm-0
peter@peter-Lenovo-G510:~$ sudo dmsetup info /dev/dm-0
[sudo] password for peter:
Name: veracrypt1
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 253, 0
Number of targets: 1
Let me give an explanation too.
You have probably heard of VeraCrypt, the successor to TrueCrypt. On my Windows NTFS drive I have a VC container. When I installed Mint, I was flabbergasted to see that Mint detected ALL the Windows files - system files and personal files - and that I could access them. I could mount the VC container like before, which pleased me no end because that way I did not have to move any of my personal files, they could stay in place and be shared between Mint and Windows. I mount the VC container manually every day after booting my computer to Mint.
The only oddity I have found is that sometimes - I have not yet identified what causes it - all the folders and files in VC are locked and inaccessible. In the right hand column of the file explorer I right-click on the VC container and unmount it. Except it does not really unmount, because when I right-click to mount it, it says it is already mounted, but all the folders and files are back to normal, i.e. unlocked and accessible and usable.
well dmesg is suggesting the filesystem of dm-0 may be corrupt … what it probably means is it wasn’t unmounted properly at some point.
Boot into Windows … mount the encrypted volume … run a windows disk check … unmount the encrypted volume … shutdown, and boot into Mint.
did it boot faster this time ?
A few months ago, before I installed Mint, when I would mount the encrypted drive (Q) I got this message:
‘ Warning: Thefilesystem on the volume mounted as 'Q:' was not cleanly
; dismounted and thus may contain errors. Using a corrupted filesystem
can cause data loss or data corruption.
Note: Before you physically remove or switch off a device (such as a
USB flash drive or an external hard drive) where a mounted VeraCrypt
volume resides, you should always dismount the VeraCrypt volume in
VeraCrypt first.
Do you want Windows to attempt to detect and fix errors (if any) on the
?lesystem?
When I 1st saw that message I ran “scannow”, which did not find any problems so I did not take any further action. The encrypted volume functioned fine.
Anyway, I did what you said: booted into Windows, mounted the encrypted volume, ran CHKDSK, then dismounted the encrypted, shut down, booted into Mint, which did not show an improvement in boot time. The result from CHKDSK was as follows:
Windows has scanned the file system and found
No further action is required.
831458303 KB total disk space.
229841640 KB in 235510 files.
162200 KB in 50736 indexes.
0 KB in bad sectors.
1434559 KB in use by the system.
65536 KB occupied by the log file.
600019904 KB available on disk.
4096 bytes in each allocation unit.
207864575 total allocation units on disk.
150004976 allocation units available on disk.
As before, no problems were encountered, so I did not take any further action.
Okay can you again run:
dmesg > ~/Desktop/dmesg.txt
you’ll then find a file called dmesg.txt on your desktop.
Can you host that file somewhere like
http://www.tinyupload.com/
and post a link to it
Mark, any idea?
Does running
sudo journalctl --vacuum-time=1d
speed up your next boot ?