Posts made by duanekaeb

@Sebastian-Roth, here you go.

That may not be what you’re looking for. I pressed enter and the command line popped up. Parted -1 returned an error but I was able to get something when I typed in parted. This is a screen shot of the print command.

@Quazz I ran all four of these commands I found on another post but still no go.

---

kafluke Apr 24, 2019, 10:06 AM
@Quazz I saw a post by you in another thread and took your advice. I ran all these commands and it’s capturing now:

dism /online /cleanup-image /startcomponentcleanup
dism /online /cleanup-image /restorehealth
sfc /scannow
chkdsk /f

---

@Sebastian-Roth any recommendations?

@Sebastian-Roth

@sudburr Thanks for the script. I executed it but I’m still getting the same shrinkPartitiion error.

@Quazz & @Sebastian-Roth, I ran a chkdsk and did a defrag/trim and I’m still getting a resize test.

@Sebastian-Roth is it safe to run defrag when using an SSD?

I have a windows 10 machine that has 25GB of windows.old temp files. I’m unable to capture an image after I free up the temp files using the built in windows 10 storage clean tool.

This is not a picture from the system I’m imaging but wanted to show where I’m doing the cleanup.

This is the error message I get when I try and capture the image.

@Sebastian-Roth Thanks you!!! I swapped out the ipxe.kpxe file and it worked.

@Sebastian-Roth I’m using intel.pxe and it’s hanging up at the same point.

@Sebastian-Roth Thanks for that info. I’ve tried a number of iPXE binary but not the intel.pxe.

Something I did find interesting is that if I force the host to use bzimage32 it doesn’t hang up at this step. However it doesn’t matter if I use init.xz or init_32.xz, it still hangs up.

This is the network card I’m using.

I’ve seen similar post about this issue but I haven’t come across a solution.

I received a new model of industrial grade computer and I configured the BIOS as I normally do.
UEFI - Disabled
Legacy Boot - Enabled
Load OPROM - ALL

The system booted into the fog UI, deploy image, full registration… Since I’m going to Capture an Image I started with Full Registration. Things were seeming to work until it got to bzImage… % where it slowed to a crawl after some time it got to a 100% and then got stuck on init.xz.

I manually added the host to Fog and scheduled a Capture task. Same results, got stuck on bzimage and init.xz.

I removed the task, booted back into fog and selected “Client System Information Compatibility” and got the same results, hanging up again.

I’ve tired a dozen Official Published Kernels but have had no luck.

I’m running Fog Version 1.4.4

I’m trying to create an image of a windows 10 machine using Single-Disk-Resizable and I get the following.

Restoring MBR…Done
No Partition
and then it reboots and the task shows as finished

I’m able to use (Multiple Partition Image) to upload the image but it wont allow for easy re-sizing and it takes over 5 hours to upload the image.

@Wayne-Workman I can’t thank you enough. I forced the replication and my Scope Options are on both servers. I was able successfully access Fog 10 straight times.

We might be getting somewhere. I have the DHCP roll install on two of my Win 2012R2 VM with one being the primary and one being the replica. The Scope options do not replicate from the primary to the replica for some reason just the address leases.

The Computer in this picture is getting the same IP address each time and its pulling the correct bootfile. I only have 066 and 067 on our primary DHCP server which means it has to be using that server other wise I wouldn’t even get this far, correct?

@Wayne-Workman I just tried this and I got the same results. Four out of the seven times I tried it it worked. Here is the error I got.

I’ve been having the same problem for a long time now. When I use the default undionly.kpxe and boot off my NIC port 50% of the time I get this error. Could not start download: Operation not supported (http://ipxe.org/3c092003) PXE-M0F: Exiting PXE Rom.

I had been running Ubuntu 13.10 with Fog 1.2.0 and had been using a custom undionly.kpxe file I found online that worked a little better but it took over a minute to boot into the fog interface. I got frustrated with it and decided to start over and set up a new fog server. This time I installed ubuntu 14.04 with Fog 1.2.0 and I’m have the same issue.