[SOLVED] Slow Booting F16

[robertdaleweir]

Hi
I am having a very slow boot on my F16 install. I run "systemd-analyze blame" and get the first three as shown below:
---->
52102ms systemd-tmpfiles-setup.service
15117ms fedora-storage-init-late.service
8802ms boot.mount
<----
Why is it taking so long for these services to start and is there a way to resolve this problem?

[robertdaleweir]

Originally Posted by robertdaleweir

Hi
I am having a very slow boot on my F16 install. I run "systemd-analyze blame" and get the first three as shown below:
---->
52102ms systemd-tmpfiles-setup.service
15117ms fedora-storage-init-late.service
8802ms boot.mount
<----
Why is it taking so long for these services to start and is there a way to resolve this problem?

That first item is taking almost one full minute and I don't know why it should. My '/usr/lib/tmpfiles.d/systemd.conf is as follows ---->
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.

# See tmpfiles.d(5) for details

d /run/user 0755 root root 10d
F /run/utmp 0664 root utmp -

f /var/log/wtmp 0664 root utmp -
f /var/log/btmp 0600 root utmp -

d /var/cache/man - - - 30d

r /forcefsck
r /forcequotacheck
r /fastboot

d /run/systemd/ask-password 0755 root root -
d /run/systemd/seats 0755 root root -
d /run/systemd/sessions 0755 root root -
d /run/systemd/users 0755 root root -

<----
Can anyone see a potential problem with this?

[JamesNZ]

Originally Posted by robertdaleweir

Hi
I am having a very slow boot on my F16 install. I run "systemd-analyze blame" and get the first three as shown below:
---->
52102ms systemd-tmpfiles-setup.service
15117ms fedora-storage-init-late.service
8802ms boot.mount
<----
Why is it taking

This page says it deals with temporary files. You can try disabling it with 'systemctl mask <serviceName.service>', and if it breaks something then you can run 'systemctl unmask <serviceName.service>'. You can safely disable all services beginning with 'fedora-storage-' if you don't have a LVM/RAID setup.

HTH

[robertdaleweir]

Originally Posted by JamesNZ

This page says it deals with temporary files. You can try disabling it with 'systemctl mask <serviceName.service>', and if it breaks something then you can run 'systemctl unmask <serviceName.service>'. You can safely disable all services beginning with 'fedora-storage-' if you don't have a LVM/RAID setup.

HTH

Hi JamesNZ
Thank you for your reply. Is there a place to put these 'systemctl mask <serviceName.service' items so that they persist from boot to boot. Can they be somehow put in the '/usr/lib/tmpfiles.d/systemd.conf' file or somewhere else in the boot up sequence?
I do not use LVM nor RAID. So you are saying that any service which starts with the preface 'fedora-storage-" is OK to mask?

[JamesNZ]

Originally Posted by robertdaleweir

Can they be somehow put in the '/usr/lib/tmpfiles.d/systemd.conf' file or somewhere else in the boot up sequence?

The mask command does that automatically, it symlinks the service to /dev/null so it becomes untouchable

Originally Posted by robertdaleweir

I do not use LVM nor RAID. So you are saying that any service which starts with the preface 'fedora-storage-" is OK to mask?

Correct.

[robertdaleweir]

Originally Posted by JamesNZ

The mask command does that automatically, it symlinks the service to /dev/null so it becomes untouchable


Correct.

Hi JamesNZ
Thank you very much, I will give that a try.