Posts made by pugnacious

@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?

Well, it failed to work yet again. Is there anything I can check to find out what’s not working? I’m trying a debug capture now.

If i connect to the FTP server, type the command to change directory to the root, it defaults to inside the images folder. Should it be one directory up?

Yes, I verified all the credentials just in case. The only thing I could think of was perhaps a space in the storage node name or the lack of a trailing slash on the path. I just recreated the node and re-verified everything in the config just to check. I’ll know in about 4 minutes. The good thing about using the node on the company NFS server is that the upload speed is about 4 GB/min which is amazing. Now if I can just get the image to go the other direction.

That was the first thing i checked. The FTP is working on the storage node server. I can connect and create/delete/download/move files.

Well, the fog server accepts the node now, however it doesn’t move the images from the dev folder, and I can’t deploy the image to another machine. I’m obviously missing something.

I’ve tossed that info to our network engineer, and he seems to understand it. He’s going to add the network NFS share as the primary storage node once he can make it work as a secondary node. Do you have a link to where I should have him look for more information? I know some of the wiki is outdated when it comes to the trunk build.

in that case, i’m not sure how to help you best. perhaps someone else could. the file is in the trunk builds.

What operating system are you using for the fog server? I have a guide I wrote for installation of trunk on Centos 7 for my personal use. I could publish it for you.

Perhaps some of you enlightened individuals can shed some light on this subject. I’m currently running fog (trunk) on a centos 7 vm running under a vmware hypervisor. The company I work for will be setting up a very large hypervisor in the next month and we plan on moving the fog server to it once it’s active. we are a primarily windows based organization and most of our servers are windows. Our network engineer mapped an NFS share from our storage node and mounted it under the fog server. He mounted it in place of /images on the fog server. To the fog server’s view, the /images folder is identical. Now however we are getting an inability to mount the NFS share from the clients being imaged. I suspect it’s a permissions issue of some kind. The mounted NFS share is NTFS formatted. If one of you has any insight, I’d be happy to provide specific logs or details.

I had the same issue using 1.2.0. The best thing to do would be to update to trunk. I was having issues with pxe booting on uefi devices until i did that. I originally updated the kernel to the trunk version, but it’s much easier to update the whole thing from the start.