Okay when creating a new image that was resizable I receive the dirty filesystem 0,0 error.
rebooted the system and turned fast startup off.
After doing so I was able to create the image successfully.
Tried to deploy the newly created image on the smaller HDD and so far so good we are writing the image now.

Recap for marking the post solved.

Could not image HDD with known good image was getting a “No image file(s) found that would match the partition(s) to be restored (performRestore)”
Ran Debug mode to see what partitions were being created on the HDD.
Checked the partition table on the image on the server.
Noticed that the image was a MPS(Multiple Partition Single Disk) and HDD in host was smaller than the original used to create the image.
Disabled Fast booting on the host I need to re-create an image from.
Re-created an image using SDR (Single Disk Resizable).
Was then able to deploy the image to the host with the smaller HDD with no problems.

SUCCESS! I have successfully created and deployed the images for these machines in efi mode. Thank you for all the help!

@Wayne-Workman

as much as I hate giving up on fixing a problem it appears that rebuilding will be the easier route. thanks for the link for rebuilding fog server I was unaware of how to copy the images and and migrate them to a new server.

I am working on a Latitude 5300 Laptop it has a NVMe SSD installed I am booting to the Dell USB 3.0 to Ethernet adapter with PXE boot to image these machines. The workstation will boot to the fog menu but when I try upload an image i get this after the bzimage and init.xz loads – “usb usb2-port2: cannot enable. Maybe the USB cable is bad?” If I unplug the usb and plug it back in it will stop and allow me to plug the usb back in once I do it works properly. attached is a screenshot after I have re-seated the usb nic. Any help to not have to do the “Re-seat” step would help me out a lot.

I have tried adding the Kernel Args. usbcore.old_scheme_first=1 has_usb_nic=1 and it has not resolved the issue.

I am running FOG Version 1.5.6 bzImage Version 4.19.36

Secondly, if we could get the NVMe drive to be recognized using the SATA Mode “Raid on” instead of “AHCI” would help out as well.

@george1421

Also, something to note, I had another machine I was testing this on and if you do not do the disk cleanup and remove the old windows installations the new inits work just fine. It appears the cleanup messes something up for some reason.

@george1421 Correct

@george1421 Actually as long as you update the init.xz and init_32.xz it appears to work in 1803!

No I hadn’t.

Since you suggested it I did and it appears to be working now. Glad it was such an easy fix! Thanks!

So I am trying to update my image of a machine I updated to Winodws 10 Version 1803 (Spring update 2018) and I am getting the “Error Could Not Open inode XXXXXXX Through Library”

I visited the (https://forums.fogproject.org/topic/11207/error-could-not-open-inode-xxxxxx-through-the-library) and updated the init.xz and the init_32.xz files and tried to re-run the capture task but am still having the same error occur.

I will note I ran disk cleanup and removed previous windows installations before trying to update this image to reduce the size of the image as much as possible.

Server Info
FOG Version 1.5.2
Ubuntu 16.04 LTS

@Tom-Elliott yes

Okay when creating a new image that was resizable I receive the dirty filesystem 0,0 error.
rebooted the system and turned fast startup off.
After doing so I was able to create the image successfully.
Tried to deploy the newly created image on the smaller HDD and so far so good we are writing the image now.

Recap for marking the post solved.

Could not image HDD with known good image was getting a “No image file(s) found that would match the partition(s) to be restored (performRestore)”
Ran Debug mode to see what partitions were being created on the HDD.
Checked the partition table on the image on the server.
Noticed that the image was a MPS(Multiple Partition Single Disk) and HDD in host was smaller than the original used to create the image.
Disabled Fast booting on the host I need to re-create an image from.
Re-created an image using SDR (Single Disk Resizable).
Was then able to deploy the image to the host with the smaller HDD with no problems.

AH yeah it is a smaller drive than the original. I happen to have another one of those computers I can recreate an image using single disk resizable. If my memory serves me correctly I was having trouble getting it to create an image that way. I will update this when I run into problems.