Posts made by arduinoAndMore

@Wayne-Workman It’s saying “no installation candidate” I tried installing and configuring dhcp3 before, but this didn’t seem to work either. That’s when I decided to try a re-installation of FOG (which also didn’t do it). I do have an up-to-date installation of isc-dhcp-server according to apt. Apparently it’s not running or something. If I try to run sudo service isc-dhcp-server start It says “Job failed to start.” I’m going to go check my config.

@Wayne-Workman Ah…it’s saying “unrecognized service” I’m not sure why the service wouldn’t be installed/running. Installation of FOG went smoothly and I had the DHCP selected. That’s curious

@Wayne-Workman Thanks for your quick response. I tested those things you recommended and here’s what I found.

Iptables comes back with 0 packets 0 bytes on INPUT, FORWARD, and OUTPUT.

Cables are fine/tested.

Windows laptop isn’t receiving an IP.

Quick and simple (I hope) question on DHCP for FOG. I’m trying to set up a dedicated imaging network with a switch, imaging server, and clients. There is no existing DHCP (or anything else) attached to the imaging network. I’d like to use FOG as the DHCP server (which I did last year very easily) and I’m having trouble getting it to answer DHCP discover requests.

I’m not sure why it’s not working, so I thought I’d ask here and see if I’ve missed something simple.

Info: I’m using the most recent trunk version of FOG, Ubuntu 15 VM, static IP on FOG server, bridged connection to switch and physical client machine.

When I PXE boot the client, it searches for DHCP and nobody answers (confirmed in Wireshark). When I installed FOG, I told it to act as DHCP so I expected it to be fine. I’m not sure what to check next. It’s just not answering. If someone with more experience can help me I’d appreciate it!

Thanks!

SOLVED: Had to delete the /var/lib/dhcp/dhcpd.leases file. Started working again like a charm. Thanks again!

That would make sense. I assumed that FOG did not have very long lease periods. So if it doesn’t recycle IP’s, how do I clear the current leases?

I have a FOG 1.2.0 server running on Ubuntu 14.04.3. I have been imaging for a day and a half now, and I have completed around 200 successful images. I came in this morning and was getting ready for the first batch of 36 machines. All but four PXE booted properly, so I just tossed them into another pile and started without them. The 32 that were left finished just fine like all the others. I set up the next run, and now none of the clients are getting DHCP addresses from the server. I have restarted the server (virtual) and the host. I restarted the switch, and I have not changed any settings in FOG. It has just decided to stop working. I have restarted the server several times, and for some reason I can’t always access the web interface. This server was 100% functional yesterday so I have no idea what has happened to it overnight. I have at least 2-3 more runs to complete before the day is out, so any assistance is greatly valued. I’ll be sticking around the forum to be sure and see your reply promptly.

Thanks!

SOLVED: Switching to the multiple partition image type solved the problem. I’m deploying a 13.xGB image in around 20 minutes in batches of 36. It’s going just fine now. Thank you for all your help. Seems to be a good active forum

Thanks again!

@Wayne-Workman I deployed to a different machine with the same BIOS settings. My (new) suspicion is this: The image in question was a “single disk resizable” type, so I think (and gparted live cd confirms) that we aren’t cloning all of the partitions on the original disk. It might be rolling the old ones into one partition? It comes up with one large partition, and one partition that is about 100MB. In gparted there is a warning sign over the 100MB partition. I’m currently capturing a single disk multiple partition image that I hope will grab and restore all partitions correctly. Does this seem reasonable?
Thanks!

Update on the main topic: I finished a unicast deployment to one Lenovo, and I still get the disk read error nonsense. I’m trying another machine to rule out hardware (we are suspicious of that particular machine) but honestly I’m suspecting the image itself. So I guess we are back where the thread started Any continued help is greatly appreciated!

Thanks for the replies. I neglected to mention this is my first real deployment with FOG, so I’m still getting to know it. The reason I asked about this feature was because I wanted to make sure it was an error on my part during setup or configuration.

I was virtually unaware of the trunk version, (I’m new like I said) so that will definitely be a good thing to look at.

Thanks for your help!

@Wayne-Workman I never though about the fragmentation being the culprit. I was capturing that image from an old machine which probably hasn’t been de-fragmented lately. I should note that I took several uploads from that same machine, all with the same settings, but sometimes it took drastically longer. Oddly enough, my longest (and last) upload produced my fastest multicast sessions. A 2hr upload of a 4GB image (uncompressed) deployed in 3 minutes as opposed to 12 minutes with the 1hr upload. That’s actually not a bad deal if you’re doing a few batches Anyway, I’m going to guess that the fragmentation has something to do with it.

Thanks again!

I have a 36 node imaging network setup with FOG 1.2.0 running on Ubuntu 14.04.3 on VMWare Player. I need to image around 270 machines in the next two days.

My question is about starting a multicast session. All of my machines are registered via the csv file, but when I go grab a batch of 36 machines from the stack, I have no way of knowing which exact machines I have grabbed. I’m not excited about looking up each MAC manually. What I would like to do is set up a multicast session with image XYZ, PXE boot all the clients (all of which are registered already with image associations), then, when I’m done, come back to the server and click “Go”. To this point, I have only found where I can say “watch for these specific MAC’s, then when you see the last one come up, start multicast session”.

Perhaps I could add a menu option that joins a multicast session with the registered image (similar to “quick image”), then I could just go back to FOG server and set it off?

Is there any way of doing this deployment without digging up the MAC address for each one?

Thanks!

@Wayne-Workman I’m on a closed imaging network. The FOG server VM has been rebooted several times. The switch has been running <24 hrs. This morning I am capturing an image of Windows from the aforementioned Lenovo machine (30GB) and the time is looking like it will come in at around 1:10 or so. I guess that is about normal. I don’t know why sometimes it takes longer than others.

Thanks for your reply

Update: we are still preparing the base image for the Lenovo machines, so there isn’t anything new to report there. I touched on the Linux deployment I’m doing, so I’d like to expound on that a little more. I’m deploying a customized version of Lubuntu which boots to fullscreen Firefox 39 with some addins to lock it down. The distro is going on older Dell 2100 netbooks (Atom, 2GB) to be used for k-2 education websites. I have been through several deployments so far as I work the bugs out of the master image.

Issues I’ve had:

• Multicasting only likes to work reliably after running the following after a clean boot and clear task list.

mysql -u root <-p password> fog
truncate table multicastSessions;
truncate table multicastSessionsAssoc;
exit;

sudo service FOGMulticastManager stop
sudo killall udp-sender
sudo killall udp-sender
sudo killall udp-sender
sudo service FOGMulticastManager start

• Multicasting sometimes takes 3 minutes, but more recently that has jumped to 12 with the same size image.
• Capturing a 3.x GB image takes 1-2 hours, which it should not <— probably the most annoying thing.

I set up NIC bonding (mode 6) on my Ubuntu 14.04.3 server running FOG 1.2.0 but that doesn’t seem to do much. I’m not very read-up on bonding though so maybe that’s normal with multicast.

I hope someone can shed some light on these issues as well (don’t think it’s worth a separate thread). Thanks!

@Junkhacker Hi Junkhacker, thanks for your quick response.

1. Yes you’re right. That’s why I didn’t want to invest a lot of time trying it before asking here. The documentation of this error after using FOG isn’t documented in very many places

2. There was an issue with the existing MDT server that wasn’t letting the newer Lenovo BIOS PXE boot. We imaged the older Dell and tried to copy/paste the image. I think we are going to try to rebuild the image on a Lenovo. Lenovo tends to do interesting things with partition tables anyway, so hopefully going from Lenovo to Lenovo will be more workable. I intend to try using the resizable image unless someone has a reason to consider another option.

3. The 4 hour upload time is very odd. I can’t imagine what is causing it. Still open to thoughts. More info on that:

• Closed imaging network using VMWare Player for the Ubuntu server
• Gigabit NIC from my workstation to an HP 2650 gigabit 48 port switch, into a gigabit port on the client.
• No throttling or bandwidth limits are set on VMWare’s virtual adapter.

4. Yes. It went exactly as it does when it works (like on the Linux deployment)

Thanks again for any advice!

Hi all, I set up a FOG server (FOG 1.2.0, Ubuntu 14.04.3) And I’m preparing for a Windows deployment for almost 300 units. We have used MDT to lay a slightly outdated image on a Dell machine we had laying around. It was sysprep’d, and I uploaded its image to FOG this afternoon. For some reason it took 4 hours to capture a 27GB image (gigabit all the way), but it seemed to be successful. I deployed the image to one of the new Lenovo laptops (that’s what we will be imaging). The image deployed in 17 minutes (unicast) and it rebooted when done. When it came up it said “A disk read error occurred Press Ctrl+Alt+Del to restart”. This is problematic.

I found a post here (http://www.edugeek.net/forums/o-s-deployment/41560-nc10-imaging.html) where “ssx4life” suggests in a post from 2009 that FOG should capture the image using the multi-partition single disk mode rather than the single disk resizable mode I’ve been using. There is surprisingly little FOG-specific information on this error, and that’s about all I have to go on.

The plan was:

1. Image Dell machine with WDS (Lenovo machines are having trouble with PXE boot to the WDS for some reason)
2. Sysprep Dell
3. Capture image of Dell with FOG
4. Deploy image to Lenovo
5. Customize/update, sysprep.
6. Multicast deployment to the rest of the Lenovo machines.

Step 4 looks good until reboot. From what I can find there is something wrong with the disk or the partitions. I’m thankful for any advice you can give!

EDIT: Note I also use this server under the same configuration (and image type) to deploy Linux and it works correctly.