@Fog_Newb Oh those are random, I thought you were talking about the /images/dev/{mac} that is used when capturing.
So /images and /images/dev are 2 nfs shares on your FOG server. You’ll see this defined in /etc/exports
If you aren’t able to manually move the file on the FOG server from /images/dev to /images then there’s some other weird permissions issue on the server.
When you are capturing an image though, the host boots to FOS, and part of the capture process is mounting the 2 NFS shares from the FOG server, /images and /images/dev. The capture process has partclone writing the captured image files to /images/dev/{mac}/*
Once complete, it moves them over to /images (technically it deletes the old version if any in /images and then moves the new version into its place).
I don’t recall if in the stable/dev branch if we are using sftp yet, so it may be doing ftp (1.6 for sure uses sftp). Point being it does technically remote into the server to do the move operation because the /images nfs share is a read only share.
When you have nfs shares mounted in the same folder that are actually on different disks, I’ve seen weirdness like you’re experiencing is what I’m saying.
So all of that is to say
Try moving/copying a file from /images/dev to /images on the server directly, confirm that works. Try booting into a debug capture session, capture the image (use the command fog and hit enter to step through. Capture any errors.Technically if you’ve captured the image, you can manually move it on the server to the /images/{imageName} folder and you should be able to deploy as a workaround while we figure this out.
You could also try installing 1.6-beta.