Image too large to write back to card

Asked by Laird on 2017-07-17

Hi, I used Win32 Disk Imager to create an image of a 16GB card. I then tried to write it to an identical 16GB card (same manufacturer, model, size, etc) but it tells me there is not enough space on the destination card. I put the original card back in and tried to write the image to it and it tells me that it is too small to hold the image as well. Any assistance would be greatly appreciated.

Question information

English Edit question
Image Writer Edit question
Tobin Davis Edit question
Last query:
Last reply:
Tobin Davis (gruemaster) said : #1

Which version of Win32DiskImager did you use? Also, did you try checking the 'Read Only Allocated Partitions' checkbox? This will read to the last used block on the device (as opposed to the end of the device) and may help with this issue. Not sure why writing to the original device would fail, but knowing the version number would help.

There is an issue where reading from a device from vendor A and writing to a device listed as the same size from vendor B can fail, as they are often inaccurately listed and can differ by as much as 4k in size. Win32DiskImager looks at the number of blocks in the file and compares it with the number of blocks defined by the device, and will fail if the file is bigger. Using the checkbox will in most cases work around this issue.

Laird (ve3lks) said : #2

Tnx for the quick reply Tobin. I am using the latest version, 1.0. I will try creating the image with the "Read Only Allocated Partitions" when I get back home tonight. This card is out of a Raspberry Pi 3 with Jessie. Not sure if that will make a difference with a Windows program trying to read a card with another OS but I had read that it was possible. I will let you know how it goes.

Tobin Davis (gruemaster) said : #3

Win32DiskImager won't care what OS created the SD image. We do a raw read from sector 0 - end, including partition tables, etc. Windows may not like the resulting write if the image is not using Windows filesystems, but that's life (I'm actually a Linux developer).

When I test each release, I also do comparative testing with images created using dd on Linux. I even use that for benchmarking to make sure we're not doing something to slow down read/writes significantly (aside from the normal Windows overhead). Unfortunately, I only have limited resources, so some of the issues people are seeing are nearly impossible for me to replicate. But I do my best. In this case, it may be a simple indexing issue that got inadvertently added, so if you could also test with v0.9.5, that would help eliminate that possibility.

Mike (futuretense) said : #4

I just had the same exact problem burning a Raspberry Pi image. It was too large to burn back to the original SD card.

Laird (ve3lks) said : #5

HI Tobin, I tried creating the image with the "Read Only Allocated Partitions" option but the image was the exact same size. Where do I find the v0.9.5 version as I could only find the v1.0 on SourceForge? I will give that version a shot once I download it. I am hoping that we can find out what is happening because this would be an awesome tool to have in the arsenal.

Laird (ve3lks) said : #6

Mike, as a temporary work around if you are using a GUI interface on a RPi3 then there is an option under ACCESSORIES called SD CARD COPIER. This allows you to copy your internal RPi3 SD card to one that you put in one of the USB ports. The big downside to this is that you would need an SD card for every card you want to make a copy of. With Win32DiskImager we will be able to save an actual image on a PC or server which will be a lot more convenient and easier to use. Anyway, something to consider until this great little program is working.

Tobin Davis (gruemaster) said : #7

V0.9.5 is available under the Files->Archive section on SF (all releases are there). To make it easier, just download the binary zip file instead of the installer. It will run from where ever you unzip the archive (easier for testing purposes).

Can you help with this problem?

Provide an answer of your own, or ask Laird for more information if necessary.

To post a message you must log in.