> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000005295.md).

# Troubleshooting Fatal error, exiting application. Unable to find a device on the NovaSeq 6000

The following error can appear at install while booting the NovaSeq Control Software (NVCS) and NovaSeq Service Software (NVSS):

ERR: "Fatal error, exiting the application. Unable to find a device. Hostname:novaseq\_chm BoardID:CHM"

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-1c86a15ec53560e329fd6aead0cb5187d3e52a88%2Fimage1.png?alt=media\&token=94d1b5e6-21d7-416f-8681-b574f57eee2a)

**Potential Causes**

1. Two instances of the control software/service software are open.
2. The system was power cycled too quickly.
3. Network configuration issue.

**Troubleshooting steps:**

1. Close all instances of NovaSeq Control Software (NVCS) and NovaSeq Service Software (NVSS), then relaunch the desired software.
2. If the error appears again, perform a power cycle on the system and allow **2-5 minutes** between toggling the power switch at the back to ON position and the power button on the side to ON position.
   * For more information on power cycling, please review the Knowledge Base article [How to Power Cycle the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002470.md)
3. If the issue persists after power cycling, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for the next steps.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5295), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005295%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000005295.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.
