[Solved] - Metal 2SHPn not booting

RouterOS Wireless Networking
1

I’ve got Mikrotik Metal 2SHPn. After it have been working outdoor few years I unexpectedly found that the device is not replying for pings. When I troubleshooted I found the following:

  1. PoE port on the downlink router is active, TX is slowly growing, RX is zero.
  2. If I unplug and plug the cable into the Metal, it beeps, then LED is green for few seconds and after few seconds LED switchs off.
  3. If I unplug the cable, press the reset button and plug the cable back - after few seconds LED begin to blink green. Then I release the reset button, but after few seconds LED is switch off and nothing happens, device is not discovered by winbox or netinstall.
  4. Device is not discovered via Winbox (even 0.0.0.0), does not reply to default IP 192.168.88.1 etc. Also it is not reachable via netinstall with direct attach to laptop LAN with PoE injector.
  5. If I leave the device for 10-20 minutes it becomes warm, so at least something is alive inside :slight_smile:

Tried to google but found nothing. Please advice. Thnx.

2

I found out that the reason was a boot loop after upgrade to 6.42.6.
Firmware 6.42.6 sends to the boot loop at least Metal 2Shpn and Groove 52Hpacn.

Solution:

  1. Download 6.40.8 firmware for MIPSBE platform and netinstall for 6.40.8.
  2. Download old winbox version (i’ve used 2.2.18).
  3. Disable all wifi and virtual and other interfaces on the PC/laptop except single LAN. Disable windows firewall.
  4. Connect device direclty to the LAN with POE adapter or via single switch with POE port if you dont have poe injector.
  5. Push RESET button and plug the cable. Important - you should hold RESET button even after LED starts blinking. It is not like recover manuals says. Users on other forums suggest to try to push reset button 5, 10, 20 seconds. In my case it was 20 seconds - after LED end blinking and few seconds after that starts to light permanently - only after that I’ve released RESET button. If I release the RESET button before it then I’ve got the error “recvfrom failed 10054”.
  6. Upload firmware via netinstall according to recover manuals. If nothing happens when you push install button in netinstall, i.e. progress bar not rising, that you should close netinstall but don’t disconnect device and right after thatn open netinstall again.
  7. If IP adress not assigned after recovery or default config not applied then use winbox to connect to the device via MAC address. In my case only old version of winbox worked.