With the upcoming announcement of Release 2.5 I remembered my SD card Images for my openHAB installation.
So I thought let’s create a new image from my openhabian installation, take the same type / size SD Card and test a restore - it turned out to be a BAD IDEA the cloned SD card didn’t boot in my Pi3.
I got nervous, checked our community and googled for different tools on Mac to create an SD card clone
Tested native DD, Etcher, ApplePiBaker, reformated several times with SD Card Formatter etc. - created an image, restored it on another card --> PI doesn’t start.
So I’m still nervous…and would appreciate your thoughts regarding my observations:
When I put in my productive openhabian based installation SD Card into the MAC, the MAC can not mount it (but recognizes it and PiBaker can capture it, visible as 0 in diskutil).
This is not the case with another native Jessie installation SD Card from my other Pi. It can be mounted
and I can see the visible files in the main structure (like cmdline.txt boot.txt etc…)
The cloning process of the openhabian based installation works without any errors. When I format the new SD card it is correctly mounted in the MAC, after I restored the openhabian image it can not be mounted anymore - like the productive / running SD Card which is working great in the Pi…
Is it normal that the openHABian based SD-Card can not be mounted in a Mac while I can see the files from another “non-openhabian image” installed Pi Card (mounted) ?
As I currently do not know what or where to modify / change the image capture procedure I’m pretty lost to search for reasons why an SD card clone does not boot up in the same Pi…
Would appreciate your thoughts / help where to further investigate…
With still nervous regards,