• Home
  • Categories
  • WIKI
  • LANGUAGE: en
    • Slow boot after upgrade
    Community Discussion 875 views · 1 replies ·
    Tofloor
    poster avatar
    bezerra_3
    deepin
    2019-03-22 08:38
    Author
    Hi everyone!

    Recently, after upgrade 15.9.2, I has experienced a very slow boot. I have attached the logs with the informations about my problem. Any idea how to fix this? Thank you!
    1. bezerra@bezerra-PC:~$ systemd-analyze blame
    2.          18.059s nmbd.service
    3.          13.972s exim4.service
    4.          13.324s plymouth-quit-wait.service
    5.          13.319s ufw.service
    6.          12.911s dev-sda5.device
    7.          10.522s systemd-journal-flush.service
    8.          10.021s dde-filemanager-daemon.service
    9.           9.999s deepin-accounts-daemon.service
    10.           9.742s ModemManager.service
    11.           9.298s udisks2.service
    12.           9.278s keyboard-setup.service
    13.           7.863s NetworkManager.service
    14.           7.343s accounts-daemon.service
    15.           6.226s virtualbox.service
    16.           6.136s avahi-daemon.service
    17.           6.077s systemd-logind.service
    18.           5.997s wpa_supplicant.service
    19.           5.131s bluetooth.service
    20.           4.021s lvm2-monitor.service
    21.           3.397s systemd-udevd.service
    22.           3.281s colord.service
    23.           2.956s smbd.service
    24.           1.874s networking.service
    25.           1.701s lastore-daemon.service
    26.           1.611s systemd-sysusers.service
    27.           1.604s lightdm.service
    28.           1.568s systemd-hwdb-update.service
    29.           1.538s systemd-fsck@dev-disk-by\x2duuid-93a45fe9\x2d3dc6\x2d4cdc\x2d9c55\x2decedc4608b48.service
    30.           1.454s systemd-tmpfiles-setup-dev.service
    31.           1.276s systemd-binfmt.service
    32.           1.204s systemd-tmpfiles-setup.service
    33.           1.104s systemd-modules-load.service
    Copy the Code
    1. bezerra@bezerra-PC:~$ systemd-analyze critical-chain
    2. The time after the unit is active or started is printed after the "@" character.
    3. The time the unit takes to start is printed after the "+" character.

    5. graphical.target @49.093s
    6. └─multi-user.target @49.093s
    7.   └─smbd.service @46.136s +2.956s
    8.     └─nmbd.service @28.076s +18.059s
    9.       └─network-online.target @28.075s
    10.         └─network.target @28.074s
    11.           └─NetworkManager.service @20.210s +7.863s
    12.             └─dbus.service @20.206s
    13.               └─basic.target @19.626s
    14.                 └─sockets.target @19.625s
    15.                   └─dbus.socket @19.625s
    16.                     └─sysinit.target @19.535s
    17.                       └─systemd-timesyncd.service @18.806s +729ms
    18.                         └─systemd-tmpfiles-setup.service @17.599s +1.204s
    19.                           └─local-fs.target @17.598s
    20.                             └─home.mount @16.524s +1.073s
    21.                               └─systemd-fsck@dev-disk-by\x2duuid-93a45fe9\x2d3dc6\x2d4cdc\x2d9c55\x2decedc4608b48.service @14.949
    22.                                 └─dev-disk-by\x2duuid-93a45fe9\x2d3dc6\x2d4cdc\x2d9c55\x2decedc4608b48.device @14.948s
    Copy the Code

    Reply Favorite View the author
    All Replies
    avatar
    suzuki88
    deepin
    2019-03-22 23:51
    #1
    yes, the same problem. the hard drive keeps running.
    Reply View the author