• Home
  • Categories
  • WIKI
  • LANGUAGE: en
    • deepin每次启动都要花很久(2分钟左右)，求帮忙分析启动日志
    Experiences and Insight 7448 views · 7 replies ·
    Tofloor
    poster avatar
    mutong
    deepin
    2017-11-26 20:52
    Author
    日志中出现的FAILED：
    1. [FAILED] Failed to start Load Kernel Modules.
    2. See 'systemctl status systemd-modules-load.service' for details.
    Copy the Code
    全部启动日志：
    1. /dev/sdb5: clean, 297745/2689904 files, 3092076/10751744 blocks
    2. [FAILED] Failed to start Load Kernel Modules.
    3. See 'systemctl status systemd-modules-load.service' for details.
    4.          Mounting FUSE Control File System...
    5.          Starting Apply Kernel Variables...
    6. [  OK  ] Mounted FUSE Control File System.
      [  OK  ] Started Create Static Device Nodes in /dev.
    7.          Starting udev Kernel Device Manager...
    8. [  OK  ] Started Apply Kernel Variables.
    9. [  OK  ] Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
    10. [  OK  ] Started udev Kernel Device Manager.
    11.          Starting Remount Root and Kernel File Systems...
    12. [  OK  ] Started Remount Root and Kernel File Systems.
    13.          Starting Flush Journal to Persistent Storage...
    14.          Starting udev Coldplug all Devices...
    15.          Starting Load/Save Random Seed...
    16. [  OK  ] Reached target Local File Systems (Pre).
    17. [  OK  ] Started udev Coldplug all Devices.
    18.          Starting Show Plymouth Boot Screen...
    19. [  OK  ] Started Load/Save Random Seed.
    20. [  OK  ] Started Show Plymouth Boot Screen.
    21. [  OK  ] Reached target Encrypted Volumes.
    22. [  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
    23. [  OK  ] Created slice system-systemd\x2dbacklight.slice.
    24.          Starting Load/Save Screen Backlight Brightness of backlight:acpi_video1...
    25.          Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...
    26. [  OK  ] Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
    27. [  OK  ] Started Load/Save Screen Backlight Brightness of backlight:acpi_video1.
    28.          Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
    29. [  OK  ] Started Load/Save Screen Backlight Brightness of backlight:acpi_video0.
    30. [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
    31.          Starting Load/Save RF Kill Switch Status...
    32. [  OK  ] Started Load/Save RF Kill Switch Status.
    33.          Starting Show Plymouth Boot Screen...
    34.          Starting Load Kernel Modules...
    35. [  OK  ] Reached target Sound Card.
    36. [  OK  ] Found device HITACHI_HTS547550A9E384 6.
    37.          Starting File System Check on /dev/disk/by-uuid/09ab3bf6-b227-40f5-9ca6-acd40f5302e6...
    38. [  OK  ] Started Show Plymouth Boot Screen.
    39. [  OK  ] Started File System Check Daemon to report status.
    40. [FAILED] Failed to start Load Kernel Modules.
    41. See 'systemctl status systemd-modules-load.service' for details.
    42. [  OK  ] Started Flush Journal to Persistent Storage.
    43. [  OK  ] Started File System Check on /dev/disk/by-uuid/09ab3bf6-b227-40f5-9ca6-acd40f5302e6.
    44.          Mounting /home...
    45. [  OK  ] Mounted /home.
    46. [  OK  ] Reached target Local File Systems.
    47.          Starting Tell Plymouth To Write Out Runtime Data...
    48.          Starting Create Volatile Files and Directories...
    49.          Starting Raise network interfaces...
    50. [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
    51. [  OK  ] Started Create Volatile Files and Directories.
    52.          Starting Network Time Synchronization...
    53.          Starting Update UTMP about System Boot/Shutdown...
    54. [  OK  ] Started Update UTMP about System Boot/Shutdown.
    55. [  OK  ] Started Network Time Synchronization.
    56. [  OK  ] Reached target System Time Synchronized.
    57. [  OK  ] Reached target System Initialization.
    58. [  OK  ] Listening on ACPID Listen Socket.
    59. [  OK  ] Started Daily apt activities.
    60. [  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
    61. [  OK  ] Listening on D-Bus System Message Bus Socket.
    62. [  OK  ] Started Daily Cleanup of Temporary Directories.
    63. [  OK  ] Started ACPI Events Check.
    64. [  OK  ] Listening on CUPS Scheduler.
    65. [  OK  ] Reached target Sockets.
    66. [  OK  ] Started Clean PHP session files every 30 mins.
    67. [  OK  ] Reached target Timers.
    68. [  OK  ] Started CUPS Scheduler.
    69. [  OK  ] Reached target Paths.
    70. [  OK  ] Reached target Basic System.
    71.          Starting Avahi mDNS/DNS-SD Stack...
    72.          Starting Save/Restore Sound Card State...
    73. [  OK  ] Reached target Login Prompts.
    74.          Starting Modem Manager...
    75. [  OK  ] Started irqbalance daemon.
    76.          Starting Accounts Service...
    77.          Starting Login Service...
    78. [  OK  ] Started Read some files that necessary to DDE before DDE starts..
    79. [  OK  ] Started Regular background program processing daemon.
    80. [  OK  ] Started D-Bus System Message Bus.
    81. [  OK  ] Started Avahi mDNS/DNS-SD Stack.
    82.          Starting Network Manager...
    83.          Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
    84. [  OK  ] Started CUPS Scheduler.
    85.          Starting Bluetooth service...
    86. [  OK  ] Started Save/Restore Sound Card State.
    87.          Starting Authorization Manager...
    88. [  OK  ] Started Login Service.
    89. [  OK  ] Started Raise network interfaces.
    90. [  OK  ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
    91. [  OK  ] Started Authorization Manager.
    92. [  OK  ] Started Accounts Service.
    93. [  OK  ] Started Bluetooth service.
    94. [  OK  ] Reached target Bluetooth.
    95.          Starting Hostname Service...
    96. [  OK  ] Started Hostname Service.
    97. [  OK  ] Started Network Manager.
    98. [  OK  ] Reached target Network.
    99.          Starting Deepin Lastore Daemon...
    100.          Starting Permit User Sessions...
    101.          Starting MySQL Community Server...
    102.          Starting The Apache HTTP Server...
    103.          Starting Network Manager Wait Online...
    104. [  OK  ] Started Permit User Sessions.
    105.          Starting Hold until boot process finishes up...
    106.          Starting Light Display Manager...
    107. [  OK  ] Started Deepin Lastore Daemon.
    Copy the Code
    执行  systemctl status systemd-modules-load.service 命令后得到的结果如下：
    1. ● systemd-modules-load.service - Load Kernel Modules
    2.    Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
    3.    Active: failed (Result: exit-code) since Sun 2017-11-26 04:41:09 CST; 8h ago
    4.      Docs: man:systemd-modules-load.service(8)
    5.            man:modules-load.d(5)
    6.   Process: 440 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
    7. Main PID: 440 (code=exited, status=1/FAILURE)

    9. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    Copy the Code
    大家看下，我应该怎么做才能提升启动速度
    Reply Favorite View the author
    All Replies
    avatar
    mutong
    deepin
    2017-11-26 21:01
    #1
    虽然是周末，但还是期待能有大牛伸手相助
    Reply View the author
    avatar
    wtz
    deepin
    2017-11-27 00:18
    #2
    你确定是因为“systemd-modules-load.service”这个服务才拖慢了启动？
    建议先用
    1. systemd-analyze blame
    Copy the Code
    分析一下。
    Reply View the author
    avatar
    mutong
    deepin
    2017-11-27 02:03
    #3
    本帖最后由 mutong 于 2017-11-26 18:11 编辑

    执行命令：
    1. systemd-analyze blame
    Copy the Code


    结果如下：
    1. 21.071s mysql.service
    2.          14.958s NetworkManager-wait-online.service
    3.          10.097s apache2.service
    4.           8.375s ModemManager.service
    5.           6.205s dev-sdb5.device
    6.           5.833s nmbd.service
    7.           4.519s systemd-journal-flush.service
    8.           3.727s wpa_supplicant.service
    9.           3.406s networking.service
    10.           2.991s accounts-daemon.service
    11.           2.326s systemd-logind.service
    12.           2.267s alsa-restore.service
    13.           2.264s avahi-daemon.service
    14.           2.141s NetworkManager.service
    15.           1.765s lvm2-monitor.service
    16.           1.637s lightdm.service
    17.           1.636s plymouth-quit-wait.service
    18.           1.488s systemd-fsck@dev-disk-by\x2duuid-09ab3bf6\x2db227\x2d40f5\x2d9ca6\x2dacd40f5302e6.service
    19.           1.195s upower.service
    20.            984ms systemd-udevd.service
    21.            942ms systemd-tmpfiles-setup-dev.service
    22.            929ms bluetooth.service
    23.            817ms systemd-rfkill.service
    24.            750ms lastore-daemon.service
    25.            666ms systemd-binfmt.service
    26.            662ms polkit.service
    27.            640ms sys-kernel-debug.mount
    28.            640ms dev-hugepages.mount
    29.            627ms smbd.service
    30.            593ms dev-mqueue.mount
    31.            543ms pppd-dns.service
    32.            410ms systemd-tmpfiles-setup.service
    33.            408ms proc-sys-fs-binfmt_misc.mount
    34.            350ms systemd-backlight@backlight:acpi_video1.service
    35.            303ms systemd-sysctl.service
    36.            285ms systemd-journald.service
    37.            281ms kmod-static-nodes.service
    38.            281ms user@1000.service
    39.            259ms systemd-random-seed.service
    Copy the Code

    除了mysql，apache 其他服务不知道干啥的，该咋优化
    Reply View the author
    avatar
    jingle
    deepin
    2017-11-27 17:15
    #4
    谢谢反馈不过 和内核没有关系  nm mysql 加载了太多时间
    Reply View the author
    avatar
    mutong
    deepin
    2017-11-27 19:25
    #5
    https://bbs.deepin.org/post/148996
    谢谢反馈不过 和内核没有关系  nm mysql 加载了太多时间

    10s钟以上的服务我现在已经取消了，但是启动依然很慢。其中出现deepin logo后黑屏时间挺长的
    Reply View the author
    avatar
    iminto
    deepin
    2017-12-28 06:23
    #6
    https://bbs.deepin.org/post/148996
    10s钟以上的服务我现在已经取消了，但是启动依然很慢。其中出现deepin logo后黑屏时间挺长的 ...

    和开机服务无关,是deepin自己的问题,目前无解.

    你开机优化得再好都没用,deepin logo后黑屏时间是固定不变的
    Reply View the author
    avatar
    春歌
    deepin
    2022-04-20 00:53
    #7

    如何查看启动日志 ？？？

    Reply View the author