Workaround for “Error EFI Partition missing” during Windows SYNC

This article describes steps to resolve an error, “The target is UEFI and would be missing an EFI System Partition.”, when ‘provisioning’ or ‘syncing’ to a Windows Server

Note – This issue was seen by the Customer is OCI – However, the issue is more with the ORIGIN/TARGET configuration than specifically with any Cloud Provider.

Background:

When ‘provisioning’ or ‘syncing’ to a Windows Server in OCI, RMM shows an error:

RSP_SYNC_ERROR   SYNC_ERROR_NO_ESP_FILE_SYSTEM   STATUS_ERROR

Details:

The target is UEFI and would be missing an EFI System Partition.

If the source is UEFI, make sure the EFI System Partition isn't excluded.

If the source is BIOS, make sure the boot file system isn't excluded.

The SYNC fails at this point and unable to proceed

RC of the Issue:

RMM currently does NOT support conversion of a Windows host from BIOS to UEFI, if the boot disk is a dynamic disk.

From what we have seen this far, it is pretty rare for the ‘boot’ disk to be made a ’dynamic disk’, because the ‘boot’ disk always contains the C: drive. And the C: drive is usually restricted.  

Even if made ‘dynamic’, it can't take advantage of the dynamic features (it can't be spanned, for example).

Before you Begin:

On the ORIGIN server (and if able to on TARGET server as well), note down the following information:
a) # of disks/size

b) # of volumes/size, partition type and other useful information

Use case/Applicable To:  

Migrating WINDOWS Servers ONLY (this issue is not applicable to Linux OS)

Preparation/Pre Req’s:
a) you should be able to RDP to both ORIGIN server and TARGET.  If your SYNC fails after the Target is created and you are unable to RDP/SSH to it, recreate a new Windows Target.

b) RMM should be able to SSH to both ORIGIN and TARGET servers & they both should meet RMM Pre-reqs (AV, Windows Defender, OS Firewall, etc.)

Steps:  

1) On the Target server, ensure the # of disks/volumes/size match the ORIGIN server

2) Assuming there are more than 1 Volumes/File System on the ORIGIN server (other than SYSTEM RESERVE & WinRE), perform a SYNC to the Target server with the following SYNC options:

a) this sync only includes file systems that reside on the origin boot disk (a list of which can be seen in disk management on the origin).  Exclude ALL other volumes

b) Select the option “Keep Target layout”. 

Perform a SYNC. 

(IOW, for the first sync with "keep target layout"  enabled, only file systems from the boot disk should be included. That includes any file systems on the boot disk, including any data volumes. So it's not so much that it specifically needs to include C: and System Reserved, but that it needs to include anything on the boot disk. C: and System Reserved are pretty much always on the boot disk. But sometimes there is also a WinRE file system, or sometimes it's called Recovery, and there may be other file systems on the boot disk as well. Sometimes there is no System Reserved file system.)

3) Upon a successful SYNC, follow it up with another sync – this time without option “Keep Target Layout" and NOT excluding any Volumes

In other words, REMOVE Volume exclusion and REMOVE "Keep Target Layout" option(s) and perform another SYNC.

This follow up sync will ensure the entire server is SYNC’d on the Target.

4) You can perform multiple Sync's thereafter as in step #3 above

This completes the procedure of SYNCING the server with above configuration.

Post Changes:
None

Contact:

Any issues or you need assistance with, please contact Support@RackwareInc.com