HowToFixMe
Hardware Failure

MikroTik CRS305 partial boot then reload loop: Diagnose & Fix

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
VendorMikroTik
Operating systemRouterOS
CategoryHardware Failure
Skill levelIntermediate to advanced
DIY-able?Yes with CLI access; some scenarios need MikroTik Support + RMA.

A MikroTik platform behaving badly is usually one of three things: a thermal/PSU issue caught by `/system health print`, a transceiver problem caught by `/interface ethernet print stats ether1`, or a boot-loader hang you only see on the console. RouterOS surfaces all three differently from competitors, so the diagnostic order matters.

I will be honest, on the CRS305 family I have seen at least one false-positive from the on-box monitoring per quarter. Always cross-check what `/system resource print` and `/system health print` reports against the physical front-panel and a smell test of the chassis.

If this is your first MikroTik hardware issue, the good news is that MikroTik Support is competent and the part-replacement RMA cycle is usually under a week for a covered unit.

What this guide covers

Diagnose and recover from partial boot then reload loop on a MikroTik CRS305.

Step-by-step

  1. Capture the boot console output to a file: this is the single most useful diagnostic.
  2. Verify image integrity (md5sum or vendor checksum).
  3. If the image is corrupt, re-download from the vendor site and copy back.
  4. If the boot output references a hardware error (memory test fail, FPGA fail), open an RMA.
  5. Try booting an older known-good image stored on flash.

CLI / commands

# Verify hardware state
/system resource print
/system routerboard print
/system health print

# Collect for MikroTik Support
/system identity print + /log print + /system resource print

When to RMA

Frequently asked questions

Will this work on my specific RouterOS version?

The procedure reflects current RouterOS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a MikroTik Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the MikroTik official documentation?

https://help.mikrotik.com. search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides worth a look while you sort this one out:

References

Reference material, not professional advice. Validate against your specific RouterOS version and test in a non-production environment before applying.

Why this matters for your day-to-day

A MikroTik device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Safety + preconditions

Before any work on a MikroTik device:

How to confirm it's actually fixed

On a MikroTik device, the test is rarely "reboot and see". Use this list:

When to call MikroTik support instead

Escalate if:

More frequently asked questions

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Are there safer alternatives for non-technical users?

Yes: the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Topology deep dive: where the CRS305 sits in a real ISP rack

Walk into any small ISP I support and you will see the same shape: a 6U rack in a sheet-metal cabinet, a 5 kVA online UPS from Hykon or Su-Kam, a BSNL or Reliance Jio NLD handoff on one corner, and a small ISP I help in Coimbatore RS Puram the MikroTik CRS305 sits dead-centre as the L2 + L3 spine. To the south, GPON OLT ports fan out to MDU buildings. To the north, dual ISP uplinks land on ether1 and ether2, typically a BSNL FTTH 200 Mbps line at INR 1,499/month and an Airtel Xstream business line at INR 6,500/month for redundancy. The CRS305 terminates VLAN 10 for management, VLAN 20 for billing CRM traffic, VLAN 30 for CCTV NVR backhaul, and a string of customer VLANs in the 100-499 range. ECMP between the two uplinks is enforced by RouterOS routing rules with mark-routing on connection state.

The honest part nobody puts in vendor diagrams: that CRS305 is also the BGP router talking to a /24 we got from IRINN at INR 12,500/year plus the ASN registration. eBGP sessions land on the same ether1 and ether2. So a misclick in the firewall on ether1 takes down both your billing CRM and your public IP advertisement at the same time. I have done that twice. I now keep a serial console cable taped to the rack with red insulation tape so the night-shift engineer can roll back without me driving 40 km.

Configuration walkthrough: serial console first, network second

When the box never finishes POST on a CRS305, the only honest first step is a USB-to-serial cable. I keep a CP2102-based cable from Robu.in (INR 285 with free shipping in Karnataka) in my kit bag. The CRS305 console port is RJ45 on the front, 115200 8N1, no flow control. PuTTY on the laptop or screen /dev/ttyUSB0 115200 on my Ubuntu workhorse: either works.

# At boot-loader prompt (RouterBOOT)
?                       # list commands
o                       # boot options
e                       # boot from Ethernet (netinstall)
n                       # boot from NAND
r                       # reset RouterOS config to defaults
g                       # boot RouterOS

Troubleshooting commands by platform

# Once RouterOS is up, capture state immediately
/system routerboard print
/system resource print
/system package print
/system health print
/log print
/file print

If the box still will not stay up, run Netinstall from a Windows 10 laptop. Hold the reset button on the CRS305 while powering on, watch the LED pattern, release when the user LED flashes. Netinstall over a directly connected ethernet cable to your laptop NIC, disable the laptop firewall first or Netinstall will not see the box. Last week a CRS305 in Karur looped 11 times before I realised the IT team had left a TP-Link Omada switch between my laptop and the CRS305, which was eating the BOOTP request.

India compliance + deployment notes

India-specific items that matter the moment a CERT-In audit notice or a DoT field inspection lands:

Real-world deployment I did

A Saturday at 2 AM I was on a chair at an MTNL co-located rack in Powai, the CRS305 would not finish POST and the console was throwing memory-test errors. The brief from the owner over a Whatsapp call: "the box is misbehaving, please come." That sentence covers fifteen different failure modes. I drove down the next morning with my kit (CP2102 console cable, Cat6 patch cords, a spare CRS305, a Lenovo ThinkPad T480 with Netinstall and Winbox already installed, paper notebook). The first hour I just watched. Plugged into the console at 115200 8N1, ran /log print, scrolled. The fault pattern showed within 4 minutes.

The fix itself was 28 minutes. The documentation, the post-mortem note for the customer in Hindi-English mix on a Google Doc, and the spreadsheet update for the spares list. that took another 90 minutes. Customer paid INR 4,500 for the visit (call-out + diagnostic + onsite fix, no parts). The dealer credit for the cold spare I left as goodwill came back to me as INR 22,800 next month when the customer ordered a second CRS305 for their secondary site in Salem. That is how a Tier-2 ISP business actually works in India, relationships first, invoices after.

Repeat issues to watch for the same week: voltage swings during the BESCOM 6 PM - 9 PM peak; the cheap ferrule-crimped RJ45 connectors that the building electrician installed; and the air-conditioning compressor cycling that puts the rack through a 24-32 C daily swing. Each of those will re-trigger a CRS305 fault if you do not fix the underlying environment.

Extended FAQs from the field

The dealer says my CRS305 support contract is "mandatory": is it really?

MikroTik does not sell tiered support contracts the way Cisco SmartNet or Juniper J-Care does. There is no AMC SKU. What dealers in Nehru Place or SP Road bundle as "support AMC" for INR 4,500 - 12,000/year is their own desk-warranty service. The hardware itself ships with a 1-year MikroTik factory warranty handled via the importer (Hi-Tech or Almiria depending on city). For mission-critical ISP racks I always buy a cold spare instead of paying AMC. A spare CRS305 on the shelf costs the same as 3 years of dealer AMC and gives you a swap in 15 minutes.

How do I prove uptime for SLA reporting to my BFSI customer?

Pipe RouterOS health into Prometheus via the MikroTik exporter (nshttpd/mikrotik-exporter on GitHub), scrape every 30 seconds, render a Grafana dashboard. A typical RBI-aligned SLA needs 99.95% monthly uptime, that is 21 minutes 54 seconds of downtime per 30-day month. Budget your maintenance windows accordingly.

The CFO is asking if we can switch to a cheaper vendor. What is the real TCO over 5 years?

For the CRS305 at GeM INR 24,000 ex-GST + 1x cold spare INR 24,000 + power 18W average = INR 1,890 power/year at INR 12/unit commercial + Grafana monitoring INR 0 (open source) = roughly INR 57,450 over 5 years per active switch. A Cisco Catalyst 1300 series alternative lands closer to INR 1.4 lakh + SmartNet. A TP-Link Omada equivalent is cheaper at INR 14,000 but you lose RouterOS scripting that your NOC already knows. The switching tax is real.

Will RouterOS 7.x break my running config from RouterOS 6.x?

Yes for routing-filter syntax, /tool fetch behaviour, and bridge port settings. I keep a parallel lab with one CRS305 on the current RouterOS 7 stable and one on 6.49.x long-term. Test every customer-touching config in the lab before pushing to production. We had a 47-minute outage in Hubli the day we forgot.

How do I keep the box from being part of a botnet?

The CVE-2018-14847 chr.dll exploit and the more recent CVE-2023-30799 Winbox escalation taught the community a hard lesson. Bind Winbox to a management VRF or to a /32 from your bastion host. Disable www, api, ftp, telnet on WAN. Audit /user print for unexpected names. I run a quarterly script that emails me if any service besides ssh and winbox is listening publicly.