Sounds like power control could be an issue.
During manufacturing test and in other CM5 automated provisioning systems the controller Pi always disconnects power to the target device before it is removed.
I noticed that you are using 'dd', it may be perferable to use rpi-imager cli because in addition to verifying the device it writes a zero MBR initially then only writes the MBR at the end.
This prevents the OS on the controller from seeing these new, incomplete block devices and attempting to mount them. This is slightly easier than tweaking the OS drive detection / auto-mount policy.
During manufacturing test and in other CM5 automated provisioning systems the controller Pi always disconnects power to the target device before it is removed.
I noticed that you are using 'dd', it may be perferable to use rpi-imager cli because in addition to verifying the device it writes a zero MBR initially then only writes the MBR at the end.
This prevents the OS on the controller from seeing these new, incomplete block devices and attempting to mount them. This is slightly easier than tweaking the OS drive detection / auto-mount policy.
Code:
sudo rpi-imager --cli ./2024-11-19-raspios-bookworm-armhf-lite.img.xz /dev/sda Statistics: Posted by timg236 — Thu Mar 06, 2025 9:42 am