i couldnt login anymore, only via tty12, despite 66-update so i played around a little with 66 commands (deleting, creating trees)
now i get even into openbox via tty1 again but bluetooth sound printer etc wont work. i am guessing dbus?
now i think i try creating a new user and copy the home folder over.
or maybe i can rescue my current account named z?
thats what my intrees look like:

z@ obliveS6 [255] ~ % 66-intree
Name : zz
Initialized : no
Enabled : yes
Starts after : None
Current : yes
Allowed : z
Symlinks : svc->source db->source
Contents : xdg-user-dirs pulseaudio-log pulseaudio dbus-session@ z-log dbus-session@ z

z@ obliveS6 ~ % sudo 66-intree
[sudo] password for z:
Name : boot
Initialized : yes
Enabled : yes
Starts after : root
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : tty12 system-hostname mount-run populate-run mount-tmp populate-tmp mount-proc mount-sys populate-sys mount-dev mount-pts mount-shm populate-dev mount-cgroups 00 modules-kernel udevd udevadm devices-dmraid system-hwclock system-random modules-system system-sysctl system-fontnkey devices-btrfs devices-crypttab devices-lvm devices-zfs system-Devices all-Mount system-fsck mount-fstab all-System mount-rw local-iptables local-ip6tables local-loop local-time local-authfiles local-tmpfiles local-rc local-dmesg mount-swap local-sethostname all-Local all-Runtime All

Name : root
Initialized : yes
Enabled : yes
Starts after : None
Current : no
Allowed : root
Symlinks : svc->source db->source
Contents : wpa_supplicant-log wpa_supplicant fan dhcpcd-log dhcpcd cupsd-log bluetoothd-log bluetoothd cupsd tty@ tty1 tty@ tty2 mount-run-z setenv-z scandir-z-log scandir-z All-z dbus-log dbus connmand-log connmand consolekit-log consolekit
z@ obliveS6 [111] ~ % sudo 66-inservice dbus
Name : dbus
Version : 0.1.6
In tree : root
Status : enabled, down (exitcode 111) 178904 seconds, ready 178904 seconds
Type : longrun
Description : dbus system daemon
Source : /usr/lib/66/service/dbus
Live : /run/66/tree/0/root/servicedirs/dbus
Dependencies : dbus-log
External dependencies : None
Optional dependencies : None
Start script : execl-toc -S ${socket_name} -m 0777
foreground { dbus-uuidgen --ensure }
execl-cmdline -s { dbus-daemon ${cmd_args} }
Stop script : s6-rmrf ${socket_name}
Environment source : /etc/66/conf/dbus
Environment file : cmd_args=!--system --print-pid=4 --nofork --nopidfile --address=unix:path=/run/dbus/system_bus_socket
socket_dir=!/run/dbus
socket_name=!system_bus_socket
Log name : dbus-log
Log destination : /var/log/66/dbus
Log file :
2020-06-09 12:49:59.802954735 execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-06-09 12:50:00.806662602 execl-toc: fatal: unable to get dirname of: system_bus_socket
2020-06-09 12:50:01.802806639 execl-toc: fatal: unable to get dirname of: system_bus_socket
z@ obliveS6 ~ % 66-enable dbus
66-enable: fatal: unable to parse service file: /usr/lib/66/service/dbus: or its dependencies
z@ obliveS6 [111] ~ % 66-enable -t zz dbus
66-enable: fatal: unable to parse service file: /usr/lib/66/service/dbus: or its dependencies
z@ obliveS6 [111] ~ % sudo 66-enable -t zz dbus
[sudo] password for z:
66-enable: fatal: unable to find tree: /var/lib/66/system/zz: No such file or directory
z@ obliveS6 [111] ~ % sudo 66-enable -t z dbus
66-enable: fatal: unable to find tree: /var/lib/66/system/z: No such file or directory
z@ obliveS6 [111] ~ % sudo 66-enable dbus
66-enable: fatal: unable to find the current tree. You must use -t options
gives me:

z@ obliveS6 ~ % 66-mods.sh boot-user@ z
66-mods.sh: fatal: /usr/lib/66/service/boot-user@ z already exist
z@ obliveS6 [111] ~ % 66-tree -nE boot-user
66-tree: info: Created successfully tree: boot-user
66-tree: info: Enabled successfully tree: boot-user
z@ obliveS6 ~ % 66-enable -t boot-user All-z
66-enable: fatal: unable to parse service file: /usr/lib/66/service/boot-user-z/All-z: or its dependencies
z@ obliveS6 [111] ~ % 66-enable dbus-session@ z
66-enable: info: Ignoring: dbus-session@ z service: already enabled
z@ obliveS6 ~ %
Like the other comment says, you are mixing root level trees and user trees.
User trees go to /home/z/66/....
To see what trees you have created and need/don't need
z@ hostname % sudo 66-intree
shows root's trees
z@ hostname % 66-intree

note any commands you see with % (or $) are run as user, # indicates root

If you use su your prompt will be root@ hostname #
it seems root does not have the env variables

z@ obliveS6 ~ % sudo dbus-launch
dbus-daemon[3928]: Failed to start message bus: "XDG_RUNTIME_DIR" is not set
EOF in dbus-launch reading address from bus daemon

but how to set them?

z@ obliveS6 ~ % sudo 66-enable -t root All-root
66-enable: fatal: unable to resolve source path of: All-root

maybe something like that?
You did a lot of mistake :).

Ok first, you dbus service is not correct. Please be sure to use the last dbus service (0.1.6). 
% sudo pacman -Sy dbus-66serv
Also, in your root tree you mix two different network service. Make a choice between dhcpcd or connmand but do not enable the both. These two service will enter in conflict. In my example i will use connmand.

I assume on this explanation that you don't have any trees (root or regular user) existing on your system. I start from the scratch.
So, first your boot tree should not be enabled. This tree is an exception. 66-boot will bring up this tree at boot time.Well the correct way to create it is: 
% sudo 66-tree -n boot
% sudo 66-enable -C -t boot boot
Now, edit your /etc/66/boot.conf file to suit your needs.
Ok, at this point you should be able to boot properly, but you need to set up some more service like the tty, dbus, .... I will enable it on a tree called root 
% sudo 66-tree -cnE root
% sudo 66-enable -C -t root tty@ tty1 tty@ tty2 dbus connmand consolekit cupsd bluetoothd
Well, your 66 ecosystem is operational to make a reboot. But for now, you want the ability to start an user supervision tree to have dbus-session@ service and other stuff for a regular user.
Creates a new tree and enable the module inside. 
% sudo 66-tree -nE boot-user
% sudo 66-tree -S root boot-user # be sure here to start the boot-user tree after the root tree
Now enable the module inside this new tree 
% sudo 66-mods.sh boot-user@ z
% sudo 66-enable -t boot-user All-z
Ok, the user z will have it's own supervision tree started at boot time.
Now you need to make a new tree for the user z and enable the dbus-session@ service inside it
(note i don't use sudo here, i make this command with z user permissions) 
% 66-tree -cnE base
% 66-enable -C -t base dbus-session@ z
It should be ok, you can try to reboot.
thanks! this instructions are great. it makes more sense to me now.
still dbus seems not to run as root. only as user.
how do i set XDG_RUNTIME_DIR etc for root?

i think i need to put 
export XDG_RUNTIME_DIR=/run/dbus
into some file?

or does it have anything to do that this happens on boot?
login: trying to run a sulogin command
Give root password for maintenance
(or press Control-D to continue):  sulogin: cannot read /dev/tty1: operation not permited
before going further, you need to have an operational system, which is apparently not the case. Your machine doesn't boot properly.
So boot your machine, switch to the tty12 and log on with your user

Now, please provide the following 
% cat /run/66/log/0/current
% 66-intree -g
% sudo 66-intree -g
/run/66/log/0/current seems all good until: 
@ 400000005ee2d3c714caa032 s6-rc: fatal: unable to take locks: Resource temporarily unavailable
@ 400000005ee2d3c714cb8917 66-start: fatal: unable to start services selection
@ 400000005ee2d3c714cd3dab 66-all: fatal: unable to start services of tree: boot
@ 400000005ee2d3c714d26cdd 66-dbctl: fatal: unable to start services selection
@ 400000005ee2d3c714dbe8ba rc.init: fatal: please see the log at /run/66/log/0/current

z@ pc ~ % 66-intree -g
Name         : base
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : z
Symlinks     : svc->source db->source
Contents     : /
               ├─(1078,Enabled,longrun) dbus-session@ z-log
               └─(1082,Enabled,longrun) dbus-session@ z

z@ pc ~ % sudo 66-intree -g
[sudo] password for z: 
Name         : boot
Initialized  : yes
Enabled      : yes
Starts after : root boot-user
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(258,Enabled,classic) tty12
               ├─(down,Enabled,oneshot) system-hostname
               ├─(down,Enabled,oneshot) mount-run
               ├─(down,Enabled,oneshot) populate-run
               ├─(down,Enabled,oneshot) mount-tmp
               ├─(down,Enabled,oneshot) populate-tmp
               ├─(down,Enabled,oneshot) mount-proc
               ├─(down,Enabled,oneshot) mount-sys
               ├─(down,Enabled,oneshot) populate-sys
               ├─(down,Enabled,oneshot) mount-dev
               ├─(down,Enabled,oneshot) mount-pts
               ├─(down,Enabled,oneshot) mount-shm
               ├─(down,Enabled,oneshot) populate-dev
               ├─(down,Enabled,oneshot) mount-cgroups
               ├─(down,Enabled,bundle) 00
               ├─(down,Enabled,oneshot) modules-kernel
               ├─(499,Enabled,longrun) udevd
               ├─(down,Enabled,oneshot) udevadm
               ├─(down,Enabled,oneshot) devices-dmraid
               ├─(down,Enabled,oneshot) system-hwclock
               ├─(down,Enabled,oneshot) system-random
               ├─(down,Enabled,oneshot) modules-system
               ├─(down,Enabled,oneshot) system-sysctl
               ├─(down,Enabled,oneshot) system-fontnkey
               ├─(down,Enabled,oneshot) devices-btrfs
               ├─(down,Enabled,oneshot) devices-crypttab
               ├─(down,Enabled,oneshot) devices-lvm
               ├─(down,Enabled,oneshot) devices-zfs
               ├─(down,Enabled,bundle) system-Devices
               ├─(down,Enabled,oneshot) mount-swap
               ├─(down,Enabled,bundle) all-Mount
               ├─(down,Enabled,oneshot) system-fsck
               ├─(down,Enabled,oneshot) mount-fstab
               ├─(down,Enabled,bundle) all-System
               ├─(down,Enabled,oneshot) mount-rw
               ├─(down,Enabled,oneshot) local-iptables
               ├─(down,Enabled,oneshot) local-ip6tables
               ├─(down,Enabled,oneshot) local-loop
               ├─(down,Enabled,oneshot) local-time
               ├─(down,Enabled,oneshot) local-authfiles
               ├─(down,Enabled,oneshot) local-tmpfiles
               ├─(down,Enabled,oneshot) local-rc
               ├─(down,Enabled,oneshot) local-dmesg
               ├─(down,Enabled,oneshot) local-sethostname
               ├─(down,Enabled,bundle) all-Local
               ├─(down,Enabled,oneshot) all-Runtime
               └─(down,Enabled,bundle) All

Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) mount-run-z
               ├─(up,Enabled,oneshot) setenv-z
               ├─(943,Enabled,longrun) scandir-z-log
               ├─(972,Enabled,longrun) scandir-z
               └─(up,Enabled,bundle) All-z

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(842,Enabled,classic) fan
               ├─(845,Enabled,classic) cupsd-log
               ├─(844,Enabled,classic) bluetoothd-log
               ├─(982,Enabled,classic) bluetoothd
               ├─(850,Enabled,classic) cupsd
               ├─(1013,Enabled,classic) tty@ tty1
               ├─(849,Enabled,classic) tty@ tty2
               ├─(877,Enabled,longrun) dbus-log
               ├─(881,Enabled,longrun) dbus
               ├─(875,Enabled,longrun) connmand-log
               ├─(889,Enabled,longrun) connmand
               ├─(876,Enabled,longrun) consolekit-log
               └─(890,Enabled,longrun) consolekit
i said before your boot tree should not be marked enabled and should be the first to start(so your Starts after need to be: None). so simply 
% sudo 66-tree -D boot
% sudo 66-tree -S boot boot
reboot, it should be ok
did it, now its booting a bit less. hangs in tty1. login only possible via tty12
and to start x i had to manually 
% sudo export XDG_RUNTIME_DIR=/run/dbus
% sudo 66-all up
% 66-all up
% sudo dbus-launch
to get it on

but the only error in the log is now:
@ 400000005ee3067f01065d63 66-dbctl: fatal: unable to start services selection

and my intree
z@ pc ~ % sudo 66-intree -g
[sudo] password for z: 
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(259,Enabled,classic) tty12
               ├─(down,Enabled,oneshot) system-hostname
               ├─(down,Enabled,oneshot) mount-run
               ├─(down,Enabled,oneshot) populate-run
               ├─(down,Enabled,oneshot) mount-tmp
               ├─(down,Enabled,oneshot) populate-tmp
               ├─(down,Enabled,oneshot) mount-proc
               ├─(down,Enabled,oneshot) mount-sys
               ├─(down,Enabled,oneshot) populate-sys
               ├─(down,Enabled,oneshot) mount-dev
               ├─(down,Enabled,oneshot) mount-pts
               ├─(down,Enabled,oneshot) mount-shm
               ├─(down,Enabled,oneshot) populate-dev
               ├─(down,Enabled,oneshot) mount-cgroups
               ├─(down,Enabled,bundle) 00
               ├─(down,Enabled,oneshot) modules-kernel
               ├─(498,Enabled,longrun) udevd
               ├─(down,Enabled,oneshot) udevadm
               ├─(down,Enabled,oneshot) devices-dmraid
               ├─(down,Enabled,oneshot) system-hwclock
               ├─(down,Enabled,oneshot) system-random
               ├─(down,Enabled,oneshot) modules-system
               ├─(down,Enabled,oneshot) system-sysctl
               ├─(down,Enabled,oneshot) system-fontnkey
               ├─(down,Enabled,oneshot) devices-btrfs
               ├─(down,Enabled,oneshot) devices-crypttab
               ├─(down,Enabled,oneshot) devices-lvm
               ├─(down,Enabled,oneshot) devices-zfs
               ├─(down,Enabled,bundle) system-Devices
               ├─(down,Enabled,oneshot) mount-swap
               ├─(down,Enabled,bundle) all-Mount
               ├─(down,Enabled,oneshot) system-fsck
               ├─(down,Enabled,oneshot) mount-fstab
               ├─(down,Enabled,bundle) all-System
               ├─(down,Enabled,oneshot) mount-rw
               ├─(down,Enabled,oneshot) local-iptables
               ├─(down,Enabled,oneshot) local-ip6tables
               ├─(down,Enabled,oneshot) local-loop
               ├─(down,Enabled,oneshot) local-time
               ├─(down,Enabled,oneshot) local-authfiles
               ├─(down,Enabled,oneshot) local-tmpfiles
               ├─(down,Enabled,oneshot) local-rc
               ├─(down,Enabled,oneshot) local-dmesg
               ├─(down,Enabled,oneshot) local-sethostname
               ├─(down,Enabled,bundle) all-Local
               ├─(down,Enabled,oneshot) all-Runtime
               └─(down,Enabled,bundle) All

Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) mount-run-z
               ├─(up,Enabled,oneshot) setenv-z
               ├─(885,Enabled,longrun) scandir-z-log
               ├─(914,Enabled,longrun) scandir-z
               └─(up,Enabled,bundle) All-z

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(791,Enabled,classic) fan
               ├─(798,Enabled,classic) cupsd-log
               ├─(793,Enabled,classic) bluetoothd-log
               ├─(922,Enabled,classic) bluetoothd
               ├─(796,Enabled,classic) cupsd
               ├─(801,Enabled,classic) tty@ tty1
               ├─(800,Enabled,classic) tty@ tty2
               ├─(826,Enabled,longrun) dbus-log
               ├─(832,Enabled,longrun) dbus
               ├─(828,Enabled,longrun) connmand-log
               ├─(841,Enabled,longrun) connmand
               ├─(827,Enabled,longrun) consolekit-log
               └─(840,Enabled,longrun) consolekit
but i do have everything right now, no?
i don't know what happens on your machine but i will find it :p.
An error in your /run/66/log/0/current meaning that something is wrong
So, please, edit your /etc/66/init.conf and set VERBOSITY=4.
Reboot and send us the complete /run/66/log/0/current file.
@ 400000005ee3394a0911a69c [Initiate db of tree boot...]
@ 400000005ee3394a092346dc 66-init(src/lib66/rc_init.c: rc_init: 119): tracing: initiate db of tree: boot ...
@ 400000005ee3394a0a5e96e4 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-hostname
@ 400000005ee3394a0a5e9ce2 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-hostname
@ 400000005ee3394a0a5ea4cf 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-run
@ 400000005ee3394a0a5ea6cf 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-run
@ 400000005ee3394a0a5ea8df 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-run
@ 400000005ee3394a0a5ee7a9 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-run
@ 400000005ee3394a0a5ee9ea 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-tmp
@ 400000005ee3394a0a5eeb29 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-tmp
@ 400000005ee3394a0a5eec98 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-tmp
@ 400000005ee3394a0a5f03d5 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-tmp
@ 400000005ee3394a0a5f059d 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-proc
@ 400000005ee3394a0a5f1a66 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-proc
@ 400000005ee3394a0a5f1c1e 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-sys
@ 400000005ee3394a0a5f631c 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-sys
@ 400000005ee3394a0a5f6625 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-sys
@ 400000005ee3394a0a5f7c0e 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-sys
@ 400000005ee3394a0a5f8ee5 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-dev
@ 400000005ee3394a0a5fe1df 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-dev
@ 400000005ee3394a0a5fe436 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-pts
@ 400000005ee3394a0a5fe587 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-pts
@ 400000005ee3394a0a5ffcb8 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-shm
@ 400000005ee3394a0a60107f 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-shm
@ 400000005ee3394a0a60122f 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: populate-dev
@ 400000005ee3394a0a6039d9 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: populate-dev
@ 400000005ee3394a0a603bdb 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-cgroups
@ 400000005ee3394a0a60628c 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-cgroups
@ 400000005ee3394a0a6064cf 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: 00
@ 400000005ee3394a0a608af2 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: 00
@ 400000005ee3394a0a608cf4 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-swap
@ 400000005ee3394a0a612789 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-swap
@ 400000005ee3394a0a612bcf 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-Mount
@ 400000005ee3394a0a612d48 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-Mount
@ 400000005ee3394a0a612eb5 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-hwclock
@ 400000005ee3394a0a615980 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-hwclock
@ 400000005ee3394a0a615b7e 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: modules-kernel
@ 400000005ee3394a0a6187db 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: modules-kernel
@ 400000005ee3394a0a618a15 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-random
@ 400000005ee3394a0a61c06e 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-random
@ 400000005ee3394a0a61c283 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: modules-system
@ 400000005ee3394a0a61dbad 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: modules-system
@ 400000005ee3394a0a61dd64 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-sysctl
@ 400000005ee3394a0a6216c3 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-sysctl
@ 400000005ee3394a0a6218ee 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: udevd
@ 400000005ee3394a0a622f29 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: udevd
@ 400000005ee3394a0a6230a7 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: udevadm
@ 400000005ee3394a0a62526b 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: udevadm
@ 400000005ee3394a0a62540f 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-fontnkey
@ 400000005ee3394a0a62a378 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-fontnkey
@ 400000005ee3394a0a62a5e4 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-dmraid
@ 400000005ee3394a0a62a730 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-dmraid
@ 400000005ee3394a0a62be94 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-btrfs
@ 400000005ee3394a0a62d2a8 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-btrfs
@ 400000005ee3394a0a62d451 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-crypttab
@ 400000005ee3394a0a62fad2 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-crypttab
@ 400000005ee3394a0a62fcc7 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-lvm
@ 400000005ee3394a0a632452 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-lvm
@ 400000005ee3394a0a632670 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: devices-zfs
@ 400000005ee3394a0a634d0b 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: devices-zfs
@ 400000005ee3394a0a634efe 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-Devices
@ 400000005ee3394a0a637539 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-Devices
@ 400000005ee3394a0a637729 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: system-fsck
@ 400000005ee3394a0a63c929 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: system-fsck
@ 400000005ee3394a0a63cb91 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-fstab
@ 400000005ee3394a0a63cce4 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-fstab
@ 400000005ee3394a0a63e427 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-System
@ 400000005ee3394a0a63f809 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-System
@ 400000005ee3394a0a63f9c5 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: mount-rw
@ 400000005ee3394a0a642020 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: mount-rw
@ 400000005ee3394a0a64222c 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-iptables
@ 400000005ee3394a0a64488f 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-iptables
@ 400000005ee3394a0a647df2 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-ip6tables
@ 400000005ee3394a0a64b4f4 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-ip6tables
@ 400000005ee3394a0a64b735 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-loop
@ 400000005ee3394a0a64f0bf 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-loop
@ 400000005ee3394a0a64f26b 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-sethostname
@ 400000005ee3394a0a652f6f 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-sethostname
@ 400000005ee3394a0a653104 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-time
@ 400000005ee3394a0a656087 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-time
@ 400000005ee3394a0a65621d 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-authfiles
@ 400000005ee3394a0a6589f5 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-authfiles
@ 400000005ee3394a0a658b8e 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-tmpfiles
@ 400000005ee3394a0a65b486 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-tmpfiles
@ 400000005ee3394a0a65b623 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-rc
@ 400000005ee3394a0a65dce7 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-rc
@ 400000005ee3394a0a65de7b 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: local-dmesg
@ 400000005ee3394a0a6605aa 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: local-dmesg
@ 400000005ee3394a0a660742 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-Local
@ 400000005ee3394a0a662f30 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-Local
@ 400000005ee3394a0a6630c4 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: all-Runtime
@ 400000005ee3394a0a6657ac 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: all-Runtime
@ 400000005ee3394a0a665947 66-init(src/lib66/rc_init.c: rc_init: 145): tracing: Write state file of: All
@ 400000005ee3394a0a6680ad 66-init(src/lib66/rc_init.c: rc_init: 151): info: Initialized successfully: All
@ 400000005ee3394a0a7204ec [Start db services of tree boot...]
@ 400000005ee3394a0acfaaaa s6-rc: info: bringing selected services up
@ 400000005ee3394a0ad748b3 s6-rc: info: processing service s6rc-oneshot-runner: starting
@ 400000005ee3394a0b2886c3 s6-rc: info: service s6rc-oneshot-runner started successfully
@ 400000005ee3394a0b3225db s6-rc: info: processing service system-hostname: starting
@ 400000005ee3394a0b33fc78 s6-rc: info: processing service mount-tmp: starting
@ 400000005ee3394a0b35c636 s6-rc: info: processing service mount-run: starting
@ 400000005ee3394a0b38388c s6-rc: info: processing service mount-proc: starting
@ 400000005ee3394a0b44c13e s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0b44c5c4 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0b44c83b s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0b49d89c s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0bbf2387 [system-hostname] starts...
@ 400000005ee3394a0be4fa95 [system-hostname] started successfully
@ 400000005ee3394a0be89152 s6-rc: info: service system-hostname started successfully
@ 400000005ee3394a0c5c9e45 s6-rc: info: service mount-proc started successfully
@ 400000005ee3394a0c5f21fb s6-rc: info: processing service mount-sys: starting
@ 400000005ee3394a0c5fb34a s6-rc: info: service mount-run started successfully
@ 400000005ee3394a0c625357 s6-rc: info: processing service populate-run: starting
@ 400000005ee3394a0c681a62 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0c6a6285 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0c7f0893 [mount-tmp] starts...
@ 400000005ee3394a0c982b9b [populate-run] starts...
@ 400000005ee3394a0ca6f1a5 [mount-tmp] started successfully
@ 400000005ee3394a0cac3435 s6-rc: info: service mount-tmp started successfully
@ 400000005ee3394a0cae0333 s6-rc: info: processing service populate-tmp: starting
@ 400000005ee3394a0cae9f97 s6-rc: info: service mount-sys started successfully
@ 400000005ee3394a0cb0820e s6-rc: info: processing service populate-sys: starting
@ 400000005ee3394a0cb7d5ba s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0cb99b22 s6-rc: info: processing service mount-dev: starting
@ 400000005ee3394a0cc040e6 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0cc04659 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0cf50c07 [populate-sys] starts...
@ 400000005ee3394a0d07db97 [populate-tmp] starts...
@ 400000005ee3394a0d210e29 s6-rc: info: service mount-dev started successfully
@ 400000005ee3394a0d236c90 s6-rc: info: processing service populate-dev: starting
@ 400000005ee3394a0d2aaff2 s6-rc: info: processing service mount-shm: starting
@ 400000005ee3394a0d2e6f0c s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0d2fb876 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0d32a6e4 s6-rc: info: processing service mount-pts: starting
@ 400000005ee3394a0d3805da s6-rc: info: processing service mount-cgroups: starting
@ 400000005ee3394a0d3d1720 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0d40ecf1 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0d4c51b2 s6-rc: info: processing service devices-zfs: starting
@ 400000005ee3394a0d54e865 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a0d972d4a [mount-shm] starts...
@ 400000005ee3394a0d98aec6 [populate-dev] starts...
@ 400000005ee3394a0d9e6241 [populate-tmp] started successfully
@ 400000005ee3394a0da3d422 s6-rc: info: service populate-tmp started successfully
@ 400000005ee3394a0dac636f [populate-run] started successfully
@ 400000005ee3394a0db505fe [mount-pts] starts...
@ 400000005ee3394a0dbddee0 s6-rc: info: service populate-run started successfully
@ 400000005ee3394a0df96e71 [mount-zfs] deactivated
@ 400000005ee3394a0e032511 [mount-cgroups] starts...
@ 400000005ee3394a0e035399 s6-rc: info: service devices-zfs started successfully
@ 400000005ee3394a0e0468d8 [mount-shm] started successfully
@ 400000005ee3394a0e0defed s6-rc: info: service mount-shm started successfully
@ 400000005ee3394a0e251c6c [mount-pts] started successfully
@ 400000005ee3394a0e317879 s6-rc: info: service mount-pts started successfully
@ 400000005ee3394a0e845c9f [populate-dev] started successfully
@ 400000005ee3394a0e87bd3f s6-rc: info: service populate-dev started successfully
@ 400000005ee3394a0ec7d841 [populate-sys] started successfully
@ 400000005ee3394a0eca8b3f s6-rc: info: service populate-sys started successfully
@ 400000005ee3394a11d65d1c [mount-cgroups] started successfully
@ 400000005ee3394a11d9ca2e s6-rc: info: service mount-cgroups started successfully
@ 400000005ee3394a11dc78ab s6-rc: info: processing service system-sysctl: starting
@ 400000005ee3394a11de8251 s6-rc: info: processing service system-random: starting
@ 400000005ee3394a11edb5ad s6-rc: info: processing service system-hwclock: starting
@ 400000005ee3394a11edba56 s6-rc: info: processing service mount-swap: starting
@ 400000005ee3394a11edbce2 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a11edbf5e s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a11edc165 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a11edc35a s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a11f4d048 s6-rc: info: processing service modules-system: starting
@ 400000005ee3394a11fcb352 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a11fe2313 s6-rc: info: processing service modules-kernel: starting
@ 400000005ee3394a1205b1c2 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee3394a124ae1ca [system-random] starts...
@ 400000005ee3394a125425a9 [system-hwclock] starts...
@ 400000005ee3394a125aa6fa [modules-system] starts...
@ 400000005ee3394a1261955f [modules-kernel] starts...
@ 400000005ee3394a12700e07 [mount-swap] deactivated
@ 400000005ee3394a12760c5a s6-rc: info: service mount-swap started successfully
@ 400000005ee3394a127fc77e [system-sysctl] starts...
@ 400000005ee3394a12a620b4 [system-random] started successfully
@ 400000005ee3394a12a984e2 s6-rc: info: service system-random started successfully
@ 400000005ee3394a12d5f3f1 kernel.sysrq = 1
@ 400000005ee3394a12d5f800 kernel.core_uses_pid = 1
@ 400000005ee3394a12d5f961 fs.protected_hardlinks = 1
@ 400000005ee3394a12d5fac0 fs.protected_symlinks = 1
@ 400000005ee3394a12d5fc35 fs.inotify.max_user_instances = 1024
@ 400000005ee3394a12d5fdea fs.inotify.max_user_watches = 524288
@ 400000005ee3394a12eabf86 [system-sysctl] started successfully
@ 400000005ee3394a12ee0645 s6-rc: info: service system-sysctl started successfully
@ 400000005ee31d2a135ffb81 [system-hwclock] started successfully
@ 400000005ee31d2a13633594 s6-rc: info: service system-hwclock started successfully
@ 400000005ee31d2a17da79ca Load modules crypto_user.ko.xz 
@ 400000005ee31d2a180727e2 [modules-system] started successfully
@ 400000005ee31d2a180cc22a s6-rc: info: service modules-system started successfully
@ 400000005ee31d2a35ff943f [modules-kernel] started successfully
@ 400000005ee31d2a360ab257 s6-rc: info: service modules-kernel started successfully
@ 400000005ee31d2a3610189a s6-rc: info: processing service udevd: starting
@ 400000005ee31d2a36624690 [udevd] starts...
@ 400000005ee31d2b36eee67c s6-rc: info: service udevd started successfully
@ 400000005ee31d2b36f1de80 s6-rc: info: processing service udevadm: starting
@ 400000005ee31d2b36f9aa0f s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee31d2b372231f9 [udevadm] starts...
@ 400000005ee31d2e223bdf73 [udevadm] started successfully
@ 400000005ee31d2e2241d78a s6-rc: info: service udevadm started successfully
@ 400000005ee31d2e224527eb s6-rc: info: processing service system-fontnkey: starting
@ 400000005ee31d2e22476460 s6-rc: info: processing service devices-lvm: starting
@ 400000005ee31d2e2253ed08 s6-rc: info: processing service devices-dmraid: starting
@ 400000005ee31d2e2253f236 s6-rc: info: processing service devices-crypttab: starting
@ 400000005ee31d2e2253f5bc s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee31d2e2253f7f0 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee31d2e2253fa9d s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee31d2e226826b0 s6-rc: info: processing service devices-btrfs: starting
@ 400000005ee31d2e22682d29 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee31d2e22683003 s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee31d2e22a779f4 [system-fontnkey] starts...
@ 400000005ee31d2e22bb2519 [devices-lvm] deactivated
@ 400000005ee31d2e22bca72f [devices-dmraid] deactivated
@ 400000005ee31d2e22c08c3d s6-rc: info: service devices-dmraid started successfully
@ 400000005ee31d2e22c1a3a9 s6-rc: info: service devices-lvm started successfully
@ 400000005ee31d2e22c66fd6 [devices-crypttab] deactivated
@ 400000005ee31d2e22ca469e s6-rc: info: service devices-crypttab started successfully
@ 400000005ee31d2e22d2176f [devices-btrfs] deactivated
@ 400000005ee31d2e22d60e92 s6-rc: info: service devices-btrfs started successfully
@ 400000005ee31d2e23ecff07 [system-fontnkey] started successfully
@ 400000005ee31d2e23f23f46 s6-rc: info: service system-fontnkey started successfully
@ 400000005ee31d2e23f43ab4 s6-rc: info: processing service system-fsck: starting
@ 400000005ee31d2e23faf69c s6-ipcclient: connected to /run/66/tree/0/boot/servicedirs/s6rc-oneshot-runner/s
@ 400000005ee31d2f00cc6746 e2fsck: Cannot continue, aborting.
@ 400000005ee31d2f00cc6fc7 
@ 400000005ee31d2f00cc722b 
@ 400000005ee31d2f00d30a4e s6-rc: warning: unable to start service system-fsck: command exited 8
@ 400000005ee31d2f00d45721 66-dbctl(src/lib66/ssexec_dbctl.c: ssexec_dbctl: 343): fatal: unable to start services selection
@ 400000005ee31d2f00dfb16a rc.init: fatal: please see the log at /run/66/log/0/current
e2fsck: Cannot continue, aborting.
is ab bit wierd because my root sda is clean and other then that are no drives connected
first time i see this error, something strange here.
please provide 
% sudo 66-inservice -t boot system-fsck

z@ pc ~ % sudo 66-inservice -t boot system-fsck
[sudo] password for z: 
Name                  : system-fsck
Version               : None
In tree               : boot
Status                : enabled, down
Type                  : oneshot
Description           : Check filesystem partition
Source                : /usr/lib/66/service/boot-old/system/system-fsck
Live                  : /run/66/tree/0/boot/servicedirs/system-fsck
Dependencies          : all-Mount system-Devices system-fontnkey
External dependencies : None
Optional dependencies : None
Start script          : 	execl-envfile ${conf_file}
                        	ifelse -X { s6-test ${FORCECHCK} = yes }
                        	{
                        		redirfd -w 1 /dev/console
                        		if { 66-echo -- [system-fsck] FORCECHCK was asked... }
                        		execl-cmdline -s { fsck -f ${cmd_args} }
                        	}
                        	if { 66-echo -- [system-fsck] starts... }
                        	foreground { execl-cmdline -s { fsck ${cmd_args} } }
                        	importas ? ?
                        	ifelse { test $? -gt 1 }
                        	{ 
                        		if { 66-echo -- fsck reports errors -- at least system should be rebooted }
                        		redirfd -w 1 /dev/console
                        		66-echo -- fsck reports errors -- at least system should be rebooted
                        		
                        	}
                        	66-echo -- [system-fsck] started successfully
Stop script           : None
Environment source    : /etc/66/conf/system-fsck
Environment file      : cmd_args=!-A -T -a noopts=_netdev
                        conf_file=!/etc/66/boot.conf
Log name              : None
Log destination       : None
Log file              : None
any fancy filesystem partition that e2fsck can not read maybe?
Or a filesystem marked as of different type on fstab?
any fancy filesystem partition that e2fsck can not read maybe?
yes, this can cause trouble
Or a filesystem marked as of different type on fstab?
fstab cannot interfere here because the mount-fstab service is launched after the system-fsck service.

What is surprised me is this: 
Source                : /usr/lib/66/service/boot-old/system/system-fsck
You seem to use your own boot directory called boot-old.

So first, this not the good way to make your own service(frontend or folder). The /usr/lib/66/service is the reserved directory for the packager(pacman). Every service with the same name will be overwritten by pacman at an service upgrade, and so you loose your changes. If you want to change a service, make a copy from /usr/lib/66/service/<service> to /etc/66/service/<service>. This directory take precedence when you enable the service. So, in that case when an upgrade come out the service of you local copy at /etc/66/service is not touched.

So, you have some partition/disk that fsck cannot read properly. Look the exit code 
@ 400000005ee31d2f00d30a4e s6-rc: warning: unable to start service system-fsck: command exited 8
According to the https://www.man7.org/linux/man-pages/man8/e2fsck.8.html fsck man page, the exit code 8 point out to an operational error. At this point i can't help you more without a direct access on your system.
Boot your machine, log on tty12 and try to run the fsck manually to see what happen. Check every single disk that you have. Remove any external disk,... So diagnose.

Now, about your boot directory copy. You can try to test with the original boot services set moving your /usr/lib/66/service/boot-old somewhere else (not on /etc/66/service) and enable again the complete boot services set: 
# 66-enable -C -F -t boot boot
I don't think that will help but you can try to be sure.

Powered by Obarun