romanbelkov / diskimager Goto Github PK

• Choose a CI server
• Add CI to this repo

If you launch 1.2.1 the issues is resolved and 1.2.2 can launch without errors.

Very repeatable on a windows 7 virtual machine.

I can seem to post an image of the error message, but it is unhappy with the change language/read registry code.

• Check if GPT works ok
• Add support of loop (no partition table) devices
• Nicer MBR check (e. g. look into first bytes of partitions to see if they're OK)

Tip: Pick up ideas from parted utility

Hi,

First of all thanks for this tool - really helpful.
One suggestion - when writing image to SD, it would be great to get an error in the beggining if image size is greater than the SD card (in my case both cards were 8GB, both from the same manufacturer, but slightly different size). Currently the error comes up only after almost all image is loaded.

Thanks again

• UI tests
• Integration tests (Ideas about how this should be done)

Hey, nice piece of software!
I need to write images on several SDcards at once using Win7 x64.
Instead of opening many win32diskimage instances, I was looking for an altered version that needs only one instance and so I found your program.

But I can't write to any SD card at all!
After selecting one or many drives and clicking on the "restore ..." button, selected an .img-File I get a message saying "Write Error" "Problem writing to disk. Is it write-protected?"
After that I get "All done!" "All drives are ready"

But none of the SDcards are protected or done!

This is horrible. We need to go from this nightmare to safe .NET functions

There is a need to switch user interface to something similar to wizard installation guides

I just wanted to start by thanking Mr. Belkov for developing this software as it has been very useful. Unfortunately, I have encountered an issue with the software and have since found a workaround (by using another program) but I wanted to leave details of what I found here for anyone interested.

I originally had three primary partitions of which the third was encrypted. This seemed to work fine but the third partition was actually encrypted and formatted after the image was deployed to a microSD card (so it could have had an issue that was masked by my post deployment method).

My new image has four primary partitions (see table below) that follows the same general format of the previous image (i.e. basically the same as the three partition backups) except I have increased the sizes of the second and third as well as adding a fourth partition. Although I'm still leaving the third partition encrypted (which is then re-encrypted and reformatted once the image has been deployed), the fourth partition has been formatted to ext4 (BEFORE using the program to image it) and left as-is.

The problem I have is that when I backup my image and then restore it onto a different card (the original/master microSD card works okay), I get a bad superblock error on the fourth partition. I have tried several different cards, zeroing out the card and then trying, etc. and they all result in the same. If I use the original card, there is no error.

What I believe is happening is that the program isn't properly detecting either the fourth partition boundary and/or the third (I suspect the fourth) and then not backing it up during the imaging process. My reason for this assumption is that although the image should be around 7.25G the program only backs up 3.25G. If I use Win32 Disk Imager, I can successfully backup and restore the image but it's also the larger file size (i.e. ~7.25G).