Cannot capture image: run lists overlap

[Tom Elliott]

@jheikkila54 Is 10.20.16.184 the proper fog server?

What’s in that server’s exports file? (/etc/exports)

[jheikkila54]

@Tom-Elliott Yes that is the correct IP address

[Tom Elliott]

@jheikkila54 Can you make sure nfs is running?

service nfs-kernel-server restart

OR

service rpcbind restart
service nfsd restart
service nfs restart

I know you’re running centos and all but i can’t remember what is what so just try the whole thing.

Also please check that firewall isn’t running.

[jheikkila54]

@Tom-Elliott Thank you Tom!!! RPCBIND was not running, I started that service and configured it to run at startup and is now working. Again, thank you very much for the help, it is greatly appreciated.

[rogalskij]

@Tom-Elliott said in Cannot capture image: run lists overlap:

nfs-kernel-server

I am getting this error in 1.5.10.41 after updating. I am running on CentOS 8. I restarted my NFS Server, but that didn’t seem to do anything. I noticed that the NFS “interfaces” were pointing to something other than my servers interfaces so i changed those to match what the server says is the network interface. Not sure if NFS interfaces are something different or they should match as well? Any assistance on how to troubleshoot this would be great as I have an image to capture and at this time can’t accomplish that.

[Tom Elliott]

@rogalskij So while the images were lost, the issue in this particular case seems more in line with the problem that was originally described (and fixed) with the check disk utilities.

Can you boot into windows and run check disk, scan disk/verify disk on this machine? I presume this is only happening for this particular machine and as such may just be related to it alone.

I know the chkdsk and scan and all that will take some time, but while we do have utilities that can perform these actions somewhat automated, it’s also not the ‘native’ tools and Windows would have a much better system for performing the checks than what our tools will.

[rogalskij]

@Tom-Elliott I believe you are correct. I ran a CHKDSK /F and it repaired the disk, but now I am faced with a new error. It claims “could not allocate new MFT record: No space left on device” and several other issues. Not sure where to go from here other than perhaps start a new Fresh Windows image?

[Tom Elliott]

@rogalskij This is very interesting as initially I thought this was on some code I wrote (not that it still couldn’t be) but appears more like maybe the percent of free disk space has been unset and your drive is literally sitting as full as if at the hotdog championships and Joey Chestnut just won for 75th time in a row.

There’s a field in fog that is supposed to ensure free space left on the disk, but where yours is failing seems to be due to paging space / minimum size.

I might suggest, if you’re up for it again

Chkdisk again a few times,

Also defragment the disk a few times. THis should move your paging file (which cannot be resized around) toward the end of hte disk which shoul’d prevent the no space left on device issue I believe you’re currently seeing.

[rogalskij]

@Tom-Elliott Was going to try, but discovered that after the last CHKDSK, the FOG Client wasn’t running correctly. Now I can’t uninstall or reinstall it correctly. I think for now I am going to re-create this image from scratch. I am speculating that since this was an older image that we had added onto several times, that a Windows update of some kind caused partition issues of some sort. I plan to format and install Windows from Scratch, and then build the image and pull it tomorrow. If this works I will report back with my findings.

In the meantime, are there any logs that I could send that would help you or anyone else who also finds themselves having this issue? Happy to assist in any way I can. I sincerely appreciate all the support and assistance on this.

[rogalskij]

Finally finished a brand new image this morning where we started from a fresh Windows install. The image captured without an issue. I suspect the age of our previous image was to blame for the issues with the capture. I think recent Windows updates by Microsoft to the recovery partition may have modified the size or something else in those recovery partitions.

New image pulled using the 6.6.34 Kernel, and then deployed successfully as well. If anyone is having issues related to the errors I posted above, I would try the CHKDSK + defrag/trim, and if that doesn’t work I recommend rebuilding your image from a clean Windows install with the absolute latest Windows enterprise installer.

Thank you Tom and crew for all the excellent technical assistance!