Cannot capture image: run lists overlap
- FOG Version: 1.4.2
- OS: CentOS 6.9
- Service Version:
- OS: Windows 10 Pro 1607
I recently updated FOG to 1.4.2 and it appears I cannot capture my image anymore and I have searched high and low for an answer with no success. The error I get is:
Could not mount /dev/sda2 (/bin/fog.upload->beginUpload)
Reason: Run lists overlap. Cannot merge: Numerical result out of range
@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.
@jheikkila54 Can you make sure nfs is running?
service nfs-kernel-server restart
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.
@Tom-Elliott Yes that is the correct IP address
@jheikkila54 Is 10.20.16.184 the proper fog server?
What’s in that server’s exports file? (
@Tom-Elliott Oh that it is, sorry I am multitasking excessively currently.
@jheikkila54 That’s a different error from the other pictures.
@Tom-Elliott It all flies by so it is a bit difficult to catch, looks to be failing at “Mounting File System” I am not quite sure how to run a debug.
@jheikkila54 So what is the spot it’s failing?
Can you run a debug?
@Tom-Elliott I have preformed a full checkdisk and returned 0 errors. I then created a new image to test, this image failed in the same spot with the same error.
@jheikkila54 Try to run a checkdisk on the system. While FOG Tries, the tools available are very very basic. It seems, to me, something is shifting around the partitions. There were issues with this in 1.3.5-RC-9 and a small portion through 1.3.5-RC-10. There was more work done in 1.4.0-RC-1 as well, but these have since been worked out. Maybe it was just left overs from older imaging layouts?
It may have been partclone, I deleted the image and created a new one as a troubleshooting step, it must have defaulted to “partimage” I did just try it with “partclone” with same results. I can boot into Window with no issue, what would you like me to do?
Is it possible there’s a problem with the disk?
It would appear, to me, you’re trying to capture the image. So “image manager” should be partclone, especially if this was captured in the past.
Can you boot the device into windows or even a windows recovery mode and have it run some tests?
I upgraded from 1.3.5-RC10
OS - Windows 10
Image Path - /images/Windows10x64_PRO
Image Type - Single Disk - Resizeable
Partition - Everything
Compression - 6
Image Manager - Partimage
I am not sure what you mean by “box model” but this is a virtual machine that has 1 disk. I have been using this VM to update my image for about 1.5 years now with 0 issues, until now.
- What version did you upgrade from? (please be specific, look in /home for clues)
- What image settings are you using?
- What model is the box?
- Anything special about the box or disk layout?