Details
Error code -701 means a failure occurred while reading from or writing to the recovery target during image file decompression. When restoring an image using Deploy or Recovery USB media, the following errors are typically recorded in the logs.
If an error occurs, a log file named “XXXXXXXXXX.log” is created. You can find it in the logs/Recovery folder after extracting the USBPE-support-yyyymmddhhmm.zip file located in the second partition (ImageData label) on the USB media.
Error Pattern 1
11/05/2025 04:23:41.372 Debug Note: Decompress() returned == 65967, (514,17658)
11/05/2025 04:23:41.372 Failed on checksum verification block 512(2): 0x101af 0xa9cd911 0xc5c2a2af Level = ERROR[0]
11/05/2025 04:23:41.372 ##### Pipe line encounter ERROR: 112, last error code:0, 512 Level = ERROR[0]
11/05/2025 04:23:41.388 Debug Note: Decompress() returned == 65542, (425,53779)
11/05/2025 04:23:41.388 Debug Note: Decompress() returned == 65544, (465,57752)
11/05/2025 04:23:41.388 Debug Note: Decompress() returned == 65578, (466,59959)
11/05/2025 04:23:41.403 Debug Note: Decompress() returned == 65540, (505,54365)
11/05/2025 04:23:41.403 Debug Note: Decompress() returned == 65598, (508,44823)
11/05/2025 04:23:41.403 ###### something wrong during run pipe line
11/05/2025 04:23:41.403 Pipeline end, exit code: -701
11/05/2025 04:23:41.403 #### ERROR wq.RunIt(LoadMyString(IDS_STRING3066), dwBlocksWritten,
dwBlocksPerRead, CCommWithService::GetSingleton().GetCurrentProcess(), fRatio) @ RestoreImage2.cpp(4119): -701 Level = ERROR[0]
11/05/2025 04:23:41.481 {IDS_STRING3018}Exit Code: -701
11/05/2025 04:23:41.481 [-701] an error occurred in pipe line
...Error Pattern 2
11/07/2025 04:08:32.214 OOOW: Yes
11/07/2025 04:09:13.764 Error calling ZSTD_decompressDCtx(), error -20 (Data corruption detected), compressed size: 57097, block: 166311 (48)
11/07/2025 04:09:13.765 ##### Pipe line encounter ERROR: 109, last error code:0, 166311 Level = ERROR[0]
11/07/2025 04:09:13.765 Busy for what:
STATUS_RESTORE_READ: 376 41
STATUS_RESTORE_DECOMPRESS_ZSTD: 375 9
STATUS_RESTORE_DEDUP: 374 0
STATUS_RESTORE_VERIFY_CRC: 374 1
STATUS_RESTORE_WRITE: 374 5
11/07/2025 04:09:13.871 ###### something wrong during run pipe line
11/07/2025 04:09:13.871 Pipeline end, exit code: -701
11/07/2025 04:09:13.871 #### ERROR wq.RunIt(LoadMyString(IDS_STRING3066), dwBlocksWritten, dwBlocksTotal, CCommWithService::GetSingleton().GetCurrentProcess(), fRatio) @ C:\Gitlab-Runner\builds\RzH5YZ9JQ\0\actiphy\activeimage-protector\Core\AipCopy\AgentBasedRestore.cpp(1827): -701 Level = ERROR[0]
11/07/2025 04:09:13.872 [DeDedup result] DeDedupCacheFound=0, DeDedupCacheNotFound=0
11/07/2025 04:09:13.872 {IDS_STRING3018}Exit Code: -701
...The main causes are:
- The source image was corrupted when copied to the Deploy or Recovery USB media.
- There is a read/write issue with the Deploy or Recovery USB media.
If the Deploy or Recovery task keeps failing with this error, please check the following:
● If the original source image for deployment is saved on the Desktop, etc.:
1) Create the Deploy/Recovery USB again using the same USB device. After recreating the USB media, run the Deploy or Recovery task. If the same error still occurs, the USB device itself may be faulty.
If the source image was copied to the Desktop, it may have become corrupted. If the original image is still on the original USB device, use that image to create the Recovery USB again.
If the issue continues, proceed to step 2.
● To create Recovery USB media, a Deploy USB media is required.
Note: Creating a Deploy USB media requires one license. Please contact our support desk to purchase a license.
2) Please create the Deploy or Recovery USB using a different USB device.
● If the source image is stored on the existing Deploy/Recovery USB, it may not be reusable. In that case, create a new Deploy/Recovery USB.
● When creating a new Deploy USB, if there is still an available license on the problematic USB, please contact our Support Desk.
Target Product
- ActiveImage DeployUSB
- DeployMediaCreator
(55218651318937)
Comments
0 comments
Please sign in to leave a comment.