My boot is horribly slow, and I don't know why.

$ systemd-analyze 
Startup finished in 10.975s (kernel) + 49.732s (userspace) = 1min 708ms
$ systemd-analyze blame 
         34.971s apt-daily.service
         20.590s snapd.refresh.service
         17.113s grub-common.service
         16.033s apport.service
         16.027s networking.service
         15.894s ondemand.service
         15.860s irqbalance.service
         15.655s speech-dispatcher.service
         11.695s ModemManager.service
          9.772s accounts-daemon.service
          8.626s NetworkManager-wait-online.service
          8.058s systemd-logind.service
          8.053s bluetooth.service
          7.944s gpu-manager.service
          7.896s alsa-restore.service
          7.892s pppd-dns.service
          7.882s rsyslog.service
          7.860s avahi-daemon.service
          7.844s dev-sda1.device
          7.842s systemd-user-sessions.service
          7.648s lightdm.service
          7.610s teamviewerd.service
          6.445s apparmor.service

Also, during boot-up, I see a message that says something like:

device descriptor read/all, error -62
ata1 softreset failed (device not ready) #most of the times
error loading journal #(sometimes)
Test WP failed, assume Write Enabled
Asking for cache data failed     #most of the times
Assuming drive cache: write through

apt-daily.service slows the boot the most. Any idea on how to tackle that?

I have Ubuntu MATE 16.04.

  • I had this same issue. You can see in that link that I stripped away so much to speed it up that it was causing issues. I changed over to Ubuntu Gnome 14.04 and it's been lightning fast ever since and went from booting in 55 seconds to 20 seconds. After changing over to SSD it now boots in about 4 seconds.
    – Delorean
    Sep 28, 2016 at 20:20
  • This used to happen to me, but when you first install Ubuntu, you get the option to divide your hard drive. This is very useful also for people who have low ram. There are other ways. Look at this link. help.ubuntu.com/stable/ubuntu-help/disk-partitions.html I have 1 GB for booting in my hard drive, and it works very quickly. Hope that helps!
    – schung
    Oct 5, 2016 at 0:44

3 Answers 3


This is Debian bug #844453. apt-daily.service shouldn't be run during boot, but only some time afterward.

As a workaround, do sudo systemctl edit apt-daily.timer and paste the following text into the editor window:

# apt-daily timer configuration override

This changes the "timer" that triggers apt-daily.service to run at a random time between 15 min and 45 min after boot, and once a day thereafter. See the systemd.timer manpage for additional (not very well written, alas) explanation of what this means.

  • Does this apply to any of the services listed by the systemd-analyze blame command ? Oct 21, 2017 at 21:04
  • @MuhammadGelbana I don't understand what you are trying to ask me.
    – zwol
    Oct 22, 2017 at 2:02
  • 1
    I'm asking if I can run a similar command such as sudo systemctl edit snapd.refresh.timer and add the same text you posted in your answer to override the timer configuration for snapd.refresh ? Oct 22, 2017 at 8:18
  • 1
    It should work for anything that is actually a "timer", yes, but not for arbitrary services started on boot.
    – zwol
    Oct 22, 2017 at 13:37
  • 1
    @openCivilisation Yes, create /etc/systemd/system/apt-daily.timer.d/override.conf and put the text shown there -- which is exactly what systemctl edit does. You'll have to run systemctl daemon-reload or reboot afterward. See serverfault.com/questions/840996/…
    – zwol
    Feb 27, 2021 at 0:18

The other answer addresses the second block of text in the question.

For me, to solve apt-daily.service taking forever, this Ubuntu Forums post seems to have worked.

issue these commands as an example of how to edit /etc/systemd/system.conf

sudo cp /etc/systemd/system.conf /etc/systemd/system.conf.bak 

That will make a back-up for safety.

gksudo gedit /etc/systemd/system.conf 

Look for and change these 2 lines:


Mine now look like this:


Been doing that for year now and nothing bad has come of it.

Remove the leading #'s which disable the line, and change the value.

  • 1
    I could not boot with this timeouts and had to comment this lines back from recovery mode.
    – Yuri Gor
    Feb 2, 2019 at 16:14
  • 1
    @YuriGor my apologies, i guess something changed since 16.10
    – cat
    Feb 5, 2019 at 19:49
  • 1
    Mine is 18.04. I don't remember clearly, but it was an issue related to sda, so probably my hdd takes too long to mount or whatever.
    – Yuri Gor
    Feb 6, 2019 at 18:39

If it's a desktop, open it and disconnect then reconnect All HDD cables including MB.

Failing that, it sounds like your HDD is timing out. BACKUP all data now.

Burn Live network install of Ubuntu to suite your system, boot to Try Ubuntu. Then run Gparted: by default it checks for HDD read errors. If you have a backup of all your data maybe someone else could advise.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .