@Wayne-Workman
The issue i was having with windows storage nodes is likely a permissions issue, but the first thing we tried was setting the permissions across the board to full control. Good luck figuring it out. It was so annoying, we swapped the storage node for a linux machine.

@Sebastian-Roth I never got it to work at all. I ended up swapping to a different solution.

Version: 6122 6128
bzImage Version: 4.4.0
bzImage32 Version: 4.4.0

Edit: Just updated to check. Still no go. Rebuilding that machine from scratch and i’ll take a new reference image i guess.

Alright, I’ve swapped out the VM to a full machine. Got it working on the latest GIT version, and found a rogue dhcp server causing issues. Now though, after taking an image of a reference machine, it gives me the error while trying to redeploy the same image to the same machine, Image Store Corrupt Unable to locate MBR.

The machine is a single disk resizable running windows 7. Any thoughts?

I’ve got three machines that I’ve been waiting to image. We need to put those in production and the work is already done creating the images for them. We just need to do a quick clone. I’m thinking it’s either the ftp commands or possibly the NTFS file system on the NFS share. To bypass the problem, i threw together a system and stashed it under my desk running CentOS 7 and with a decently sized hard drive. Now i’m running into another issue installing fog to the machine. It’s running trunk (svn) and it’s freezing at “Downloading inits, kernels, and the fog client”.

I did notice that the svn build was behind what i’m using on the other server. I did use the command to update the svn, and it said it was the same build. I’m going to try and download a fresh copy through git instead as that seems to be the most updated.

Alright, after a full debug capture, stepping through the steps, it shows no message related to FTP at all. I was thinking it was just too fast, but, it’s simply not there. It says Image Uploaded, restoring MBR, Resizing NTFS Volume, clearing ntfs flag, stopping fog status reporter.

Any suggestions on how I can make it report the error?

It’s moving too fast for me to see the error message. Would a copy of the FTP logs help (edited to remove security details of course)?

From this, it looks like it’s deleting the files, and directory and then quitting instead of moving the files.

Anyway, I won’t be back until monday. I’ll check any reply then.

I just got back to the office. I’m running it again now and i’ll know in a few minutes. Thanks for checking up.

standing by. I’m taking notes as I run into issues, so perhaps in the future, some other person might benefit from my roadblocks.

What command does fog use to move it? Also, Ctrl + C to drop out of the script, correct?