# After several times of reboots, Legato EthLink ECM not available **URL:** \ **Category:** Legato Application Framework\ **Created:** [January 10, 2020, 10:48am UTC](https://forum.legato.io/t/after-several-times-of-reboots-legato-ethlink-ecm-not-available/4943 "2020-01-10T10:48:40Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![lotam](https://avatars.discourse-cdn.com/v4/letter/l/958977/32.png) [@lotam](https://forum.legato.io/u/lotam)\ **Post date:** [January 10, 2020, 1:04pm UTC](https://forum.legato.io/t/after-several-times-of-reboots-legato-ethlink-ecm-not-available/4943/2 "2020-01-10T13:04:09Z")
Hi AE\_1, The behavior you observed could be related to the boot loop detection feature of Legato. You can find similar log: > [@Disable boot loop detection](https://forum.legato.io/t/disable-boot-loop-detection/3483/1): > > Hi, One of our demo units that uses the mangOH Red stopped working in the field. On inspecting the log, we found that the Legato framework didn’t start because of a ‘boot loop’. Jan 6 00:00:34 swi-mdm9x28 user.info Legato: INFO | \_UNKNOWN\_[644]/framework T=main | LE\_FILENAME GetStatus() 1034 | Status of system 'current' is 'good'. Jan 6 00:00:34 swi-mdm9x28 user.info Legato: INFO | \_UNKNOWN\_[644]/framework T=main | LE\_FILENAME FindNewestSystemIndex() 1287 | System 'current' is OK. Jan … It is designed feature to avoid continues unexceptional reset/crash, if you want to stop this feature, please remove the bootCount file during system init. > rm /legato/bootCount Or you should enhance your reboot mechanism, I understand you want to retry and recover from situation of no network connection… but if it is network/coverage issue it may fall into boot loop without help… Personally, I would prefer radio on/off or restart app instead of system reboot. Hope it helps. --- _[View the full topic](https://forum.legato.io/t/after-several-times-of-reboots-legato-ethlink-ecm-not-available/4943)._