> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/amd/r8000-r7000/sbc-platform/bedrock-r8000-technical-documentation/software-bedrock-r8000/troubleshooting-bedrock-r8000-r7000.md).

# Troubleshooting - Bedrock R8000 | R7000

## Introduction

**Purpose of the Guide:** Help customers troubleshoot basic problems and save time troubleshooting by themselves.

**Scope of Troubleshooting:** problems booting, constantly rebooting devices etc…

## Pre-Troubleshooting Checklist

* Ensure that you have all necessary tools and information.
* Verify that the system is set up correctly.
* Make sure there is a backup of any important data.

## Common Issues and Solutions

### Constant reboots

**Symptoms:**

* Device is able to get to BIOS, but when the OS is about to boot, the device always reboots.

**Possible Causes:**

* Power supply is too weak and cannot supply the amperage needed for the Bedrock to boot.

**Steps to Resolve:**

* Change to a more powerful power supply, or use the power supply provided by SolidRun.

## Contact and Support

If any issues Persist you can always reach out to in our support channels.

**Support Channels:**

* [Support inquiry](https://www.solid-run.com/contact-us/#technical-support)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.solid-run.com/amd/r8000-r7000/sbc-platform/bedrock-r8000-technical-documentation/software-bedrock-r8000/troubleshooting-bedrock-r8000-r7000.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.