So in both cases Ubuntu MATE is the only OS installed on the boot disk - correct?
If so possibly GRUB menu is showing and waiting for input [10 seconds]
Please paste the output from inxi -ACDMNSG one of your machines [we'll work on 1 at a time].
In order to use this command enter a MATE terminal by either:
Accessing menu Applications > System Tools > MATE Terminal or
pressing Ctrl+Alt+t keys simultaneously
use the code tag </> [see below] to mark the output
I’ve seen this 90 sec “stop job is running…” previously in 15.10, but only occasionally, and now in the last 2 shut-downs in 16.04 it is here again. I did my fresh install just a few days ago! Doesn’t look like any solution is coming anytime soon. I also use U. Mate 14.04, and it never happens on that (no systemd!).
I didn’t know about the timeout time being user setable. I will use that. Thanks for this tip!
In 15.10, It didn't happen very often, and I didn't know when, so I pretty much ignored it. That 15.10 has now been replaced. We'll see if two of these in a row is unusual, or a portent of something worse. In any case, changing the delay will help.
I just had the occasion to reboot my Dell laptop So instead I choose to shut down and do a fresh start from power up. Here are the times:
1-from clicking shut down to full power off > 7.68 sec
2-from power up to first grub screen >>>>>>> 16 sec
3-from power up to login prompt >>>>>>>>>> 53 sec
4-from power up to running >>>>>>>>>>>>> 72 sec
Processor 4x Intel® Core™ i3 CPU M 330 @ 2.13GHz
Memory 7839MB (1320MB used)
ATA TOSHIBA MK5056GS [500GB 7200 RPM 16MB Cache SATA 3.0]
That is slow! I tested a single core 64 bit boot in VirtualBox. It took 40 seconds from starting the virtual machine to up and running. You night want to look at your dmesg log to see if some device is hanging up the boot.
I’m attempting to speed up my laptop boot times [posted above 72 seconds]. I used [quote=“lah7, post:10, topic:5622”]
systemd-analyze blame[/quote] and found the top 26 listed processes on my system totaled 2.05 minutes. So can I assume that the listed programs are concurrent?
My slowest 10
I'm not quite sure to whom That Is Slow! refers. Additionally booting a guest OS in an already running host is probably not a good comparison.
I suggest comparing boot times we use a benchmark to 'handicap' stastics ... I found a benchmark utility in Software Boutique that's gui driven and provides an extremely comprehensive output.
Certainly the entire report will be TMI for posting, but type cpu and 1 benchmark would provide others a comparison. Here's the type of output hardinfo produces: Computer
Processor4x Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz
Memory7838MB (1289MB used)
Operating SystemUbuntu 16.04 LTS
User Namepfeiffep (Pete)
Date/TimeSat 30 Apr 2016 02:42:50 PM EDT FPU Raytracing
This Machine1066 MHz5.699
Intel(R) Celeron(R) M processor 1.50GHz(null)40.8816714
PowerPC 740/750 (280.00MHz)(null)161.312647
The Operating System identifies OS = Ubuntu, in my case really UM 16.04LTS
I’ll answer …
to view the contents of the file cat /etc/systemd/system.conf or less /etc/systemd/system.conf
Editing system files and making a mistake can render your computer un-bootable
issue these commands as an example of how to edit /etc/systemd/system.conf
sudo prefacing the command elevates the privilege [you must enter you password but no text will appear]
sudo cp /etc/systemd/system.conf /etc/systemd/system.conf.bu above makes a safety copy
gksudo pluma /etc/systemd/system.conf launches MATE’s text editor with elevated privilege
Remember to save th file after you’ve made the desired changes.
Since you had to ask how … I strongly suggest posting here for guidance prior to making changes. Also if you want to learn please do practice on some files - the command cp will make a copy to your home directory.
i found out, that my installation of ubuntu mate 16.04 was also a bit slow. “sudo fdisk -l” showed me, that my linux partition was not correctly aligned on the ssd. could this be a reason, why its starting slowly?
systemctl mask name.service is rather drastic - rendering the actual unit file inaccessible to systemd.
this action can be reversed by systemctl unmask name.service
whereas systemctl disable name.service stops the service from being automatically started
Providing you absolutely know a service is never required in your setting disablle will work, OTOH preventing automatic start up at boot by setting disable renders the service available to systemd if required later.
in short:
mask = never available
disable = won’t start at boot available later if needed