System can't boot after 66 snapshot restore

dvam

Hello Eric and obaruners,

upgrading to 66 0.9.1.2 went smoothly, yesterday. But ... my curiosity to try way back to 66 0.8.2.2, by snapshot restore and downgrading of packages, with a few missteps, resulted in a system that wouldn't boot after that.

[Starts stage1 process ...]
boot: info: Create live scandir at: /run/66
scandir: info: Create scandir /run/66/scandir/0 ...
boot: info: Initiate earlier service of tree: boot
tree: warning: unable to get information of service: boot@system:canopy: Invalid argument
tree: warning: unable to include dependences of service: boot@system:tty-rc@tty1 in fraph selection
tree: fatal: unable to resolve the graph: Invalid argument
boot: warning: unable to initiate earlier service of tree: boot: Invalid argument
Enter root password for system maintenance
(or press Control-D to

Any help or advice are welcome! Thank's.

eric

dvam with a few missteps

i don' know what you did exactly and how you did. To properly downgrade, you need to:

66 restore system@0.8.2.2
pacman -U /var/cache/pacman/pkg/<oblibs> # do the same for skalibs, execline, s6-linux-utils, s6-portable-utils, 66, 66-tools, obsysusers, oblog, and ALL services that you used (boot@system, boot-user@,...) before the migration.

After, do not try to use 66 but reboot immediately. You should get the exact same system than before the migration.

66 migration don't know anything about the packages installed and do not known how to downgrade, the migration work only work from the top down. To downgrade you need to take yourself of package eco-system around 66.

dvam

It seems that's exactly what I did, except that firstly I did

pacman -Rns 66-userd-66serv

because that was a prerequisite for downgrading other packages, as you suggest.

After that I did

66 restore system@0.8.2.2

and then rebooted the system ... which didn't happen because it staled , and after a while I shutdown the system because it was unresponsive.

Does it make sense to repeat the upgrade to 66 0.9.1.2 on a system that doesn't boot?

eric

dvam It seems that's exactly what I did, except that firstly I did

pacman -Rns 66-userd-66serv

because that was a prerequisite for downgrading other packages, as you suggest.

That's ok.

It's difficult to help you because you only provide few information. Did you got the tty12 running? do you get a sulogin?

dvam Does it make sense to repeat the upgrade to 66 0.9.1.2 on a system that doesn't boot?

no sense at all. How to do apply it? but again do you any tty running?

dvam

I was bussy, sorry ... I repeated the process of restoring the previous snapshot 0.8.2.2 ... now there is no warning from last time: unable to: get, include, resolve, initiate ... but the boot process stops again ...

[Starts stage1 process ...]
boot: info: Create live scandir at: /run/66
scandir: info: Create scandir /run/66/scandir/0 ...
boot: info: Initiate earlier service of tree: boot
tree: info: Initialized successfully: boot@system: tty-earlier@tty12
boot: info: Starts boot logger at /run/66/log/0

Ctrl+Alt+F12 gives the login and then you get the desktop which is completely unresponsive. Everything is there and nothing works...

2026-09-02 18:38:41.755020772  [Start services of tree ...]
2026-09-02 18:38:41.779516200  start: info: Initialized successfully: openntpd
2026-09-02 18:38:41.779524539  start: info: Initialized successfully: openntpd-log
2026-09-02 18:38:41.779526555  start: info: Initialized successfully: crond
2026-09-02 18:38:41.779528976  start: info: Initialized successfully: crond-log
2026-09-02 18:38:41.779530615  start: info: Initialized successfully: dbus
2026-09-02 18:38:41.779532079  start: info: Initialized successfully: dbus-log
2026-09-02 18:38:41.779534060  start: info: Initialized successfully: bluetoothd
2026-09-02 18:38:41.779536606  start: info: Initialized successfully: bluetoothd-log
2026-09-02 18:38:41.779538507  start: info: Initialized successfully: networkmanager
2026-09-02 18:38:41.779540118  start: info: Initialized successfully: networkmanager-log
2026-09-02 18:38:41.793644203  66-execute: info: Starting service: networkmanager-log
2026-09-02 18:38:41.796330952  66-execute: info: Starting service: dbus-log
2026-09-02 18:38:41.797286284  66-execute: info: Starting service: openntpd-log
2026-09-02 18:38:41.799381634  66-execute: info: Starting service: crond-log
2026-09-02 18:38:41.801794251  signal: info: Successfully started service: networkmanager-log
2026-09-02 18:38:41.802112504  66-execute: info: Starting service: bluetoothd-log
2026-09-02 18:38:41.804296499  signal: info: Successfully started service: dbus-log
2026-09-02 18:38:41.804381689  signal: info: Successfully started service: crond-log
2026-09-02 18:38:41.805768598  signal: info: Successfully started service: openntpd-log
2026-09-02 18:38:41.806618163  signal: info: Successfully started service: bluetoothd-log
2026-09-02 18:38:41.815877717  signal: info: Successfully started service: crond
2026-09-02 18:38:41.821618741  signal: info: Successfully started service: bluetoothd
2026-09-02 18:38:41.825495655  signal: info: Successfully started service: openntpd
2026-09-02 18:38:41.883710599  signal: info: Successfully started service: dbus
2026-09-02 18:38:41.889981763  signal: info: Successfully started service: networkmanager
2026-09-02 18:38:41.890934260  tree: info: Successfully started tree: global
2026-09-02 18:38:41.913871442  start: info: Initialized successfully: boot-user@qwe
2026-09-02 18:38:41.914109608  start: info: Initialized successfully: scandir@qwe
2026-09-02 18:38:41.914115068  start: info: Initialized successfully: scandir@qwe:svscan@qwe-log
2026-09-02 18:38:41.914117074  start: info: Initialized successfully: scandir@qwe:svscan@qwe
2026-09-02 18:38:41.919122427  signal: warning: scandir@qwe:setenv@qwe already initialized -- ignore it
2026-09-02 18:38:41.919272051  signal: warning: scandir@qwe:svscan@qwe-log already initialized -- ignore it
2026-09-02 18:38:41.919304706  signal: warning: scandir@qwe:svscan@qwe already initialized -- ignore it
2026-09-02 18:38:41.934988522  66-execute: info: Starting service: scandir@qwe:svscan@qwe-log
2026-09-02 18:38:41.943335330  signal: info: Successfully started service: scandir@qwe:svscan@qwe-log
2026-09-02 18:38:42.011621094  signal: info: Successfully started service: scandir@qwe:setenv@qwe
2026-09-02 18:38:42.034146246  signal: info: Successfully started service: scandir@qwe:svscan@qwe
2026-09-02 18:38:42.034467524  signal: info: Successfully started service: scandir@qwe
2026-09-02 18:38:42.035117135  signal: warning: boot-user@qwe:mount-run@qwe already initialized -- ignore it
2026-09-02 18:38:42.058343784  signal: info: Successfully started service: boot-user@qwe:mount-run@qwe
2026-09-02 18:38:42.058631166  signal: info: Successfully started service: boot-user@qwe
2026-09-02 18:38:42.059024493  tree: info: Successfully started tree: session
2026-09-02 18:38:42.746613545  66-execute: info: Starting service: boot@system:tty-earlier@tty12

This is /run/66/log/0/current file.
Thanks a lot.

eric

It sound like a boot tree contents services which are not enabled. Your boot doesn't crash, it seems to just not activate the services.
This is easy to check:

# 66 tree status -g boot

You should see the services marked enabled

Anyway, try this:

# 66 enable boot@system
# check again the state
# 66 tree status -g boot
# check your configuration
# 66 configure boot@system
# apply  the changes if any
# 66 reconfigure boot@system
# reboot

It should be ok.

dvam

No change yet ... all boot services were already enabled but uninitialized, with the exception of: udevd, tty-rc@tt1, tty-rc@tt2 all with (pid=0 ...) and boot@system: tty-earlier@tty12 which was (obviously) started.

I noticed when the system is accessed from an external maintenance system and when the 66 status is requested, the message is as follows

[qwe@qs6 /]$ sudo 66 status
status: fatal: unable to read state file of: boot@system:system-hostname -- please make a bug report
[qwe@qs6 /]$ 66 status
status: fatal: unable to read state file of: xdg-user-dirs -- please make a bug report
[qwe@qs6 /]$

and that is the point where the boot process stops.

Could it be that the snapshot is corrupted?

eric

dvam Could it be that the snapshot is corrupted?

An error at read of a state file may say that your 66 eco-system is corrupted. maybe it will be better to start from scratch.

follow this to get the machine booting(from the new version):

boot and go to tty12, take care of your boot configuration if you don't remember your previous configuration making a copy (this is optional):

cp /etc/66/conf/boot@system/version/boot@system /path/to/save/the/file

You can use tricks below, you need to be root (not sudo), and do the same for each user.

remove all services from all trees

# for i in $(66 tree resolve -nf contents Master); do for s in $(66 tree resolve -nf contents $i); do case $s in *-log) ;; *) 66 remove $s ;; esac; done ;done

remove your trees

# for i in $(66 tree resolve -nf contents Master); do 66 tree remove $i;done

Now rebuild your trees and enable services on it.

Remaking the boot operational

# 66 enable boot@system
# 66 configure boot@system
# 66 reconfigure boot@system

This should be sufficient for the boot part. Try to reboot, you should get at least the tty1 running and the tty12(obviously).

If you boot is ok, you can now enable your previous services.

dvam

No change again ... the first command gives a message ...

# for i in $(66 tree resolve -nf contents Master); do for s in $(66 tree resolve -nf contents $i); do case $s in *-log) ;; *) 66 remove $s ;; esac; done ;done
tree: fatal: unable to find tree: -nf: No such file or directory

so I gave up and decided to continue removing the boot services and tree manually ... it all went normally, except during the configuration which was done but with a message ...

#66 configure boot@system
Cannot open master and slave sides of pty: No such file or directory

In the end I returned to the beginning:

all boot services enabled and uninitialized (except the three previously mentioned)
on the global and session trees all services started
on the user tree global all services enabled with pid=0 except xdg-user-dirs which is uninitialized.

eric

dvam tree: fatal: unable to find tree: -nf: No such file or directory

Are you using the latest version?

i can help you like that, i'm completely blind.

please share the following (as root):

66 tree status -g
66 tree resolve boot
66 log system # or with the previous version give the contents of /run/66/log/0/current

dvam

Last Sunday my system was on 66 0.8.2.2 ... then the time is come to upgrade to 66 0.9.1.2 and it went smoothly. After a few hours, out of curiosity, I decided to try the way back to 66 0.8.2.2 ...

During the migration 66 from version 0.9.1.2 to version 0.8.2.2, which went normally including: restoring snapshot and downgrading 66 eco-system packages and services, the system got stuck and no longer boots.

#66 tree status -g

Name        : boot
Current     : no
Enabled     : no
Allowed     : root
Groups      : boot
Depends     : \
              └─None
Required by : \
              └─None
Contents    : \
              ├─boot@system:mount-run (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:system-hostname (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-tmp (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-proc (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:system-sysctl (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:udevd-log (pid=0, state=Enabled, type=classic, tree=boot)
              ├─boot@system:tty-earlier@tty12 (pid=229, state=Enabled, type=classic, tree=boot)
              ├─boot@system (pid=unitialized, state=Enabled, type=module, tree=boot)
              ├─boot@system:populate-run (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:populate-tmp (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-sys (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:populate-sys (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-dev (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-pts (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-shm (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:populate-dev (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-cgroups (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-branch (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:system-hwclock (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:modules-kernel (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:system-random (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:modules-system (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:udevd (pid=0, state=Enabled, type=classic, tree=boot)
              ├─boot@system:udevadm (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:system-fontnkey (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:system-fsck (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-fstab (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:system-branch (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-rw (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:local-authfiles (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:local-loop (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-netfs (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:local-sethostname (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:local-time (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:local-tmpfiles (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:local-dmesg (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:mount-swap (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:local-branch (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:runtime-branch (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:canopy (pid=unitialized, state=Enabled, type=oneshot, tree=boot)
              ├─boot@system:tty-rc@tty1 (pid=0, state=Enabled, type=classic, tree=boot)
              └─boot@system:tty-rc@tty2 (pid=0, state=Enabled, type=classic, tree=boot)

Name        : global
Current     : no
Enabled     : yes
Allowed     : root
Groups      : admin
Depends     : \
              └─None
Required by : \
              └─session (Enabled)
Contents    : \
              ├─openntpd-log (pid=277, state=Enabled, type=classic, tree=global)
              ├─connmand-log (pid=0, state=Disabled, type=classic, tree=global)
              ├─dbus-log (pid=282, state=Enabled, type=classic, tree=global)
              ├─wpa_supplicant-log (pid=0, state=Disabled, type=classic, tree=global)
              ├─crond-log (pid=279, state=Enabled, type=classic, tree=global)
              ├─bluetoothd-log (pid=283, state=Enabled, type=classic, tree=global)
              ├─networkmanager-log (pid=274, state=Enabled, type=classic, tree=global)
              ├─openntpd (pid=299, state=Enabled, type=classic, tree=global)
              ├─dbus (pid=297, state=Enabled, type=classic, tree=global)
              ├─connmand (pid=0, state=Disabled, type=classic, tree=global)
              ├─wpa_supplicant (pid=0, state=Disabled, type=classic, tree=global)
              ├─crond (pid=290, state=Enabled, type=classic, tree=global)
              ├─bluetoothd (pid=295, state=Enabled, type=classic, tree=global)
              └─networkmanager (pid=309, state=Enabled, type=classic, tree=global)

Name        : session
Current     : no
Enabled     : yes
Allowed     : root
Groups      : admin
Depends     : \
              └─global (Enabled)
Required by : \
              └─None
Contents    : \
              ├─boot-user@qwe:mount-run@qwe (pid=up, state=Enabled, type=oneshot, tree=session)
              ├─scandir@qwe (pid=up, state=Enabled, type=module, tree=session)
              ├─scandir@qwe:setenv@qwe (pid=up, state=Enabled, type=oneshot, tree=session)
              ├─scandir@qwe:svscan@qwe-log (pid=324, state=Enabled, type=classic, tree=session)
              ├─boot-user@qwe (pid=up, state=Enabled, type=module, tree=session)
              └─scandir@qwe:svscan@qwe (pid=353, state=Enabled, type=classic, tree=session)

$ 66 tree status -g

Name        : global
Current     : no
Enabled     : yes
Allowed     : qwe
Groups      : user
Depends     : \
              └─None
Required by : \
              └─None
Contents    : \
              ├─dbus@qwe-log (pid=0, state=Enabled, type=classic, tree=global)
              ├─obexd-log (pid=0, state=Enabled, type=classic, tree=global)
              ├─check_mail-log (pid=0, state=Enabled, type=classic, tree=global)
              ├─check_update-log (pid=0, state=Enabled, type=classic, tree=global)
              ├─xdg-user-dirs (pid=unitialized, state=Enabled, type=oneshot, tree=global)
              ├─dbus@qwe (pid=0, state=Enabled, type=classic, tree=global)
              ├─obexd (pid=0, state=Enabled, type=classic, tree=global)
              ├─check_mail (pid=0, state=Enabled, type=classic, tree=global)
              └─check_update (pid=0, state=Enabled, type=classic, tree=global)

#66 tree resolve boot

name        : boot
enabled     : 0
depends     : None
requiredby  : None
allow       : 0
groups      : boot
contents    : boot@system:mount-run boot@system:populate-run boot@system:system-hostname boot@system:mount-tmp boot@system:populate-tmp boot@system:mount-proc boot@system:mount-sys boot@system:populate-sys boot@system:mount-dev boot@system:mount-pts boot@system:mount-shm boot@system:populate-dev boot@system:mount-cgroups boot@system:mount-branch boot@system:system-hwclock boot@system:modules-kernel boot@system:system-random boot@system:modules-system boot@system:system-sysctl boot@system:udevd boot@system:udevadm boot@system:system-fontnkey boot@system:system-fsck boot@system:mount-fstab boot@system:system-branch boot@system:mount-rw boot@system:local-authfiles boot@system:local-loop boot@system:tty-earlier@tty12 boot@system:mount-netfs boot@system:local-sethostname boot@system:local-time boot@system:local-tmpfiles boot@system:local-dmesg boot@system:local-branch boot@system:runtime-branch boot@system:canopy boot@system:tty-rc@tty1 boot@system:tty-rc@tty2 boot@system:udevd-log boot@system boot@system:mount-swap
ndepends    : 0
nrequiredby : 0
nallow      : 1
ngroups     : 1
ncontents   : 42
rversion    : 0.8.2.2

This is /run/66/log/0/current file

2026-09-06 11:04:07.759420263  66-execute: info: Starting service: boot@system:tty-earlier@tty12
2026-09-06 11:04:07.762037870  [Start services of tree ...]
2026-09-06 11:04:07.789283365  start: info: Initialized successfully: openntpd
2026-09-06 11:04:07.789341745  start: info: Initialized successfully: openntpd-log
2026-09-06 11:04:07.789391829  start: info: Initialized successfully: crond
2026-09-06 11:04:07.789433922  start: info: Initialized successfully: crond-log
2026-09-06 11:04:07.789475760  start: info: Initialized successfully: dbus
2026-09-06 11:04:07.789516526  start: info: Initialized successfully: dbus-log
2026-09-06 11:04:07.789558257  start: info: Initialized successfully: bluetoothd
2026-09-06 11:04:07.789614119  start: info: Initialized successfully: bluetoothd-log
2026-09-06 11:04:07.789658233  start: info: Initialized successfully: networkmanager
2026-09-06 11:04:07.789699928  start: info: Initialized successfully: networkmanager-log
2026-09-06 11:04:07.802811851  66-execute: info: Starting service: dbus-log
2026-09-06 11:04:07.804918825  66-execute: info: Starting service: bluetoothd-log
2026-09-06 11:04:07.808018896  66-execute: info: Starting service: crond-log
2026-09-06 11:04:07.808034463  66-execute: info: Starting service: openntpd-log
2026-09-06 11:04:07.812022768  signal: info: Successfully started service: crond-log
2026-09-06 11:04:07.814230521  signal: info: Successfully started service: dbus-log
2026-09-06 11:04:07.816716987  66-execute: info: Starting service: networkmanager-log
2026-09-06 11:04:07.816776038  signal: info: Successfully started service: openntpd-log
2026-09-06 11:04:07.817697272  signal: info: Successfully started service: bluetoothd-log
2026-09-06 11:04:07.821465018  signal: info: Successfully started service: crond
2026-09-06 11:04:07.826026659  signal: info: Successfully started service: networkmanager-log
2026-09-06 11:04:07.830413235  signal: info: Successfully started service: bluetoothd
2026-09-06 11:04:07.834093118  signal: info: Successfully started service: openntpd
2026-09-06 11:04:07.878722737  signal: info: Successfully started service: dbus
2026-09-06 11:04:07.886609825  signal: info: Successfully started service: networkmanager
2026-09-06 11:04:07.887183145  tree: info: Successfully started tree: global
2026-09-06 11:04:07.919668673  start: info: Initialized successfully: boot-user@qwe
2026-09-06 11:04:07.919743190  start: info: Initialized successfully: scandir@qwe
2026-09-06 11:04:07.919820984  start: info: Initialized successfully: scandir@qwe:svscan@qwe-log
2026-09-06 11:04:07.919994789  start: info: Initialized successfully: scandir@qwe:svscan@qwe
2026-09-06 11:04:07.923088152  signal: warning: scandir@qwe:setenv@qwe already initialized -- ignore it
2026-09-06 11:04:07.923133320  signal: warning: scandir@qwe:svscan@qwe-log already initialized -- ignore it
2026-09-06 11:04:07.923159939  signal: warning: scandir@qwe:svscan@qwe already initialized -- ignore it
2026-09-06 11:04:07.933278699  66-execute: info: Starting service: scandir@qwe:svscan@qwe-log
2026-09-06 11:04:07.940021087  signal: info: Successfully started service: scandir@qwe:svscan@qwe-log
2026-09-06 11:04:08.006820149  signal: info: Successfully started service: scandir@qwe:setenv@qwe
2026-09-06 11:04:08.030274664  signal: info: Successfully started service: scandir@qwe:svscan@qwe
2026-09-06 11:04:08.031146923  signal: info: Successfully started service: scandir@qwe
2026-09-06 11:04:08.031422064  signal: warning: boot-user@qwe:mount-run@qwe already initialized -- ignore it
2026-09-06 11:04:08.052285974  signal: info: Successfully started service: boot-user@qwe:mount-run@qwe
2026-09-06 11:04:08.052426443  signal: info: Successfully started service: boot-user@qwe
2026-09-06 11:04:08.052947002  tree: info: Successfully started tree: session