Skip to content

Commit 71cab23

Browse files
committed
Added guide to recover Arch Linux from black screen boot without live USB
1 parent cf2af19 commit 71cab23

File tree

1 file changed

+61
-0
lines changed

1 file changed

+61
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
cover:
3+
image: /images/grub_shell.jpg
4+
alt: Recovering Arch Linux from a Black Screen Boot Without a Live USB
5+
relative: false
6+
title: 'Recovering Arch Linux from a Black Screen Boot Without a Live USB'
7+
author: 'iniridwanul'
8+
date: 2025-05-08T15:18:02+06:00
9+
tags:
10+
- Black Screen
11+
- GRUB
12+
- Shell
13+
- TTY
14+
- Kernel
15+
- Arch Linux
16+
draft: false
17+
categories:
18+
- Linux
19+
---
20+
21+
When using Arch Linux, sometimes the system may break in such a way that it boots into a black screen and doesn't even allow TTY (terminal) access using typical key combinations like `Ctrl + Alt + F2`. This can be a frustrating situation especially if you don't have a bootable USB to access a live environment for troubleshooting.
22+
23+
Fortunately, there is a way to recover from this kind of issue using the GRUB bootloader. This article will walk you through how to bypass the graphical boot and access a working terminal by modifying boot parameters directly in GRUB.
24+
25+
## Symptoms
26+
System powers on, but instead of reaching the login screen, it displays a black screen that blinks or remains completely unresponsive.
27+
- You are unable to access TTY by pressing Ctrl + Alt + F2, F3, etc.
28+
- No bootable USB or live environment is available for rescue.
29+
30+
## Cause
31+
This usually happens due to:
32+
- Misconfiguration in the display manager (like GDM, LightDM, etc.)
33+
- Broken graphical drivers (e.g., after a package update)
34+
- Corrupted graphical target
35+
36+
When the system attempts to boot into the graphical target (graphical UI) and fails, it doesn't automatically fall back to a safe mode or CLI interface.
37+
38+
## Boot into Multi-User Target from GRUB
39+
Instead of booting into the graphical interface, you can instruct your system to boot directly into the multi-user target, which gives you terminal (TTY) access.
40+
41+
- Reboot your system and enter the BIOS/UEFI boot menu (usually by pressing F12, ESC, or DEL, depending on your system).
42+
- Select the disk where your Arch Linux system is installed.
43+
- When the GRUB menu appears, highlight the default boot option (don’t press Enter yet).
44+
- Press `e` to edit the selected boot entry.
45+
- You will see a number of lines. Look for the line that starts with linux. It will look something like:
46+
`linux /boot/vmlinuz-linux root=UUID=xxxxxx rw loglevel=3 quiet`
47+
- At the end of that line, add the following:
48+
`systemd.unit=multi-user.target`
49+
The full line might look like:
50+
`linux /boot/vmlinuz-linux root=UUID=xxxxxx rw loglevel=3 quiet systemd.unit=multi-user.target`
51+
- Press `Ctrl + X` to boot with the modified settings.
52+
53+
## What Happens Next
54+
Your system will boot into TTY mode (non-graphical terminal).
55+
56+
You will see a login prompt. Use your username and password to log in.
57+
58+
From here, you can troubleshoot the graphical environment or any other system issue.
59+
60+
## Conclusion
61+
Even without a live USB, it's possible to recover a non-booting Arch Linux system stuck at a black screen. Using GRUB to boot into multi-user.target provides a safe and accessible environment for recovery. This technique is invaluable for system administrators and users who frequently work with minimal or broken systems.

0 commit comments

Comments
 (0)