Reading a Boot-Cycle Log After a Power Event
A walkthrough of timestamp fields in our CSV exports — what each column means when the grid flickers and you need evidence fast.
After a brief grid dip or storm-related outage, hosting staff often restart rows manually. Our boot-cycle CSV exports give a chronological record independent of pool dashboards.
Column overview
timestamp — Local Korea Standard Time at log write.
event_type — cold_start, warm_restart, power_dip, or hash_stable.
seconds_to_hash — Elapsed time from power-on until sustained hash at or above rated floor (0.05 TH/s minimum for assessed units).
intake_c — Intake air temperature at event time.
hash_th_s — Observed hash rate in TH/s at stabilisation.
notes — Technician observation: fan error code, extra cycle required, aborted start.
Interpreting clusters
Single failed cold start during a week may be inconclusive. Three failures under similar intake temperatures suggest a pattern. Compare event_type rows after outages — if only cold_start fails but warm_restart succeeds, focus on startup draw and capacitor health.
Using logs with suppliers
Export snippets with serial numbers attach cleanly to RMA correspondence. We provide the raw CSV alongside the PDF summary so you control which timestamps are shared.
When to request a new run
If your PDU schedule or ventilation changed since the last assessment, older logs may not predict current boot behaviour. A 24-hour diagnostic updates the record without a full 72-hour commitment.
Need help interpreting an existing log? Email info@service-ashfield.click with the assessment reference from your report cover page.