Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow boot on debian stretch with "Begin: Running /scripts/local-block .. done" message #40

Open
SalemHarrache opened this issue Feb 14, 2019 · 0 comments

Comments

@SalemHarrache
Copy link
Contributor

Hello,

I have just built a debian stretch image from the template default/from_upstream_build/debian-stretch

This message appears when booting the new VM

Begin: Running /scripts/local-block .. done
Begin: Running /scripts/local-block .. done
Begin: Running /scripts/local-block .. done
Begin: Running /scripts/local-block .. done
Begin: Running /scripts/local-block .. done
Begin: Running /scripts/local-block .. done

It really slows down the boot process (40-50 seconds instead of the usual 2-3 seconds)

This is a known bug of initramfs-tools on stretch, which was corrected with version 0.130:

The final version that is installed is indeed the 0.130 one:

root@new-vm: /root # dpkg -l | grep initramfs-tools
ii  initramfs-tools               0.130                          all          generic modular initramfs generator (automation)
ii  initramfs-tools-core          0.130                          all          generic modular initramfs generator (core tools)
root@new-vm: /root # cat /etc/initramfs-tools/conf.d/resume 
RESUME=none

However in the debian-stretch_20190124.tar.xz archive it's not quite the same:

$ docker import - debian-stretch_20190124 < debian-stretch_20190124-1.tar.xz
$ docker run --rm -it debian-stretch_20190124 dpkg -l | grep initramfs
ii  initramfs-tool 0.130        all          generic modular initramfs generat
ii  initramfs-tool 0.130        all          generic modular initramfs generat
$ docker run --rm -it debian-stretch_20190124 cat /etc/initramfs-tools/conf.d/resume 
RESUME=UUID=32be9420-d98b-4dea-9a5c-8370c9544a46

My temporary workaround is for now to launch the (re)generation of initramfs on the new vm
$ update-initramfs -u -k all

But I think we should find out why the value of RESUME is not set to None in the recipe archive of debian-stretch_20190124-1

See you !

PS: I could take a look at it this week-end if no one can before that ;-)

npf pushed a commit that referenced this issue Jan 7, 2020
[infiniband] change NETMASK=255.255.240.0 by 255.255.255.0 in ifcfg-i…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant