I think it’s ok to persist here. If the issue goes silent for a day or so, then perhaps. But at the moment, there’s a few here who are engaged with the topic.
Nov 17 00:09:33 Archven systemd[1]: Removed slice Slice /system/systemd-fsck.
Nov 17 00:09:33 Archven systemd[1]: Stopped target Preparation for Local File Systems.
Nov 17 00:09:33 Archven systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or prog
ress polling…
Nov 17 00:09:33 Archven systemd[1]: systemd-remount-fs.service: Deactivated successfully.
Nov 17 00:09:33 Archven systemd[1]: Stopped Remount Root and Kernel File Systems.
Nov 17 00:09:33 Archven systemd[1]: systemd-fsck-root.service: Deactivated successfully.
Nov 17 00:09:33 Archven systemd[1]: Stopped File System Check on Root Device.
Nov 17 00:09:33 Archven systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
Nov 17 00:09:33 Archven systemd[1]: Stopped Create Static Device Nodes in /dev.
Nov 17 00:09:33 Archven systemd[1]: systemd-tmpfiles-setup-dev-early.service: Deactivated successfully.
Nov 17 00:09:33 Archven systemd[1]: Stopped Create Static Device Nodes in /dev gracefully.
Nov 17 00:09:33 Archven systemd[1]: lvm2-monitor.service: Deactivated successfully.
Nov 17 00:09:33 Archven systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progr
ess polling.
Nov 17 00:09:33 Archven systemd[1]: Reached target System Shutdown.
Nov 17 00:09:33 Archven systemd[1]: Reached target Late Shutdown Services.
Nov 17 00:09:33 Archven systemd[1]: systemd-poweroff.service: Deactivated successfully.
Nov 17 00:09:33 Archven systemd[1]: Finished System Power Off.
Nov 17 00:09:33 Archven systemd[1]: Reached target System Power Off.
Nov 17 00:09:33 Archven systemd[1]: Shutting down.
Nov 17 00:09:33 Archven systemd-shutdown[1]: Syncing filesystems and block devices.
Nov 17 00:09:33 Archven systemd-shutdown[1]: Sending SIGTERM to remaining processes…
Nov 17 00:09:33 Archven systemd-udevd[651]: Failed to remove file descriptor “config-serialization” from the s
tore, ignoring: Connection refused
Nov 17 00:09:33 Archven systemd-journald[610]: Received SIGTERM from PID 1 (systemd-shutdow).
Nov 17 00:09:33 Archven systemd-udevd[651]: Failed to push serialization fd to service manager: Connection ref
used
Nov 17 00:09:33 Archven systemd-journald[610]: Journal stopped
To format it as a block of preformatted text, use 3 back ticks `, before and after:
```
entire output goes here
```
I’m trying but its not doing anything
does that matter for the OP? I mean I get what they are saying but this is just to see if the machine is actually shutting off. I’m not interested in semantics just if the computer can shutdown or not. Which according doesn’t
All that matters to me is i want both the Computer, the operating system, programs, ASWELL AS, my fans and lights on my physical desktop hardware to shut off along side it, when i press the big “Shut down” button. It’s not insanely complex and i apologize if i mmade it so
you can just highlight the text and press ctrl+e
The man pages and --help are there for something. Whether you are interested in semantics or not is irrelevant.
My post was intended to be informative and for the record not as a critique to “your way” 
Asrock motherboards with B650E seem to have issues to power off after a shutdown.
Try a BIOS update first. Your BIOS version 2.01 is very old. There have been multiple new releases in the meantime. Current version is 3.50.
Thank you very much for this clarification, it’ll take a hot second to update it but i’ll give it a shot
Okay this ended up being the solution, thank you very much
The bios being oudated, me updating it, trying to press “shut down"“ again actually shutdown the OS AND the hardware of the lights and fans so i’m fully satisfied now
That’s great @Timpani! Hopefully smooth sailing now 