anyone know how to decrease boot time?

Student of UNSRI · 2026-02-20 06:36:00

 Dhaxa@archlinux ~ [2]> systemd-analyze blame
34.209s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_Z99JP6W8T\x2dpart2.device
34.209s dev-disk-by\x2duuid-22b3c34c\x2dc9ee\x2d4977\x2d9c67\x2d3d71168c6ae6.device
34.209s dev-disk-by\x2dpartuuid-7f3724f0\x2d3739\x2d486f\x2d8f94\x2daa7631823df2.device
34.209s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1\x2dpart2.device
34.209s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2dpartuuid-7f3724f0\x2d3739\x2d486f\x2d8f94\x2daa7631823df2.device
34.209s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2dpartnum-2.device
34.209s dev-disk-by\x2ddiskseq-1\x2dpart2.device
34.209s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart2.device
34.208s dev-disk-by\x2did-wwn\x2d0x50000399b2a8340a\x2dpart2.device
34.208s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2duuid-22b3c34c\x2dc9ee\x2d4977\x2d9c67\x2d3d71168c6ae6.device
34.208s dev-sda2.device
34.208s sys-devices-pci0000:00-0000:00:11.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device
34.176s dev-disk-by\x2ddesignator-esp.device
34.176s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1\x2dpart8.device
34.176s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_Z99JP6W8T\x2dpart8.device
34.176s sys-devices-pci0000:00-0000:00:11.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda8.device
34.176s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2dpartnum-8.device
34.176s dev-disk-by\x2dpartuuid-04c27b57\x2d9f7b\x2d42b7\x2d8719\x2dd9f12766cb71.device
34.176s dev-sda8.device
34.176s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2duuid-4228\x2d453F.device
34.176s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart8.device
34.176s dev-disk-by\x2duuid-4228\x2d453F.device
34.176s dev-disk-by\x2ddiskseq-1\x2dpart8.device
34.176s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2dpartuuid-04c27b57\x2d9f7b\x2d42b7\x2d8719\x2dd9f12766cb71.device
34.176s dev-disk-by\x2did-wwn\x2d0x50000399b2a8340a\x2dpart8.device
34.147s dev-disk-by\x2ddesignator-swap.device
34.147s sys-devices-pci0000:00-0000:00:11.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
34.147s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2dpartuuid-b8dbd877\x2d69ff\x2d4bba\x2dbe6c\x2da6fa18e22556.device
34.147s dev-disk-by\x2did-wwn\x2d0x50000399b2a8340a\x2dpart1.device
34.147s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_Z99JP6W8T\x2dpart1.device
34.147s dev-disk-by\x2dpartuuid-b8dbd877\x2d69ff\x2d4bba\x2dbe6c\x2da6fa18e22556.device
34.147s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1\x2dpart1.device
34.147s dev-disk-by\x2ddiskseq-1\x2dpart1.device
34.147s dev-sda1.device
34.147s dev-disk-by\x2duuid-64d39b33\x2dde67\x2d4210\x2d9a88\x2d0188d3084d66.device
34.147s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2duuid-64d39b33\x2dde67\x2d4210\x2d9a88\x2d0188d3084d66.device
34.147s dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
Dhaxa@archlinux ~> systemd-analyze
Startup finished in 5.281s (firmware) + 8.988s (loader) + 1.235s (kernel) + 14.536s (initrd) + 29.357s (userspace) = 59.400s 
graphical.target reached after 29.356s in userspace.

i already using linux zen,do e4defrag,and fix the fstab(maybe? because i accidentally do genfstab twice),it decrease from 1 minute 3 second to 59 second,before it i get 45 second (idk why and how)

i use hdd (i want to upgrade to ssd,but you know lah why)

note for admin/mod :sorry if i put this on wrong place again

Student of UNSRI · 2026-02-20 07:29:11

nevermind, i think this is the max of my hdd

seth · 2026-02-20 09:04:41

59 second,before it i get 45 second (idk why and how)

14.536s (initrd)

Does the initramfs load faster when using the busybox hooks?
https://wiki.archlinux.org/title/Mkinitcpio#Hook_list

In doubt please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

This seems overall too long

Student of UNSRI · 2026-02-20 13:55:58

the heck is initramfs is that X(

anyway,here the output of

sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/PSzw.txt

seth · 2026-02-20 14:29:58

Feb 20 14:22:58 archlinux systemd[1]: systemd-battery-check.service: Deactivated successfully.
Feb 20 14:22:58 archlinux systemd[1]: Stopped Early Battery Level Check.
Feb 20 14:23:10 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
…
Feb 20 14:23:10 archlinux systemd[1]: Switching root.
Feb 20 14:23:11 archlinux systemd-journald[123]: Journal stopped
Feb 20 14:23:16 archlinux systemd-journald[123]: Received SIGTERM from PID 1 (systemd).

Other than those gaps the system really just moves w/ glacial speed.

Feb 20 14:22:57 archlinux kernel:  sda: sda1 sda2 sda8 sda9
Feb 20 14:22:57 archlinux kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 20 14:22:58 archlinux systemd-fsck[191]: /dev/sda2: clean, 468733/29278208 files, 6602688/117095424 blocks
Feb 20 14:22:58 archlinux kernel: EXT4-fs (sda2): mounted filesystem 22b3c34c-c9ee-4977-9c67-3d71168c6ae6 r/w with ordered data mode. Quota mode: none.
Feb 20 14:23:16 archlinux kernel: EXT4-fs (sda2): re-mounted 22b3c34c-c9ee-4977-9c67-3d71168c6ae6.
Feb 20 14:23:23 archlinux kernel: Adding 4194300k swap on /dev/sda1.  Priority:-2 extents:1 across:4194300k 
Feb 20 14:23:23 archlinux kernel: FAT-fs (sda8): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Feb 20 14:23:23 archlinux kernel: EXT4-fs (sda9): mounted filesystem 6df59aab-a737-4ebb-b42f-06f99726de48 r/w with ordered data mode. Quota mode: none.

Partition layout looks a bit funny?

Feb 20 14:22:57 archlinux kernel: ata1.00: ATA-10: TOSHIBA MQ04ABF100, JU001J, max UDMA/100
Feb 20 14:22:57 archlinux kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=22b3c34c-c9ee-4977-9c67-3d71168c6ae6 rw loglevel=3 quiet nowatchdog libdata.force=noncq

Disk is a bit older slow spinner and ncq forcefully disabled.
What's sda1? ESP? sda8 is /boot and sda2 your root partition?
You might be sending the disks reading head around a bit

Student of UNSRI · 2026-02-20 14:46:20

Feb 20 14:22:58 archlinux systemd[1]: systemd-battery-check.service: Deactivated successfully.
Feb 20 14:22:58 archlinux systemd[1]: Stopped Early Battery Level Check.
Feb 20 14:23:10 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
…
Feb 20 14:23:10 archlinux systemd[1]: Switching root.
Feb 20 14:23:11 archlinux systemd-journald[123]: Journal stopped
Feb 20 14:23:16 archlinux systemd-journald[123]: Received SIGTERM from PID 1 (systemd).

so this is just the hdd issue?

for the partition, before it i use dualboot,and because i know i'm gonna distro hop or do something else,i choose to make my / and /home partition separated,and after that,i delete my windows and just focus for using arch (that windows is not mine,i buy this laptop from the previous owner)

and for the last part,i really didnt understand what do you say
ESP? what is that? anyway,my sda1 is swap,sda2 is root,sda8 is my efi/boot,and last,sda9 is my /home

seth · 2026-02-20 15:57:20

ESP? what is that?

sda8 is my efi/boot

so this is just the hdd issue?

Apparently - according to your OP you lost 15s and you could try whether that's because the default initramfs config "recently" switched from busybox to systemd - there's some unaccounted stalls

Student of UNSRI · 2026-02-20 16:07:57

so,my best option right now is switch back to busybox,right?

seth · 2026-02-20 16:10:40

It's a shot to shave off those 15 extra seconds - but that's a guess and in might not improve the situation at all.

Student of UNSRI · 2026-02-20 19:26:29

seth wrote:

It's a shot to shave off those 15 extra seconds - but that's a guess and in might not improve the situation at all.

yeah,but i gonna take it anyway

Student of UNSRI · 2026-02-20 19:45:13

Student of UNSRI wrote:

seth wrote:
It's a shot to shave off those 15 extra seconds - but that's a guess and in might not improve the situation at all.

yeah,but i gonna take it anyway

here the result after i switch from systemd to busybox

Dhaxa@archlinux ~> cat systemd-analyze 
Dhaxa@archlinux ~> systemd-analyze
Startup finished in 5.419s (firmware) + 5.066s (loader) + 15.402s (kernel) + 19.841s (userspace) = 45.730s 
graphical.target reached after 19.841s in userspace.

Dhaxa@archlinux ~> systemd-analyze
Startup finished in 5.307s (firmware) + 4.288s (loader) + 15.283s (kernel) + 19.440s (userspace) = 44.320s 
graphical.target reached after 19.439s in userspace.

Dhaxa@archlinux ~> systemd-analyze
Startup finished in 5.332s (firmware) + 8.828s (loader) + 15.302s (kernel) + 17.318s (userspace) = 46.782s 
graphical.target reached after 17.318s in userspace.

it cut arround 4 second faster than systemd,this is good,but if still possible to speed up a little bit,maybe arround 40 second,it gonna be so good

Last edited by Student of UNSRI (2026-02-20 19:47:04)

seth · 2026-02-20 20:50:46

before it i get 45 second (idk why and how)

45.730s - 44.320s - 46.782s

I'd say you've reached the status quo ante?
I suppose disabling/limiting the journal might improve things - at the obvious cost of not having the journal if you run into problems.

Scimmia · 2026-02-20 20:55:03

With a HDD, filesystem compression can help, too. You're trading lower read time for more CPU cycles.

Student of UNSRI · 2026-02-20 21:11:30

seth wrote:

before it i get 45 second (idk why and how)
45.730s - 44.320s - 46.782s
I'd say you've reached the status quo ante?
I suppose disabling/limiting the journal might improve things - at the obvious cost of not having the journal if you run into problems.

maybe this is the limit

Student of UNSRI · 2026-02-20 21:12:50

Scimmia wrote:

With a HDD, filesystem compression can help, too. You're trading lower read time for more CPU cycles.

acer aspire A314-41 only have amd A9-9420e,it low entry laptop maybe,so i dont think that good

Maniaxx · 2026-02-22 20:40:44

seth wrote:

libdata.force=noncq

Why do you want to disable that in the first place? Isn't NCQ a good thing? Note the typo. It's "libata" not "libdata".

Beside that, I would check swap right after boot if it's already filled a lot (too aggressive).

You could try 'ordered->writeback' as mount option'.

Arch Linux

#1 2026-02-20 06:36:00

anyone know how to decrease boot time?

#2 2026-02-20 07:29:11

Re: anyone know how to decrease boot time?

#3 2026-02-20 09:04:41

Re: anyone know how to decrease boot time?

#4 2026-02-20 13:55:58

Re: anyone know how to decrease boot time?

#5 2026-02-20 14:29:58

Re: anyone know how to decrease boot time?

#6 2026-02-20 14:46:20

Re: anyone know how to decrease boot time?

#7 2026-02-20 15:57:20

Re: anyone know how to decrease boot time?

#8 2026-02-20 16:07:57

Re: anyone know how to decrease boot time?

#9 2026-02-20 16:10:40

Re: anyone know how to decrease boot time?

#10 2026-02-20 19:26:29

Re: anyone know how to decrease boot time?

#11 2026-02-20 19:45:13

Re: anyone know how to decrease boot time?

#12 2026-02-20 20:50:46

Re: anyone know how to decrease boot time?

#13 2026-02-20 20:55:03

Re: anyone know how to decrease boot time?

#14 2026-02-20 21:11:30

Re: anyone know how to decrease boot time?

#15 2026-02-20 21:12:50

Re: anyone know how to decrease boot time?

#16 2026-02-22 20:40:44

Re: anyone know how to decrease boot time?

Board footer