Posts made by mageta52

@Wayne-Workman I contacted the vendor today, and unfortunately I can’t make changes to the partitioning system.

@george1421 This is a product that we resell, that is CentOS based. I’m not sure if I even have the choice to configure the disk layout. I’ll have to check tomorrow when I build another one.

Server

• FOG Version: 7887
• OS: Fedora 23

Client

• Service Version:
• OS: CentOS 6

Description

I’m trying to capture an image from a CentOS 6 box, and the image is uploaded as a 240 GB raw image.

This is part of the output from fdisk -l

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 29186 234327040 8e Linux LVM
Partition 2 does not end on cylinder boundary.

I’m not really clear on what settings I should use to capture this image. I read that I can’t use single image resizable for LVM. I’m surprised I didn’t get any error messages. Is there a way I can capture this without it being raw?

@george1421I’ll run tcpdump on that interface tomorrow when I get in and see what happens during the PXE boot.

@george1421 Under boot options, it lists UEFI and legacy. All of the boot devices are set under legacy mode, including the NIC.

I just logged into the PFSense box and was set up for undionly.kpxe, I tried switching to undionly.kkpxe but got the same error. I’m assuming that the boot files under /tftpboot are the options available to me? There are a lot of them there, not sure if I should just start cycling through them, trying them all until one works?

1. PFSense is handling DHCP. I’ve been using this setup for a while now and it works great.
2. Yes I can image from other models. 90% of what we do is on an Asrock Z97E board.
3. Legacy mode. We’ve had issues with images not restoring properly if the install was done in UEFI.

How do I change the boot file? It seems like I’ve had to do this in the past but can’t remember what needs to be edited, or where the config file is.

Server

• FOG Version: 1.2.0 7887
• OS: Fedora 23

Client

• Service Version: Intel NUC Kit NUC6i7KYK
• OS: CentOS 7

Description

I just configured a system on a Skull Canyon NUC, and wanted to create an image. I tried PXE booting to my FOG server and received “PXE-EC8: !PXE structure was not found in UNDI driver code segment”

It then exits and boots to the hard drive. This happens instantly, and I had to take a picture of the screen to even read the error message.

I looked up the error, but the description didn’t really help me understand where to look, or what the solution might be. Any help would be appreciated.

@Wayne-Workman The problem has been solved. Thanks.

I did not see that there was a dedicated tasks section. I’m still learning to find my way around the web GUI. The issue has been resolved, thank you!

I accidentally went in and created a deploy task for a host, when I really wanted to create a capture task. Now it tells me that the host already has a task and I can’t create the capture task. I go into the host and there is a delete button, it asks if I want to delete the host but I don’t want to do this, I just want to get rid of the deployment task. If I delete the host will it go and get rid of the data that was created during the full host registration process? I don’t see an option to get rid of just the task.

@Wayne-Workman I will keep this in mind for the future. Will I have to use the raw option?

I am attempting to capture an image from a Gigabyte Brix unit that has CentOS 7 installed. This is the setup I tried using

When I booted up the Brix to start the process it errored out with “No resizable partitions found”. I’ve seen this before on other boxes, but don’t know what it means or how it is fixed. To be honest, I have no idea what the various options for image type mean in the FOG web GUI, I’ve just read that “resizable” is the best option.

@george1421 Alright, so here’s what I’m going to do.

I’ve got an old PFsense box that I set up to handle DHCP, and it can hand the clients off to FOG. This will happen on a separate subnet on the FOG servers second NIC. I’ll still be hooked up to the core network via the first NIC for easy access and management to the box.

This way I can have my unmanaged switch, and be open to multicasting.

Now that it is an option, it kind of goes back to my original question; if I’m going to image via multicast, my understanding is that it takes some setup, with making the group and registering hosts. I won’t be able to use quick image for this will I?

@george1421 The situation is a bit odd.

Originally I wanted an isolated network, with FOG dishing out DHCP addresses. This did not work out, no matter what, the DHCP service would not hand out an address to more than one host. There was a pretty lengthy thread on this, and eventually the consensus was to just turn it off and leverage the existing DHCP server on our network, and configure it to point to FOG for any client looking for PXE boot.

In our lab, we have some really small 4 port switches, that go back to the core switch for connectivity. What I planned to do was stack all the 1RU boxes on a lab table, introduce a 24 port unmanaged switch to connect them all, then connect that up to the core switch. They’ll all be able to get addresses off of the existing Windows server, and that will point them to FOG to PXE boot. Then I can image them from there. The problem is that if I multicast, that traffic will reach the core switch, and the other engineers have said this absolutely cannot happen. I’ve been told it will hose up the phone system and bring traffic to a crawl. We don’t have QoS set up for VoIP traffic, and that core switch is not set up for IGMP snooping.

I’m not sure what the best option here if the FOG server is truly incapable of reliably handling DHCP, otherwise the solution would be an isolated network with the unmanaged switch.

That makes sense. We won’t be using any of the management features.

Unfortunately multicast is not an option on the network. I will have to use unicast. This should still be much faster than our old method of doing clonezilla + external hard drive on each box, one at a time. I’ve been told in the past that there’s usually a tipping point where it really starts to get slow, over the network with unicast. My understanding is that you can limit the number of hosts that can be imaged at once, and then any additional units will be queued up and start imaging once one finishes. Is this correct? What I’d probably do is set up a flat 24 port switch and set the limit and fill the switch and let it go to town.

I had been told several months ago that we will be getting a large volume of machines in that will need to be imaged. I built a FOG server in preparation for this, unfortunately it’s been sitting idle for a long time. The most I’ve done with it is backed up a few machines, and imaged just one at a time.

What is the difference between going through the host registration process, and simply doing “quick image” from the PXE menu? It seems that doing a full registration, going into the gui and associating an image and OS with the host, setting up the task ect, takes a lot longer than just booting and quick imaging, especially if it’s a large number of machines.