Merhaba, 18.04 LTS sürümünü kurdum ancak açılış sürem çok fazla windows 7 kullanırken bu kadar yavaş açılmıyordu. Yardımcı olursanız sevinirim.
systemd-analyze
Startup finished in 38.997s (kernel) + 46.691s (userspace) = 1min 25.689s
graphical.target reached after 46.588s in userspace
systemd-analyze blame
17.889s dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
14.922s plymouth-quit-wait.service
13.759s dev-loop1.device
13.756s dev-loop0.device
13.659s dev-loop6.device
13.630s dev-loop5.device
13.592s dev-loop8.device
13.589s dev-loop9.device
13.577s dev-loop3.device
13.570s dev-loop4.device
13.494s dev-loop2.device
13.486s dev-loop7.device
13.265s dev-loop10.device
13.242s apparmor.service
13.162s dev-loop11.device
11.052s systemd-journal-flush.service
10.715s snapd.service
10.279s ModemManager.service
9.303s udisks2.service
8.959s networkd-dispatcher.service
7.600s grub-common.service
6.260s systemd-rfkill.service
5.358s NetworkManager.service
5.110s apport.service
4.908s NetworkManager-wait-online.service
4.744s speech-dispatcher.service
4.232s accounts-daemon.service
3.932s polkit.service
3.899s avahi-daemon.service
3.842s gpu-manager.service
3.819s alsa-restore.service
3.818s bluetooth.service
3.817s thermald.service
3.810s rsyslog.service
3.806s pppd-dns.service
3.635s systemd-logind.service
3.582s wpa_supplicant.service
2.916s lvm2-monitor.service
2.783s systemd-udevd.service
2.473s binfmt-support.service
2.253s dns-clean.service
2.251s systemd-sysctl.service
2.056s keyboard-setup.service
1.852s gdm.service
1.796s systemd-tmpfiles-setup.service
1.777s systemd-modules-load.service
1.777s systemd-tmpfiles-setup-dev.service
1.606s fwupd.service
1.274s systemd-remount-fs.service
1.237s packagekit.service
1.225s dev-mqueue.mount
1.221s sys-kernel-debug.mount
1.215s dev-hugepages.mount
1.202s systemd-timesyncd.service
1.172s systemd-resolved.service
1.166s snap-gnome\x2dsystem\x2dmonitor-39.mount
1.159s snap-canonical\x2dlivepatch-39.mount
1.042s snap-gnome\x2d3\x2d26\x2d1604-59.mount
950ms snap-gnome\x2dcharacters-86.mount
907ms snap-gnome\x2dlogs-31.mount
901ms networking.service
830ms snap-gnome\x2dlogs-25.mount
830ms console-setup.service
813ms snap-gnome\x2dcalculator-154.mount
812ms systemd-random-seed.service
784ms kmod-static-nodes.service
769ms snap-gnome\x2d3\x2d26\x2d1604-62.mount
725ms lvm2-pvscan@8:1.service
699ms snap-core-4486.mount
665ms snap-gnome\x2dcalculator-167.mount
656ms snap-gnome\x2dsystem\x2dmonitor-36.mount
621ms snap-gnome\x2dcharacters-69.mount
570ms colord.service
565ms ufw.service
461ms proc-sys-fs-binfmt_misc.mount
431ms systemd-backlight@backlight:acpi_video0.service
418ms systemd-journald.service
269ms upower.service
264ms systemd-update-utmp.service
254ms bolt.service
138ms systemd-user-sessions.service
111ms kerneloops.service
99ms setvtrgb.service
97ms blk-availability.service
90ms systemd-udev-trigger.service
85ms user@1000.service
64ms dev-mapper-ubuntu\x2d\x2dvg\x2dswap_1.swap
63ms user@120.service
44ms systemd-tmpfiles-clean.service
33ms rtkit-daemon.service
14ms ureadahead-stop.service
14ms plymouth-start.service
11ms plymouth-read-write.service
10ms systemd-update-utmp-runlevel.service
3ms sys-kernel-config.mount
3ms sys-fs-fuse-connections.mount
1ms snapd.socket
blkid
/dev/sda1: UUID="9NTOvv-ETmL-UUId-WD6C-f0Lc-ClzX-cjeUX9" TYPE="LVM2_member" PARTUUID="50adb487-01"
/dev/mapper/ubuntu--vg-root: UUID="7680befc-784e-42bd-a8d1-b440514d7aa6" TYPE="ext4"
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>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=1366x768-64
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
Aynı benimle olur, yerel depolama neredeyse tam kapasiteye sahip iken, Windows 7 daha hızlı oldu, bu ubuntu için ben yeni bir başlangıç yaptım ve hala bana bu sorunu veriyor.
@OrhanSrydn; LVM bölümleri hakkında bilgim yok ama disk bölümü ve görüntü sürücüsüne bağlı, başlıca iki ayrı sorun görünüyor. Diğer süreler ise muhtemelen diske bağlıdır. O ikisi çözülürse normale dönecektir diye düşünüyorum. Şu çıktıları aktarabilir misin?
sudo fdisk -l
lsblk -f
systemd-analyze critical-chain
systemctl list-dependencies dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
# bu şekilde hata alırsan aşağıda ki gibi dene
systemctl list-dependencies dev-mapper-ubuntu--vg-root.device
systemctl list-dependencies dev-loop1.device
lspci -kk|grep -A2 -i vga
@haanuman; her sistemde sorunun sebebi aynı olmayabilir. @OrhanSrydn ilk verdiği çıktıları kendi sisteminden verebilir misin?