Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently installed systemd on my Debian 7.4 system. The time from pressing the power button to usable desktop is around 42-44 seconds. The BIOS takes 6-7 seconds to load and transfer control to GRUB. GRUB has a timeout of 0, in /etc/default/grub. After that the system takes almost 35 seconds more. However, systemd reports taking just 19 seconds.

$ systemd-analyze
Startup finished in 4353ms (kernel) + 14291ms (userspace) = 18644ms

That means, that there is a 16 second delay somewhere. This delay appears to occur just after GRUB finishes and transfers control to the OS. The boot process gets stuck on a screen that says "Loading, please wait" for this time. After the 16 seconds pass, I get a feedback stating these two things:

systemd-fsck [..] : /dev/sda1 .... clean
... bad mmio address ...

Firstly, what is taking these extra 16 seconds? Is it fsck or the mmio address error?

I feel that it is systemd-fsck, and I have tried to solve the problem. I have edited /etc/fstab and changed the pass parameter to 0 for all volumes. However, this still continues to occur. So, how do I disable fsck on boot for the root (/dev/sda1) partition, or otherwise reduce the time during boot? This thread suggests a solution for non-root drives, which I haven't attempted on /.

share|improve this question
Look at the rest of the systemd-analyze tools... – jasonwryan May 5 '14 at 2:22
Then you could try the kernel parameters systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M for more verbose detail. – jasonwryan May 5 '14 at 2:39
@jasonwryan systemd doesn't even seem to know about the extra 16 seconds. Will the debug mode be useful? At best, I think it will get me more detail about the 19 seconds that it records, not the rest. – AsheeshR May 5 '14 at 2:41
I don't know, I've never had to use it. You will get a lot more logging detail, which may help pinpoint the issue. – jasonwryan May 5 '14 at 2:42

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.