I just did an upgrade ("pacman -Syy && pacman -Su && 66-update -d && 66-update"), and the system froze on reboot. It turned out that `/usr/lib/66/script/modules.sh` was no longer there, which was causing the boot tree to fail.

I copied the `modules.sh` (and also `tmpfiles.sh`, since that one was missing) from a boot image, and it now boots properly.

Two questions:
1) Did I do something wrong in the upgrade process that caused this?
2) Could those manually-copied files eventually cause problems, perhaps by being out of sync with the latest packages, etc?

Thanks
Killed me too. Stuck after system_fsk on mount_fstab: info: starts ...

but I had only done the pacman update so that might have been the issue. This time I did the full upgrade as root
pacman -Syy
pacman -Su
66-update -d
66-update

then checked the two scripts were in /usr/bin opentmpfiles and modules.

then I'm about to reboot again.
No. Stuck again. Clearly I don't know how to do a system update correctly. Can anyone point me at instructions?

I'm going to try to do:

https://web.obarun.org/index.php?id=116

hmmm. whats the new version of 66-info ... 66-intree maybe ?

Didn't manage to make it work so I'll delay my upgrade until I have time to work through the instructions on that page & anything that might enlighten me about what some of the phrases actually mean.
You don't need to use 66-update.
You just need to sync pacman and install the update, then you need to enable again the boot@ service with 
# 66-enable -t boot -F boot@ system
But apparently this simple instructions seems doesn't working for you.
So, first , you can see the log of the boot sequence at /run/66/log/0/current (please post it).
Your refer to a very old news page. This is absolutely out of date. At this period an important tool was renamed and separate in two different binaries : 66-intree, 66-inservice.
In your case the 
# 66-intree -zg
will give you some informations(please post the output of this command).
Before changes: 
Name         : base
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : no
Allowed      : john
Symlinks     : svc->source db->source
Contents     : /
               ├─(1168,Enabled,longrun) dbus-session@ john-log
               ├─(1172,Enabled,longrun) dbus-session@ john
               └─(up,Enabled,oneshot) xdg-user-dirs

Name         : root
Initialized  : no
Enabled      : yes
Starts after : base
Current      : no
Allowed      : john
Symlinks     : svc->source db->source
Contents     : /
               └─None

Name         : john
Initialized  : yes
Enabled      : yes
Starts after : base root
Current      : yes
Allowed      : john
Symlinks     : svc->source db->source
Contents     : /
               ├─(1202,Enabled,longrun) pipewire-pulse-log
               ├─(1203,Enabled,longrun) pipewire-log
               ├─(1208,Enabled,longrun) pipewire
               ├─(1204,Enabled,longrun) pipewire-media-session-log
               ├─(1216,Enabled,longrun) pipewire-media-session
               └─(1215,Enabled,longrun) pipewire-pulse
then sudo pacman -Syyu

then `66-enable -t boot -F boot@ system`

And that worked perfectly. Thanks again. Where should I have looked for that simple final instruction?
Thanks Galeano,

10 years+ debian & debian derivative user coming to arch commands and the first init where I've had to make changes after upgrades. It keeps it interesting and I'm having to build a faq of my own for the simple tasks that I might not repeat again for 6-12 months.

Yes. My network setup is static so networking services are unneeded and I've just pruned root so I'm back to base and john. sudo 66-intree reveals boot, root and boot-user.

Powered by Obarun