Intermittent Boot Failure on Steam Deck LCD After SteamOS Updates / Reimage with Third-Party NVMe SSD

Open
#2,547 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet

Research direction

Start by reproducing the cold-boot and resume failures with the TEAMGROUP MP44S after a SteamOS re-image, then compare the SteamOS bootloader, BIOS F7A0133, Recovery Environment, and kernel logs. Done means a reproducible failure with fresh kernel, SMART, and Btrfs diagnostics that narrows the possible interaction between SteamOS, firmware, and NVMe initialization.

Written by the indexing model from the issue text.

Description

Summary

I would like to report an intermittent boot issue that has persisted across multiple SteamOS installations.

The problem began sometime after replacing the factory SSD with a TEAMGROUP MP44S 2230 1TB NVMe SSD. The SSD initially worked perfectly and SteamOS operated normally for an extended period.

Over time, after one or more SteamOS updates, intermittent boot failures started occurring. These failures gradually became more frequent.

I have performed multiple troubleshooting steps, including a complete SteamOS Re-image, filesystem integrity checks, SMART diagnostics, and hardware inspection.

Although the SteamOS Re-image significantly improved stability, the issue has not been completely eliminated.

I am not reporting this as proof of a SteamOS bug or a defective SSD. I simply hope the information below may help investigate whether there is a compatibility or initialization issue involving SteamOS, firmware, or certain NVMe SSDs.


Device Information

Device

  • Steam Deck LCD

SteamOS Version

  • SteamOS 3.8.11 Stable

BIOS Version

  • F7A0133

Internal SSD

  • TEAMGROUP MP44S 2230 NVMe SSD

Capacity

  • 1 TB

SSD Firmware

  • 1.F.L.38

The SSD is the only hardware modification made to the device.


Timeline

Initial SSD Upgrade

I replaced the factory SSD with a TEAMGROUP MP44S 2230 1TB NVMe SSD.

SteamOS was installed successfully.

The system operated normally for quite some time.

At this point I did not observe any boot instability.


After SteamOS Updates

After the system had received one or more SteamOS updates, intermittent boot failures began appearing.

Initially they were rare.

Over time they became more frequent.

The failures were difficult to reproduce consistently.


Typical Boot Behaviour

Most failures occur during cold boots.

Typical sequence:

  • Press power button.
  • Steam logo appears.
  • Boot process stops indefinitely.
  • Sometimes the system automatically reboots.
  • Sometimes SteamOS enters the A/B boot recovery mechanism.
  • Occasionally the boot menu reports multiple failed boot attempts.

Several times I simply waited without pressing any buttons.

Unexpectedly, after several minutes, the boot process continued by itself and SteamOS loaded successfully.

This behavior has occurred multiple times.


Boot Errors Observed

Across different failed boot attempts I have observed various bootloader-related messages, including:

  • inode not found
  • extent not found
  • couldn't find chunk descriptor
  • zstd-related errors
  • terminal "gfxterm" isn't found
  • alloc magic is broken at
  • unaligned pointer at

The exact messages vary between boot attempts.

Sometimes only one message appears.

Other times several messages appear before the device eventually boots successfully.


Sleep / Resume

The primary issue occurs during cold boot.

However, I have also experienced occasional freezes after resuming the device from sleep.

These resume issues are less frequent than the boot failures but may indicate the same underlying initialization problem.


SSD Detection Incident

At one point the SSD was suddenly no longer detected.

This happened not only during normal boot but also inside the official SteamOS Recovery Environment.

The recovery installer reported that no NVMe device could be found.

After physically reseating the SSD, the drive immediately became detectable again.

SteamOS Recovery successfully detected the drive and completed a full reinstallation.


SteamOS Re-image

I performed a complete SteamOS Re-image using the official Steam Recovery Image.

The installation completed successfully.

During the first setup process, after connecting to Wi-Fi, SteamOS automatically downloaded updates before reaching the desktop.

The final installed version became SteamOS 3.8.11 Stable.

No additional software or system modifications were made after installation.


Long-Term Observation

I have noticed a recurring pattern over the course of multiple SteamOS installations.

Earlier Installation

During a previous SteamOS installation (using an older BIOS and SteamOS version), I performed a complete SteamOS Re-image.

Following the reimage, the Steam Deck booted normally for approximately one to two weeks.

During that period I did not encounter the intermittent boot failures.

After the system later received one or more SteamOS updates, the boot failures gradually returned.

Current Installation

More recently, after updating to BIOS F7A0133, I again performed a complete SteamOS Re-image.

Immediately after the reimage the system behaved normally.

However, unlike the previous installation, the intermittent boot failures returned much sooner, approximately one to two days after the reimage.

I cannot determine whether this timing is coincidental or related to software or firmware updates.

I only wish to report the recurring pattern that I have personally observed.


Diagnostics Performed

SMART

SMART Overall Health:
PASSED

Media and Data Integrity Errors:
0

Percentage Used:
0%

No media errors were reported.


Btrfs Scrub

Completed successfully.

No errors found.


Btrfs Check

Completed successfully.

No filesystem errors found.


Kernel Investigation

During successful boots I inspected kernel logs.

I did not observe:

  • NVMe controller resets
  • NVMe timeout errors
  • PCIe AER errors
  • Btrfs corruption

The filesystem mounted normally during successful boots.


Additional Observations

Several observations make me question whether this is ordinary filesystem corruption.

  • SMART consistently reports the SSD as healthy.
  • Filesystem integrity checks consistently pass.
  • SteamOS functions normally once it successfully boots.
  • The failures appear to occur very early during the boot process.
  • Some failed boots recover automatically after several minutes without any user interaction.
  • A complete SteamOS Re-image significantly improves stability but does not completely eliminate the issue.
  • The SSD was once temporarily undetected by both SteamOS and the Recovery Environment but became fully functional again after reseating.

Why I Am Reporting This

I understand that replacing the factory SSD with a third-party NVMe drive is a user modification.

However, SSD replacement is also a common upgrade performed by many Steam Deck owners.

Because the SSD appears healthy and all filesystem integrity checks pass, I would like to report the possibility that there may be an interaction involving:

  • SteamOS bootloader
  • Steam Deck BIOS / firmware
  • NVMe initialization timing
  • A/B boot mechanism
  • Compatibility with certain third-party NVMe firmware

I am not claiming that SteamOS is defective.

I am not claiming that the SSD is defective.

I simply hope these observations may help identify whether there is an unexpected compatibility issue during the early boot process.


Additional Notes

Unfortunately, I no longer have the original journal logs from the earlier installation because I had to perform a complete SteamOS Re-image to make the device usable again.

Those logs were lost during the reinstall.

If this issue occurs again, I would be happy to collect and provide fresh diagnostic logs, kernel logs, SMART information, and any additional data requested by the development team.

Thank you very much for your time and for investigating this report.

Dominant language
No language data
Stars
2.6k
Forks
83
Avg merge
4m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ValveSoftware/SteamOS

All issues in ValveSoftware/SteamOS

Similar issues

More Operating Systems issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.