This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] BADMD-APP error for v3 probe #25855
- Previous message (by thread): [atlas] BADMD-APP error for v3 probe #25855
- Next message (by thread): [atlas] BADMD-APP error for v3 probe #25855
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hans Kuhn
hans at flyingpoodle.com
Tue Nov 21 02:16:33 CET 2023
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
- Previous message (by thread): [atlas] BADMD-APP error for v3 probe #25855
- Next message (by thread): [atlas] BADMD-APP error for v3 probe #25855
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]