> 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/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000005674.md).

# Setting external hard drives as the default output folder on NextSeq 1000/2000

The NextSeq 1000/2000 system can output data directly to an external hard drive. As Instrument Orchestrator and Universal Copy Service run as `ilmnuser`, the workflows for setting an external hard drive as the default output folder will differ between the `ilmnuser` and `ilmnadmin` accounts.

**Instructions for ilmnuser Account**

1. Plug in an external portable drive using the 3.0 USB port on the side or back of the instrument.
2. Create a new folder on the external portable drive. This folder will become the default output folder location on the external hard drive.
3. From the Control Software dropdown menu in the top left corner, select **Settings**.
4. Under Instrument Customization, select **Default Output Folder**, select the existing folder path, and navigate to the new folder on the external portable drive.
   * The external will typically mount to `/run/media/ilmnuser/[HDD name]`
5. \[Optional] If **Online Run Setup** is selected, select a **Hosting Location** from the drop-down menu.
6. Select **Save**.

Reference: Sequencing systems guide can be found in [English](https://support-docs.illumina.com/IN/NextSeq10002000/Content/IN/FrontPages/NextSeq10002000.htm) and [other languages](https://support.illumina.com/sequencing/sequencing_instruments/nextseq-1000-2000/documentation.html).

Per the [NextSeq 1000/2000 Sequencing System Guide](https://support-docs.illumina.com/IN/NextSeq10002000/Content/IN/FrontPages/NextSeq10002000.htm), the `ilmnadmin` account is intended for applying system updates or for use by IT staff to mount a persistent network drive. All other actions, including sequencing, must be performed from `ilmnuser.` It is **STRONGLY** encouraged to switch to `ilmnuser` for sequencing.

If workflow mandates sequencing from `ilmnadmin` account and outputting to an external hard drive, [contact Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further assistance.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5674), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005674%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/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000005674.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.
