PassMark Software
Global (Go to Australian site)

Announcement

Collapse
No announcement yet.

ImageUSB Limits?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • ImageUSB Limits?

    Hello,

    I'm capturing a 32GB USB; it runs to 100%. When I assume the 'Post Image Verification' is about to begin I get a crash dialog. The .bin file is 32,094,814,720 bytes.

    Are there limits? Are there any secret builds other than v1.1 build 1008 that may address something like this? I'm going to reboot and attempt again as well.

    Thanks

    Brad
    Last edited by bradfordm; 04-10-2012, 11:19 PM. Reason: Rouge Smile!

  • #2
    There is no known problem that we are aware of that would cause this.

    Starting imageUSB with the "-d" command line argument will save a debug log. The filename for the logfile is "imageUSB.log" and can be found in the same directory as the executable.

    If you can send this log in, we will see if there is any useful information.

    Comment


    • #3
      Experiencing crashes during image Creation from 8GB UFD

      Hi Richard

      I am also experiencing crashes after image creation indicates 100% with a FAT32 formatted 8 GB flash drive.

      This has occurred on two different computers (32-bit Windows 7sp1 and 32-bit Windows XP sp3).

      I experimented with a 1 GB flash drive and was able to successfully complete the process.

      Any help would be very much appreciated.

      Thanks

      Patrick



      The following is a truncated excerpt from my imageUSB.log file:

      19-Apr-2012 - 17:44:46:770 - PassMark Software - imageUSB v1.1.1008
      19-Apr-2012 - 17:44:46:770 - Getting list of available removable USB drives...
      19-Apr-2012 - 17:44:46:770 - Debug: Thread (3076) Drive F:\ Size: 8162099200 Bytes Volume: MYLINUXLIVE Other: FAT32

      19-Apr-2012 - 17:44:46:770 - Ready...
      19-Apr-2012 - 17:45:08:013 - User chose to overwrite existing file (C:\Users\GTI\Desktop\test.bin).
      19-Apr-2012 - 17:45:08:029 - Drive F:\ added to queue.
      19-Apr-2012 - 17:45:08:029 - Creating image from Drive [F:\]...
      19-Apr-2012 - 17:45:08:029 - Debug: Thread (2572) Drive F:\ size [ 8178892800 bytes ]

      19-Apr-2012 - 17:45:08:357 - Debug: Thread (2572) Successfully opened image file C:\Users\GTI\Desktop\test.bin for write acess.
      19-Apr-2012 - 17:45:08:357 - Creating image C:\Users\GTI\Desktop\test.bin from F:\ (drive 2)
      19-Apr-2012 - 17:45:09:230 - Debug: Thread (2572) Creating...0.1%
      19-Apr-2012 - 17:45:10:088 - Debug: Thread (2572) Creating...0.3%
      (truncated)
      19-Apr-2012 - 17:56:28:563 - Debug: Thread (2572) Creating...99.6%
      19-Apr-2012 - 17:56:29:484 - Debug: Thread (2572) Creating...99.7%
      19-Apr-2012 - 17:56:30:420 - Debug: Thread (2572) Creating...99.9%
      19-Apr-2012 - 17:56:31:340 - Debug: Thread (2572) Creating...100.0%

      Comment


      • #4
        Unfortunately, the logs are not helpful in determining the cause. We have not run into this problem in house.

        We will do some more testing in house. Can you elaborate on the brand/model of the USB flash drive you are using. We will see if we have something similar to try to recreate the problem.

        A possibility is that the destination drive where the image file is being saved is also a FAT32 filesystem. The max file size on a fat 32 filesystem is 4GB.

        Comment


        • #5
          App Crash Upon Image Verification

          Originally posted by Richard (PassMark) View Post
          Unfortunately, the logs are not helpful in determining the cause. We have not run into this problem in house.

          We will do some more testing in house. Can you elaborate on the brand/model of the USB flash drive you are using. We will see if we have something similar to try to recreate the problem.

          A possibility is that the destination drive where the image file is being saved is also a FAT32 filesystem. The max file size on a fat 32 filesystem is 4GB.
          Has anyone determined the cause and solution to this issue? I am experiencing it too

          Comment


          • #6
            Can you elaborate on
            - The version of imageusb you are using
            - the brand/model of the USB flash drive you are using
            - the size of the drive
            - the file system on the source USB drive and the file system in use on the destination drive.

            As noted above there is a limit of 4GB per file on the FAT file system. (using NTFS solves this)

            Comment


            • #7
              Hi.


              I'm having exactly the same issue with version 1.1 Build 1009 of ImageUSB with a 16gb Pretec i-Disk Bulletproof flash drive (http://www.pretec.com/products/usb-flash-drives/item/usb-flash-drives/bulletproof).


              The logfile generated doesn't offer much help I'm afraid. It reads (minus the hundreds of lines containing the "Debug: Thread (4140) Creating...0.1%" stuff:


              04-Oct-2012 - 12:22:46:536 - PassMark Software - imageUSB v1.1.1009
              04-Oct-2012 - 12:22:46:552 - Getting list of available removable USB drives...
              04-Oct-2012 - 12:22:46:567 - Inspecting Drive C:\...
              04-Oct-2012 - 12:22:46:567 - Debug: Thread (7816) Drive C:\: Not of USB Type Skipping. DriveType 3
              04-Oct-2012 - 12:22:46:567 - Inspecting Drive D:\...
              04-Oct-2012 - 12:22:46:567 - Debug: Thread (7816) Drive D:\: Not of USB Type Skipping. DriveType 1
              04-Oct-2012 - 12:22:46:583 - Inspecting Drive E:\...
              04-Oct-2012 - 12:22:46:583 - Debug: Thread (7816) Drive E:\: Not of USB Type Skipping. DriveType 0
              04-Oct-2012 - 12:22:46:583 - Inspecting Drive F:\...
              04-Oct-2012 - 12:22:46:598 - Debug: Thread (7816) Drive F:\ Size: 1500299390976 Bytes Volume: BackpDrv Other: NTFS


              04-Oct-2012 - 12:22:46:598 - Inspecting Drive G:\...
              04-Oct-2012 - 12:22:46:598 - Debug: Thread (7816) Drive G:\ Size: 16155394048 Bytes Volume: Other: FAT32


              04-Oct-2012 - 12:22:46:614 - Ready...
              04-Oct-2012 - 12:23:20:801 - User chose to overwrite existing file (C:\local\imageusb\USB_Key_Backups\RJC_16GB.bin).
              04-Oct-2012 - 12:23:20:816 - Drive G:\ added to queue.
              04-Oct-2012 - 12:23:20:832 - Creating image from Drive [G:\]...
              04-Oct-2012 - 12:23:20:863 - Debug: Thread (4140) Drive G:\ size [ 16173182976 bytes ]


              04-Oct-2012 - 12:23:21:472 - Debug: Thread (4140) Successfully opened image file C:\local\imageusb\USB_Key_Backups\RJC_16GB.bin for write acess.
              04-Oct-2012 - 12:23:21:472 - Creating image C:\local\imageusb\USB_Key_Backups\RJC_16GB.bin from G:\ (drive 2)


              04-Oct-2012 - 12:23:22:314 - Debug: Thread (4140) Creating...0.1%
              .
              .
              .
              .
              .
              .
              04-Oct-2012 - 12:39:16:065 - Debug: Thread (4140) Creating...99.7%
              04-Oct-2012 - 12:39:16:673 - Debug: Thread (4140) Creating...99.7%
              04-Oct-2012 - 12:39:17:250 - Debug: Thread (4140) Creating...99.8%
              04-Oct-2012 - 12:39:17:859 - Debug: Thread (4140) Creating...99.8%
              04-Oct-2012 - 12:39:18:420 - Debug: Thread (4140) Creating...99.9%
              04-Oct-2012 - 12:39:19:029 - Debug: Thread (4140) Creating...100.0%


              ....and then a crash window appears that simply says:


              "imageUSB has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."


              NOTE: This is with the 'Post Image Verification' option off.


              This is the corresponding information from the Event Log:


              Faulting application name: imageUSB.exe, version: 1.1.1009.0, time stamp: 0x4ffb6c60
              Faulting module name: imageUSB.exe, version: 1.1.1009.0, time stamp: 0x4ffb6c60
              Exception code: 0xc0000005
              Fault offset: 0x00001ef9
              Faulting process id: 0x2538
              Faulting application start time: 0x01cda21d18d69b4e
              Faulting application path: C:\local\imageusb\imageUSB.exe
              Faulting module path: C:\local\imageusb\imageUSB.exe
              Report Id: bfc7c58a-0e12-11e2-9ee9-acb354cf2cca


              ...which doesn't appear to give much away. I've tried this on two different laptops, although both running 64-bit Windows 7. I've also tried with a test USB key (256MB) which worked successfully.


              Any ideas?


              Thanks.

              Comment


              • #8
                Originally posted by Craz View Post
                Any ideas?
                We haven't been able to reproduce this error on our test USB Flash Drives. I sent you a PM regarding testing a debug build, get back to me if you wouldn't mind testing.

                Comment


                • #9
                  Originally posted by Richard (PassMark) View Post
                  We haven't been able to reproduce this error on our test USB Flash Drives. I sent you a PM regarding testing a debug build, get back to me if you wouldn't mind testing.
                  I emailed you about the debug build (didn't work). I assume you received it? Any other ideas?

                  Comment


                  • #10
                    Sorry, I've been a little busy trying to get the benchmark charts in order for the release of PerformanceTest 8 and haven't been able to get around to imageUSB.

                    But yes, I have received it. I have a hunch on what the issue might be. It seems that either your USB Flash Drive or the Windows API (for some particular drives) is not correctly reporting the end of the drive. So imageUSB reading beyond what the reported size of the drive is.

                    I will try to get you another build today and if all goes well, we'll release it on our site next week.

                    Comment


                    • #11
                      We have release imageUSB V1.1 Build 1010 which should fix the crashing issue seen with fake USB drives and reading past the end of such a drive. When creating an image, if there is a possibility of reading past the end of the drive, we will only only write the image up to reported size of the drive.

                      In the meantime, we are trying to acquire an actual fake USB drive (ones that report incorrect size compared to actual available space) to do some more testing.

                      Comment

                      Working...
                      X