@ 400000005d3c46321dbb714c [mount-swap] starts...
@ 400000005d3c46321dbbe67c [mount-zfs] desactived
@ 400000005d3c46321dc0fb44 s6-rc: info: service mount-zfs started successfully
@ 400000005d3c46322629b104 [system-random] started successfully
@ 400000005d3c4632262cdd84 s6-rc: info: service system-random started successfully
@ 400000005d3c4632292e907c kernel.sysrq = 1
@ 400000005d3c4632292ea01c kernel.core_uses_pid = 1
@ 400000005d3c4632292ea01c fs.protected_hardlinks = 1
@ 400000005d3c4632292ea01c fs.protected_symlinks = 1
@ 400000005d3c4632292ea404 fs.inotify.max_user_instances = 1024
@ 400000005d3c4632292ea404 fs.inotify.max_user_watches = 524288
@ 400000005d3c4632294fb0f4 [system-sysctl] started successfully
@ 400000005d3c46322955ee9c s6-rc: info: service system-sysctl started successfully
Nothing except for successfully and desactived (by the way this needs to be corrected to deactivated)
When I use filechecks on boot.conf which take much longer than in the past I get a "warning" on / root that it has a superblock that it was last written in the future. But why would that cause 66 to prevent root initialization
I removed root2 again and created root from scratch
I enabled dhcpcd, one at a time, then ntpd, then tty@ tty3, then tty2, then rebooted, in case there was a problem somewhere with tty1
Same thing. 66-all and all ok, I enabled tty1 without specifying -t and all three ttys were up and running.
Reboot ... same crap.
I even edited fstab and left root and swap, nothing else, ... the same.
This is the exact same behavior I've had on another pc for a long time, nothing to do with v02, I just don't go there often to pursue it.
PS I removed kernels and installed different ones, just in case the img was corrupt or something. No change.