We’ve been looking at the logs and it doesn’t seem to be standard behavior, which might indicate some HW failure. For that reason we’d like to get our hands on your device and run more intensive tests. Would you be able to send an email to store@balena.io with a link to this thread so we can get you a replacement?
@crbn60 do you have physical access to the device or would you require to do the backup remotely?
If you do have access to it, we can ship the replacement device before retrieving the problematic one. That way you could use etcher’s clone function to clone them.
This is assuming you want the data and keys from that device copied to the replacement. Let me know if that isn’t the case.
Sorry, you’re right and thanks for adding this.
What happens (as far as I understand, but I am not an expert on this ) - etcher is bootstrapping a variant of rpi-boot ( GitHub - raspberrypi/usbboot: Raspberry Pi USB booting code, moved from tools repository ) into the CM3 module - the CM3 is basically booting the code provided by etcher from your computers USB - which is a mini program only having one purpose: Mounting the eMMC memory as a flash drive to your computer and making it accessible. The eMMC is hardwired via the SODIMM slot to the CM3 and is not available via USB or other means, so the CM3 is just providing it to your PC as an emulated harddrive. Without the CM3 as the “converter bridge” inbetween USB and eMMC, this is not possible .