BADMD-APP error for v3 probe #25855
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
n Mon 2023-11-20 13:03:51-0800 Hans wrote:
I'm trying to resurrect a v3 probe that had a status of "Bad Firmware". I did the usual: [...] Is there anything that I can do to resurrect this probe? I'm not afraid to TFTP...
Hi Hans, Check out this thread from earlier this year on this exact topic: https://www.ripe.net/ripe/mail/archives/ripe-atlas/2023-August/005535.html Regards, Robert -- USC Information Sciences Institute <http://www.isi.edu/> Networking and Cybersecurity Division
On 20 Nov 2023, at 14:54, Robert Story wrote:
On Mon 2023-11-20 13:03:51-0800 Hans wrote:
I'm trying to resurrect a v3 probe that had a status of "Bad Firmware". I did the usual: [...] Is there anything that I can do to resurrect this probe? I'm not afraid to TFTP...
Hi Hans,
Check out this thread from earlier this year on this exact topic:
https://www.ripe.net/ripe/mail/archives/ripe-atlas/2023-August/005535.html
Regards, Robert
Thanks Robert. I spent quite a bit of time reading the mailing list archives before posting, but hadn't read that entire thread. I tried two different "silly" formats for the USB drive: - APFS - dd if=/dev/zero of=/dev/sdX ... (this took quite some time and definitely qualifies as unrecognizable) Neither option worked, and I'm getting the exact same BADMD-APP BADMD-KERNEL errors in the SOS log. Hans
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
Hi Michel, Thanks for looking at the logfiles. Do you mind if I update the ripe-atlas mailing list thread sharing your findings? Please don't send a replacement probe. I have plenty. :) Randy provided me with a replacement probe to install and it's now online (#25898). Shall I mark #25855 as a "write off"? warm regards, Hans On 22 Nov 2023, at 4:56, Michel Stam wrote:
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
Randy provided me with a replacement probe to install and it's now online (#25898).
so now we need to learn how to retire and replace randy
Hi Hans, Not a problem at all, please do update the list. Although I sent a similar response there IIRC. The probe is in a continuous upgrade loop. It downloads kernel, downloads application, tries an upgrade, fails, reboots, tries again. Since the USB flash has been replaced 3 times and the kernel is also reported “bad” I can only conclude that the internal flash is then flawed. I’ve had several returned probes with that issue too. Please mark the 25855 as a write off yes :) thank you Hans! Cheers, Michel
On 22 Nov 2023, at 19:22, Hans Kuhn <hans@flyingpoodle.com> wrote:
Hi Michel,
Thanks for looking at the logfiles. Do you mind if I update the ripe-atlas mailing list thread sharing your findings?
Please don't send a replacement probe. I have plenty. :)
Randy provided me with a replacement probe to install and it's now online (#25898).
Shall I mark #25855 as a "write off"?
warm regards, Hans
On 22 Nov 2023, at 4:56, Michel Stam wrote:
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
participants (4)
-
Hans Kuhn -
Michel Stam -
Randy Bush -
Robert Story