You are not logged in.
Pages: 1
Hello there,
Lately I have been trying to decrease arch linux boot time. I have tried most things that I could off of the wiki: https://wiki.archlinux.org/title/Improv … ot_process like switching from grub to efistub, replacing base and udev in mkinitcpio.conf with systemd but there is not much of a difference. When I use
systemd-analyze blame
I get the following output
16.563s dev-disk-by\x2duuid-A24262DC4262B527.device
16.563s dev-disk-by\x2did-wwn\x2d0x50014ee0ada08949\x2dpart4.device
16.563s dev-disk-by\x2did-ata\x2dWDC_WD5000AAKX\x2d753CA1_WD\x2dWMAYU7793734\x2dpart4.device
16.563s dev-disk-by\x2dpartuuid-88669789\x2d00a6\x2d4287\x2dba8d\x2d812211179a58.device
16.563s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda4.dev>
16.563s dev-sda4.device
16.563s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart4.device
16.563s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart4.device
16.247s dev-disk-by\x2did-ata\x2dWDC_WD5000AAKX\x2d753CA1_WD\x2dWMAYU7793734\x2dpart3.device
16.247s dev-disk-by\x2dpartuuid-4403f306\x2d8b6d\x2d429d\x2da30b\x2d2f801acee581.device
16.247s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart3.device
16.247s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda3.dev>
16.247s dev-sda3.device
16.247s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart3.device
16.247s dev-disk-by\x2did-wwn\x2d0x50014ee0ada08949\x2dpart3.device
16.247s dev-disk-by\x2duuid-4A006B0D006AFEF7.device
16.247s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
16.029s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart1.device
16.029s dev-disk-by\x2did-wwn\x2d0x50014ee0ada08949\x2dpart1.device
16.029s dev-disk-by\x2duuid-FC35\x2d814C.device
16.029s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda1.dev>
16.029s dev-sda1.device
16.029s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
16.029s dev-disk-by\x2dpartuuid-09b7bc01\x2dc7b5\x2d4981\x2d83ca\x2da26c5154d9ce.device
16.029s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart1.device
16.029s dev-disk-by\x2did-ata\x2dWDC_WD5000AAKX\x2d753CA1_WD\x2dWMAYU7793734\x2dpart1.device
15.905s dev-disk-by\x2dlabel-Linux\x5cx20Drive.device
15.905s dev-disk-by\x2dpartuuid-4d511efa\x2d46d3\x2db448\x2da4a1\x2d24b27c8c63da.device
15.905s dev-disk-by\x2did-wwn\x2d0x50014ee0ada08949\x2dpart6.device
15.904s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart6.device
15.904s dev-sda6.device
15.904s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda6.dev>
15.904s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart6.device
15.904s dev-disk-by\x2did-ata\x2dWDC_WD5000AAKX\x2d753CA1_WD\x2dWMAYU7793734\x2dpart6.device
15.904s dev-disk-by\x2duuid-24dada7f\x2d446a\x2d4af5\x2d8660\x2d221e0c34dbf1.device
15.838s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart2.device
15.838s dev-disk-by\x2did-ata\x2dWDC_WD5000AAKX\x2d753CA1_WD\x2dWMAYU7793734\x2dpart2.device
15.838s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart2.device
15.838s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda2.dev>
15.838s dev-sda2.device
15.838s dev-disk-by\x2did-wwn\x2d0x50014ee0ada08949\x2dpart2.device
15.838s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
15.838s dev-disk-by\x2dpartuuid-060312dd\x2daa86\x2d40ad\x2d90ec\x2d50379ad99a97.device
15.789s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0\x2dpart5.device
15.789s dev-sda5.device
15.789s dev-disk-by\x2dpartuuid-b4613461\x2dbe1d\x2d0b4d\x2d9978\x2d498308b643db.device
15.789s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda5.dev>
15.789s dev-disk-by\x2did-ata\x2dWDC_WD5000AAKX\x2d753CA1_WD\x2dWMAYU7793734\x2dpart5.device
15.789s dev-disk-by\x2did-wwn\x2d0x50014ee0ada08949\x2dpart5.device
15.789s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2\x2dpart5.device
15.789s dev-disk-by\x2duuid-C8A1\x2dD9A3.device
15.316s dev-disk-by\x2dpartuuid-da9fda9f\x2d01.device
15.316s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart1.device
15.316s dev-disk-by\x2duuid-28f4056a\x2dc23e\x2d4a56\x2d9a29\x2dc9f0dccecc8c.device
15.316s sys-devices-pci0000:00-0000:00:1f.2-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb1.dev>
15.316s dev-sdb1.device
15.316s dev-disk-by\x2dlabel-QEMU\x5cx20Disks.device
15.316s dev-disk-by\x2did-ata\x2dST3160811AS_5PT0LMM5\x2dpart1.device
15.316s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4\x2dpart1.device
15.308s dev-disk-by\x2ddiskseq-2.device
15.308s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.device
15.308s dev-sdb.device
15.308s dev-disk-by\x2did-ata\x2dST3160811AS_5PT0LMM5.device
15.308s sys-devices-pci0000:00-0000:00:1f.2-ata4-host3-target3:0:0-3:0:0:0-block-sdb.device
15.308s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0.device
15.229s dev-disk-by\x2ddiskseq-1.device
15.229s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sda.device
15.229s dev-sda.device
15.229s dev-disk-by\x2did-ata\x2dWDC_WD5000AAKX\x2d753CA1_WD\x2dWMAYU7793734.device
15.229s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.device
15.229s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0.device
15.229s dev-disk-by\x2did-wwn\x2d0x50014ee0ada08949.device
14.382s sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d1.device
14.382s dev-bus-usb-003-002.device
14.183s sys-devices-pci0000:00-0000:00:16.3-tty-ttyS4.device
14.183s dev-ttyS4.device
14.096s sys-devices-platform-serial8250-tty-ttyS13.device
14.096s dev-ttyS13.device
14.095s sys-devices-platform-serial8250-tty-ttyS11.device
14.095s dev-ttyS11.device
14.095s sys-devices-platform-serial8250-tty-ttyS27.device
14.095s dev-ttyS27.device
14.095s dev-ttyS10.device
14.095s sys-devices-platform-serial8250-tty-ttyS10.device
14.094s dev-ttyS1.device
14.094s sys-devices-platform-serial8250-tty-ttyS1.device
14.094s sys-devices-platform-serial8250-tty-ttyS19.device
14.094s dev-ttyS19.device
14.094s dev-ttyS15.device
14.094s sys-devices-platform-serial8250-tty-ttyS15.device
14.093s sys-devices-platform-serial8250-tty-ttyS22.device
14.093s dev-ttyS22.device
14.093s dev-ttyS20.device
14.093s sys-devices-platform-serial8250-tty-ttyS20.device
14.093s sys-devices-platform-serial8250-tty-ttyS21.device
14.093s dev-ttyS21.device
14.092s sys-devices-platform-serial8250-tty-ttyS25.device
14.092s dev-ttyS25.device
14.092s dev-ttyS23.device
14.092s sys-devices-platform-serial8250-tty-ttyS23.device
14.092s sys-devices-platform-serial8250-tty-ttyS7.device
14.092s dev-ttyS7.device
14.091s dev-ttyS26.device
14.091s sys-devices-platform-serial8250-tty-ttyS26.device
14.091s dev-ttyS24.device
14.091s sys-devices-platform-serial8250-tty-ttyS24.device
14.090s dev-ttyS29.device
14.090s sys-devices-platform-serial8250-tty-ttyS29.device
14.090s sys-devices-platform-serial8250-tty-ttyS28.device
14.090s dev-ttyS28.device
14.089s sys-devices-platform-serial8250-tty-ttyS31.device
14.089s dev-ttyS31.device
14.088s dev-ttyS30.device
14.088s sys-devices-platform-serial8250-tty-ttyS30.device
14.088s dev-ttyS3.device
14.088s sys-devices-platform-serial8250-tty-ttyS3.device
14.088s sys-devices-platform-serial8250-tty-ttyS17.device
14.088s dev-ttyS17.device
14.082s dev-ttyS8.device
14.082s sys-devices-platform-serial8250-tty-ttyS8.device
14.081s sys-devices-platform-serial8250-tty-ttyS16.device
14.081s dev-ttyS16.device
14.076s sys-devices-platform-serial8250-tty-ttyS6.device
14.076s dev-ttyS6.device
14.073s sys-devices-platform-serial8250-tty-ttyS9.device
14.073s dev-ttyS9.device
14.073s dev-ttyS5.device
14.073s sys-devices-platform-serial8250-tty-ttyS5.device
14.068s dev-ttyS14.device
14.068s sys-devices-platform-serial8250-tty-ttyS14.device
14.067s dev-ttyS2.device
14.067s sys-devices-platform-serial8250-tty-ttyS2.device
14.067s sys-devices-platform-serial8250-tty-ttyS18.device
14.067s dev-ttyS18.device
14.067s sys-devices-platform-serial8250-tty-ttyS12.device
14.067s dev-ttyS12.device
13.927s sys-module-configfs.device
13.899s sys-devices-pnp0-00:05-tty-ttyS0.device
13.899s dev-ttyS0.device
12.951s systemd-journal-flush.service
10.662s ananicy.service
7.868s cups.service
6.893s initrd-switch-root.service
5.133s libvirtd.service
2.817s systemd-udevd.service
2.332s accounts-daemon.service
2.108s udisks2.service
1.898s lvm2-monitor.service
1.812s systemd-tmpfiles-setup-dev.service
1.506s dbus.service
1.409s packagekit.service
1.397s systemd-logind.service
1.395s systemd-machined.service
1.284s systemd-modules-load.service
1.145s colord.service
985ms NetworkManager.service
971ms systemd-udev-trigger.service
923ms systemd-random-seed.service
890ms systemd-binfmt.service
756ms polkit.service
682ms wpa_supplicant.service
623ms gdm.service
532ms systemd-fsck@dev-disk-by\x2duuid-C8A1\x2dD9A3.service
488ms systemd-tmpfiles-clean.service
441ms user@1000.service
358ms boot.mount
274ms systemd-tmpfiles-setup.service
231ms lm_sensors.service
212ms modprobe@fuse.service
170ms systemd-journald.service
165ms systemd-sysctl.service
164ms kmod-static-nodes.service
163ms modprobe@drm.service
140ms systemd-timesyncd.service
138ms systemd-rfkill.service
133ms systemd-update-utmp.service
129ms initrd-parse-etc.service
105ms systemd-user-sessions.service
105ms dev-hugepages.mount
105ms dev-mqueue.mount
104ms sys-kernel-debug.mount
103ms sys-kernel-tracing.mount
87ms rtkit-daemon.service
84ms upower.service
44ms tmp.mount
22ms sys-fs-fuse-connections.mount
14ms initrd-cleanup.service
7ms user-runtime-dir@1000.service
5ms initrd-udevadm-cleanup-db.service
5ms systemd-remount-fs.service
3ms systemd-fsck-root.service
2ms modprobe@configfs.service
2ms sys-kernel-config.mount
1ms proc-sys-fs-binfmt_misc.mount
I have 2 operating systems on the same disk but both of them have separate efi partitions. My linux partitions are : (/dev/sda5 --> efi) and (/dev/sda6 --> root) I am currently thinking if there is anyway to stop every other dev-sdaX.device from causing the system to slow down.
Here is my fdisk -l output if that helps.
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AAKX-7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 717BAFC6-2B44-41FE-91A8-EA7263AC458D
Device Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda2 206848 239615 32768 16M Microsoft reserved
/dev/sda3 239616 205039615 204800000 97.7G Microsoft basic data
/dev/sda4 975728640 976773119 1044480 510M Windows recovery environment
/dev/sda5 205039616 205654015 614400 300M EFI System
/dev/sda6 205654016 975728639 770074624 367.2G Linux filesystem
Partition table entries are not in disk order.
Disk /dev/sdb: 149.05 GiB, 160041885696 bytes, 312581808 sectors
Disk model: ST3160811AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xda9fda9f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 312578047 312576000 149G 83 Linux
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
Maybe have a look here regarding 'ananicy.service'
and
man systemd-udevd.service
(the '-t' flag in particular) - maybe you can decrease the 180s default timeout without breaking stuff...
Last edited by dogknowsnx (2022-08-05 14:58:56)
Offline
What is the output of systemd-analaze blame ? Let's see what is slowing things down.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
What is the output of systemd-analaze blame ? Let's see what is slowing things down.
See OP...
Offline
`systemd-analyze critical-chain` would be more helpful.
Offline
`systemd-analyze critical-chain` would be more helpful.
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @25.506s
└─multi-user.target @25.505s
└─libvirtd.service @21.006s +4.498s
└─network.target @21.004s
└─wpa_supplicant.service @25.474s +533ms
└─dbus.service @18.662s +1.344s
└─basic.target @18.661s
└─sockets.target @18.660s
└─virtlogd.socket @18.659s
└─sysinit.target @18.623s
└─systemd-update-done.service @18.599s +23ms
└─ldconfig.service @16.229s +2.368s
└─local-fs.target @16.229s
└─boot.mount @15.937s +291ms
└─systemd-fsck@dev-disk-by\x2duuid-C8A1\x2dD9A3.service @14.746s +1.099s
└─dev-disk-by\x2duuid-C8A1\x2dD9A3.device @584542y 2w 2d 20h 1min 31.349s +32.947s
Here you go
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
Maybe have a look here regarding 'ananicy.service'
andman systemd-udevd.service
(the '-t' flag in particular) - maybe you can decrease the 180s default timeout without breaking stuff...
Thanks I will look into it
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
graphical.target @25.506s
This service alone takes 25 seconds, can you post the output of
journalctl -b -u graphical.target
Fan of Giorgio Moroder & Mohammad Ammax enemy
Offline
dev-disk-by\x2duuid-C8A1\x2dD9A3.device @584542y 2w 2d 20h 1min 31.349s +32.947s
It's looking more you're having mounting issues. Check your fstab and your UUID's for your drive. Was your fstab autogenerated?
Offline
my fstab is generated by
genfstab -U >> /mnt
during install
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
BaigGam3rss wrote:graphical.target @25.506s
This service alone takes 25 seconds, can you post the output of
journalctl -b -u graphical.target
Aug 05 13:04:52 archlinux systemd[1]: Reached target Graphical Interface.
this is it
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
my fstab is generated by
genfstab -U >> /mnt
during install
Could you post the output of
cat /etc/fstab
ls -l /dev/disk/by-uuid
Offline
my fstab is generated by
genfstab -U >> /mnt
during installCould you post the output of
cat /etc/fstab ls -l /dev/disk/by-uuid
output of cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda6
UUID=24dada7f-446a-4af5-8660-221e0c34dbf1 / ext4 rw,relatime 0 0
# /dev/sda5
UUID=C8A1-D9A3 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
output of ls -l /dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 10 Aug 5 13:04 24dada7f-446a-4af5-8660-221e0c34dbf1 -> ../../sda6
lrwxrwxrwx 1 root root 10 Aug 5 13:05 28f4056a-c23e-4a56-9a29-c9f0dccecc8c -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 5 13:04 4A006B0D006AFEF7 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 5 13:32 63E7-A296 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Aug 5 13:04 A24262DC4262B527 -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug 5 13:04 C8A1-D9A3 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 5 13:04 FC35-814C -> ../../sda1
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
lrwxrwxrwx 1 root root 10 Aug 5 13:04 C8A1-D9A3 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 5 13:04 FC35-814C -> ../../sda1
What's in sda1?
It might be that you have multiple efi partitions.
Offline
lrwxrwxrwx 1 root root 10 Aug 5 13:04 C8A1-D9A3 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 5 13:04 FC35-814C -> ../../sda1What's in sda1?
It might be that you have multiple efi partitions.
yes I do have multiple efi partitions as stated at the top of this thread one is for windows and the other is for linux. sda5 is linux and sda1 is windows
Last edited by BaigGam3rss (2022-08-06 19:33:18)
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda5 205039616 205654015 614400 300M EFI System
Yes but do you actually know which one is Windows and which one is Linux?
Normally it's best to have just one efi partition per disk.
Have a good read of this as well:
https://wiki.archlinux.org/title/Dual_b … FI_systems
Offline
yes I do have multiple efi partitions as stated at the top of this thread one is for windows and the other is for linux. sda5 is linux and sda1 is windows
I have stated that right here
If I posted this in the wrong section of the forums or broke any rules please let me know so that I can take this post down
Thankyou!
Offline
Pages: 1