I'm currently trying to use 'Minitool Partimage Image' on Windows 10 - this works with all standard hard drive duplication. After a lot of testing of various size microSD cards, why when you perform a sector by sector copy of a know working and fully configured RPi4 microSD card (holds standard 2 partitions of FAT32 and Ext4) in windows does the microSD card fail to boot?
If the new 'backup' microSD card is placed in the RPi4 and turned on, classic repeating 4x green LED flashes are observed i.e. can't find a valid 'start.elf' file?
The only thing I've read somewhere was about filesystem guids as apposed to labels being used and that's something to do with why the duplicates don't boot?
I'm trying to understand why standard partition imaging and copying tools appear to fail with RPi4 microSD cards?
For reference: -
- The 'working' microSD card is a standard created with 'Raspbian Buster Lite' (2019-09-26 version 4.19)
- RPi4 booted and configured asdesired Now trying to create a physical 'backup' microSD card using a windows 10 PC Both cards are the same type/size (Transcend 8GB microSD card)
- If the 'backup' microSD card is created from scratch using 'Ethcer' and the original downloaded image - it boots 1st time without issues - try duplicating it again - still fails?
- Both original and 'backup' microSD cards seem to be identical i.e. 2x partitions (FAT32 and Ext4)
- RPi4 is a headless / keyboard less system with access when running via SSH to commandline only - gui desktop not installed so 'SD card copier' can't be used.
- Standard windows SD card copier programs referenced on various forums appear to fail when writing back a backup image that they take i.e. 2nd partition appears to not be copied back?