> 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/iseq-100/instrumentation-iseq-100-reference_material-list/000006672.md).

# How to clear hard drive space on the iSeq 100

A sequencing run on the iSeq 100 requires about 2.5 GB of local hard drive space. If space is low, a warning notification will be generated. Follow the below steps to delete completed runs and clear space:

**Note:** Only delete runs using the iSeq 100 Control Software rather than manually through the operating system or File Explorer. Deleting runs manually can negatively impact the Control Software.Deleting runs via the Process Management workflow below will only remove them from the instrument's temporary folder (`D:\Illumina\iSeq Runs\[RunFolder]`)

1. From the Control Software menu, select Process Management.
   1. The **Process Management** screen appears with a list of runs saved to the local hard drive.
2. For the run to delete, select **Delete Run**.
   1. Deleting a run deletes the local run folder. The output folder, which is a copy of the run folder, is retained. If the output folder is designated as also being on the D:\ drive, it will have to be manually curated via the Windows File Explorer. This will not negatively impact the control software like it would for manual curation of the temporary folder.
3. In the dialog box, select **Yes, Delete Run** to confirm deleting the run.
4. Repeat steps 2 and 3 to delete runs as needed.
5. When finished, close Process Management to return to the **Home** screen.

**Note:** Deleted files/folders cannot be recovered.

\
\
\ <br>

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