Opengear OM22xx - Recovering a Console Server from a Boot Loop
An Opengear OM2200 console server was stuck in a boot loop and could no longer be reached, neither via the web interface nor via SSH. Opengear support provided a recovery image which is booted from a USB drive and restores the device to factory defaults. This post summarizes the procedure. Requirements A USB flash drive with at least 2 GB. It will be erased completely. A computer that can run balenaEtcher The OM2200 recovery image from Opengear Create the Recovery USB Drive Extract the downloaded ZIP file. It contains two files; the smaller .bmap file can be ignored, as balenaEtcher doesn’t need it. Open balenaEtcher and select Flash from file. Select core-image-recovery-ogpuma-1.0.0-production-signed.wic. Select the USB drive as target and double-check that it is the correct one. Click Flash! and wait until flashing and validation have finished. Depending on the PC and the drive, this takes a few minutes. Safely remove the USB drive. Recover the OM2200 Remove power from the OM2200. Insert the recovery USB drive into one of the USB ports below the RJ45 console ports on the front of the device. Locate the ERASE button on the front. Reapply power and immediately press and hold the ERASE button with a paperclip or similar. Keep holding it for about 20 seconds. The power LED comes on after roughly 8 seconds and goes out around the 20-second mark. Release the button when it goes out. The recovery now starts automatically. The LEDs may blink and cycle several times, which is expected. Don’t interrupt the power and don’t remove the USB drive. The device should be back at factory defaults about 4 minutes and 20 seconds after releasing the ERASE button. Remove the USB drive once the recovery has finished. After the Recovery On the local console port a login prompt appears eventually. Without a console connection, the device is reachable on its default NET1 address: ...