ZRAM not starting happens when there’s a circular dependency of services that systemd cannot resolve such as can be seen on L1144 of your log.
The exact start order is coincidential and it is also coincidence where systemd decides to break it.
So sometimes you run into cycles and sometimes you do not.
@narf27 as a test, before you reinstall can you try this with your current test system:
add DefaultDependencies=no in the [Unit] section of all /etc/systemd/system/srv-openhab*.mount
Note the star in the filename so edit all 5 files, after that enter systemctl daemon-reload and reboot to see if zram starts reliably.
If that does not work, remove the files completely then reload,reboot,check again.
If that does not work, remove those After= and WantedBy= lines, too (and no DefaultDependencies line any more), then reload,reboot,check again.
If ZRAM startup succeeds, check what Samba exports. Create a file in /var/log/openhab2/ and see if it appears on the Windows share.
Sep 01 11:38:57 openhab systemd[1]: local-fs.target: Found ordering cycle on srv-openhab2\x2duserdata.mount/start
Sep 01 11:38:57 openhab systemd[1]: local-fs.target: Found dependency on zram-config.service/start
Sep 01 11:38:57 openhab systemd[1]: local-fs.target: Found dependency on sysinit.target/start
Sep 01 11:38:57 openhab systemd[1]: local-fs.target: Found dependency on systemd-tmpfiles-setup.service/start
Sep 01 11:38:57 openhab systemd[1]: local-fs.target: Found dependency on local-fs.target/start
Sep 01 11:38:57 openhab systemd[1]: local-fs.target: Job srv-openhab2\x2duserdata.mount/start deleted to break ordering cycle
Try again with master (but flash again), I’ve just copied the changes from testbuild into master.