Arch Linux

rck

Member

Registered: 2011-01-06

Posts: 4

boot time/systemd-analyze: mkinitcpio vs. dracut

I started to use systemd about two months ago and fiddled around with systemd-analyze. What seemed strange to me is that most of the time is spent in initramfs. Today I tried dracut and it really makes a difference:

mkinitcpio: Startup finished in 1715ms (kernel) + 12965ms (initramfs) + 6896ms (userspace) = 21576ms

dracut: Startup finished in 1948ms (kernel) + 3209ms (initramfs) + 6742ms (userspace) = 11900ms

Do other users experience the same inequality? I think in my case it is the mdadm hook. Wiith mkinitcpio it hangs there for ages :-/

I think my HOOKS are pretty standard and OK?

 $ egrep "^HOOKS" /etc/mkinitcpio.conf
HOOKS="base udev autodetect pata scsi sata mdadm filesystems fsck timestamp"

djgera

Developer

From: Buenos Aires - Argentina

Registered: 2008-12-24

Posts: 723

Website

Re: boot time/systemd-analyze: mkinitcpio vs. dracut

I guess [pata] and [scsi] are uneeded for you, anyway [autodetect] will remove uneeded files.
[mdadm] should be replaced by [mdadm_udev]

progandy

Member

Registered: 2012-05-17

Posts: 5,305

Re: boot time/systemd-analyze: mkinitcpio vs. dracut

Is the dracut configuration similar to that of mkinitcpio?

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |

rck

Member

Registered: 2011-01-06

Posts: 4

Re: boot time/systemd-analyze: mkinitcpio vs. dracut

[mdadm] should be replaced by [mdadm_udev]

thx, that did the trick! initramfs is now at "3165ms". => "pacman -Rsn dracut"