A date range is not enough evidence
Check stock firmware compatibility before VNISH
Stock firmware restrictions and supported install paths change over time. Use the full build, miner model and control board together before selecting any recovery or update method.
Pre-flight record
| Input | Record | Why it matters |
|---|
| Exact model | Full chassis model and revision | Similar product names can require different files |
| Control board | XIL, AML, CV, BB or exact part number | Board images and recovery methods are not interchangeable |
| Current build | Full version and date string | Some builds restrict direct installation |
| Cooling | Air, hydro or immersion | Control and safety behaviour differs |
| Target method | Update, NAND, SD recovery or vendor tool | Update and recovery packages serve different purposes |
When direct update may be inappropriate
- The current interface rejects third-party packages.
- The package target does not exactly match the board.
- The miner is unstable or loses power/network.
- You do not have a tested recovery path.
- The current vendor instructions contradict an older date rule.
Safe next step
- Keep the current configuration and original image.
- Use the model guide as a starting point.
- Verify current primary documentation.
- Prepare the correct recovery media.
- Test one miner during a maintenance window.
Why this page avoids universal date rules: a remembered month range can become outdated and may not cover every board or regional build. The full build identifier and current model-specific instructions are safer evidence.
VNISH Guides