MiningOS Logo
Use MiningOS

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

SectionDescription
Monitoring & AlertsAlert visibility and metric tracking
Inventory ManagementFleet tracking best practices
Spare Parts & RepairsComponent and maintenance guidelines
Container OperationsCooling and deployment procedures
Pool ManagementMining pool configuration
Administrative TasksUser 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:

MetricLocationWarning SignsDocumentation
Miners OnlineHeader — Miners StatusSudden drop in green countExplorer
HashrateHeader — HashrateMiningOS/Pool discrepancyDashboard
EfficiencyHeader — EfficiencyRising W/TH/s valuesHeatmaps
PowerHeader — PowerUnexpected fluctuationsWidgets 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 ColorMeaningImmediate Action
GreenNormal operationNone required
OrangeMajor errorsInvestigate within 1 hour
RedOffline/SleepVerify intended state

For power mode capabilities by model, see Power Mode Support Table.

The W/TH/s metric displayed in the Header and Dashboard serves as an early warning system for:

TrendPossible CauseInvestigation
Gradually risingEquipment degradationCheck Heatmaps for thermal issues
Sudden spikeCooling failureCheck Container status
Seasonal variationAmbient temperatureReview 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 PatternIndicationAction
Large green segmentHealthy fleetContinue monitoring
Growing orange (Faulty)Repair backlogIncrease repair capacity
Large yellow (On Hold)Status uncertaintyAudit and update
Many Unknown locationsTracking breakdownPhysical audit

For status definitions, see Miners Inventory — Status Selector.

Balance Distribution

Use the Miner Distribution table to identify deployment bottlenecks:

ScenarioIndicationAction
High "Unknown" countsLocation tracking issuesPhysical inventory audit
Many in Workshop LabRepair capacity constraintsReview repair workflow
Low Available PositionsNear capacityPlan expansion
High Available PositionsUnderutilizationInvestigate 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:

  1. Filter for Unknown in Miners Inventory
  2. Review Movement History via Actions menu → Inventory Logs
  3. Check last known location in Historical Movements
  4. Physically locate the equipment
  5. Update location using inline dropdown
  6. 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.

ScenarioStatus to UseNotes
Part from scrapped miner, tested goodRecoveredReady for reuse
Part from scrapped miner, untestedOn HoldTest before deployment
Part from scrapped miner, failed testFaultyRepair or scrap
New part from manufacturerBrand NewDirect to deployment

For status definitions, see Spare Parts — Status Selector.

Use Bulk Import for Large Shipments

When receiving large component shipments:

  1. Download CSV template from Bulk Add Parts
  2. Populate with shipment data using consistent formatting
  3. Validate before import — check serial numbers and model codes
  4. Import via Bulk register button
  5. 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:

PatternIssueAction
Part shows "Not Assigned" but should be installedMissing repair recordReview Repair History
Part shows association but miner is scrappedStale associationUpdate via repair workflow
Multiple parts associated with same minerData errorInvestigate and correct

Document Repairs

Use the Comments feature to record:

InformationWhy Important
Symptoms observedPattern recognition for future issues
Diagnostic steps takenReduce duplicate effort
Parts replacedCost tracking and warranty claims
Technician notesKnowledge transfer
Firmware changesTroubleshooting reference

For repair workflow, see Repair History.


Container Operations

Verify Cooling Systems Before Mining

Always confirm cooling systems are operational before enabling miners:

Container TypeVerification StepsDocumentation
BitdeerCheck pump status, tank circulation, fan statusBitdeer — Home
Antspace HydroVerify return pressure > 0.05 MPa, check curvesAntspace — Home
Antspace ImmersionConfirm liquid temps in rangeAntspace — Settings

For container-specific alerts, see Alerts Manual — Visual Alerts by Container Type.

Monitor Temperature Heatmaps

Use the Heatmaps feature regularly to identify:

PatternPossible CauseAction
Localized red clusterCooling blockagePhysical inspection
Entire row redRack-level cooling issueCheck rack cooling systems
Single red unitIndividual miner faultInvestigate via Explorer
Gradient front-to-backNormal 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 MethodIncorrect MethodConsequence of Incorrect
MiningOS Pool ManagerVendor web interfaceWorker name mismatch
MiningOS Pool ManagerVendor CLI toolsAlerts triggered
MiningOS Pool ManagerDirect API callsTracking 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:

ConfigurationRiskRecommendation
Primary onlyHigh — single point of failureAdd at least 1 failover
Primary + 1 failoverMedium — limited redundancyAdd 2nd failover for critical operations
Primary + 2 failoversLow — full redundancyRecommended configuration

For endpoint configuration, see Pool Manager — Pool Endpoints.

Use Sleep Mode for Reconfiguration

When changing pool assignments, place miners in sleep mode first:

  1. Select miners in Pool Manager — Sites Overview
  2. Set to Sleep mode via Explorer
  3. Configure new pool via Setup Pools
  4. 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:

IndicatorMeaningAction
Green numberMiners connectedNormal operation
Red "0"No pool connectionsImmediate investigation
Discrepancy with MiningOS countPartial connectivityCheck Pool Manager Dashboard

For pool-related alerts, see Pool Manager — Alerts Integration.


Administrative Tasks

Follow Approval Workflows

Double-authorization actions require proper approval:

ActionAuthorization RequiredApprovers
Reboot MiningOSDoubleAdmin, Site Manager
Most device operationsSingleAny 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 TaskFrequencyDocumentation
Review active usersMonthlyUser Management
Verify role assignmentsQuarterlyRole Capabilities Matrix
Remove departed usersAs neededUser Management
Review action historyAfter incidentsRequests & Approvals

For role definitions, see Settings — User Roles.

Use Backend Operations Carefully

Backend Operations like firmware updates require careful planning:

StepActionDocumentation
1Test firmware on isolated deviceBackend — Firmware Updates
2Clear pending actionsHeader — Actions Chart
3Notify operatorsComments
4Schedule maintenance window
5Execute updateBackend Operations
6Verify operationDashboard

Never update S19XP firmware from Bitmain's public website. See Backend Operations — Firmware Updates for critical warnings.


Daily Operations Checklist

TimeTaskDocumentation
Start of shiftReview Dashboard for overnight issuesDashboard
Start of shiftCheck Alerts page for critical alertsAlerts Manual
HourlyScan Header metricsHeader
HourlyReview Widgets Page for container statusWidgets Page
DailyCheck Current Site OverviewCurrent Site Overview
WeeklyReview Miner DistributionMiner Distribution
WeeklyAudit Unknown locationsHistorical Movements
MonthlyReview user permissionsSettings

Operator Manual

Architecture & Installation

Contributor Guide

External Resources

On this page