gerj52 wrote:Thanks guys, not sure I know what I'm doing but will play around with your suggestions and hopefully speed things up.
I think most of us spend 90% of our time not sure that we know what we are doing. Especially in parenting... Playing around with the system is often a great way to learn. But...
Back up Everything! When playing in Root, I have learned a little slung mug goes a long way.
If you feel uncertain, remember that You Are Not Annoying. This forum is not here for Swarfendor or Zorins health, it is here for yours.
Ask, clarify, seek out more information.
For example, in my post above, I suggested you use a terminal command. You might say, "Ok but what exactly am I looking for?"
A: Any process that shows a longer time than the rest.
Trying it out on my machine, I enter "systemd-analyze" and my output looks like:
- Code:
Aspire-V3-551:~$ systemd-analyze
Startup finished in 6.542s (kernel) + 44.504s (userspace) = 51.047s
graphical.target reached after 44.491s in userspace
Not horrible
- Code:
systemd-analyze critical-chain
- Code:
Aspire-V3-551:~$ 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 @44.491s
└─multi-user.target @44.491s
└─kerneloops.service @43.804s +686ms
└─network-online.target @43.523s
└─NetworkManager-wait-online.service @32.793s +10.729s
└─NetworkManager.service @26.357s +6.428s
└─dbus.service @21.332s
└─basic.target @21.294s
└─sockets.target @21.294s
└─snapd.socket @21.292s +1ms
└─sysinit.target @21.182s
└─systemd-timesyncd.service @20.794s +387ms
└─systemd-tmpfiles-setup.service @20.313s +435ms
└─systemd-journal-flush.service @4.784s +14.706s
└─systemd-journald.service @4.011s +770ms
└─systemd-journald-dev-log.socket @4.008s
└─system.slice @3.886s
└─-.slice @3.792s
For the line NetworkManager-wait-online.service, we see a loading time of about 32.8 seconds.
systemd-timesyncd.service took about 20.8 seconds to load. And network-online.target took 43.5 seconds. Now, what if you see an entry in there that shows a loading time of Over 60 seconds? That would be Slow and suggests that it is waiting for something else. Often, what it is waiting for is no longer installed or has not yet been installed and it waits until that times out and then starts the next loading process.
That would be the clue to look for, if it is there. If everything looks normal, we would need to try something else to look for clues.
The next suggestion was to look in var/log/boot (I found nothing in mine, the log was empty) and var/log/syslog. From your home folder, navigate to "other places" or "File system" depending on which file manager you are using- but simply put, you are moving Upward. If you look at the Toolbar in your file manager and see an Up Arrow (Enable the toolbar under 'view' from the menubar if you do not see a toolbar) hit that up arrow until nothing happens anymore, you have reached the top.
You will see your system folders: bin, boot, dev, home, lib, etc., uhhhh... etc...
In that grouping is also the 'var' folder. Open that. Then open the folder titled 'log.' Scroll down to 'boot.log' and to 'syslog' and open them.
In the syslog, you are looking for anything that tried to initialize but failed. It sounds and looks harder than it is; you will see it noted that the service failed or was unavailable- so you are really scanning as you read over it for those kinds of keywords. No heavy handed interpretation necessary.
