"Cannot verify digital signature" boot error on target during X2P migration

Document ID:7008925
Creation Date:30-Jun-2011
Modified Date:25-Jul-2017
- Micro Focus Products:
  PlateSpin Forge
  PlateSpin Migrate
  PlateSpin Portability Suite
  PlateSpin Protect

Environment

PlateSpin Portability Suite

PlateSpin Protect/Migrate

PlateSpin Forge

Situation

X2P migration to a target machine with a Broadcom HT1000 series SATA controller will go into recoverable error during the Configure Target Machine step.

Due to a driver signing issue with the Broadcom HT1000 series SATA controller drivers, target physical machine may fail to boot up correctly. The problem is with the file "bchtsw64.sys". This will result in the job going into recoverable error during the Configure Target Machine step. The target machine will display the following error:

"Unable to verify the digital signature of the file"

Resolution

1. Check the target machine with the Broadcom HT1000 series SATA controller. It should have a boot error with the message "Unable to verify the digital signature of the file".

2. To temporarily disable the signature requirement during startup, press ENTER, then F8. This will get you to Windows boot options.

3. Select the "Disable Driver Signing" option. This will temporarily disable driver signing and allow the machine to boot properly.

4. Repeat steps 2-5 until the "Configure Target Machine" step has completed the "Installing Drivers" step.

You may be required to do this 1 to 4 times. After this process, target machine should have no problems booting up.

Note: The job might or not recover from the current error state. However, once the target is up and functional as expected, the job is considered complete. It can be aborted to move it to failed state.

This issue can also be worked around by disabling driver signing on source before discovering or adding workload. For considerably large number of migrations to the specific hardware, this approach can be used.