1. The image was greater than 2 GB but only the first image.img file was available. The subsequent image file image files (.002, .003, etc.) were missing.
2. Drive mappings or image path locations were incorrect.
3. The image or one of the image files was corrupt. It is also possible that creating the image captured bad sectors from the source machine.
4. When using Linux Automation and the image is located on spanned CD/DVDs, the error can occur when RDeploy tries to signal the user that the next CD/DVD is required.
If the image is larger than 2 GB, the image will be split into separate files with the subsequent files using the file extension of .002, .003, etc. Use an .img image that includes all parts of the image in the same location.
Verify correct drive mappings in the PXE Server Configuration and correct image location path in the Distribute Image task.
Run CHKDSK on the source machine and capture the image again. Running CHKDSK should mark all bad sectors so when the image capture process takes place, it will not try to capture corrupt information on those sectors. After the CHKDSK is run on the source machine, recapture the image. Note: Unfortunately, there is no way to fix a corrupted image file.
The RDeploy application, when run through Linux Automation, is unable to interact with the user.
Applies To Deployment Solution 6.8 through 6.9 SP3.
Imported Document ID: TECH27931
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe