@Sebastian-Roth @Wayne-Workman @ITSolutions I’m running Ubuntu Server 14.04 with Fog Trunk (7669). The image that i’m using was built for fog 0.32 as a Multi-Partition Single Disk Type. When I transferred that image to my current Fog server, I did it by capturing it and uploading it directly to my new fog server rather than just trying to import the file from the old fog server.

Currently the image type is set as Multi-Partition All Disk and its format is set by default as partclone. The Multi-Partition Single Disk Type failed on capture during the sda3 upload part and the Single Disk Type failed right off the bat if I remember correctly.

Belong is everything you guys requested that I knew how to get. Either I’m not looking in the right place or I just don’t have some of those files. I can’t find anything that says original and only the d1.partition file has anything readable using cat. The d1.mbr and others are just a gobbled mess of random text and symbols.

I’m able to capture and deploy images fine however just recently I’ve noticed that the second partition (sda2) on the image appears to have shrink and the extra space that should be apart of that partition has become unallocated space. The image i’m deploying has 3 partitions, one for the OS/boot, one for regular storage data, and a backup/recovery. Both the Boot and Backup are exactly the size they’re suppose to be but the storage/data drive which should be around 12BG has loss about 10GB and that loss 10GB just sits out there in no where land.

If I run the backup/recovery partition, when it’s done re-imaging this problem doesn’t occur. It appears exactly as it should be. The issue only happens on a fresh deployment. I’m unsure if its the image or a setting in fog i need to change.

@george1421 UPDATE: I followed your instructions and I got my system to work exactly how I wanted it too. I really appreciate the help. Thanks again.

Unfortunately I ran into a small hiccup during the deployment process. You’ll see the post soon once I get the photo uploaded haha.

@george1421 Thanks for the guide. I’ll work through this and get back to you if things go well or if i run into any problems. I should of followed the set up like this when i started because the current fog .32 i’m using is set up like that. The management side has a 192.x.x.x and the fog deployment has something like 10.x.x.x

Again I really appreciate the help. Thanks!

@george1421 I read around and some people said different subnets and/or same subnets and I couldn’t figure it out (My networking knowledge is pretty eh…).

So I should keep my fog server as is with the 192.168.224.82 and change my management one to something like 192.168.223.xxx OR vice versa and keep my management one and change my fog server? Do I have that right or am I even further off?

@george1421 Alright so I hashed out the gateway option for the fog server interface (eth1) and rebooted the computer.

I then ran the ip route command and got this…

Again eth0 is my fog deployment which I set statically as 192.168.224.82 and eth1 is my internet I got as 192.168.224.24

@george1421 No problem. I appreciate the help. and I apologize if i’m confusing you.

eth0 is suppose to be the fog deployment only while the eth1 is connected straight to the internet.

The set up you described is exactly how i’m trying to set it up. The deployment lan should be completely separate and isolated, no need for internet access. And the management lan connected to the internet for just regular daily task.

@george1421 the 192.168.224.1 is the address of my default gateway. I"ll remove that from the fog interface and reboot. Am I also removing the dns-nameserver from that entry as well?

As for the management nic, I’ll just try to manually bring down that interface and start over there. I don’t understand it either. I thought if its hashed out in the configuration file, it would automatically be brought down and wouldn’t be pulling an IP address from my local dhcp. But it randomly got an IP address and I can still get internet.

@george1421 eth0 is my deployment interface and eth1 is my internet side interface. That exact configuration you see in my OP is exactly what I have set as currently. Even though my eth1 is hashed out in my configuration file, it still works. If i do a “ip addr” , it shows that its up and running. And I get internet, very slow though.

I do have a gateway defined for my eth0 which is my deployment LAN. I’m pretty sure i was suppose to leave that out or set it to "gateway 0.0.0.0 " I was unsure.

And the 192.168.224.82 is the IP address assigned to my deployment LAN. The other one is the management LAN that DHCP gave me that originally I change to a static address.

@george1421 UPDATE: I honestly can’t explain it myself but I responded to your post and went home. I came back today and by some miracle everything kind of works now. The Fog facing nic can pxe boot, capture images, and deploy them. And the management side nic gets internet, even though there’s a few hiccups with speed, it works.

Even though it works I know something isn’t set right. The internet goes in and out and when it does work, its super slow. I have both nics connected. One to a switch for imaging and one to the internet. The problem is I can’t ping the router. I also can’t ping websites by name. I can ping websites by IP address but I lose roughly half the packets sent/received. DHCP gave me a random IP for the internet side nic however I haven’t even added or edited the /etc/network/interfaces to include that specific interface. In my first post is the exact configuration settings I set up in my /etc/network/interfaces file.

@george1421 That sounds like a good idea, thanks. I did however just spend the past few hours finally getting fog trunk to correctly capture an image haha. So i’m a little hesitant to remove fog completely and re-install everything. I did also have an issue when I did have fog trunk up, removed fog completely, and when I tried to reinstall fog 1.2 I got some apache2 error that I couldn’t fix.

But if no other option is feasible i’ll bite the bullet. Thanks again for the tip.

@Wayne-Workman When you say the imaging NIC, to clarify you’re talking about the nic facing the switch to be used for deploying/capturing images as well as the fog server ip address I statically gave it? If that’s what you’re saying then both of those appear to be set correctly.
I gave my fog server an address of 192.168.224.82 and the interface is eth0.

And when I re-run the installer am I making any changes or just making sure the interface name and ip address match up.

It would also help to tell you that originally i didn’t bother with the second nic when installing fog. I used the same nic for getting internet as well as installing the fog server. So now i’m just trying to separate them.

I have a computer with Ubuntu Server 14.04 and Fog trunk installed on there. I need one nic to connect to the internet just for maintenance and the other nic will be connected to a switch used solely for capturing and deploying images and no internet access. I’m running into problems where if I have both connected, I get internet but can’t pxe boot any host. If I disconnect the internet cable, i can pxe boot but no internet.

To my knowledge I’m suppose to set up the internet facing side with DHCP and the local fog network with a static address. This is my set up below. eth0 is my fog side and eth1 is my internet side.

I’ve tried setting the internet side with both dhcp and with a static address but maybe i’m doing it wrong. Any help would be appreciated.

@Sebastian-Roth I have fully functioning .32 Fog server with images saved on them. I deployed one of these images from the .32 fog onto a host computer. Separately I had set up a 1.2 Fog server and using the same host computer I uploaded the image to the new fog server.

I think my issue might be this partclone vs partimage thing. I got impatient and upgrading to TRUNK, hoping that would solve some issues but now I can’t even capture an image. I’ll start a new post and detail out my new set up. Thanks again.

So i’m still having issues deploying an image to a host. I’m running Fog 1.2 with Ubuntu Server 14.04

I was originally running Fog .32 and upgraded to Fog 1.2. I uploaded an image from a host to my new fog server using an image from fog .32 and made the changes to allow me the option of setting the image type to partclone or partimage. I set the image type to partimage and every time I try and deploy the image i get the following errors.

Also if I change the image type to partclone, the image will deploy and I see the status bars ,but when it finishes I get an error that says “This is not parclone image”

I made sure the image name matches whats in the web GUI and whats in the /images directory.

And If I try and manually type in the path like the error suggest. It won’t let me hit OK or Cancel to continue.

@Wayne-Workman Stupid question but how do I check that? I’m new to linux and this is my first fog server build. I’m been using fog .32 that someone else built for me. The source image is a mult-partition Windows 7 image being deployed onto a 64 GB msata.

@Quazz I do get an MBR error 1 message upon restarting.

@Wayne-Workman After the stripped down fog grub menu and I restart the computer, if I try and boot straight from the hard drive I get an MBR error 1 message.

Here’s the output you requested.

I’m deploying a windows 7 embedded image on a custom built computer. Its got an MSI board, AMD Processor, 4GB Ram, and a 64GB SSD.

So I just setup the fog server and am able to pxe boot and register a host/client computer. I then was able to upload my first image and store it on the fog server. My problem now is that after I register a host, start the job to deploy the image, the host computer fails to image properly.

The host computer gets to the partclone page and I can see it uploading. It gets to 100% and then it brings me to a stripped down fog grub menu. If I hit boot from hard disk nothing happens. And if restart the computer it just pxe boots again because there’s no OS installed on it to boot from.

For the image i’m deploying, I’ve tried setting the type to both single partition and multiple partition image -Single Disk. The image is also a windows embedded image.

I’m using Ubuntu 14 server with Fog 1.2

Any help would be greatly appreciated.