USBit 1.8.5 on WinPE (HBCD x64)

[benryanau]

Hiren's Boot CD released a HBCD Win x64 environment image withg a shell, tools (macrium etc).
It's Win PE x64 (W10 v19041.1 ADK v2004/aka 20H1) .

Running USBit 1.8.5 (program dir on r/w mounted D: drive usb key), it loads up okay both cmdline and gui but only shows the USB key it's running off - and lists no other devices or volumes in device or volume mode. I grabbed the debug logs from cmdline with "d" and "l" switches as well as GUI (with "show all drives" selected) It's Quoted below at EOM.

I use USB Image Tool to image disks over other tools because it is reliable, repeatable and its streaming compression allows 4tb+ disks to be new-out-of-box imaged to capture factory formatting - very handy fior SD cards given the minefield of partition/FS variables that seem different for each model of even the same mfg. That factory layout is hard to capture and reproduce let alone document and record so I just image the things out of the box.

Here I'm trying to use USBit to grab a disk image of a system's internal SATA disk (MBR w/ WS2012R2) from an external boot image of WinPE, where I'll save the disk image to a temporary mounted removable USB HDD.
I also wanted to use this bootcd/usbit combo as an independent stable platform where I could reliably (and permanently) work on all my usbit-created images both now and in the future.. i already have piles of orphaned images from a dozen imaging/virtualdisk platforms over the years and for one example, my Ghost boot floppy no longer gets me anywhere when it comes to 15 year old GHO image files

Thanks for USB Image Tool Alex

Ben



====

Code: Select all

D:\tools\usbit185>usbitcmd.exe l /debug

USB Image Tool 1.85
COPYRIGHT 2006-2022 Alexander Beug
http://www.alexpage.de


FD01: \\?\scsi#disk&ven_wdc&prod_wd3200bekt-75pvm#4&1c6b71d1&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: WDC WD3200BEKT-75PVMT1
FD04: Device ID is SCSI\DISK&VEN_WDC&PROD_WD3200BEKT-75PVM\4&1C6B71D1&0&000000
FD05: Media Type is 12
FD06: Location PCI bus 0, device 31, function 2
FD07: Hardware ID PCI\VEN_8086&DEV_1E02&SUBSYS_052C1028&REV_04
FD08: Device Number is 0

FD01: \\?\usbstor#disk&ven_verbatim&prod_store_n_go&rev_2.00#1313063727081578&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: Verbatim STORE N GO USB Device
FD04: Device ID is USBSTOR\DISK&VEN_VERBATIM&PROD_STORE_N_GO&REV_2.00\1313063727081578&0
FD05: Media Type is 11
FD06: Location Port_#0002.Hub_#0003
FD07: Hardware ID USB\VID_18A5&PID_0302&REV_0200
FD08: Device Number is 1
FD09: FOUND!


FV01: \\?\scsi#cdrom&ven_plds&prod_dvd+-rw_ds-8a9sh#4&1c6b71d1&0&000100#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

FV01: \\?\storage#volume#{188b273c-26cc-11ed-8ad9-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

FV01: \\?\storage#volume#{188b273c-26cc-11ed-8ad9-806e6f6e6963}#0000000015f00000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

FV01: \\?\ramdisk#ramvolume#{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

FV01: \\?\storage#volume#_??_usbstor#disk&ven_verbatim&prod_store_n_go&rev_2.00#1313063727081578&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 1
FV03: Volume match Port_#0002.Hub_#0003
FV04: Partition number is 1
FV05: Volume name is \\?\Volume{188b27a6-26cc-11ed-8ad9-eff2eebe525e}\ (U2V32GBF32R)
FV06: Volume path is D:\
FV07: MATCHED!
  Device | P# | Friendly Name            | V# | Volume Name | Path | Size
 ------------------------------------------------------------------------------
       2 |  1 | Verbatim STORE N GO USB  |  1 | U2V32GBF32R | D:\  |  29983 MB

==========

Code: Select all

FD01: \\?\scsi#disk&ven_wdc&prod_wd3200bekt-75pvm#4&1c6b71d1&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: WDC WD3200BEKT-75PVMT1
FD04: Device ID is SCSI\DISK&VEN_WDC&PROD_WD3200BEKT-75PVM\4&1C6B71D1&0&000000
FD05: Media Type is 12
FD06: Location PCI bus 0, device 31, function 2
FD07: Hardware ID PCI\VEN_8086&DEV_1E02&SUBSYS_052C1028&REV_04
FD08: Device Number is 0

FD01: \\?\usbstor#disk&ven_verbatim&prod_store_n_go&rev_2.00#1313063727081578&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: Verbatim STORE N GO USB Device
FD04: Device ID is USBSTOR\DISK&VEN_VERBATIM&PROD_STORE_N_GO&REV_2.00\1313063727081578&0
FD05: Media Type is 11
FD06: Location Port_#0002.Hub_#0003
FD07: Hardware ID USB\VID_18A5&PID_0302&REV_0200
FD08: Device Number is 1
FD09: FOUND!

[Alex]

Thanks for your feedback on USB Image Tool. As you have noticed, USB Image Tool does not list the internal HDDs but only USB mounted devices. This limitation is intentional for 2 reasons.

1. I wanted to create a tool especially dedicated to USB devices, simple and easy to use. I didn't wanted to replicate full size HDD cloning tools like Ghost, Clonezilla (which I use myself for cloning HDDs) and others. I aslo wanted to minimize the risk of users accidently overwriting their data HDDs or system drives, so I decided to filter devices for USB attached ones.
2. Live cloning system HDD's requires techniques like VSS, that are not implemented in USB Image Tool. In your case with a PE environment, this would probably work with the system booted from USB, but usually USB Image Tool runs from a live system and not on a PE environment.

I might remove the limitation to USB with one of the next versions, but right now I'm afraid USB Image Tool can't help you with this task alone. But maybe with a little addition from a tool, that also comes with HBCD (I checked the website). It also contains Minitool Partition Wizard, that I also use myself for partitioning USB devices. This does not allow you to clone a disk to an image, but seems like it can clone a disk 1:1 to another. If your first clone your system drive 1:1 to an additional USB HDD and then use USB Image Tool to create a RAW image of the first USB device to the 2nd USB HDD, this might be the result, you want. Downside is the need for an additional USB HDD + more time for the first disk cloning step.