PassMark Software

Announcement

Collapse
No announcement yet.

ImageUSB - Failure to extend partition

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

  • ImageUSB - Failure to extend partition

    Good Morning,

    I ran across your ImageUSB software this evening and it could help me immensly, but I ran into an issue I think.

    I have to create 40+ duplicates of Corporate Imaging USB Thumb Drives when a new image is released. I've been using batch files I created up till now, but as you can realize error checking is non existent, and the keys are starting to get some age on them so I need to correct this. In comes ImageUSB

    I tested it. The log is below. I took a ready-created 16GB USB Key with the Bootable Image on it and created a .bin with ImageUSB. So far so good.

    I then inserted two new 32GB keys into the system, refreshed, and wrote the bin back out to them. I selected Post Image Verification and Extend Partition as options.

    The copy seemed to go fine, but the partition extensions both failed. It was my assumption that this feature was intended for my situation, where the image is from a 16GB key and the new destinations are 32GB keys. Was I correct?

    All keys are Kingston.

    The log is below. Plese let me know what I might be doing wrong.

    Thanks for an awesome program

    Larry

    01:43:59 - PassMark Software - imageUSB v1.2.1004
    01:43:59 - Getting list of available removable USB drives...
    01:43:59 - Inspecting Drive C:\...
    01:43:59 - Inspecting Drive D:\...
    01:43:59 - Inspecting Drive E:\...
    01:43:59 - Inspecting Drive F:\...
    01:43:59 - Inspecting Drive G:\...
    01:43:59 - Inspecting Drive H:\...
    01:43:59 - Inspecting Drive I:\...
    01:43:59 - Ready...
    01:45:43 - Getting list of available removable USB drives...
    01:45:43 - Inspecting Drive C:\...
    01:45:43 - Inspecting Drive D:\...
    01:45:43 - Inspecting Drive E:\...
    01:45:43 - Inspecting Drive F:\...
    01:45:43 - Inspecting Drive G:\...
    01:45:43 - Inspecting Drive I:\...
    01:45:43 - Inspecting Drive J:\...
    01:47:22 - Drive J:\ added to queue.
    01:47:22 - Creating image from Drive J:\ - Image FileName: C:\Users\Larry\Desktop\Current GL Image\GL793c_09-03-2015.bin
    01:47:22 - Starting to Create From Drive J:\
    01:47:22 - Creating image C:\Users\Larry\Desktop\Current GL Image\GL793c_09-03-2015.bin from J:\ (drive 7)
    02:05:12 - Drive J:\ - Image completed.
    02:05:12 - Drive J:\ - MD5 Checksum: CF3B46C2C4C787B2788ED113409989E5
    02:05:12 - Drive J:\ - SHA1 Checksum: 1A6BACA08DB23F5E4DA4C4A09BEAF62583DFDCAF
    02:05:13 - Verifying Image C:\Users\Larry\Desktop\Current GL Image\GL793c_09-03-2015.bin created from Drive J:\...
    02:06:35 - Drive J:\ checksum completed.
    02:06:35 - Image C:\Users\Larry\Desktop\Current GL Image\GL793c_09-03-2015.bin - MD5 Checksum: CF3B46C2C4C787B2788ED113409989E5
    02:06:35 - Verification passed - MD5 matched. (J:\).
    02:06:35 - Image C:\Users\Larry\Desktop\Current GL Image\GL793c_09-03-2015.bin - SHA1 Checksum: 1A6BACA08DB23F5E4DA4C4A09BEAF62583DFDCAF
    02:06:35 - Verification passed - SHA1 matched. (J:\).
    02:08:11 - Getting list of available removable USB drives...
    02:08:11 - Inspecting Drive C:\...
    02:08:11 - Inspecting Drive D:\...
    02:08:11 - Inspecting Drive E:\...
    02:08:11 - Inspecting Drive F:\...
    02:08:11 - Inspecting Drive G:\...
    02:08:11 - Inspecting Drive H:\...
    02:08:11 - Inspecting Drive I:\...
    02:08:11 - Inspecting Drive J:\...
    02:09:17 - Drive H:\ added to queue.
    02:09:17 - Drive J:\ added to queue.
    02:09:17 - Starting to Write to Drive H:\
    02:09:17 - Starting to Write to Drive J:\
    02:09:17 - Writing image C:\Users\Larry\Desktop\Current GL Image\GL793c_09-03-2015.bin to J:\ (drive 7)
    02:09:17 - Writing image C:\Users\Larry\Desktop\Current GL Image\GL793c_09-03-2015.bin to H:\ (drive 5)
    02:12:30 - Drive J:\ write completed.
    02:12:30 - Verifying written image on Drive J:\
    02:12:36 - Drive H:\ write completed.
    02:12:36 - Verifying written image on Drive H:\
    02:16:04 - Drive J:\ checksum completed.
    02:16:04 - MD5 matched. (J:\).
    MD5 (Drive) : CF3B46C2C4C787B2788ED113409989E5
    MD5 (Image) : CF3B46C2C4C787B2788ED113409989E5


    02:16:04 - SHA1 matched. (J:\).
    SHA1 (Drive) : 1A6BACA08DB23F5E4DA4C4A09BEAF62583DFDCAF
    SHA1 (Image) : 1A6BACA08DB23F5E4DA4C4A09BEAF62583DFDCAF


    02:16:04 - Attempting to Extend Partition with Volume J:\
    02:16:04 - Failed to Extend Volume J:\. (Error 87)
    02:16:04 - Failed to Extend Partition for Drive J:\
    02:16:10 - Drive H:\ checksum completed.
    02:16:10 - MD5 matched. (H:\).
    MD5 (Drive) : CF3B46C2C4C787B2788ED113409989E5
    MD5 (Image) : CF3B46C2C4C787B2788ED113409989E5


    02:16:10 - SHA1 matched. (H:\).
    SHA1 (Drive) : 1A6BACA08DB23F5E4DA4C4A09BEAF62583DFDCAF
    SHA1 (Image) : 1A6BACA08DB23F5E4DA4C4A09BEAF62583DFDCAF


    02:16:10 - Attempting to Extend Partition with Volume H:\
    02:16:10 - Failed to Extend Volume H:\. (Error 87)
    02:16:10 - Failed to Extend Partition for Drive H:\

  • #2
    Also, would it be possible to add a "format before writing" option to clear out the old USB keys before they are re-written? I have to re-use them as they are sent back by tech's to be refreshed with the new image.

    Comment


    • #3
      What was the file system and partition setup of the source drive?
      e.g. Two FAT32 partitions of size X and Y?

      Writing a new image effectively does a quick format on the drive. So there shouldn't be any need for a format before writing.

      Also if these drives are just used for distributing information and not for storage of additional data, then you don't really need to worry about extending the partition.
      Another solution would be to use a 32GB source drive and not a 16GB source drive.

      Comment


      • #4
        Originally posted by David (PassMark) View Post
        What was the file system and partition setup of the source drive?
        e.g. Two FAT32 partitions of size X and Y?

        Writing a new image effectively does a quick format on the drive. So there shouldn't be any need for a format before writing.

        Also if these drives are just used for distributing information and not for storage of additional data, then you don't really need to worry about extending the partition.
        Another solution would be to use a 32GB source drive and not a 16GB source drive.
        The source is a 16GB NTFS. The destination is a 32GB. I assume the program quick formats the destination in the same format as the source .bin.

        Comment


        • #5
          Can you email in and we can send you a debug build that will log more information around the extend partition functionality to try to pinpoint where it is failing.

          Comment


          • #6
            Originally posted by Richard (PassMark) View Post
            Can you email in and we can send you a debug build that will log more information around the extend partition functionality to try to pinpoint where it is failing.
            Sure! What do you need me to do?

            Comment


            • #7
              Send email referencing this thread. We will send you a debug build that you can run to collect more information. After you do this, send the files back for us to investigate. Email us at:
              help [at] passmark [dot] com

              Comment


              • #8
                Will do. I sent a PM but will email too

                Thanks!

                Comment


                • #9
                  New build of imageUSB (V1.2.1006) was released to address the issue.

                  Comment


                  • #10
                    Thanks a ton to Richard for helping get this resolved. Smooth sailing now !!!

                    Great job guys.

                    Comment

                    Working...
                    X