[SOLVED] Arch not booting

LeonN · 2023-01-09 20:54:31

Hello, after I turning my laptop on, it turned out Arch is stuck in a screen saying

Starting systemd-udevd version 252.4-2-arch
/dev/nvme0n1p3: clean, 184745/1966080 files, 3126442/7864320 blocks

At the begginig, I thought it was a problem with the NVMe where my root partition is, but after checking the output of smartctl -a /dev/nvme0n1, I noticed there was no warnings or errors with the NVMe. I have no clue about how to solve it.

Last edited by LeonN (2023-01-10 05:27:52)

jasonwryan · 2023-01-09 21:03:59

Arch is booting, but your graphical environment is not starting. From a chroot, read the journal for a failed start, or change the current target: https://wiki.archlinux.org/title/System … ent_target

LeonN · 2023-01-10 04:23:08

I mounted the root partition and chrooted in it, I ran systemctl get-default and the output is graphical.

When I try to run systemctl list-units --type=target, the only output I get is "Running in chroot, ignoring command 'list-units'.

jasonwryan · 2023-01-10 04:33:00

Just change the kernel line when you boot and read the journal from the TTY.

LeonN · 2023-01-10 04:44:42

Sorry to keep bothering, but I'm still new at this and I partially get what you mean. If you could add a link or be more clear, I'd be great. I'm not used to the abbreviations and names of some things I encounter.

jasonwryan · 2023-01-10 04:48:55

I've already added the link, in post #2. It says,

wiki wrote:

Alternatively, append one of the following kernel parameters to your bootloader:
systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3),

If you need to work out how to do that, "kernel parameters" is also a link you can follow with details on proceeding.

LeonN · 2023-01-10 05:27:34

Thanks for clearing things out. Well, I did what you told me and I got into a cli version of Arch, with no graphical interface, since I changed the parameters. After doing that, I wasn't sure if I was supposed to reboot the system and then got inti the graphical target normally, but as infered it might be a problem with Xorg, I remembered I added a file into /etc/X11/xorg.conf.d/ which I thought it was meaningless (it was a file that was supposed to allow me to switch between languages) so I ended up deleting that file and rebooting the system. After that I was able to get into the graphical interface. Thanks for your help.

jasonwryan · 2023-01-10 05:41:54

No problem. It's a good idea to be comfortable working from the TTY. If you had read the journal, it would likely have pointed at the graphical failure, and you could have then looked at why X wasn't starting.

LeonN · 2023-01-10 05:45:02

Actually, I did read it, it's just that I could barely compregend much of the terminology and it was quite hard to get it. Anyway, it was helpful enough to figure out what the problem was.

Arch Linux

#1 2023-01-09 20:54:31

[SOLVED] Arch not booting

#2 2023-01-09 21:03:59

Re: [SOLVED] Arch not booting

#3 2023-01-10 04:23:08

Re: [SOLVED] Arch not booting

#4 2023-01-10 04:33:00

Re: [SOLVED] Arch not booting

#5 2023-01-10 04:44:42

Re: [SOLVED] Arch not booting

#6 2023-01-10 04:48:55

Re: [SOLVED] Arch not booting

#7 2023-01-10 05:27:34

Re: [SOLVED] Arch not booting

#8 2023-01-10 05:41:54

Re: [SOLVED] Arch not booting

#9 2023-01-10 05:45:02

Re: [SOLVED] Arch not booting

Board footer