Thanks for the replies. I can’t find any other info int he logs that may indicate a problem.
Here is what I have after the reached target shutdown entry, which is the last one visible during the actual shutdown sequence:
I don’t know that haveged is, or why it’s starting back up right after stopping, could that be an issue or is that normal? After the last journal entry it just sits there for almost a minute before powering off.
I saw another post where someone said the lvm2 package was causing their system to be slow to shutdown. I thought about removing it, but zypper also wants to remove a bunch of libvirtd packages, which probably isn’t going to work for me. I’ll deal with it if I have to, it’s just a minor annoyance.
After a bit of troubleshooting and reading other posts, I’ve discovered that the lvm2-lvmetad service is what is causing the problem. Uninstalling lvm2 is not an option because it’s a dependency of libvirtd, which I use. Disabling lvm2-lvmetad is evidently not possible because it restarts on every boot regardless of whether or not it’s disabled. Any suggestions on how I can disable this service without uninstalling lvm2?
Ah, what you should have said is something along the lines of “there are other lvm2 services/sockets that need to be disabled as well.” Disabling the monitoring service was sufficient to stop it from re-activating on every boot.