Posts made by george1421

I think I would still go down the live boot path. Just get ubuntu 15 desktop iso and burn it to CD. Then boot from the CD, there is an option to try it first (or something like that). I would be interested to know what a production kernel reports. But /dev/nvme0 would be a sane name for that hard drive.

ok then, I think we’ll need one of the @Developers to look into the code to see if it is honoring the “Host Primary Disk” field when launching the partclone.

@Arrowhead-IT I was just editing my previous post about using compatibility menu to get the info.

Now this is just me guessing out loud here (since I haven’t had this exact issue just yet). But if you look in the FOG GUI, and the host management details for this specific computer. Note there is a field called “Host Primary Disk”, it would be interesting to know if you entered /dev/nvme0n1 in that field, would it blow up (Err… work as intended)?

Interesting… the first thought is to get a live boot linux distro and see what the real device is called. I would still think it would be /dev/sda something since its still … maybe not using the sata interface (just reread your post).

I was also thinking the trunk build had a debug mode where you could boot to a command prompt to inspect the devices. I know the live boot will work.

[Edit] Ok, if you boot into the fog menu then check system compatibility. Once in system compatibility select partition information. If that shows up blank then we will have to go the live linux route [/Edit]

I checked and while the 1.2.0 stable release does have quick image it is only for registered hosts. The 1.2.0 stable version does not have the flexibility in managing the ipxe menu as the current pre1.3.0 release has so it will be a bit more difficult to accomplish.

I was able to “tweak” the ipxe boot menu in 1.2.0 to display the quick image option for unregistred systems, but I don’t know if that will break something else during image deployment because I had to bend the rules a bit for it to display. The other issue with running a “tweaked” version of the boot menu is there is no support from the dev team for this so the OP is on his own if it works or breaks something else.

In the end the OP would be better of living with short term instability in the pre 1.3.0 trunk release than “tweaking” the boot menu code. BUT, if the OP wants what the code that I updated I’ll post it here with no guaranty that it will work as intended.

Lets start with the basics

1. What version of fog are you using? (1.2.0 stable or an trunk version (pre1.3.0)
2. What OS is the FOG server running?
3. Lets just make sure we know the unit of measure. You are telling me Mb/s [mega bits] and not MB/s [mega bytes] right? (the reason why I ask is 1000Mb/s is 125MB/s so if you are seeing 100MB/s then is reasonable)
4. Is your FOG server a physical box or is it virtual?
5. Have you confirmed that the FOG server is connected via a GbE link? (I would assume so because each host is seeing 100mb/s according to your post)
6. If you are able to get multiple hosts to image at 100mb/s at the same time, then you don’t have a 100mb/s switch somewhere in the database.

To my knowledge there is no throttling for image creation, only for image replication to other storage nodes

OK let me build a new fog 1.2 server and see what we have to work with.

@Jbob So is this considered solved, since it is already part of 2.0?

@Robx64 Yes, I guess if all you have is a hammer, everything looks like a nail Windows will work for that, but it would be way cooler with linux.

So to translate the device ID is 14e4:167b which is different than what @Sebastian-Roth expected.

Is this an add in card or something built into the motherboard?

For a bit more details, that is listed as
BCM5755 NetXtreme Desktop/Mobile

on the broadcom page: https://www.broadcom.com/application/ethernet_nic.php

@mitzayapa Its been too long since I ran the 1.2.0 stable build, but when you pxe boot the client computer, quick image should be one of the options. There is nothing to enable as long as you have captured images in your inventory. If you don’t see it, I will spin up a 1.2.0 install to confirm.

Just to add some info to this thread.

If you don’t have a live linux distribution in mind, the Ubuntu 15 desktop version has a live boot option.

http://releases.ubuntu.com/15.04/

Once booted into the desktop use the search function to find terminal. That will open a console window for you.

I can see issues where IT installers are getting confused between the default admin console login of fog and the linux user fog used for back end services.

Recommendation: Either change the default gui login from fog/password to admin/password or change the back end account from fog to something like fogsvc or some other method as long as there is a distinction between the GUI login account and the back end service account.

@Robx64 Well shame on me I was looking at the intel IO controller model not the broadcom nic.

Can you include a screen shot (mobile phone picture is OK as long as we can read the errors). Because right now I’m not sure if the error is with ipxe or the boot kernel.

This sounds like a very new computer, so I might expect that the nic driver is not part of the ipxe build.

The one bit you left out of the info is are you using uefi or bios settings?

Moving back to unsolved, because there is still an issue. Button exists but only first time works.

@mitzayapa First I have to say, if you have a problem with release of a trunk version you should post it here. The debug cycle is very short with the fog project. Your issue could have been resolved since there are typically updates daily. The only way we can get to a stable very faster is to have people help with the debugging phase, then everyone wins.

As Tom noted below the all versions of the 1.x.x support quick image, so your 1.2.0 stable release supports it. What 1.2.0 doesn’t support will is uefi and gpt disk. If you need those and are unable to use the trunk build then you will have to wait until 1.3.0 is officially released.

I don’t know if they have released an official go-live date with a stable release. The developers have issued a new feature hold for the 1.3.0 release. The current (unstable but highly functional) trunk version is still in beta. I can tell you having more people test and use the trunk build will help us get to a stable release faster. I can tell you the (de)bug turnaround is typically very fast with the fog project.

I do suggest (if you have time in your project) that you give the pre-1.3.0 version a try. If you discover issues post them here.

@Pikmin You didn’t mention the FOG host system OS.

But my fog servers are behind proxy servers.

For fog itself there are proxy settings inside the FOG management gui that you need to set.

From the OS level you need to do a few things.

for rhel based systems you need to update bashrc and add the following to the very end.

export http_proxy=http://<proxy_server_ip>:<proxy_server_port>
export https_proxy=http://<proxy_server_ip>:<proxy_server_port>
export ftp_proxy=http://<proxy_server_ip>:<proxy_server_port>
export no_proxy="<fog_server_ip>"

You also need to enabled and update the proxy settings in /etc/wgetrc

If you are using subversion behind a proxy you will need to update the /etc/subversion/servers file with the proxy server settings.

If you log out and back in once these changes are made FOG will download correctly and install correctly, without a bunch of crazy command line switches every time you ugrade fog.

The key is getting wgetrc updated and then setting the environment variable to tell wget to not use the proxy for the FOG servers IP address.

Here are the examples on how to hack the old version of fog to produce a dynamic client host name (I can’t seem to find the actual instructions from long ago, but the code may spark an idea.)

http://www.ehu.eus/fogenehu/doc/old/html/hosts_8inventory_8include_8php_source.html
http://www.ehu.eus/fogenehu/doc/html/HostManagementPage_8class_8php_source.html

For clarity here the fragment of my fog post install script that was never put into production because of loosing functionality in fog.

  # need to find a way to get storage location set it manually for now
  sitecode="NYC";

  chassis=`dmidecode -s chassis-type`;
  chassis="${chassis%"${chassis##*[![:space:]]}"}";
  chassis="${chassis%,,}"; # Convert string to lower

  if [ "$chassis" = "laptop" ]
  then
    chtype="P";
  elif [ "$chassis" = "tablet" ]
  then
    chtype="T";
  else
    chtype="D";
  fi

  serialno=`dmidecode -s chassis-serial-number`;
  serialno="${serialno%"${serialno##*[![:space:]]}"}";  # Remove trailing whitespace

  # get the serial no from the baseboard if bios doesn't give it up
  if [ "$serialno" = "" ]
  then
    serialno=`dmidecode -s baseboard-serial-number`;
    serialno="${serialno%"${serialno##*[![:space:]]}"}";
  fi

  LEN=$(echo ${#serialno});
  if [ $LEN -gt 11 ]
  then
    # get the right most characters of the serial number (usually the most
    # unique characters)
    serialno=${serialno:(-11)};
  fi

  compname="$sitecode$chtype$serialno";

  echo Setting computer name to: $compname;

  sed -i -e "s#<ComputerName>\([^<][^<]*\)</ComputerName>#<ComputerName>$compname</ComputerName>#gi" /ntfs/Windows/System32/sysprep/Unattend.xml