Hello All
I have been using LM for some years now and until recently 19.3 was booting quite fast - roughly 20 - 30 seconds but something happened and boot time went out to minutes so I eventually followed the upgrade path to 20 and boot time is still much slower than originally experienced.
Reading some instructions from Larry on this subject I hope I am providing the necessary info to be able to ask for help/guidance to reduce the boot time back to where it roughly has been.
peter@PeterDell1:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 32.763s
└─multi-user.target @1min 32.763s
└─smbd.service @1min 32.682s +80ms
└─nmbd.service @1min 32.616s +64ms
└─network-online.target @1min 32.610s
└─NetworkManager-wait-online.service @1min 30.677s +1.932s
└─NetworkManager.service @1min 30.512s +163ms
└─dbus.service @1min 30.509s
└─basic.target @1min 30.495s
└─sockets.target @1min 30.495s
└─uuidd.socket @1min 30.495s
└─sysinit.target @1min 30.491s
└─apparmor.service @1.181s +78ms
└─local-fs.target @1.181s
└─run-user-1000-gvfs.mount @1min 32.095s
└─run-user-1000.mount @1min 31.905s
└─local-fs-pre.target @443ms
└─keyboard-setup.service @307ms +136ms
└─systemd-journald.socket @301ms
└─-.mount @298ms
lines 1-23
I hope I have posted these results correctly - not sure as it does not look like other posts I have seen.
Any help is appreciated
Regards
Peter
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason:Topic automatically closed 6 months after creation. New replies are no longer allowed.
Cavemann wrote: ⤴Mon Nov 02, 2020 10:29 pm
I hope I am providing the necessary info to be able to ask for help/guidance to reduce the boot time back to where it roughly has been.
Not really, but no problem Some of the data was cut off due to the terminal not being wide enough anyway, so for the next set of instructions, widen the terminal...
peter@PeterDell1:~$ 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/sdb1 during installation
UUID=189ec425-59f0-4d0d-bbd8-e2b89481f283 / ext4 errors=remount-ro 0 1
# /boot was on /dev/sdb4 during installation
#UUID=753348eb-a9db-49b8-9d5d-dad498e50113 /boot ext4 defaults 0 2
# /home was on /dev/sdb2 during installation
UUID=e043a902-c263-470a-a0a4-63f9bf0cd2d0 /home ext4 defaults 0 2
# swap was on /dev/sdb3 during installation
UUID=277fede5-5b43-4f83-bae2-f0215dddfb97 none swap sw 0 0
UUID=753348eb-a9db-49b8-9d5d-dad498e50113 /boot ext4 defaults 0 2
peter@PeterDell1:~$
How is that this time please - terminal at full screen size - thought I did that previously but may have overlooked it as I practised a couple of times before posting.
Thanks
Peter
Hello again Kadaitcha Man
The # in front of the UUID=277fede5 ... certainly helped a lot with boot time under 1 minute now.
Also now that you point it out, originally I had the disk partitioned with a separate swap partition but in reading either the forum or some notes somewhere it was said (or I thought it was said) that the swap partition was no longer required in 19.3 as a dynamic swap file is created in the home partition - so I probably deleted it.
Maybe that makes some sense
Regards
Peter
Cavemann wrote: ⤴Tue Nov 03, 2020 6:00 am
... so I probably deleted it.
I was going to suggest that but didn't want to appear accusatory or rude
You can recreate the partition in the Disks tool and flag it as linux swap, then use lsblk to get the UUID and replace it in /etc/fstab. You don't have a swap file because it's not listed in fstab, so let me know if you want the instructions for one, which you don't need if you rebuild that partition and set the UUID in fstab.
Hello Kadaitcha Man
I have made a swap partition and edited the fstab file to show the new UUID.
Not sure that I have done it the conventional / correct way but it is there.
Boot now about 1 min 5 secs.
Below are the new results.
Wondering if there is anything else I can do for further improvements or is that where it stands?
Thank you for your help
Regards
Peter
peter@PeterDell1:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @3.767s
└─multi-user.target @3.767s
└─smbd.service @3.679s +86ms
└─nmbd.service @3.619s +58ms
└─network-online.target @3.614s
└─NetworkManager-wait-online.service @1.505s +2.107s
└─NetworkManager.service @1.265s +238ms
└─dbus.service @1.262s
└─basic.target @1.250s
└─sockets.target @1.250s
└─uuidd.socket @1.250s
└─sysinit.target @1.245s
└─apparmor.service @1.163s +81ms
└─local-fs.target @1.162s
└─run-user-1000-gvfs.mount @3.380s
└─run-user-1000.mount @3.176s
└─swap.target @1.122s
└─dev-sdb3.swap @1.074s +48ms
└─dev-sdb3.device @1.073s
peter@PeterDell1:~$
peter@PeterDell1:~$ 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/sdb1 during installation
UUID=189ec425-59f0-4d0d-bbd8-e2b89481f283 / ext4 errors=remount-ro 0 1
# /boot was on /dev/sdb4 during installation
#UUID=753348eb-a9db-49b8-9d5d-dad498e50113 /boot ext4 defaults 0 2
# /home was on /dev/sdb2 during installation
UUID=e043a902-c263-470a-a0a4-63f9bf0cd2d0 /home ext4 defaults 0 2
# swap was on /dev/sdb3 during installation
#UUID=f71dc60b-7022-4ae9-8821-66f7a703eb12 /swap swap sw 0 0
UUID=753348eb-a9db-49b8-9d5d-dad498e50113 /boot ext4 defaults 0 2
peter@PeterDell1:~$
Your network manager wait online service seems to be a recurring problem with both your readouts...I disabled mine when it acted up as it is not really necessary for startup.
Copy and paste the following command into your terminal to disable it, and then reboot the system and see if there is some improvement...DAMIEN
Hi Damien
Thank you for your reply
I have just now disabled Network Manager wait online as you suggested and boot up time is now about 45 seconds which is great.
This is much easier to live with so I am more than happy with the overall result from all help received.
I will mark as solved but happy to receive any further suggestions for improvement
Regards to all
Peter
peter@PeterDell1:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @7.560s
└─multi-user.target @7.560s
└─smbd.service @7.489s +70ms
└─nmbd.service @1.548s +5.938s
└─network-online.target @1.536s
└─network.target @1.536s
└─wpa_supplicant.service @1.332s +204ms
└─dbus.service @1.287s
└─basic.target @1.273s
└─sockets.target @1.273s
└─uuidd.socket @1.273s
└─sysinit.target @1.266s
└─apparmor.service @1.170s +96ms
└─local-fs.target @1.169s
└─run-user-1000-doc.mount @5.073s
└─run-user-1000.mount @3.303s
└─swap.target @1.127s
└─dev-sdb3.swap @1.086s +41ms
└─dev-sdb3.device @1.085s
peter@PeterDell1:~$
Above are the current results
Thank you for your suggestions
Regards
Peter
I have now disabled udisks2.service as you suggested but it does not seem to make much difference that I can detect so far??
Im thinking that you have done what can be done for now, especially if your still using a regular "spinner" type HDD vs an SSD drive, 45 or so seconds startup is satisfactory...DAMIEN
Hi Damien
There are 2 HDDs in this Dell Optiplex 7010 i7 3.4GHZ 8GB Ram which was originally win7 on a conventional HDD but rather than removing that drive I added a 480GB Evo SSD as the primary drive booting with LM so maybe the system is booting fast from the ssd but waiting for the other drive to catch up before finishing??
All help and guidance is certainly appreciated and it is quite liveable with as it is now.
Regards
Peter
Put a single #in front of that line #UUID=277fed..., save the changes, reboot and see if start up is any quicker.
# is to make a line information only, not working code or configuration
after that the system will boot without GUI or only before it with the only option for user and password text login.
to fix it you need to boot live usb, mount disk of the file, try to edit with privileges removing the added # in line and save, reboot to bring again the gui like before.
inxi -Fxz
laptop Kernel: 5.0.0-32-generic i686 bits Cinnamon 4.4.5 Linux Mint 19.3 Tricia TOSHIBA Satellite A135Dual Core Intel T2080 M Yonah, 800/1733 MHz, Intel Mobile 945GM/GMS Express Integrated Graphics, Drive 111.79 GiB, Memory 0.93 GiB
