Arch Linux

LuizF

Member

Registered: 2020-12-27

Posts: 30

[SOLVED] Arch stuck on boot

Hello, I didn't update my arch for 3 months, since i wasn't using my laptop.

When i turned it on and updated via pacman, it started to get stuck in the boot screen, printing:

"Starting version 250.5-1 arch
/dev/nvme0n1p8 clean, xxx/xxxx files, xxx/xxxx blocks"

It stays like this forever, although I have acess to TTY2, and everything is normal.

My laptop doesn't have a graphic card and I use BSPWM, what could I do to solve this?

Last edited by LuizF (2022-05-11 22:04:16)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [SOLVED] Arch stuck on boot

what could I do to solve this?

Read your xorg.log and your journal.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

LuizF

Member

Registered: 2020-12-27

Posts: 30

Re: [SOLVED] Arch stuck on boot

what could I do to solve this?

Read your xorg.log and your journal.

Solved, thank you very much.

I wrote a wrong command in the xorg file, I was trying to change the touchpad configuration.

I didn't know this could happen, thanks!

Nate_KS

Member

Registered: 2011-01-04

Posts: 5

Re: [SOLVED] Arch stuck on boot

I had a very similar symptom on an installation that resides on a USB SSD for use with a laptop with Win 10 as its primary OS.  It would come up like the OP's and I could switch to any virtual console, tty2-tty6 but I could not log in, neither as root or my normal user.  Mounting the disk on another system I was able to read the journal file and found the following two lines:

May 15 06:36:06 archsdr systemd[211]: Failed to execute /usr/lib/systemd/system-environment-generators/10-arch: No such file or directory
May 15 06:36:06 archsdr systemd[210]: /usr/lib/systemd/system-environment-generators/10-arch failed with exit status 1.

I verified the 10-arch file was actually there and looking at its contents it is a shell script that begins with '#!/bin/sh' which is quite normal.  Looking for a bit I found the /bin symlink was not there!  Creating a new symlink to usr/bin restored the system to normal operation.

I don't know when or how or by what means that symlink was deleted.  This happened back in March and just this past week got around to seriously troubleshooting this issue.  I had done fsck and badblocks tests on the drive and nothing was found to be a problem.  It's a mystery to me.