@ thededem
Many many thanks for your report.
Also I found, that on line 16 in devices-crypttab the d is missing in execl-cmdline and the service therefore fails.
this is fixed now
It did also segfault, when the filesystem was not writable.
i'm agreed about a crash not about a segfault, this should not happen in any case! So, my bad, i need to investigate and solve this issue. Again thanks for this report. This is kind of reports are very usefull and help to provide a good soft.
I was able to fix this issue for the root tree by deleting the tty1-directory from the svc-directory under /var/lib/66/system/root/servicedirs. The same issue however did also occur for tty12 in the boot tree and for that I ended up deleting and recreating the boot tree.
NEVER, should i say NEVER, touch directly the heart of 66 without a deep knowledge of is working. Removing the /var/lib/66/system/root/servicedirs/{svc,db}/ is not sufficient. Some files need to be updated(removed,added) too at e.g .resolve directory, backup directory,... and so on.
When you do stuff like this you entirely broke the working flow of 66 and you take the risk to have an inconsistent 66 eco-system. When you get trouble, simply downgrade 66 and ask here for advice. This is the best way.
I can guarantee the good working of 66 if the user broke it :).