Ubuntu 18.04 долго загружается
У меня есть система двойной загрузки (Windows 10 + Ubuntu 18.04).
Вот вывод systemd-analyze time
:
Startup finished in 6.590s (kernel) + 57.125s (userspace) = 1min 3.715s
graphical.target reached after 57.116s in userspace
Фактическое время, необходимое для перехода от выбора ОС к работающей среде рабочего стола, составляет более двух с половиной минут. Я пытался найти причину. Во время загрузки я заметил, что dev-disk-by *** занимает больше времени. Я искал Askubuntu по этому поводу и нашел этот вопрос.
После разговора я проверил свою машину. Вот что я получаю:
cat /etc/fstab
# /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/sda4 during installation
UUID=a13c28ea-a372-4fe8-a489-15620cc15233 / ext4
errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=F26F-4C7B /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda8 during installation
UUID=45395f19-eeac-4621-9882-afaa0bbe2ad4 /home ext4
defaults 0 2
# swap was on /dev/sda7 during installation
UUID=7de60d20-a59e-4227-a56b-d11981ea37f8 none swap sw
0 0
manish@lenovo-ideapad-330s:~$ sudo blkid
[sudo] password for manish:
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: LABEL="SYSTEM_DRV" UUID="F26F-4C7B" TYPE="vfat"
PARTLABEL="EFI system partition" PARTUUID="32fe2585-8d62-4ae8-bb83-
87cc3b3f3cc0"
/dev/sda2: PARTLABEL="Microsoft reserved partition"
PARTUUID="9185a073-db7d-4a47-8a4e-b8821bcba3eb"
/dev/sda3: UUID="DEB09931B099115F" TYPE="ntfs" PARTLABEL="Basic data
partition" PARTUUID="d3c471bd-e244-4551-9812-4885882b4975"
/dev/sda4: UUID="0CFA94FEFA94E56C" TYPE="ntfs" PARTUUID="bd7ce6e7-
f1f8-4633-a425-0aca217c8b7d"
/dev/sda5: UUID="a13c28ea-a372-4fe8-a489-15620cc15233" TYPE="ext4"
PARTUUID="1e5cb784-ee54-4b96-8c15-0ff69d364bc0"
/dev/sda6: UUID="7de60d20-a59e-4227-a56b-d11981ea37f8" TYPE="swap"
PARTUUID="d028d7cc-b9f4-46bb-b20e-c118361a0010"
/dev/sda7: UUID="45395f19-eeac-4621-9882-afaa0bbe2ad4" TYPE="ext4"
PARTUUID="3e0af00f-7e50-4474-821c-eb6a1e82b33f"
/dev/sda8: LABEL="LENOVO" UUID="5860554F6055354A" TYPE="ntfs"
PARTLABEL="Basic data partition" PARTUUID="507df7ac-7828-46d6-9301-
ca873893d6cc"
/dev/sda9: LABEL="WINRE_DRV" UUID="6A32731B3272EB87" TYPE="ntfs"
PARTLABEL="Basic data partition" PARTUUID="f7fc0286-2152-49d1-bf11-
d1747bf224fe"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
/dev/loop21: TYPE="squashfs"
/dev/loop22: TYPE="squashfs"
/dev/loop23: TYPE="squashfs"
/dev/loop24: TYPE="squashfs"
/dev/loop25: TYPE="squashfs"
manish@lenovo-ideapad-330s:~$ 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 @59.613s
└─multi-user.target @59.613s
└─kerneloops.service @59.604s +8ms
└─network-online.target @59.602s
└─NetworkManager-wait-online.service @51.421s +8.180s
└─NetworkManager.service @44.939s +6.479s
└─dbus.service @44.106s
└─basic.target @44.102s
└─sockets.target @44.101s
└─snapd.socket @44.095s +3ms
└─sysinit.target @43.985s
└─apparmor.service @43.310s +672ms
└─local-fs.target @43.306s
└─run-user-120.mount @53.375s
└─swap.target @42.673s
└─dev-disk-by\x2duuid-
7de60d20\x2da59e\x2d4227\x2da5
└─dev-disk-by\x2duuid-
7de60d20\x2da59e\x2d4227\x2d
lines 1-20/20 (END)...skipping...
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 @59.613s
└─multi-user.target @59.613s
└─kerneloops.service @59.604s +8ms
└─network-online.target @59.602s
└─NetworkManager-wait-online.service @51.421s +8.180s
└─NetworkManager.service @44.939s +6.479s
└─dbus.service @44.106s
└─basic.target @44.102s
└─sockets.target @44.101s
└─snapd.socket @44.095s +3ms
└─sysinit.target @43.985s
└─apparmor.service @43.310s +672ms
└─local-fs.target @43.306s
└─run-user-120.mount @53.375s
└─swap.target @42.673s
└─dev-disk-by\x2duuid-
7de60d20\x2da59e\x2d4227\x2da56b\x2dd11981ea37f8.swap @42.626s +45ms
└─dev-disk-by\x2duuid-
7de60d20\x2da59e\x2d4227\x2da56b\x2dd11981ea37f8.device @42.625s
Также с помощью gparted я получаю это:
Как видно из раздела swap, в записи / home, / partitions также есть изменения.
Это причина медленной загрузки? Как я могу решить эту проблему?