Even after enabling some services, they don't automatically start at system reboots when /usr is separated filesystem.

Solution Verified - Updated -

Issue

  • Some systemd service units don't automatically start after systemctl enable foobar.service

  • The service units are listed as not-found in the systemctl list-units --all list

    # systemctl enable foobar.service
Created symlink /etc/systemd/system/multi-user.target.wants/foobar.service → /usr/lib/systemd/system/foobar.service.
# reboot 
[...]   
# systemctl list-units --all
 UNIT                      LOAD      ACTIVE   SUB       DESCRIPTION           
[...]
● foobar.service          not-found inactive dead      FooBar service
[...]

Environment

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Red Hat Enterprise Linux 10
  • systemd
  • dracut
  • /usr is a separate filesystem from the root (/) filesystem and is on the LVM logical partition

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content