When turning off the Raspberry pi (64 bit bullseye). My shutdown command gets stuck on the following lines
[ OK ] Stopped Cryptography setup for Cryptrfs.
A start job his running for Puts a halt marker on the FAT partition for Zymbit Secure Compute Module (41s / no limit)
The seconds increase forever until I physically remove power.
What is your exact shutdown command? i.e. shutdown -h now or something different?
It’s initiated by a wittypi reaching a timeout but is still
shutdown -h now
Hi Bob,
Do you have any thoughts on how I could shutdown gracefully without this occurring?
I don’t have a wittypi to investigate, but you can try and disable the Zymbit hook to the halt service. It isn’t necessary for the ZYMKEY.
sudo systemctl disable zscm_halt.service
Thanks Bob,
I’ll try this and possibly editing systemctl edit zscm_halt.service with
if [ "$(pgrep -f cryptsetup-zfs)" ]; then
kill -9 cryptsetup-zfs
fi
Hi Bob,
Running sudo systemctl disable zscm_halt.service didn’t work. The raspberry pi was still hanging on the same line [ OK ] Stopped Cryptography setup for Cryptrfs. A start job his running for Puts a halt marker on the FAT partition for Zymbit Secure Compute Module (41s / no limit). Are there any other services which I might be responsible for this long timeout before shutdown?
I get the following logs from journalctl (in reverse order)
Apr 11 06:43:58 raspberrypi64 systemd[1]: **Shutting down.**
Apr 11 06:43:58 raspberrypi64 systemd[1]: Reached target Power-Off.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Finished Power-Off.
Apr 11 06:43:58 raspberrypi64 systemd[1]: systemd-poweroff.service: Succeeded.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Reached target Final Step.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Reached target Shutdown.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 11 06:43:58 raspberrypi64 systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped Create System Users.
Apr 11 06:43:58 raspberrypi64 systemd[1]: systemd-sysusers.service: Succeeded.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 11 06:43:58 raspberrypi64 systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped target Local File Systems (Pre).
Apr 11 06:43:58 raspberrypi64 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped File System Check on /dev/disk/by-partuuid/5ff59132-01.
Apr 11 06:43:58 raspberrypi64 systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-5ff59132\x2d01.service: Succeeded.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Reached target Unmount All Filesystems.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Unmounted /boot.
Apr 11 06:43:58 raspberrypi64 systemd[1]: boot.mount: Succeeded.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped Cryptography Setup for cryptrfs.
Apr 11 06:43:58 raspberrypi64 systemd[1]: **systemd-cryptsetup@cryptrfs.service: Failed with result 'exit-code'.**
Apr 11 06:43:58 raspberrypi64 systemd[1]: **systemd-cryptsetup@cryptrfs.service: Control process exited, code=exited, status=1/FAILURE**
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped Load Kernel Modules.
Apr 11 06:43:58 raspberrypi64 systemd[1]: systemd-modules-load.service: Succeeded.
Apr 11 06:43:58 raspberrypi64 systemd[1]: Stopped Apply Kernel Variables.
On this basis would it be OK to set the shutdown timeout to 10 seconds on the service systemd-cryptsetup@cryptrfs.service
You shouldn’t get the A start job his running for Puts a halt marker on the FAT partition for Zymbit Secure Compute Module line once the service is disabled. I don’t think it requires a reboot, but it may. It went away for me.
Oh, I see it’s gone from your journalctl output. I don’t see a delay in the journalctl output either. Do you still see a delay or are you just wondering about the systemd-cryptsetup error messages? I need to do a little more googling to hone in on the messages. I do see them also. Same with the timeout value.
According to the man page for crypttab, the entry needs the x-initrd.attach option. If you change /etc/crypttab to the following, the error messages go away. Can you try this and see if your delay(s) and error messages go away?
Change /etc/crypttab to the following:
cryptrfs /dev/mmcblk0p2 /etc/cryptroot/key.bin luks,x-initrd.attach
Hi Bob, after reloading the systemctl daemon sudo systemctl disable zscm_halt.service the hanging happening on shutdown did stop. For reference I tested this before I edited the cryptab file, I was still receiving an error but didn’t get the timeout hang.
I am still having problems using the wittypi with the Zymbit (an issue I didn’t have when I wasn’t using the zymbit). The wittypi logs read that I2C communication is happening after shutdown which causes the wittypi to reboot the pi. I have made sure the Zymbit and wittypi are on different I2C addresses and there is no GPIO conflict (by using a carrier board). If you have any thoughts on why this might be happening do let me know
I have edited the /etc/crypttab file as you suggested and now my journalctl logs do not carry an error 
lines 1-49...skipping...
-- Journal begins at Thu 2023-04-06 16:29:22 BST, ends at Thu 2023-04-13 07:42:51 BST. --
Apr 13 07:41:05 raspberrypi64b systemd-journald[448]: Journal stopped
Apr 13 07:41:05 raspberrypi64b systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 13 07:41:04 raspberrypi64b systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 13 07:41:04 raspberrypi64b systemd[1]: **Failed to set timeout to 600s: Invalid argument**
Apr 13 07:41:04 raspberrypi64b systemd[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog
Apr 13 07:41:03 raspberrypi64b systemd[1]: **Shutting down.**
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Reboot.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Finished Reboot.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-reboot.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Final Step.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Shutdown.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Create System Users.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-sysusers.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Local File Systems (Pre).
Apr 13 07:41:03 raspberrypi64b systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped File System Check on /dev/disk/by-partuuid/6a74761a-01.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-6a74761a\x2d01.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Unmount All Filesystems.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Unmounted /boot.
Apr 13 07:41:03 raspberrypi64b systemd[1]: boot.mount: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Load Kernel Modules.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-modules-load.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Apply Kernel Variables.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-sysctl.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Unmounting /boot...
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Local File Systems.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Raise network interfaces.
Apr 13 07:41:03 raspberrypi64b systemd[1]: networking.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Create Volatile Files and Directories.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-update-utmp.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Restore / save the current clock.
Apr 13 07:41:03 raspberrypi64b systemd[1]: fake-hwclock.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopping Restore / save the current clock...
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Swap.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-ask-password-wall.path: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-ask-password-console.path: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Local Encrypted Volumes.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target System Initialization.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Closed triggerhappy.socket.
Apr 13 07:41:03 raspberrypi64b systemd[1]: triggerhappy.socket: Succeeded. lines 1-49...skipping...
-- Journal begins at Thu 2023-04-06 16:29:22 BST, ends at Thu 2023-04-13 07:42:51 BST. --
Apr 13 07:41:05 raspberrypi64b systemd-journald[448]: Journal stopped
Apr 13 07:41:05 raspberrypi64b systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 13 07:41:04 raspberrypi64b systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 13 07:41:04 raspberrypi64b systemd[1]: **Failed to set timeout to 600s: Invalid argument**
Apr 13 07:41:04 raspberrypi64b systemd[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog
Apr 13 07:41:03 raspberrypi64b systemd[1]: **Shutting down.**
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Reboot.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Finished Reboot.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-reboot.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Final Step.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Shutdown.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Create System Users.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-sysusers.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Local File Systems (Pre).
Apr 13 07:41:03 raspberrypi64b systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped File System Check on /dev/disk/by-partuuid/6a74761a-01.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-6a74761a\x2d01.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Reached target Unmount All Filesystems.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Unmounted /boot.
Apr 13 07:41:03 raspberrypi64b systemd[1]: boot.mount: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Load Kernel Modules.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-modules-load.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Apply Kernel Variables.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-sysctl.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Unmounting /boot...
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Local File Systems.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Raise network interfaces.
Apr 13 07:41:03 raspberrypi64b systemd[1]: networking.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Create Volatile Files and Directories.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-update-utmp.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Restore / save the current clock.
Apr 13 07:41:03 raspberrypi64b systemd[1]: fake-hwclock.service: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopping Restore / save the current clock...
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Swap.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-ask-password-wall.path: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Apr 13 07:41:03 raspberrypi64b systemd[1]: systemd-ask-password-console.path: Succeeded.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target Local Encrypted Volumes.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Stopped target System Initialization.
Apr 13 07:41:03 raspberrypi64b systemd[1]: Closed triggerhappy.socket.
Apr 13 07:41:03 raspberrypi64b systemd[1]: triggerhappy.socket: Succeeded.
I think it could be that I have remapped GPIO4 to GPIO17 which is used by the wittypi
From the wittypi manual
After you tap the button on Witty Pi, it powers your Raspberry Pi via the GPIO header, and your Raspberry Pi will boot. Witty Pi’s software will run automatically after boot, which will send the SYS_UP signal (via GPIO-17) to Witty Pi. Witty Pi’s firmware receives the SYS_UP signal and starts to listen to Raspberry Pi’s TXD pin (GPIO-14). If you shut down your Raspberry Pi (running shutdown command or choose “Shutdown” in GUI), the TXD pin will go LOW and Witty Pi will cut the power after some delay. If you tap the button again, that equals to shorting GPIO-4 to GND, and Witty Pi’s software will run shutdown command for you.
I think that maybe on some occasions (it is not all) the wake pin on the zymkey is raised during shutdown and the wittypi interprets this as a reason to reboot. Would there be a way to ensure the zymkey does not raise the wake pin just prior to shutdown?
I have installed a fresh copy of raspbian, moved the wake pin to GPIO 22, edited etc/crypttab and encrypted the filesystem. The zymkey is working correctly to unlock the device and when I trial the example scripts.
However I get the following logs in journalctl when the device is shutting down.
-- Journal begins at Thu 2023-04-06 15:22:46 BST, ends at Sat 2023-04-15 08:04:21 BST. --
Apr 15 06:35:52 raspberrypi64b systemd-journald[446]: Journal stopped
Apr 15 06:35:52 raspberrypi64b systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 15 06:35:52 raspberrypi64b systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 15 06:35:52 raspberrypi64b systemd[1]: Shutting down.
Apr 15 06:35:52 raspberrypi64b systemd[1]: Reached target Power-Off.
Apr 15 06:35:52 raspberrypi64b systemd[1]: Finished Power-Off.
Apr 15 06:35:52 raspberrypi64b systemd[1]: systemd-poweroff.service: Succeeded.
Apr 15 06:35:52 raspberrypi64b systemd[1]: Reached target Final Step.
Apr 15 06:35:52 raspberrypi64b systemd[1]: Reached target Unmount All Filesystems.
Apr 15 06:35:52 raspberrypi64b systemd[1]: Failed to start Puts a halt marker on the FAT partition>
Apr 15 06:35:52 raspberrypi64b systemd[1]: zscm_halt.service: Failed with result 'exit-code'.
Apr 15 06:35:52 raspberrypi64b systemd[1]: zscm_halt.service: Main process exited, code=exited, st>
Apr 15 06:35:52 raspberrypi64b sh[12097]: ERROR: no zymkeys installed.
Apr 15 06:35:51 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:50 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:49 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:48 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:47 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:46 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:45 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:44 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:43 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:42 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:41 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:40 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:39 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:38 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:37 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:36 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:35 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:34 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:33 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:32 raspberrypi64b kernel: i2c-bcm2835 3f804000.i2c: i2c transfer timed out
Apr 15 06:35:26 raspberrypi64b systemd[1]: Reached target Shutdown.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Create System Users.
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-sysusers.service: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped target Local File Systems (Pre).
Apr 15 06:35:26 raspberrypi64b systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped File System Check on /dev/disk/by-partuuid/9129>
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-912929ff\x2d01.ser>
Apr 15 06:35:26 raspberrypi64b systemd[1]: Unmounted /boot.
Apr 15 06:35:26 raspberrypi64b systemd[1]: boot.mount: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Load Kernel Modules.
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-modules-load.service: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Apply Kernel Variables.
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-sysctl.service: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Unmounting /boot...
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped target Local File Systems.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Raise network interfaces.
Apr 15 06:35:26 raspberrypi64b systemd[1]: networking.service: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Create Volatile Files and Directories.
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Apr 15 06:35:26 raspberrypi64b systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Apr 15 06:35:26 raspberrypi64b systemd[1]: systemd-update-utmp.service: Succeeded.
If I disable zscm_halt with sudo systemctl disable zscm_halt.service then the pi does shutdown correctly. I assume I should edit the etc/crypttab file AND disable zscm_halt for future installs?
For completeness these are the logs when I disable zscm_halt service aswell
-- Journal begins at Thu 2023-04-06 15:22:46 BST, ends at Sat 2023-04-15 08:23:57 BST. --
Apr 15 08:20:49 raspberrypi64b systemd-journald[448]: Journal stopped
Apr 15 08:20:49 raspberrypi64b systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 15 08:20:48 raspberrypi64b systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 15 08:20:48 raspberrypi64b systemd[1]: **Shutting down.**
Apr 15 08:20:48 raspberrypi64b systemd[1]: Reached target Power-Off.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Finished Power-Off.
Apr 15 08:20:48 raspberrypi64b systemd[1]: systemd-poweroff.service: Succeeded.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Reached target Final Step.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Reached target Shutdown.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 15 08:20:48 raspberrypi64b systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped Create System Users.
Apr 15 08:20:48 raspberrypi64b systemd[1]: systemd-sysusers.service: Succeeded.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 15 08:20:48 raspberrypi64b systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped target Local File Systems (Pre).
Apr 15 08:20:48 raspberrypi64b systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped File System Check on /dev/disk/by-partuuid/91292>
Apr 15 08:20:48 raspberrypi64b systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-912929ff\x2d01.serv>
Apr 15 08:20:48 raspberrypi64b systemd[1]: Reached target Unmount All Filesystems.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Unmounted /boot.
Apr 15 08:20:48 raspberrypi64b systemd[1]: boot.mount: Succeeded.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Unmounting /boot...
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped target Local File Systems.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped Create Volatile Files and Directories.
Apr 15 08:20:48 raspberrypi64b systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Apr 15 08:20:48 raspberrypi64b systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Apr 15 08:20:48 raspberrypi64b systemd[1]: systemd-update-utmp.service: Succeeded.