Closed vaminakov closed 4 years ago
can you use systemd-nspawn
instead of chroot
:
https://github.com/random-archer/mkinitcpio-systemd-tool/wiki/System-Recovery
I also hit this problem when using arch-chroot
but systemd-nspawn
works fine. The problem is that systemctl cat $unit
now exits with code 0 if in a chroot, so the fallback code here is never executed.
@lachesis Eric:
please confirm this is in fact is the case (i.e. not due to your local misconfig):
The problem is that systemctl cat $unit now exits with code 0 if in a chroot
and what systemctl --version
says?
please confirm if v33 resolves this https://github.com/random-archer/mkinitcpio-systemd-tool/releases/tag/v33 https://www.archlinux.org/packages/community/any/mkinitcpio-systemd-tool/
assume resolved
Confirmed resolved on my system with v35 at least.
I rebuilt the initramfs after using arch-chroot /mnt
to chroot instead of using systemd-nspawn
as recommended, yet the system booted this time. Here's confirmation that systemctl cat
no longer returns a sane error code in this case.
[root@archiso /]# systemctl cat initrd-shell.service
Running in chroot, ignoring request: cat
[root@archiso /]# echo $?
0
Using systemd 245.
@lachesis Eric: thank you.
Hello! Sorry for awaiting. I'm confirm that too.
@vvl-rulez Vladislav: thank you
Hello!
When I build mkinitcpio-systemd-tool from real root:
mkinitcpio -Pvvv
:When I try to build it from chroot (arch-chroot), log have only:
I have that problem on all machines, clear install too. In what way I should look?