Несмотря на то,что есть 4 аналогичные темы......
и возможно даже их гораздо больше,
я всё же опишу свою проблему...
И да,я новичок.
cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="
http://www.ubuntu.com/"
SUPPORT_URL="
http://help.ubuntu.com/"
BUG_REPORT_URL="
http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Предыстория
У меня Trialboot. Стояла 7ая Windows (sda4),потом поставил Ubuntu 16.04 LTS (sda7),а потом уже поставил Parrot OS (sda8).
Два пингвина работают на одном swap разделе (sda6)[8 GB].
Ставил в разметке GPT. (т.к UEFI поддерживается.)
Устанавливал Parrot по этому методу,т.к без этих действий Ubuntu не видел Parrot:
https://www.youtube.com/watch?v=x7pDldI7tBY
Теперь собственно сама проблема.
После обновления системы через
sudo apt-get update Ubuntu начала дольше загружаться.
Логи : systemd-analyze :
Startup finished in 2.829s (firmware) + 3.570s (loader) + 5.924s (kernel) +
3min 1.835s (userspace) = 3min 14.159s
dmesg :
https://pastebin.com/c4zHVA8z 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 @1min 44.097s
└─multi-user.target @1min 44.097s
└─[0;1;31mteamviewerd.service @1min 42.104s +1.992s[0m
└─network-online.target @1min 42.093s
└─[0;1;31mNetworkManager-wait-online.service @1min 35.611s +6.481s[0m
└─[0;1;31mNetworkManager.service @1min 32.656s +2.945s[0m
└─dbus.service @1min 31.638s
└─basic.target @1min 31.617s
└─sockets.target @1min 31.617s
└─[0;1;31msnapd.socket @1min 31.585s +31ms[0m
└─sysinit.target @1min 31.585s
└─[0;1;31mapparmor.service @10.415s +2.376s[0m
└─local-fs.target @10.401s
└─run-user-1000-gvfs.mount @1min 50.010s
└─run-user-1000.mount @1min 48.553s
└─local-fs-pre.target @5.040s
└─[0;1;31msystemd-remount-fs.service @4.875s +115ms[0m
└─systemd-journald.socket @1.375s
└─-.mount @1.374s
└─system.slice @1.375s
└─-.slice @1.374s
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/sda7 during installation
UUID=0d7da20c-79d8-4e07-ad7e-2576c2194cd5 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda2 during installation
UUID=CAB3-339B /boot/efi vfat umask=0077 0 1
# swap was on /dev/sda6 during installation
#UUID=d0839528-e9c5-4ae1-9668-c3b6a74ea5ac none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
systemd-analyze blame :
8.158s dev-sda7.device
6.481s NetworkManager-wait-online.service
3.931s ModemManager.service
2.945s NetworkManager.service
2.746s ufw.service
2.376s apparmor.service
2.329s accounts-daemon.service
2.303s thermald.service
1.992s teamviewerd.service
1.836s systemd-udevd.service
1.269s systemd-tmpfiles-setup-dev.service
1.258s keyboard-setup.service
1.062s systemd-tmpfiles-setup.service
1.050s gpu-manager.service
1.037s ondemand.service
1.030s alsa-restore.service
1.007s rsyslog.service
1.005s avahi-daemon.service
908ms systemd-modules-load.service
856ms plymouth-start.service
820ms grub-common.service
800ms systemd-journald.service
736ms console-setup.service
690ms systemd-logind.service
624ms polkitd.service
597ms lightdm.service
578ms dev-hugepages.mount
577ms sys-kernel-debug.mount
577ms dev-mqueue.mount
383ms irqbalance.service
359ms colord.service
333ms systemd-sysctl.service
325ms udisks2.service
304ms upower.service
293ms systemd-timesyncd.service
282ms systemd-fsck@dev-disk-by\x2duuid-CAB3\x2d339B.service
269ms dns-clean.service
244ms kmod-static-nodes.service
203ms apport.service
202ms systemd-journal-flush.service
195ms networking.service
160ms systemd-update-utmp.service
152ms systemd-random-seed.service
150ms systemd-udev-trigger.service
147ms dev-sda6.swap
145ms plymouth-read-write.service
126ms systemd-user-sessions.service
115ms systemd-remount-fs.service
106ms user@1000.service
71ms resolvconf.service
52ms systemd-tmpfiles-clean.service
49ms boot-efi.mount
42ms setvtrgb.service
31ms speech-dispatcher.service
31ms snapd.socket
8ms snapd.autoimport.service
5ms pppd-dns.service
3ms ureadahead-stop.service
3ms systemd-update-utmp-runlevel.service
2ms rtkit-daemon.service
1ms sys-fs-fuse-connections.mount
865us plymouth-quit-wait.service
761us rc-local.service
system-analyze plot > new.sfw
Что делать?
Noob Saibot detected,Houston,I repeate - Noob Saibot detected.1.4. Листинги и содержимое текстовых файлов следует добавлять в сообщение с помощью тегов [spoiler]...[/spoiler] или [code]...[/code], либо прикреплять к сообщению в виде отдельного файла.
--Aleksandru