Ubuntu 18.04 boot is slow












0















My Ubtuntu installation boot time is slow. Have a SSD, so I think it should be relatively quick, but systemd-blame produces the following



root@ray-ThinkStation-S30:/home/ray# systemd-analyze
Startup finished in 1min 4.290s (kernel) + 6.327s (userspace) = 1min 10.618s
graphical.target reached after 6.323s in userspace

root@ray-ThinkStation-S30:/home/ray# systemd-analyze blame
3.876s NetworkManager-wait-online.service
1.020s dev-mapper-ubuntux2dx2dvgx2droot.device
922ms lvm2-pvscan@8:1.service
856ms fwupd.service
673ms snapd.service
485ms plymouth-quit-wait.service
256ms systemd-logind.service
237ms snap-gnomex2dsystemx2dmonitor-57.mount
232ms dev-loop9.device
229ms dev-loop8.device
221ms dev-loop0.device
218ms dev-loop1.device
216ms dev-loop2.device
213ms dev-loop12.device
213ms dev-loop14.device
211ms dev-loop10.device
208ms NetworkManager.service
205ms dev-loop3.device
204ms dev-loop13.device
202ms dev-loop7.device
193ms dev-loop4.device
187ms snap-core-6130.mount
187ms dev-loop11.device
186ms dev-loop6.device
186ms snap-gnomex2d3x2d26x2d1604-70.mount
184ms dev-loop5.device
183ms networkd-dispatcher.service
175ms systemd-timesyncd.service
174ms systemd-resolved.service
173ms apparmor.service
169ms dev-loop15.device
158ms snap-xonotic-34.mount
155ms snap-gnomex2dsystemx2dmonitor-51.mount
136ms snap-gtkx2dcommonx2dthemes-818.mount
134ms udisks2.service
131ms ModemManager.service
130ms systemd-udevd.service
122ms snap-vscode-75.mount
107ms snap-gnomex2dlogs-37.mount
106ms snap-core-4917.mount
101ms snap-gnomex2d3x2d26x2d1604-74.mount
96ms systemd-journal-flush.service
95ms accounts-daemon.service
93ms snap-gnomex2dcalculator-180.mount
86ms snap-gnomex2dcharacters-103.mount
83ms snap-gnomex2dlogs-45.mount
82ms grub-common.service
77ms keyboard-setup.service
70ms networking.service
70ms upower.service
66ms lvm2-monitor.service
66ms snap-gtkx2dcommonx2dthemes-319.mount
66ms wpa_supplicant.service
63ms snap-gnomex2dcalculator-260.mount
62ms systemd-udev-trigger.service
60ms snap-gnomex2dcharacters-139.mount
50ms thermald.service


root@ray-ThinkStation-S30:/home/ray# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @6.323s
└─multi-user.target @6.323s
└─kerneloops.service @6.315s +7ms
└─network-online.target @6.313s
└─NetworkManager-wait-online.service @2.437s +3.876s
└─NetworkManager.service @2.227s +208ms
└─dbus.service @2.210s
└─basic.target @2.205s
└─sockets.target @2.205s
└─snapd.socket @2.204s +628us
└─sysinit.target @2.203s
└─swap.target @2.203s
└─dev-mapper-ubuntux2dx2dvgx2dswap_1.swap @2.197s +5ms
└─dev-mapper-ubuntux2dx2dvgx2dswap_1.device @2.196s









share|improve this question





























    0















    My Ubtuntu installation boot time is slow. Have a SSD, so I think it should be relatively quick, but systemd-blame produces the following



    root@ray-ThinkStation-S30:/home/ray# systemd-analyze
    Startup finished in 1min 4.290s (kernel) + 6.327s (userspace) = 1min 10.618s
    graphical.target reached after 6.323s in userspace

    root@ray-ThinkStation-S30:/home/ray# systemd-analyze blame
    3.876s NetworkManager-wait-online.service
    1.020s dev-mapper-ubuntux2dx2dvgx2droot.device
    922ms lvm2-pvscan@8:1.service
    856ms fwupd.service
    673ms snapd.service
    485ms plymouth-quit-wait.service
    256ms systemd-logind.service
    237ms snap-gnomex2dsystemx2dmonitor-57.mount
    232ms dev-loop9.device
    229ms dev-loop8.device
    221ms dev-loop0.device
    218ms dev-loop1.device
    216ms dev-loop2.device
    213ms dev-loop12.device
    213ms dev-loop14.device
    211ms dev-loop10.device
    208ms NetworkManager.service
    205ms dev-loop3.device
    204ms dev-loop13.device
    202ms dev-loop7.device
    193ms dev-loop4.device
    187ms snap-core-6130.mount
    187ms dev-loop11.device
    186ms dev-loop6.device
    186ms snap-gnomex2d3x2d26x2d1604-70.mount
    184ms dev-loop5.device
    183ms networkd-dispatcher.service
    175ms systemd-timesyncd.service
    174ms systemd-resolved.service
    173ms apparmor.service
    169ms dev-loop15.device
    158ms snap-xonotic-34.mount
    155ms snap-gnomex2dsystemx2dmonitor-51.mount
    136ms snap-gtkx2dcommonx2dthemes-818.mount
    134ms udisks2.service
    131ms ModemManager.service
    130ms systemd-udevd.service
    122ms snap-vscode-75.mount
    107ms snap-gnomex2dlogs-37.mount
    106ms snap-core-4917.mount
    101ms snap-gnomex2d3x2d26x2d1604-74.mount
    96ms systemd-journal-flush.service
    95ms accounts-daemon.service
    93ms snap-gnomex2dcalculator-180.mount
    86ms snap-gnomex2dcharacters-103.mount
    83ms snap-gnomex2dlogs-45.mount
    82ms grub-common.service
    77ms keyboard-setup.service
    70ms networking.service
    70ms upower.service
    66ms lvm2-monitor.service
    66ms snap-gtkx2dcommonx2dthemes-319.mount
    66ms wpa_supplicant.service
    63ms snap-gnomex2dcalculator-260.mount
    62ms systemd-udev-trigger.service
    60ms snap-gnomex2dcharacters-139.mount
    50ms thermald.service


    root@ray-ThinkStation-S30:/home/ray# systemd-analyze critical-chain
    The time after the unit is active or started is printed after the "@" character.
    The time the unit takes to start is printed after the "+" character.

    graphical.target @6.323s
    └─multi-user.target @6.323s
    └─kerneloops.service @6.315s +7ms
    └─network-online.target @6.313s
    └─NetworkManager-wait-online.service @2.437s +3.876s
    └─NetworkManager.service @2.227s +208ms
    └─dbus.service @2.210s
    └─basic.target @2.205s
    └─sockets.target @2.205s
    └─snapd.socket @2.204s +628us
    └─sysinit.target @2.203s
    └─swap.target @2.203s
    └─dev-mapper-ubuntux2dx2dvgx2dswap_1.swap @2.197s +5ms
    └─dev-mapper-ubuntux2dx2dvgx2dswap_1.device @2.196s









    share|improve this question



























      0












      0








      0








      My Ubtuntu installation boot time is slow. Have a SSD, so I think it should be relatively quick, but systemd-blame produces the following



      root@ray-ThinkStation-S30:/home/ray# systemd-analyze
      Startup finished in 1min 4.290s (kernel) + 6.327s (userspace) = 1min 10.618s
      graphical.target reached after 6.323s in userspace

      root@ray-ThinkStation-S30:/home/ray# systemd-analyze blame
      3.876s NetworkManager-wait-online.service
      1.020s dev-mapper-ubuntux2dx2dvgx2droot.device
      922ms lvm2-pvscan@8:1.service
      856ms fwupd.service
      673ms snapd.service
      485ms plymouth-quit-wait.service
      256ms systemd-logind.service
      237ms snap-gnomex2dsystemx2dmonitor-57.mount
      232ms dev-loop9.device
      229ms dev-loop8.device
      221ms dev-loop0.device
      218ms dev-loop1.device
      216ms dev-loop2.device
      213ms dev-loop12.device
      213ms dev-loop14.device
      211ms dev-loop10.device
      208ms NetworkManager.service
      205ms dev-loop3.device
      204ms dev-loop13.device
      202ms dev-loop7.device
      193ms dev-loop4.device
      187ms snap-core-6130.mount
      187ms dev-loop11.device
      186ms dev-loop6.device
      186ms snap-gnomex2d3x2d26x2d1604-70.mount
      184ms dev-loop5.device
      183ms networkd-dispatcher.service
      175ms systemd-timesyncd.service
      174ms systemd-resolved.service
      173ms apparmor.service
      169ms dev-loop15.device
      158ms snap-xonotic-34.mount
      155ms snap-gnomex2dsystemx2dmonitor-51.mount
      136ms snap-gtkx2dcommonx2dthemes-818.mount
      134ms udisks2.service
      131ms ModemManager.service
      130ms systemd-udevd.service
      122ms snap-vscode-75.mount
      107ms snap-gnomex2dlogs-37.mount
      106ms snap-core-4917.mount
      101ms snap-gnomex2d3x2d26x2d1604-74.mount
      96ms systemd-journal-flush.service
      95ms accounts-daemon.service
      93ms snap-gnomex2dcalculator-180.mount
      86ms snap-gnomex2dcharacters-103.mount
      83ms snap-gnomex2dlogs-45.mount
      82ms grub-common.service
      77ms keyboard-setup.service
      70ms networking.service
      70ms upower.service
      66ms lvm2-monitor.service
      66ms snap-gtkx2dcommonx2dthemes-319.mount
      66ms wpa_supplicant.service
      63ms snap-gnomex2dcalculator-260.mount
      62ms systemd-udev-trigger.service
      60ms snap-gnomex2dcharacters-139.mount
      50ms thermald.service


      root@ray-ThinkStation-S30:/home/ray# systemd-analyze critical-chain
      The time after the unit is active or started is printed after the "@" character.
      The time the unit takes to start is printed after the "+" character.

      graphical.target @6.323s
      └─multi-user.target @6.323s
      └─kerneloops.service @6.315s +7ms
      └─network-online.target @6.313s
      └─NetworkManager-wait-online.service @2.437s +3.876s
      └─NetworkManager.service @2.227s +208ms
      └─dbus.service @2.210s
      └─basic.target @2.205s
      └─sockets.target @2.205s
      └─snapd.socket @2.204s +628us
      └─sysinit.target @2.203s
      └─swap.target @2.203s
      └─dev-mapper-ubuntux2dx2dvgx2dswap_1.swap @2.197s +5ms
      └─dev-mapper-ubuntux2dx2dvgx2dswap_1.device @2.196s









      share|improve this question
















      My Ubtuntu installation boot time is slow. Have a SSD, so I think it should be relatively quick, but systemd-blame produces the following



      root@ray-ThinkStation-S30:/home/ray# systemd-analyze
      Startup finished in 1min 4.290s (kernel) + 6.327s (userspace) = 1min 10.618s
      graphical.target reached after 6.323s in userspace

      root@ray-ThinkStation-S30:/home/ray# systemd-analyze blame
      3.876s NetworkManager-wait-online.service
      1.020s dev-mapper-ubuntux2dx2dvgx2droot.device
      922ms lvm2-pvscan@8:1.service
      856ms fwupd.service
      673ms snapd.service
      485ms plymouth-quit-wait.service
      256ms systemd-logind.service
      237ms snap-gnomex2dsystemx2dmonitor-57.mount
      232ms dev-loop9.device
      229ms dev-loop8.device
      221ms dev-loop0.device
      218ms dev-loop1.device
      216ms dev-loop2.device
      213ms dev-loop12.device
      213ms dev-loop14.device
      211ms dev-loop10.device
      208ms NetworkManager.service
      205ms dev-loop3.device
      204ms dev-loop13.device
      202ms dev-loop7.device
      193ms dev-loop4.device
      187ms snap-core-6130.mount
      187ms dev-loop11.device
      186ms dev-loop6.device
      186ms snap-gnomex2d3x2d26x2d1604-70.mount
      184ms dev-loop5.device
      183ms networkd-dispatcher.service
      175ms systemd-timesyncd.service
      174ms systemd-resolved.service
      173ms apparmor.service
      169ms dev-loop15.device
      158ms snap-xonotic-34.mount
      155ms snap-gnomex2dsystemx2dmonitor-51.mount
      136ms snap-gtkx2dcommonx2dthemes-818.mount
      134ms udisks2.service
      131ms ModemManager.service
      130ms systemd-udevd.service
      122ms snap-vscode-75.mount
      107ms snap-gnomex2dlogs-37.mount
      106ms snap-core-4917.mount
      101ms snap-gnomex2d3x2d26x2d1604-74.mount
      96ms systemd-journal-flush.service
      95ms accounts-daemon.service
      93ms snap-gnomex2dcalculator-180.mount
      86ms snap-gnomex2dcharacters-103.mount
      83ms snap-gnomex2dlogs-45.mount
      82ms grub-common.service
      77ms keyboard-setup.service
      70ms networking.service
      70ms upower.service
      66ms lvm2-monitor.service
      66ms snap-gtkx2dcommonx2dthemes-319.mount
      66ms wpa_supplicant.service
      63ms snap-gnomex2dcalculator-260.mount
      62ms systemd-udev-trigger.service
      60ms snap-gnomex2dcharacters-139.mount
      50ms thermald.service


      root@ray-ThinkStation-S30:/home/ray# systemd-analyze critical-chain
      The time after the unit is active or started is printed after the "@" character.
      The time the unit takes to start is printed after the "+" character.

      graphical.target @6.323s
      └─multi-user.target @6.323s
      └─kerneloops.service @6.315s +7ms
      └─network-online.target @6.313s
      └─NetworkManager-wait-online.service @2.437s +3.876s
      └─NetworkManager.service @2.227s +208ms
      └─dbus.service @2.210s
      └─basic.target @2.205s
      └─sockets.target @2.205s
      └─snapd.socket @2.204s +628us
      └─sysinit.target @2.203s
      └─swap.target @2.203s
      └─dev-mapper-ubuntux2dx2dvgx2dswap_1.swap @2.197s +5ms
      └─dev-mapper-ubuntux2dx2dvgx2dswap_1.device @2.196s






      boot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 25 at 2:20









      guiverc

      4,34111522




      4,34111522










      asked Jan 25 at 1:35









      rayjrayj

      233




      233






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112667%2fubuntu-18-04-boot-is-slow%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112667%2fubuntu-18-04-boot-is-slow%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          數位音樂下載

          格利澤436b

          When can things happen in Etherscan, such as the picture below?