Bug after upgrade SO to 43500 version release

Feedback
1

After upgrade previous version to 43500 my laptop doesn’t initialize with this error:

systemd[1]: Failed to open executor binary '/usr/lib/systemd/systemd-executor': No such file or directory
systemd[1]: Failed to allocate manager object: No such file or directory
systemd[1]: Freezing execution.
2

Looks like an initrd update went bad in this release. We’re working on a fix, but meanwhile, we’ve locked updates to the prior version, and if you already have 43500 or later, avoid rebooting until we publish a fixed release.

3

If you’ve already rebooted in 43500 and are now stuck with the error about /usr/lib/systemd/systemd-executor, here are instructions to get un-stuck:

  • Boot from a flash drive (see Install Clear Linux* OS from the live server — Documentation for Clear Linux* project)
  • Mount the root partition (hint: use blkid to identify the partitions)
    • mount <root_device> /mnt
  • Mount the boot (EFI) partition underneath that
    • mount <boot_device> /mnt/boot
  • Use swupd to recover the previous initrd version from release 43490
    • Use nmtui if necessary to bring up a network connection manually
    • swupd swupd repair --bundles=bootloader-extras --force --version=43490 --path=/mnt
  • Copy the initrd to the EFI partition to replace the faulty initrd
    • cp -p /mnt/usr/lib/initrd.d/clr-init.cpio.gz /mnt/boot/EFI/org.clearlinux/freestanding-clr-init.cpio.gz
    • The md5sum of the old, working initrd in both of those locations should now be c229aa2b9ae701ca8662ce1a1042ffbb.
  • Reboot

We will publish a new release shortly that fixes the problem.

1 Like
4

This approach could not be tested.
The last live so version 43520 simply don’t initialize.
I tried other approaches like to make a downgrade, and tried other kernels.
The downgrade with 42070 version, with 6.6 kernel, it worked,but if the swupd make a update the problems returns.
I also tried to make personalized installation a slightly larger partition boot with 500MB, but the clr-installer ignores it.
My laptop is an intel i7 with video card, but I also don’t know if it’s related with the problem. And the main partition was encrypted.

5

Using LUKS? There must be something else missing in our initrd. Can you try to get any logging info from that, by editing (e) the boot command from the menu, removing “quiet” and adding “debug”?

Meanwhile, I’ll roll back to the older initrd that was working before so our next release after 43520 will revert to it properly. You’ll need to follow the recovery instructions above again.

6

43540 is now available and contains the older initrd that was working prior to 43500.

1 Like
7

if using LUKS, you need to unlock the drive first

sudo -s /*enter root*/
cryptsetup luksOpen /dev/sdb1 home /*home is a placeholder, pick you like*/
mount /dev/mapper/home /mnt
mount /dev/sdb2 /mnt/boot /*assumes /dev/sdb2 is your EFI partition*/

once you finish running btwarden commands above for repairing

umount /mnt/boot
umount /mnt
cryptsetup close home
reboot
1 Like