Entering safe mode because firmware exited too many times in a row. Reverting to Tinker

I found an a issue. I tried to flash via webIDE but it told me Request timed out and I got following error in particle-agent logs:

pi@raspberrypi:~ $ particle-agent logs
0000000003 system: INFO: Device 7ab783469c733c63505f927f started
0000000004 hal: INFO: Virtual WLAN init
0000000004 system: INFO: ready():false,connecting():false,listening():false
0000000004 hal: INFO: Virtual WLAN on
0000000004 hal: INFO: Virtual WLAN connecting
0000000004 hal: INFO: Virtual WLAN connected
0000000004 hal: INFO: device key: 3082025D02010002818100C5A66D5084F7C8CFA662499BC94CA30EB690AE9DDF4EBCE4B22236856AD5A93985641A32E4267C238C98424751C9D73B66083FDED79C336E55887DDFB0C6~
0000000004 hal: INFO: server key: 30820122300D06092A864886F70D01010105000382010F003082010A0282010100BECCBE43DB8EEA1527A6BB526DE1512BA0ABCCA1647748AD7C66FC807FF699A525F2F2DAE043CF3A~
0000000004 system: INFO: Cloud: connecting
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  resolve: Host not found (non-authoritative), try again later
Firmware exited with status pid 620 SIGABRT (signal 6)
Quitting firmware gracefully
0000000003 system: INFO: Device 7ab783469c733c63505f927f started
0000000003 hal: INFO: Virtual WLAN init
0000000003 system: INFO: ready():false,connecting():false,listening():false
0000000003 hal: INFO: Virtual WLAN on
0000000003 hal: INFO: Virtual WLAN connecting
0000000003 hal: INFO: Virtual WLAN connected
0000000003 hal: INFO: device key: 3082025D02010002818100C5A66D5084F7C8CFA662499BC94CA30EB690AE9DDF4EBCE4B22236856AD5A93985641A32E4267C238C98424751C9D73B66083FDED79C336E55887DDFB0C6~
0000000003 hal: INFO: server key: 30820122300D06092A864886F70D01010105000382010F003082010A0282010100BECCBE43DB8EEA1527A6BB526DE1512BA0ABCCA1647748AD7C66FC807FF699A525F2F2DAE043CF3A~
0000000004 system: INFO: Cloud: connecting
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  resolve: Host not found (non-authoritative), try again later
Firmware exited with status pid 621 SIGABRT (signal 6)
Quitting firmware gracefully
0000000003 system: INFO: Device 7ab783469c733c63505f927f started
0000000003 hal: INFO: Virtual WLAN init
0000000003 system: INFO: ready():false,connecting():false,listening():false
0000000003 hal: INFO: Virtual WLAN on
0000000003 hal: INFO: Virtual WLAN connecting
0000000003 hal: INFO: Virtual WLAN connected
0000000003 hal: INFO: device key: 3082025D02010002818100C5A66D5084F7C8CFA662499BC94CA30EB690AE9DDF4EBCE4B22236856AD5A93985641A32E4267C238C98424751C9D73B66083FDED79C336E55887DDFB0C6~
0000000003 hal: INFO: server key: 30820122300D06092A864886F70D01010105000382010F003082010A0282010100BECCBE43DB8EEA1527A6BB526DE1512BA0ABCCA1647748AD7C66FC807FF699A525F2F2DAE043CF3A~
0000000003 system: INFO: Cloud: connecting
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  resolve: Host not found (non-authoritative), try again later
Firmware exited with status pid 622 SIGABRT (signal 6)
Quitting firmware gracefully
Entering safe mode because firmware exited too many times in a row. Reverting to Tinker
/usr/lib/ruby/2.1.0/fileutils.rb:525:in `rename': No such file or directory @ sys_fail2 - (/usr/share/particle/binaries/tinker, /var/lib/particle/devices/7ab783469c733c63505f927f/firmware.bin) (Errno::ENOENT)
    from /usr/lib/ruby/2.1.0/fileutils.rb:525:in `block in mv'
    from /usr/lib/ruby/2.1.0/fileutils.rb:1579:in `block in fu_each_src_dest'
    from /usr/lib/ruby/2.1.0/fileutils.rb:1595:in `fu_each_src_dest0'
    from /usr/lib/ruby/2.1.0/fileutils.rb:1577:in `fu_each_src_dest'
    from /usr/lib/ruby/2.1.0/fileutils.rb:514:in `mv'
    from /usr/lib/ruby/vendor_ruby/particle_agent/firmware_runner.rb:118:in `apply_safe_mode'
    from /usr/lib/ruby/vendor_ruby/particle_agent/firmware_runner.rb:112:in `check_safe_mode'
    from /usr/lib/ruby/vendor_ruby/particle_agent/firmware_runner.rb:28:in `run!'
    from /usr/lib/ruby/vendor_ruby/particle_agent/agent.rb:37:in `block (2 levels) in start_firmware_runners'

Any ideas?

Can you flash an empty firmware over to the rapsberry pi and see what happens?

Ah, there’s a bug in the safe mode handler that moves Tinker on top of a bad firmware file instead of copying it. I’ll release a new Particle Agent today to fix this issue.

In the mean time, please reinstall the agent using
bash <( curl -sL https://particle.io/install-pi )

1 Like