Hi Hans, I just looked at the logfiles. What I’ve seen with the probe is that it is continuously trying to download the firmware for the unit itself (the kernel), then the firmware for the usb stick (the application). Since this process does not yield a working situation, I am afraid that the internal flash is dead. Any unit I have seen this on so far would remain in this deadlock forever. Trying to resurrect this probe by opening it up may be an option but would wipe any of its state, including the keys necessary to communicate with the Atlas backend. That is not gonna yield the correct result I’m afraid. What I will do is send you instructions to apply for a new probe. I’ll notify the relevant people and you’ll get a replacement v5 shipped to you. Will that help? Regards, Michel
On 20 Nov 2023, at 22:03, Hans Kuhn <hans@flyingpoodle.com> wrote:
Hi,
I'm trying to resurrect a v3 probe that had a status of "Bad Firmware". I did the usual:
Unplug the probe from its power source Remove the USB stick from the probe Plug in the probe WITHOUT the USB stick Wait for ten minutes Insert the USB stick
I've tried 3 different 8G USB drives and they all give the same result, which is the BADMD-APP-5080 and BADMD-KERNEL-1110 error in the SOS log.
Is there anything that I can do to resurrect this probe? I'm not afraid to TFTP...
Thanks!
Hans
-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas