After Win32diskimager img on new SD card will not boot

[ILiveAHoodie]

Hello, I am using Win32diskimager in exactly the same way as stated in 10billion forums about how easy it is to use. I am copying an SD card with Raspbian on it, it is a good working image. But all the images that i make do not boot on my raspberry pi after i make the clone. In windows, before I make the clone, the original SD card shows Boot is the listed partition. After I write the img to a new SD card the partition that shows in windows is RESTORE. I look inside of Disk Management in windows and it shows all the normal partitions that should be on the SD card image. But then I put it inside my Raspberry pi 2 and just rainbow screen. Nothing else happens. /boot directory is empty on the newly written image, but populated in original. I'm using windows 7 with Win32diskimager to make the img files and then to write them to the new SD cards. They all finish writing and reading, none boot... Are there any other people who are having this issue?

[runboy93]

Might be faulty SD card somehow.

[drgeoff]

If the original card has Raspbian it will have 2 partitions, neither of which is called RESTORE. That you find a partition called RESTORE suggests an image of a card that had NOOBS. Are you sure you are writing the correct image?

[MaxK1]

The only time I have had trouble using an image was when my nephew wrote an SD card using windiskimager. Big chunks of /usr/bin and /usr/lib were missing. Wrote the same image using dd on a Linux laptop. I don't know what the problem was, but since I don't use Windows, I didn't spend any time on it. dd just works...☺

[alphanumeric]

I've backed up and restored images from and too my Pi SD cards, from Windows with win32 diskimager, with no issues. Not yet anyway. Straight up Raspbian installs, no NOOBS.

[MrEngman]

I've had problems in the past a few times. Using Win32DiskImager I've written an image, usually Raspbian, to a brand new unused SD card, both 32GB and 16GB SanDisk, and then I found the Pi would not boot and just showed the splash screen. Looking at the SD cards with my laptop and the images appear to have been written OK but they would not work with the Pi. I use a Win 7 laptop for formatting and writing the image.

I then re-formatted the SD card using SDFormatter with Option Format Size Adjustment ON and Format Type FULL(OverWrite) and then used Win32DiskImager to re-write the image to the card and then everything worked OK and the Pi would boot normally.

This has worked each time I had the problem. No idea why except it would seem to be some problem with the original format of the SD card.



MrEngman

[ILiveAHoodie]

If the original card has Raspbian it will have 2 partitions, neither of which is called RESTORE. That you find a partition called RESTORE suggests an image of a card that had NOOBS. Are you sure you are writing the correct image?

These images have been around for about a year. They could have very likely started as NOOBS, but would that present a problem with the current method of cloning? I have the orginal SD card from which the img was made and the IMG made from it at different configurations when I put the IMGs onto new card... nothing.

[ILiveAHoodie]

Might be faulty SD card somehow.

I've tried a couple different SD cards with this copy method, most of which were new, however they were all larger than the original image. Original SD was 8GB new SD the image was dumped on in 16GB. Could that cause problems. Right now I don't care about unused space for a temporary dump-and-run of the img. Just trying to not have to set up a new install of Linux.

[MaxK1]

Going to a larger card won't be a problem. Going to a smaller card will be. Even a same size card might be a problem.

[davidcoton]

Is the target a new Pi2? If so it's possible the images are too old, and need to be updated. You can do this in an older Pi (one that was arouind when you made the original image).

Code: Select all

sudo apt update
sudo apt dist-upgrade

If you only have a new Pi, then you need a new download.

Edit: corrected late-night typos.

[ILiveAHoodie]

Is the target a new Pi2? If so it's possible the images are too old, and need to be updated. You can do this inn an older Pi (one that was arouind when you made the original image).

Code: Select all

sudo apt update
sudo apt dist-upgrade

If you olny have a new Pi, then you need a new download.

This image was originally made on a Pi B+ but now I am putting the clone on a Pi2. Do you think that could be it? I thought there wasn't an issue with compatibility that would keep it from getting past the rainbow screen.

[klricks]

Is the target a new Pi2? If so it's possible the images are too old, and need to be updated. You can do this inn an older Pi (one that was arouind when you made the original image).

Code: Select all

sudo apt update
sudo apt dist-upgrade

If you olny have a new Pi, then you need a new download.

This image was originally made on a Pi B+ but now I am putting the clone on a Pi2. Do you think that could be it? I thought there wasn't an issue with compatibility that would keep it from getting past the rainbow screen.

A B+ image is not going to work especially if the P2 is the newer version V1.2.
The latest OS version can work on all RPi but older OS versions will not unless they are first updated in the older RPi before cloning. OR put the new cloned SD card in old RPi and update it.

[drgeoff]

This image was originally made on a Pi B+ but now I am putting the clone on a Pi2.

Only now do you tell us that. Your original post sounds like you have only one RPi.