> 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/000001273.md).
# How to Troubleshoot D:\ Drive Full on the NovaSeq 6000
**Background**
The D:\ partition "Performance Data" on the NovaSeq 6000 contains long term health and performance data that the system will share if connected to Illumina Proactive. The data is sometimes used for troubleshooting purposes by Illumina Support. When old runs are deleted in Process Management, it will also remove the oldest corresponding data from this partition. This normally keeps control of the volume of saved data on the D:\ partition. Under normal operations, the D:\ partition is not intended for user interaction and can be ignored.
**Note**: The D:\ partition does not contain or share any run data (eg, cbcl files)
However, some run types save more larger volumes of performance data and Illumina Field Service Engineer (FSE) troubleshooting may add to this volume. Infrequently, the D:\ partition may become critically full under normal use and can interfere with Universal Copy Service (UCS) operation, causing runs to crash or preventing new runs from starting.
If the D:\ partition is critically full, this can be verified in Windows **File Explorer** by **selecting** "My PC" and checking the D:\ volume bar. If critically full, this will turn from blue to red.
If the D:\ partition is showing as critically full, please contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for assistance in clearing the partition.
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1273), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001273%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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000001273.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.