http://bugzilla.suse.com/show_bug.cgi?id=1120256
http://bugzilla.suse.com/show_bug.cgi?id=1120256#c17
Stefan Schubert
the mkinitrd.log from the tar ball indicates a successful, complete run. The serial output contains no hint of dracut at all.
I agree 30 seconds sounds too much.
Are there differences in how mkintird/dracut is called from GUI vs Text mode?
Well y2log-1 is showing that mkinitrd/dracut is consuming this time. 2018-12-22 04:47:11 <1> install(3408) [zypp::posttrans++] RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: plymouth *** 2018-12-22 04:47:12 <1> install(3408) [zypp::posttrans++] RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: btrfs *** 2018-12-22 04:47:12 <1> install(3408) [zypp::posttrans++] RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: kernel-modules *** 2018-12-22 04:47:21 <1> install(3408) [zypp::posttrans++] RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: qemu *** ..... .... ... .. 2018-12-22 04:47:22 <1> install(3408) [zypp::posttrans++] RpmPostTransCollector.cc(executeScripts):128 dracut: *** Creating image file '/boot/initrd-4.12.14-lp151.28-default' *** 2018-12-22 04:47:24 <1> install(3408) [zypp::posttrans++] RpmPostTransCollector.cc(executeScripts):128 dracut: *** Creating initramfs image file '/boot/initrd-4.12.14-lp151.28-default' done *** The question is why it takes so long. BUT: mkinitrd will called twice: 1. RpmPostTransCollector.cc(executeScripts):122 EXECUTE posttrans: coreutils-8.29-lp151.9.20.x86_64.rpm9k7mkD 2. YaST2-Bootloader module So the consuming time will be doubled. As there are two different ways how mkinitrd will be called here (and in both cases the call is time consuming) I have doubts that it depends on the installation mode (text/graphical). So Daniel, why it takes so long ? Perhaps the QA can give you a machine where you can call mkinitrd in a console ? Josef, do we really need the mkinitrd call twice ? Perhaps we can distinguish between an running installation/update and the bootloader call in the running system ? -- You are receiving this mail because: You are on the CC list for the bug.