If I may interject with a very hypothetical statement. If you end up using the fog client portion of this solution on more than say a few hundred hosts, you may think about making the server a bit beefier. Here is my setup

For my 1500 hosts that check in with the client:

4 vcpu’s
8GB RAM
250GB storage (we use model specific images)

May be overkill but it works pretty well for me

@Sebastian-Roth So just out of a combination of desperation and curiosity, I tried a different computer with the same exact specs. Changing to AHCI worked. The original computer works fine except for this one FOG issue. I booted into Windows, ran chkdsk, installed a program, rebooted and everything worked like there wasn’t a problem. I reinstalled Windows with the Dell USB recovery disk and FOG was able to pull an AHCI mode image. Out of 15 computers, two had this issue. I think this is a fluke with Dell. Thanks for both your guys’ help.

@Sebastian-Roth Found a firmware update for the model and took a peek at it’s change log. Didn’t see anything relating to PXE in recent changes. Ran it anyway to bring it current. No changes in PXE boot behavior.

@george1421 Ran a capture job before I left Friday using the FOSLinux usb boot method. Checking the deploy sometime today.

As always, thanks for you help you two!

@tandersb the date is a nice to have feature and is not indicative of an issue. In particular the master node has a service that updates the sizes. To get the date, the image is updated once the capture task is completed. This, however, does not mean there is (or isn’t I suppose too) a problem with the image. Are you having issues using it?

And everything works!! Thank you for help!

@Zourous Sorry I should have asked this in the last round, does your fog server currently have multiple nic cards?

Dell switch, what model?

i figured out, i had to turn secure boot off!

Eric

@TBCS Mmmmmm cookies…

I’m glad you have it worked out and it was simple enough to just update your firmware (which you probably should have done anyways).

@Fernando-Gietz said in Dell Optiplex 7050 and UEFI boot. Failed:

I wonder if is a miracle that it has worked well until now in the other hardwares

I’m glad you have it working now. Yes its strange why you didn’t find another system with the same issues. But that is why I included both, I ran across a system that would boot with the netboot info alone.

@george1421 That was a really helpful guide. Easy to follow and now we’re ready for whatever type of boot we need.

@george1421 I’ve got two videos for you. The BIOS Firmware on the problematic one is newer than the one where it works. I’ll try a rollback and see if that makes a difference. Anyways…

This is for the remaining problematic 1040G3

Video 1: https://drive.google.com/open?id=1OEeLrkW2I8FIqLh092IHH03-zAhcM8X6
This is me using the USB Bootable Flash Drive

Video 2: https://drive.google.com/open?id=1Uz4cCiQf00VymXMKCqfiA7VK5-KKP3xl
PXE Booting without the USB Bootable Flash Drive

@JBrown-RCPD said in Panasonic Toughpad FZ-G1 Windows 10:

We have to disable UEFI, Secure Boot and select “Compatible” in Boot Mode to get the device to PXE boot to the FOG server however when continuing to boot to the hard drive it will not boot into Windows with UEFI still disabled.

Wow there is so much going on here.

why did you disable uefi? Is it because the device will not pxe boot in uefi mode? When the device is in uefi mode, what did you have configured for the boot file (in DHCP option 67)/ When the device is in uefi mode, you will need to disable secure boot that is a requirement since FOG doesn’t have signed boot kernels. If the target computer is in uefi mode, is your golden image also uefi? (fwiw you can’t deploy a bios captured image to a uefi based computer, or the other way around too. You can only deploy a uefi captured image to a uefi based computer. The same goes for bios based systems) Does the image deploy correctly, just the FOG is not setting the boot order correctly in the UEFI firmware, where if you manually pick the hard drive it boots correctly. What version of FOG are you using?

@omihek the information you’re giving is far too vague for an appropriate answer to be given. There’s any number of reasons that could cause this. Too many to give you a direct answer.

SSD is faster than spinner but as far as imaging faster or slower, it could be network congestion, memory issues, bad firmware, port too slow for the drive recommended speeds, and so on.

Once you have that FOS USB boot drive created I want you to do the following things BEFORE you attempt to image.

USB Boot from this FOS boot drive Pick option 6 (Debug) Watch to see if the FOS Linux boots correctly. If everything goes well, after a few enter key presses you should be dropped to a linux command prompt. At the FOS linux command prompt key in lsblk make sure you can see the disks. Please post a picture here in the forum of the disk layout. At the FOS linux command prompt key in ip addr show make sure eth0 has the proper IP address for your subnet.

If 5 and 6 pass then proceed to 7.

Schedule a capture/deployment task in the FOG Web ui. USB boot the target computer, this time pick option 1 in the grub menu.

The target computer should image just fine. Report any error back in this thread.

@UWPVIOLATOR said in Dell Precision 5530 Compatibility:

It does have Legacy Boot BUT NOT for Internal HD. Thus you must deploy a UEFI image to this model.

One additional comment on this point. It is possible with FOG to PXE boot in bios mode and with FOG deploy a UEFI image with a computer running in BIOS mode (I do this on systems where pxe booting in UEFI mode is broken, but pxe booting in BIOS mode works OK). Just be aware that you can not boot a UEFI image on a computer running in BIOS mode.

Yeah, too lessen confusion for myself, I called what you call “raw” a “super base” or “base”

Adjusting “base” for whatever I mean.

For example:

Superbase is the base image that ALL machines regardless of who or where the machine sits will start from.

XXXBase is a specific base based from the “superbase”.

Just my thoughts. No real value here!

@cool1107cm said in Maybe the USB cable is bad:

Hi @Quazz & @fry_p

How can I add kernel argument as below,
Would you please provide me more detail info?
Thank you so much

usbcore.old_scheme_first=1
has_usb_nic=1

Hi @cool1107cm ,
Much has changed in the way of Surface imaging for me. At the time of this post, I was able to image using these kernel arguments with a USB NIC on a Surface Pro 4 . However, as time passed, a number of other variables have come out of the woodwork to prevent the use of FOG on Surface Pro’s for me. I have reverted to manually installing Windows. I believe for a while I was working with @Sebastian-Roth and/or @george1421 on getting this to work. If you have a surface pro/ usb nic issue, I would highly recommend starting a new thread. Perhaps someone has come up with a solution since the time of this post.

Sorry I couldn’t be much more help. For the record, I used the Host Kernel Argument box on the host information page for the particular host on the web GUI and added these arguments in the order I specified separated by a single space.

@falko on first glance it looks like they use Intel branded NIC’s (both wired and wireless). Any ideas for which model you are going with? Full disclosure, I am US based an know very little about Stone.

@Sebastian-Roth We were able to resolve the issue. The machine has 5 NICs. The NIC we were actually using to network boot with was registered with FOG, but for some reason FOG was reading one of the other NICs during start. After registering all 5 MACs, fog worked successfully.

Re: the HP Elite X2, yes, 2 MACs on one ethernet adapter. Adapter is HP P/N: 829834-001. The second MAC only shows up when network booting - no other time.

@himem If you find this is the case; could you provide the hardware info an a clear screen shot of the setting changes to make it work taken with a mobile phone? If you have a problem, I’m sure someone else will in the near future.