Arch Linux

mibadt

Member

Registered: 2009-09-25

Posts: 396

Post new install: stuck boot/systemctl ignored in chrooted environment

Hi,
I did a fresh installation of the latest Arch (2013, 32b) on a netbook and installed GRUB2, along with Network Manager, xorg XFCE4 and SLIM DM (which I chose to automatically start using systemctl).
When I boot the new system, the system get's stuck immediately after stating that /dev/sda2 (holding my /mnt) is clean.
I suspect that that problem is related to known incompatibility of SLIM with XFCE  due to the following.
GRUB2 enables me to boot into an existing Windows (sda1).

When I boot from the installation media, mount my /mnt (sda2) and /mnt/home (sda3) partitions and chroot afterwards (arch-chroot /mnt) I can, as a regular user, start XFCE4.
Yet, when I try (as chrooted root) to run  'systemctl disable slim.service' I get a message that it's ignored as I'm in a chroot. The same happens with other systemctl commands as well.

Please advise:
1. How to analyse why my system won't complete boot (to a terminal at least)?
2. How to reconfigure my system as required.

Thanks

---

Best regards,
Michael Badt

henk

Member

From: Weert, Netherlands

Registered: 2013-01-01

Posts: 334

Re: Post new install: stuck boot/systemctl ignored in chrooted environment

Try adding 'single' as a boot parameter to your Grub-line. This will in most cases get you to your tty1-login

As to your installation, are you sure you have everything installed and configured as needed?