> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-nand-issue.md). # NAND issue Diagnose Controller 6000 NAND storage failures and identify the required recovery action. > ⚠️ **Affects controllers manufactured 2011 to 2015 only.** The fix only needs to be applied **once** to each affected controller. Resolved in firmware **v7.30 and above**. ## Background Between 2011 and 2015 the Gallagher repairs department were seeing a significant number of instances where Controller 6000s were coming back for repairs. The cause turned out to be that the **NAND flash RAM** on the 6000 was being addressed incorrectly due to a **manufacturing change by the supplier of the NAND chip**. ## Fix In **v7.30** a new firmware was released to fix these issues during a firmware update. This is reflected in the release note of v7.30 (and later versions of Command Centre). Other firmware versions with the fix for older versions of Command Centre were also released: | Firmware version | For Command Centre version | | ---------------- | -------------------------- | | `vGR6.01.92` | 6.01-era systems | | `vGR7.10.401` | 7.10-era systems | | `vGR7.20.685` | 7.20-era systems | These are available from the Gallagher File Transfer Site, in the **Controller Software > 6000NANDFix** folder. If a system is 7.05 or earlier, download `vGR6.01.92` from the Gallagher File Transfer Site, add it to the Device Software as a 6000 firmware, then downgrade the controller to the older firmware, wait for the firmware to do its work (approximately 9.5 minutes), and when it is online again, upgrade to the original firmware. *** ## Which controllers are affected | Range type | Affected range | Affected MAC range | | ------------- | ---------------------------- | ------------------------ | | Serial number | `1120xxxxxx` to `1508xxxxxx` | `00:B2:6D` to `01:38:AC` | ## How to check if the fix has been applied Run the **FT Support Tool** on a server to list controllers and show the WinCE version. If the **WinCE build version (Software Type 1)** is **`v2.00/b22` or higher**, the fix has been applied. Example FT Support Tool output: | Device | Software Type | Assigned Version | Installed Version | ItemType | Description | | --------------- | ------------- | ---------------- | ----------------- | ----------------- | --------------------------- | | Controller 6000 | 0 | vGR6.02b33 | v6.02//b33 | Controller Grover | Controller Software Version | | Controller 6000 | **1** | | **v1.00//b85** | Controller Grover | **WinCE build, check this** | | Controller 6000 | 2 | | v1.01//b6016 | Controller Grover | Bootloader Version | | Controller 6000 | 3 | | v1.02//b0 | Controller Grover | Plugin Version | | Controller 6000 | 4 | | v1.00//b25 | Controller Grover | | (In this example, Software Type 1 is `v1.00//b85`, which needs upgrading to `v2.00/b22+`.) *** ## Risks of not doing the upgrade > ⚠️ **The issue is not detectable before the problem occurs.** A controller that has been running for years could have the problem, but the controller only has a chance of failing when it restarts. If you decide not to do the upgrade, you run a real risk that every time the controller 6000 restarts, it could **render the controller unusable**. The **DIP Switch 8 procedure will not fix this**. Applying the fix will resolve this issue, but the controller patch is applied during the power up cycle. **If the controller experiences the NAND issue during this initial restart, the controller will be unusable on restart.** When doing the upgrade, have spare controllers on hand in case some fail during the patch. *** 🔗 **Related** * [DIP Switch 8 Recovery](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-dip-switch-8-recovery.md). Note that DIP Switch 8 does not fix the NAND issue. * [I2C Bus Not Responding](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-i2c-bus-not-responding.md). Another hardware fault to check before upgrading. * [Upgrading, Downgrading, Defaulting and Compatibility](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-upgrading-downgrading-defaulting-compatibility.md). Pre-upgrade checks. --- # 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-nand-issue.md?ask=&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.