Posts made by lukebarone

@Tom-Elliott said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":

@lukebarone has the keyboard on the laptop worked in the past with registering a host? What kind of keyboard is it? Does it detach or just isn’t recognizes? If you’re doing a tasking and unable to use the keyboard, this is normal.

Hi Tom,

It’s the built-in keyboard on the laptop of the Dell e3350. Plug in a USB keyboard, and it works fine. I’m thinking that Dell is just doing weird things to get everyone on to Windows 10 and their custom installs of it. The keyboard works in the menu, and logging in to FOG’s PXE boot menu. Once I select a task (i.e. Full Host Registration), it stops working. Plug in the keyboard, and I can type in the hostname and other options.

@Wayne-Workman said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":

That’s likely kernel related.

While only semi related - how can I find a kernel that works with all my hardware? Is experimentation my only way?

This issue has been fixed!

Upgrading from RC-8 to RC-9 to RC-10, somewhere in there, it started putting files in /var/www/html/fog instead of /var/www/fog like the rest of the installation. After switching the TFPTBOOT directory to /var/www/html/fog/service/ipxe, and downloading the 4.1.0 kernel, these Dell e3350’s would boot to the Deploy job. Next up, figuring out why the keyboard won’t work and I need to plug a USB one in.

Thanks for the help though, it was quite helpful.

@Tom-Elliott said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":

I wonder if you add ip=dhcp to the global kernel arts

No change. Same error message. I added that line to one host, as I don’t know where to apply it to every host.

@Sebastian-Roth So I also just tried the new version from Git (1.3.0 RC-10), and the Dell 3350’s will register OK, but I get the same error message during the image deployment. It boots to the network, downloads the bzImage and init.xz, then the same data as posted earlier. These laptops are using a Realtek driver, but I could NetBoot them and register.

@Sebastian-Roth said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":

Are you able to boot into a linux live CD and have ethernet setup properly???

Yes, I can use the NetInst ISO for Debian Jessie (8.1), and ping my machines and download web pages. Hope that helps!

@Tom-Elliott No, I could only get it to work by Quick Registering first. If I choose Full, then I get the issue shown above in the question.
After choosing Quick, I log in to the Web UI, rename the system, assign an image and tell it to join AD. Then, I can deploy the image on the next boot.

Server

• Version: 1.3.0-RC-9 (SVN Revision: 5952)
• OS: Debian Jessie x64

Client

• Version: 0.11.5
• OS: Windows 7 x64

Description

Reboot host on hostname changes and AD changes even if users are logged in? option does not remain checked when I click it. Tried changing in IE 11, Firefox and Chrome. Log file states that it cannot change names since someone is logged in. I go to the host in the Web UI, Active Directory, tick the box and click Update. A tooltip shows that settings have been saved, but the tick box is unchecked.

@Sebastian-Roth said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":

Or boot windows, go to driver manager and find out the PCI IDs there. Otherwise it’s just a lot of useless research and guesswork to find out what NIC is build into your devices.

Vendor 14E4, Device ID 1681.

@Tom-Elliott said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":

I’m now thinking the primary issue with DHCP is because of firmware. I’m guessing the tg3 fw is not available on first boot until after the error message displays. So the system doesn’t have a mapping capability to look for the nic. On a warm boot however, it’s already been uploaded to the nic. So the system can now map it as expected, which might explain why quick reg worked.
Can you remove the host from fog and let it boot into wibdows and shutdown to see if a cold boot->quick reg still works or gives the same error?

The host was never registered, and the hard drives switched out with SSDs. I’ve even tried with removing the battery and AC adapter for 5 minutes, and trying it again. Quick Reg works, Full Reg does not.

@george1421 said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":

@lukebarone it would be interesting if you manually register one of these 2 computers and then schedule a debug deploy. That should drop you to a command prompt on the target computer. From there we should run a few commands to inspect the hardware.
I’m working under the assumption this is not a spanning tree issue since you imaged the same model on the same network port.

I’m assuming it’s not an STP issue either, as that is disabled on my switches. I’ll try a debug task, but I assume I need to register the host first, right?

@george1421 @Developers

Failed to find cpu0 device node
tg3 0000:0a:00.0: Cannot map device to registers, aborting
i801_smbus 0000:00:1f.3: SMBus base address uninitialized, upgrade BIOS
/testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
/testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
/testcase-data/phandle-tests/consumer-a: could not find phandle
/testcase-data/phandle-tests/consumer-a: could not find phandle
/testcase-data/phandle-tests/consumer-a: arguments longer than property
/testcase-data/phandle-tests/consumer-a: arguments longer than property
overlay_is_topmost: #5 clashes #6 @/testcase-data/overlay-node/test-bus/test-unittest8
overlay_removal_is_ok: overlay #5 is not topmost
of_overlay_destroy: removal check failed for overlay #5
Starting logging: OK
Initializing random number generator... done.
Failed to get an IP via DHCP! Tried on interfaces(s):
Please check your network setup and try again!

Server

• Version: 1.3.0-RC-9 (SVN Revision: 5952)
• OS: Debian Jessie x64

Description

Doing a “Quick Host Registration” via PXE boot, I then log in to the WebGUI, and rename the system and choose an image. I then Apply the changes, and go to Basic Tasks-> Deploy. I click the button to start, and the following error message in red appears:

Failed to create tasking to some or all

COMPUTER_NAME Failed to start tasking type Deploy
No snapins associated with this host

The computer will still start, and seems to be deploying an image (hopefully, the correct one).

@george1421 Yes, the BIOS version is still A01. Trying to do the Quick Host Registration works… Weird!

At least we know where the issue lies now…

Server

• Version: 1.3.0-RC-9 (SVN Revision: 5952)
• OS: Debian Jessie x64

Description

When trying to PXE boot on some more Dell Latitude 5520s, I can open the FOG menu, but when I choose “Full host registration”, I get a bunch of lines about /testcase-data/phandle-tests/consumer-a: could not <extra info>, followed by:

Failed to get an IP via DHCP! Tried on interfaces(s): #<-- grammar is wrong!
Please check your network setup and try again!
Press enter to continue

I imaged 2 laptops this morning (same model, same switch, same ethernet cords) successfully with FOG. I have just tried another two, but both are showing this error message. If I reboot, I can select Client System Information (Compatibility), and the menu comes up for Reboot, Network Information, Partition Information, Check FOG Compatibility, etc. Choosing the FOG Compatibility option shows that the computer is compatible with FOG.

On the server, I do not see any log files relating to this issue. The DHCP server is hosted on another Debian Jessie x64 server, but has worked for many many years, and still offers a DHCP lease so that the computer can see the FOG menu. I have tried adding a dumb switch in between the network and the computers I am trying, but it is not making a difference. I have tried adding Kernel 4.7.1 for both 32- and 64-bit through FOG, but no change.

These machines I am trying to work on have NOT yet been registered in FOG. The first two I did this morning worked great. What can I look at next?

@Sebastian-Roth I will do that on all the Dell computers we have, and post the output (sorry, working on School Startup, and dealing with the teacher laptops right now). Can I somehow use FOG to boot to a shell and run those commands? Or do I need to boot up Debian and run it from the Live environment?

Hi team,

I’d like to request that during the capture process, FOG looks at the BIOS/UEFI setting to see if the hard drive is set to IDE (legacy) mode or AHCI mode. Saving this with the image can help prevent boot up problems if the option gets changed.

@Wayne-Workman said in Setup is preparing your computer for first use after imaging:

You should read this:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

Also, sounds like you need to update the fog server too. 7981 is behind, we already have release candidates.

I’m going to bet this is the solution… I’m rebuilding the image now, and will disable the service (I never saw that Wiki page before - lots of good info). I also just updated to the Release Candidate (using Git), so hopefully that combination works.

Server

• Version: 7981
• OS: Debian Jessie

Client

• Version: SP1
• OS: Windows 7 x64 SP1

Description

I’m trying to image some Dell laptops with Windows 7 and the new FOG client (from Trunk, downloaded from my FOG server). I went through all the steps I usually do, including SysPrep with Copy Profile set. I capture the image, and when the computer reboots, Windows brings up an error message reading:

The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click “OK” to restart the computer, and then restart the installation.

I used to be able to just restart in Safe Mode and back to Normal mode, but that’s not working anymore either. What should I look for as to finding out the reason this is happening?

This worked great! The Wiki for installing Mono should be updated for Debian Jessie, as apt-get does not work for installing Mono. I had to resort to the instructions on this page:

apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono-project.com/repo/debian wheezy main" | tee /etc/apt/sources.list.d/mono-xamarin.list
echo "deb http://download.mono-project.com/repo/debian wheezy-apache24-compat main" | tee -a /etc/apt/sources.list.d/mono-xamarin.list
echo "deb http://download.mono-project.com/repo/debian wheezy-libjpeg62-compat main" | tee -a /etc/apt/sources.list.d/mono-xamarin.list
apt-get update
apt-get install mono-complete

Hi everyone,

I’m being tasked with installing Debian Linux on some old Windows XP netbooks to hand out to students (since we don’t have the extra licenses for Windows 7, nor the money to upgrade them all). We have FOG Trunk installed and working for the Windows 7 systems on our network.

What needs to be done for Linux to get captured then deployed to multiple systems (of mostly the same model)? Do I need to do anything at all? Does the Hostname Changer work automatically? I assume I need to follow these instructions (but changing the partition numbers) to get it to boot, but is there any other configs I need to do?