You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Black screen during boot after read-only filesystem errors on elementary OS 8.1
Description
After updating elementary OS 8.1, my system began experiencing read-only filesystem errors and applications stopped launching.
Following a reboot, elementary OS no longer reaches the graphical login screen. Instead, a blinking underscore (_) appears briefly in the upper-left corner, approximately four times, followed by a completely black screen.
The issue persists across repeated boot attempts.
The system was previously working normally.
Steps to Reproduce / Sequence of Events
These are the steps that occurred on my system. I have not confirmed whether the issue can be reproduced on other installations.
Updated elementary OS 8.1.
Attempted to run Codex CLI using sudo codex.
Received the following error:
Read-only file system (os error 30)
Codex also failed to create its background daemon lock file under /root/.
Tried launching Codex normally and using codex --no-daemon. Errors continued.
Attempted to launch Slack, but the application would not open.
Rebooted the system.
During startup, a blinking underscore appeared in the upper-left corner approximately four times.
The display transitioned to a completely black screen and did not recover.
Pressed Ctrl + Alt + F3, but no terminal appeared.
Pressed Ctrl + Alt + Delete, which triggered another reboot. The same black-screen behavior occurred.
Expected Behavior
elementary OS should boot normally after an update, maintain normal filesystem read/write functionality, and display the graphical login screen.
Actual Behavior
System does not reach the graphical login screen.
A blinking cursor appears briefly before a permanent black screen.
Switching to a text console using Ctrl + Alt + F3 produces no visible result.
Ctrl + Alt + Delete triggers a reboot, but the issue persists.
Applications had stopped launching before the initial reboot.
System Information
Component | Details
-- | --
Operating System | elementary OS 8.1
Ubuntu Base | 24.04.5 LTS (reported)
Kernel | 7.0.0-43-generic (reported; needs verification)
Motherboard | Gigabyte
Storage | SanDisk SDSSDH3 1000G, 1 TB SATA SSD
Filesystem | ext4 with LVM
Boot Configuration | Not yet confirmed
Codex CLI is installed. I have not confirmed whether any custom kernel, graphics drivers, or bootloader modifications are present.
Troubleshooting Performed
1. BIOS and hardware detection
Gigabyte BIOS opens normally.
BIOS detects the SanDisk 1000G SSD.
The SSD is listed in the boot sequence.
2. Ubuntu Live USB
Successfully booted Ubuntu 24.04 from a USB drive using "Try Ubuntu."
The Live USB graphical environment works normally, and the original SSD is recognized.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Black screen during boot after read-only filesystem errors on elementary OS 8.1
Description
After updating elementary OS 8.1, my system began experiencing read-only filesystem errors and applications stopped launching.
Following a reboot, elementary OS no longer reaches the graphical login screen. Instead, a blinking underscore (
_) appears briefly in the upper-left corner, approximately four times, followed by a completely black screen.The issue persists across repeated boot attempts.
The system was previously working normally.
Steps to Reproduce / Sequence of Events
These are the steps that occurred on my system. I have not confirmed whether the issue can be reproduced on other installations.
Updated elementary OS 8.1.
Attempted to run Codex CLI using
sudo codex.Received the following error:
Codex also failed to create its background daemon lock file under
/root/.Tried launching Codex normally and using
codex --no-daemon. Errors continued.Attempted to launch Slack, but the application would not open.
Rebooted the system.
During startup, a blinking underscore appeared in the upper-left corner approximately four times.
The display transitioned to a completely black screen and did not recover.
Pressed
Ctrl + Alt + F3, but no terminal appeared.Pressed
Ctrl + Alt + Delete, which triggered another reboot. The same black-screen behavior occurred.Expected Behavior
elementary OS should boot normally after an update, maintain normal filesystem read/write functionality, and display the graphical login screen.
Actual Behavior
System does not reach the graphical login screen.
A blinking cursor appears briefly before a permanent black screen.
Switching to a text console using
Ctrl + Alt + F3produces no visible result.Ctrl + Alt + Deletetriggers a reboot, but the issue persists.Applications had stopped launching before the initial reboot.
System Information
Component | Details -- | -- Operating System | elementary OS 8.1 Ubuntu Base | 24.04.5 LTS (reported) Kernel | 7.0.0-43-generic (reported; needs verification) Motherboard | Gigabyte Storage | SanDisk SDSSDH3 1000G, 1 TB SATA SSD Filesystem | ext4 with LVM Boot Configuration | Not yet confirmedCodex CLI is installed. I have not confirmed whether any custom kernel, graphics drivers, or bootloader modifications are present.
Troubleshooting Performed
1. BIOS and hardware detection
Gigabyte BIOS opens normally.
BIOS detects the SanDisk 1000G SSD.
The SSD is listed in the boot sequence.
2. Ubuntu Live USB
Successfully booted Ubuntu 24.04 from a USB drive using "Try Ubuntu."
The Live USB graphical environment works normally, and the original SSD is recognized.
3. Disk partitions
Detected the following Linux partitions:
4. SSD SMART health
Using Ubuntu Disks:
Overall assessment: Disk is OK.
Reallocated sectors: 0.
Reported uncorrectable errors: 0.
Last recorded self-test: Completed successfully.
This does not conclusively rule out hardware or storage errors.
5. Filesystem accessibility
Successfully mounted the original elementary OS root filesystem read-only:
The filesystem was accessible, and existing user directories and files could be read.
6. Additional boot attempts
Repeated normal boot attempts produced the same blinking cursor followed by a black screen.
Current Status
The original elementary OS installation remains unbootable.
I have accessed and backed up selected personal files using an Ubuntu Live USB.
I have not reinstalled elementary OS, reinstalled GRUB, or performed filesystem repairs.
The cause remains undetermined. Possible areas to investigate include filesystem integrity, the kernel, graphics initialization, and the boot process.
Additional Diagnostic Information
I can provide:
SMART diagnostic results.
Kernel and systemd journal logs from the installed system, if accessible.
Additional hardware and firmware information.
Results of filesystem consistency checks.
Photos of the boot behavior.
Please let me know which additional logs or diagnostics would be most useful.
Thank you for your help investigating this issue.
All reactions