Operational Best Practices
Recommended practices for maximizing uptime, simplifying troubleshooting, and maintaining accurate records.
This guide consolidates recommended practices for operating Bitcoin mining infrastructure with MiningOS. Following these guidelines helps maximize uptime, simplify troubleshooting, and maintain accurate inventory records.
For system architecture and design principles, see Architecture. For initial setup, see Installation Guide.
Quick Navigation
| Section | Description |
|---|---|
| Monitoring & Alerts | Alert visibility and metric tracking |
| Inventory Management | Fleet tracking best practices |
| Spare Parts & Repairs | Component and maintenance guidelines |
| Container Operations | Cooling and deployment procedures |
| Pool Management | Mining pool configuration |
| Administrative Tasks | User and system management |
Monitoring & Alerts
Maintain Alert Visibility
Keep a dedicated browser tab open on the Alerts page to receive audio notifications for critical events. Sound notifications only trigger when this page is active.
Critical alerts require immediate attention. Configure your workstation to keep the Alerts tab visible or use a dedicated monitoring display.
For alert severity definitions, see Alerts Manual — Severity Levels.
Monitor Header Metrics
Regularly scan the header bar for anomalies:
| Metric | Location | Warning Signs | Documentation |
|---|---|---|---|
| Miners Online | Header — Miners Status | Sudden drop in green count | Explorer |
| Hashrate | Header — Hashrate | MiningOS/Pool discrepancy | Dashboard |
| Efficiency | Header — Efficiency | Rising W/TH/s values | Heatmaps |
| Power | Header — Power | Unexpected fluctuations | Widgets Page |
Investigate Status Colors
When miners appear in orange (major errors) or red (offline) categories, use the Explorer to diagnose and address issues promptly.
| Status Color | Meaning | Immediate Action |
|---|---|---|
| Green | Normal operation | None required |
| Orange | Major errors | Investigate within 1 hour |
| Red | Offline/Sleep | Verify intended state |
For power mode capabilities by model, see Power Mode Support Table.
Track Efficiency Trends
The W/TH/s metric displayed in the Header and Dashboard serves as an early warning system for:
| Trend | Possible Cause | Investigation |
|---|---|---|
| Gradually rising | Equipment degradation | Check Heatmaps for thermal issues |
| Sudden spike | Cooling failure | Check Container status |
| Seasonal variation | Ambient temperature | Review weather data |
For temperature visualization, see Heatmaps.
Inventory Management
Review Current Site Daily
The donut chart panels in Current Site Overview provide rapid visual assessment of inventory health.
| Chart Pattern | Indication | Action |
|---|---|---|
| Large green segment | Healthy fleet | Continue monitoring |
| Growing orange (Faulty) | Repair backlog | Increase repair capacity |
| Large yellow (On Hold) | Status uncertainty | Audit and update |
| Many Unknown locations | Tracking breakdown | Physical audit |
For status definitions, see Miners Inventory — Status Selector.
Balance Distribution
Use the Miner Distribution table to identify deployment bottlenecks:
| Scenario | Indication | Action |
|---|---|---|
| High "Unknown" counts | Location tracking issues | Physical inventory audit |
| Many in Workshop Lab | Repair capacity constraints | Review repair workflow |
| Low Available Positions | Near capacity | Plan expansion |
| High Available Positions | Underutilization | Investigate deployment bottlenecks |
For capacity planning, see Miner Distribution — Capacity Planning.
Leverage Inline Editing
The Miners Inventory table supports direct Location and Status updates without navigating to detail views. This enables efficient bulk management during:
- Receiving new equipment
- Physical inventory audits
- Status reconciliation exercises
- Location updates after moves
For location definitions, see Miners Inventory — Location Selector.
Audit Unknown Locations
Miners showing "Unknown" location require physical verification:
- Filter for Unknown in Miners Inventory
- Review Movement History via Actions menu → Inventory Logs
- Check last known location in Historical Movements
- Physically locate the equipment
- Update location using inline dropdown
- Document findings via Comments
For movement tracking, see Historical Device Movements.
Spare Parts & Repairs
Track Recovered Parts
The "Recovered" status unique to Spare Parts Inventory enables accurate cost accounting for salvaged components.
| Scenario | Status to Use | Notes |
|---|---|---|
| Part from scrapped miner, tested good | Recovered | Ready for reuse |
| Part from scrapped miner, untested | On Hold | Test before deployment |
| Part from scrapped miner, failed test | Faulty | Repair or scrap |
| New part from manufacturer | Brand New | Direct to deployment |
For status definitions, see Spare Parts — Status Selector.
Use Bulk Import for Large Shipments
When receiving large component shipments:
- Download CSV template from Bulk Add Parts
- Populate with shipment data using consistent formatting
- Validate before import — check serial numbers and model codes
- Import via Bulk register button
- Verify import by filtering for newly added parts
For CSV template format, see Spare Parts — CSV Template.
Monitor Part Associations
Regularly review the Miner Code column in Spare Parts Inventory to identify:
| Pattern | Issue | Action |
|---|---|---|
| Part shows "Not Assigned" but should be installed | Missing repair record | Review Repair History |
| Part shows association but miner is scrapped | Stale association | Update via repair workflow |
| Multiple parts associated with same miner | Data error | Investigate and correct |
Document Repairs
Use the Comments feature to record:
| Information | Why Important |
|---|---|
| Symptoms observed | Pattern recognition for future issues |
| Diagnostic steps taken | Reduce duplicate effort |
| Parts replaced | Cost tracking and warranty claims |
| Technician notes | Knowledge transfer |
| Firmware changes | Troubleshooting reference |
For repair workflow, see Repair History.
Container Operations
Verify Cooling Systems Before Mining
Always confirm cooling systems are operational before enabling miners:
| Container Type | Verification Steps | Documentation |
|---|---|---|
| Bitdeer | Check pump status, tank circulation, fan status | Bitdeer — Home |
| Antspace Hydro | Verify return pressure > 0.05 MPa, check curves | Antspace — Home |
| Antspace Immersion | Confirm liquid temps in range | Antspace — Settings |
For container-specific alerts, see Alerts Manual — Visual Alerts by Container Type.
Monitor Temperature Heatmaps
Use the Heatmaps feature regularly to identify:
| Pattern | Possible Cause | Action |
|---|---|---|
| Localized red cluster | Cooling blockage | Physical inspection |
| Entire row red | Rack-level cooling issue | Check rack cooling systems |
| Single red unit | Individual miner fault | Investigate via Explorer |
| Gradient front-to-back | Normal airflow (air-cooled) | Expected behavior |
For temperature metrics, see Heatmaps — Temperature Metrics.
Configure Pools Correctly
Always configure mining pools through MiningOS using the Pool Manager, not vendor tools:
| Correct Method | Incorrect Method | Consequence of Incorrect |
|---|---|---|
| MiningOS Pool Manager | Vendor web interface | Worker name mismatch |
| MiningOS Pool Manager | Vendor CLI tools | Alerts triggered |
| MiningOS Pool Manager | Direct API calls | Tracking breaks |
For pool configuration warnings, see Bitdeer Container — Pool Configuration.
Pool Management
Configure Failover Pools
Always set up at least one failover endpoint for each pool:
| Configuration | Risk | Recommendation |
|---|---|---|
| Primary only | High — single point of failure | Add at least 1 failover |
| Primary + 1 failover | Medium — limited redundancy | Add 2nd failover for critical operations |
| Primary + 2 failovers | Low — full redundancy | Recommended configuration |
For endpoint configuration, see Pool Manager — Pool Endpoints.
Use Sleep Mode for Reconfiguration
When changing pool assignments, place miners in sleep mode first:
- Select miners in Pool Manager — Sites Overview
- Set to Sleep mode via Explorer
- Configure new pool via Setup Pools
- Return to Normal mode after configuration
For model-specific sleep mode availability, see Power Mode Support Table.
Monitor Pool Connectivity
Check the header bar's Pool indicator regularly:
| Indicator | Meaning | Action |
|---|---|---|
| Green number | Miners connected | Normal operation |
| Red "0" | No pool connections | Immediate investigation |
| Discrepancy with MiningOS count | Partial connectivity | Check Pool Manager Dashboard |
For pool-related alerts, see Pool Manager — Alerts Integration.
Administrative Tasks
Follow Approval Workflows
Double-authorization actions require proper approval:
| Action | Authorization Required | Approvers |
|---|---|---|
| Reboot MiningOS | Double | Admin, Site Manager |
| Most device operations | Single | Any Action user |
Review the Requests & Approvals workflow before submitting critical operations.
Clear all pending actions before submitting a Reboot MiningOS request. See Settings — Reboot MiningOS.
Manage User Permissions
Regularly audit user roles in Settings:
| Audit Task | Frequency | Documentation |
|---|---|---|
| Review active users | Monthly | User Management |
| Verify role assignments | Quarterly | Role Capabilities Matrix |
| Remove departed users | As needed | User Management |
| Review action history | After incidents | Requests & Approvals |
For role definitions, see Settings — User Roles.
Use Backend Operations Carefully
Backend Operations like firmware updates require careful planning:
| Step | Action | Documentation |
|---|---|---|
| 1 | Test firmware on isolated device | Backend — Firmware Updates |
| 2 | Clear pending actions | Header — Actions Chart |
| 3 | Notify operators | Comments |
| 4 | Schedule maintenance window | — |
| 5 | Execute update | Backend Operations |
| 6 | Verify operation | Dashboard |
Never update S19XP firmware from Bitmain's public website. See Backend Operations — Firmware Updates for critical warnings.
Daily Operations Checklist
| Time | Task | Documentation |
|---|---|---|
| Start of shift | Review Dashboard for overnight issues | Dashboard |
| Start of shift | Check Alerts page for critical alerts | Alerts Manual |
| Hourly | Scan Header metrics | Header |
| Hourly | Review Widgets Page for container status | Widgets Page |
| Daily | Check Current Site Overview | Current Site Overview |
| Weekly | Review Miner Distribution | Miner Distribution |
| Weekly | Audit Unknown locations | Historical Movements |
| Monthly | Review user permissions | Settings |
Related Documentation
Operator Manual
- Introduction — MiningOS overview and supported hardware
- Dashboard — Main monitoring dashboard
- Explorer — Device search and management
- Alerts Manual — Complete alert reference
- Pool Manager — Mining pool configuration
- Inventory Module — Fleet management capabilities
- Settings — User and system configuration
Architecture & Installation
- Architecture — System design and component relationships
- Installation Guide — Setup and configuration
- Supported Devices — Hardware compatibility
Contributor Guide
- Repository Structure — Codebase organization
- Testing & Linting — Quality assurance
- Code Documentation — Documentation standards
External Resources
- Bitmain Support — Antminer documentation and firmware
- MicroBT Official — Whatsminer support resources
- Canaan Shop — Avalon product information
- Ocean Pool — Ocean mining pool dashboard
- F2Pool — F2Pool mining statistics