- Initial start to create the first image: download Raspbian Lite and use Win32DiskImager to create the image on a 64GB SD card (Transcend Premium 400x 64GB Class 10 micro SD XC1)
- Among other things, expanded the filesystem through raspi-config
- Once all the stuff I needed was on the SD card, I halted the RPi
I removed the SD card from the RPi and used Win32DiskImager to read the card (that is, copy the whole content to an img on my PC; takes a long time for a 64GB card)
- I took the other, identical SD card and used again Win32DiskImager to write the image from the other SD card onto the new one. When the write action started, Win32DiskImager warned me that the image to be written on the new SD card was too big but that the part that couldn't be written was not containing any data.
==> Question: How is that possible? Why is the image copied from my initial SD card not fitting onto the new card which is identical in size?
- Since Win32DiskImager informed me that the "extended" part didn't contain any data, I commanded it to continue with the write action (also took a very long time.
- The end result is that the new SD card that contained (or should contain) the image of the original SD card, didn't start up. Finally, I had to do the installation from scratch again, doubling all the actions I did for the first SD card to get my second system up and running in (hopefully) the same condition/situation as my first system.
Since it's apparently not possible to use Win32DiskImager to take an exact copy of an existing system, what tool(s) should be used then for that purpose? I'm on a Windows 10 system, but a Linux solution (dd?) is also welcome...