![]() ![]() Once we know that, we can dig deeper and get to the root of the problem. └─systemd-journald.socket using all this information from systemd-analyze we can find out what is slowing the startup process. The time the unit takes to start is printed after the "+" character. The time after the unit is active or started is printed after the character. The slow starting services will be highlighted in red. Similar to blame, but it takes into account dependencies between services. blameĭisplays an ordered list of services, from slowest to fastest. The init process, in our case is systemd and represents time spent in userspace. After the kernel finished its startup it will launch the init process (which usually has the id 1). Kernel time is used for loading drivers and other initializations. If a considerable amount of time is spent here it might mean that the bootloader can’t find some disks or maybe some kernel boot parameters are wrong. Time in loader is the time needed by your bootloader, typically Grub. If a lot of time is spent in firmware, there might be an hardware issue. If you use an older system, you may not see the firmware data as this is available only for EFI/UEFI systems. The values in this example are for my laptop which has an i7 processor, 16GB of RAM and a 512GB SSD. Startup finished in 7.541s (firmware) + 5.696s (loader) + 4.053s (kernel) + 8.206s (userspace) = 25.498sgraphical.target reached after 8.068s in userspace Shows the amount of time spent after the bootloader has given control to the kernel up until the userspace finished initialization. When opening the generated svg, you should see something similiar to These bars represent the time it took for that process to start. Outputs the svg code with all the started services, their dependencies and how long it took for them to start.įor a better visualization you can pipe the output to an svg file and then open it with an image viewer: The options that we are interested in are: But from a time perspective we’re only interested in a few of them (to see the rest of the options available you can run “man systemd-analyze” in a terminal): After installing it, restart your computer and forget about it. Open a terminal and use the following command to install preload: sudo apt install preload. There are around a dozen options that we can use from systemd-analyze to see where the startup bottleneck is. Install preload to speed up application load time: Preload is a daemon that runs in the background and analyzes user behavior and frequently run applications. “systemd-analyze” gives us information about what programs are run on startup and how much time they need to start. Systemd is not something specific to Ubuntu, but rather an industry standard that other major distributions have adopted as well: Debian, Fedora and CentOS to name a few. Since version 15.04, Ubuntu has switched from upstart to systemd as the default system and service manager. To install the OpenVPN client on Linux, it is. In my opinion the easiest way to start is by using “systemd-analyze” which is part of systemd. On Ubuntu and Debian, when you install the openvpn package, it is automatically configured to start at boot time. ![]() There are a lot of things that can go wrong: a lingering service, a bad config file, a wrong disk uuid in fstab and others. So what I need to do here is to replace the UUID value with the correct one copied from Disks utility.Investigating why Ubuntu boots slowly can be difficult. ![]() When it opens, check the Swap partition, and it obviously that the UUID value does not match the one in /etc/fstab.ĥ. Launch Disks utility from application menu.Ĥ. When the file opens, you’ll see something look like this:Īs the top picture shows, “UUID=1cdb9a5b-01a7-4b7b-a0ad-ce73676bb7c1”, mounting the Swap partition takes 1 minute and 30 seconds to boot up Ubuntu.ģ. It will open fstab (file system table) configuration file with gedit text editor.Ģ. Type user password (no asterisk feedback) when it prompts. When it opens, run command: sudo -H gedit /etc/fstab Open terminal from application menu or by pressing Ctrl+Alt+T on keyboard. UPDATE: First make a back up of /etc/fstab before editing the file by running command: sudo cp /etc/fstab /etc/fstab-backupġ. To fix the problem, do following steps one by one: “ A start job is running for dev-disk-by\x2uuid …(35s \ 1min 30s)” When it was booting into the purple screen, press F2 to show the white and black text screen. It was stuck at the purple screen with Ubuntu logo in center for more than 1 minute before booting into the login screen. Ubuntu 18.04 is quite slow to boot up in my laptop in the last few days. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |