ubuntuusers.de

Nach Upgrade auf Lubuntu 18.04 (von 17.10) lange Boot-Zeit

Status: Ungelöst | Ubuntu-Version: Lubuntu 18.04 (Bionic Beaver)
Antworten |

Pfauenauge

Anmeldungsdatum:
11. November 2017

Beiträge: 43

Hallo,

seit ich ein Upgrade auf Lubuntu 18.04 durchgeführt habe, braucht mein PC recht lange zum booten. Es wirkt als ob er an einer Stelle stecken bleibt und dann nach Wartezeit erst weiter hochfährt. Ich habe gegooglet und versucht den Fehler zu finden, aber ich kann mit den Ausgaben bisher nicht so viel anfangen.

Ausgabe von cat /etc/fstab:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda9 during installation
UUID=57e74498-cceb-47d2-bbb3-5870bba224e7 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda2 during installation
UUID=4CE0-1114  /boot/efi       vfat    umask=0077      0       1
/swapfile  

Ausgabe von sudo blkid

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
/dev/sda1: LABEL="Recovery" UUID="88C8DD47C8DD33E2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="3182d165-ae15-4f47-8a81-a3593556beb5"
/dev/sda2: LABEL="ESP" UUID="4CE0-1114" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="7b15df59-0128-4f8d-ae06-3de7f6b81d00"
/dev/sda4: LABEL="Acer" UUID="023E6E753E6E61A1" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="53e82090-006d-4e3c-97d2-1187e0a57dbb"
/dev/sda5: LABEL="Push Button Reset" UUID="909CE5369CE5180C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4f9e2979-578d-4a6b-abc6-4292bbc2ff30"
/dev/sda6: UUID="7fb576f8-371b-4601-91be-116f29f949bc" TYPE="swap" PARTLABEL="/swap" PARTUUID="bb6bf409-96a5-4f2e-bb3d-7333121f127e"
/dev/sda7: LABEL="/" UUID="29254a5b-355d-469e-877b-07dee6adfe13" TYPE="ext4" PARTLABEL="/" PARTUUID="540d6a73-e42a-4924-b8dd-3e4d5a2cb4df"
/dev/sda8: LABEL="/home" UUID="aea401dd-3e17-4571-9f8a-f321aa58453b" TYPE="ext4" PARTLABEL="/home" PARTUUID="63519d33-f138-4d7a-9cd5-4ad60cffbe11"
/dev/sda9: UUID="57e74498-cceb-47d2-bbb3-5870bba224e7" TYPE="ext4" PARTUUID="44dcef44-3be6-403c-b398-4d43ac3f7ef9"
/dev/mmcblk0p1: UUID="9016-4EF8" TYPE="vfat"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="67c74208-d050-47f5-aedc-24f1c5fc01a1"
/dev/mmcblk0: PTTYPE="dos"

Ausgabe von systemd-analyze blame:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72

         15.488s dev-sda9.device
         13.796s systemd-journal-flush.service
          9.000s systemd-udevd.service
          7.055s NetworkManager-wait-online.service
          6.058s plymouth-start.service
          5.145s udisks2.service
          4.225s networkd-dispatcher.service
          4.035s NetworkManager.service
          3.662s snapd.service
          2.516s ModemManager.service
          2.370s systemd-sysctl.service
          2.153s accounts-daemon.service
          1.678s systemd-tmpfiles-setup-dev.service
          1.552s fwupd.service
          1.367s systemd-fsck@dev-disk-by\x2duuid-4CE0\x2d1114.service
          1.350s systemd-modules-load.service
          1.312s gpu-manager.service
          1.260s keyboard-setup.service
           860ms motd-news.service
           699ms systemd-journald.service
           652ms avahi-daemon.service
           636ms lm-sensors.service
           622ms swapfile.swap
           599ms polkit.service
           579ms systemd-random-seed.service
           467ms packagekit.service
           459ms rsyslog.service
           451ms dev-hugepages.mount
           449ms sys-kernel-debug.mount
           422ms systemd-tmpfiles-clean.service
           449ms sys-kernel-debug.mount
           422ms systemd-tmpfiles-clean.service
           411ms systemd-remount-fs.service
           404ms upower.service
           390ms dev-mqueue.mount
           388ms apparmor.service
           315ms systemd-tmpfiles-setup.service
           233ms alsa-restore.service
           227ms systemd-resolved.service
           222ms systemd-udev-trigger.service
           213ms ufw.service
           207ms grub-common.service
           206ms binfmt-support.service
           175ms kmod-static-nodes.service
           166ms systemd-logind.service
           164ms user@1000.service
           160ms systemd-timesyncd.service
           149ms lightdm.service
           147ms plymouth-quit-wait.service
           139ms systemd-rfkill.service
           129ms wpa_supplicant.service
           117ms apport.service
            95ms boot-efi.mount
            85ms pppd-dns.service
            82ms systemd-update-utmp.service
            59ms plymouth-read-write.service
            46ms kerneloops.service
            41ms qemu-kvm.service
            41ms bluetooth.service
            28ms snapd.seeded.service
            19ms setvtrgb.service
            18ms ureadahead-stop.service
            13ms systemd-update-utmp-runlevel.service
            11ms console-setup.service
            10ms systemd-user-sessions.service
            10ms proc-sys-fs-binfmt_misc.mount
             9ms systemd-backlight@backlight:intel_backlight.service
             7ms openvpn.service
             6ms sys-kernel-config.mount
             5ms sys-fs-fuse-connections.mount
             2ms snapd.socket

Ausgabe von systemd-analyze time

1
2
Startup finished in 41.310s (kernel) + 32.542s (userspace) = 1min 13.852s
graphical.target reached after 32.507s in userspace

Moderiert von Taomon:

Dieses Thema ist verschoben worden. Bitte beachte die als wichtig markierten Themen („Welche Themen gehören hier her und welche nicht?“)!

Antworten |