This decidedly simple request has turned into a big PITA. I was able to boot the system with puppylinux but I think what I have on my flash drive is the 32 bit version. I’m downloading the 64 bit version to try to boot via cd in efi mode. Here is what I extracted from puppy linux in 32 bit mode with lspci -v
0_1448303778683_dell_7010b.txt
FWIW: The centos 7 rescue DVD (and centos 7) no longer uses lspci but pciutils (which is not available in rescue mode).
@Sebastian-Roth I have was able to capture the screen and uploaded it here (since this is the first time I tried this process, the relevant information is about 50% of the way through the video. And the video is quite large because of the cruddy codec I used. As they say better next time:
https://www.dropbox.com/s/7t22wb4354njp56/1448293078345_ipxe_efi.avi?dl=0
One thing I noticed is your description 0_1448292948783_ipxe.efi did not match the downloaded file 1448293078345-ipxe.efi.
[Edit] FWIW this video doesn’t play well in VLC but it does in WIndows Media player. Sorry [/Edit]
A18 will work as long as you turn off the legacy ROMS. I did see that post too, btw. I just had to try it and it worked with the same results as you. So no better or worse then.
Well this is either good or bad. I get the same results as Wayne using 7010 bios A18.
Not sure if this has any bering on anything. But I checked into the dhcp discover and the 7010s are sending out arch type 7. I noticed that there are two different arch types. One is 7 and one is 9. There is also a arch 6 for 32bit. I guess the question I have is what is the efi boot kernel that is being built?
Type Architecture Name
---- -----------------
0 Intel x86PC (BIOS pre-OS environment)
1 NEC/PC98
2 EFI Itanium
3 DEC Alpha
4 Arc x86
5 Intel Lean Client
6 EFI IA32 (UEFI 32 pre-OS environment)
7 EFI BC (UEFI 64 pre-OS environment)
8 EFI Xscale
9 EFI x86-64 (UEFI 64 pre-OS environment)
@jbsclm interesting, I’ll have to give it a spin on Monday. The discussion with my colleague was about finding a way to uefi boot systems that have a broken net boot under uefi. This may be adapted to help with that issue too.
This one may actually work a bit better since it should connect you right to the FOG menu
set fogserver:ipv4 <ip_addr_fog_server>
set next-server ${fogserver}
chain http://${fogserver}/fog/service/ipxe/boot.php?mac=${net0/mac}
Funny I was just discussing this the other day with a colleague. I haven’t had a chance to put together a POC yet on this. But the general idea is to create the ipxe boot image on the usb device and then chain to the fog server using the command like Sebastian posted. On your USB boot stick you want to enter something like this: (Understand this just came out of my head, and may be filled with bugs).
set fogserver:ipv4 <ip_addr_fog_server>
set next-server ${fogserver}
chain tftp://${fogserver}/undionly.kxpe
That “should” tell the ipxe client using the boot media to chain to the fog server. Then the fog server will take over from there.
@need2 said:
I’m late to the party, but no I never got WDS and FOG to play well together.
@FlowLive was just able to do this. Its a bit down in the thread, but he has FOG acting as the PXE boot server then you can select the WDS environment from the FOG Menu.
I went the other way around and setup FOG to be able to boot the MDT litetouch image so that you can deploy through MDT from the FOG boot menu. Two different ways to have FOG and MDT/WDS coexist.
The normal PXE boot sequence is that it waits for the dhcp server to provide the dhcp IP address and then requests the dhcp option values of 66 (boot server IP) and 67 (boot file). For option 66 you should enter the IP address of your FOG server (not the conical name) and for 67 you should enter undionly.kpxe. Those settings will tell teh client what to do next. If you see some messages about iPXE then you have connected to the FOG server.
Lets start out by getting some background information.
I see you are running Ubuntu 14.04. What version of FOG are you running are you running the stable 1.2.0 or the SVN trunk release (pre 1.3.0)? If you are running the trunk release what is the number in the cloud (upper left corner or page) on the management console?
Now that is out of the way. Have you ever setup PXE booting before (FOG or something else)?
What did values did you set for DHCP option 66 and 67?
Here is a step by step for rhel 6 distros
https://forums.fogproject.org/topic/6074/extending-a-file-system-on-redhat-base-distros
I can’t help you with the fogstorage node issue, but I can with the space issue.
Actuality what I’m going to recommend will sound counter intuitive, but its the right move. Traditionally with *nix systems you place the /home and /opt directories on their own partitions/disks. These two partitions could potentially grow out of control filling up the root partitions ( / ) basically killing the *nix systems.
What I’m going to recommend is that you do the following.
You may need to check the file permissions before you start and after you’re done to make sure things are sane. But IMO this is a better setup than placing both the /images and /opt/fog/snapins on the root partition. In this setup the /opt directory (vmdk) can go to 100% and it won’t take down the OS.
But if you want to extend your current VMDK I did a write up a bit ago on how to do this with rhel 6 based system.
I guess a question that is still not clear to me is when you ran the install.sh on the current trunk, the installer “should” download the latest client. Did that step complete as expected? Or was there an error saying that needed to manually down it?
IF your fog server sits behind a proxy server you need to update wget (what the installer uses to get the msi) with your proxy server settings.
[Edit] Well if you followed Wayne’s instructions and it worked, then something in the installer or svn trunk is broken. The wget in Wayne’s instructions should have thrown an error if there was a proxy issue [/Edit]
I’m going to guess that its not possible to change the display order. There is no concept of display order in the database so I assume the display order is being set based on the record ID where boot from the hard drive is record ID 1. I would not recommend messing with any record ID to alter the display order.
You will receive much bad karma if you do go ahead with this plan.
@FlowLive said:
Now I read that it’s not possible to change the menu order of things, WDS being all the way down, can’t I just bump it up a little?
Where it should be, way at the bottom. Where do you think the competition would put it, front and center?? 
I’m glad/happy you got that wds thing fixed out. From what I’ve read those forward / backslashes are a PITA to get worked out. It looks like you got the right combination to get it done.
Looking and the chain load link that you sent. I did see this reference
set netX/next-server ip.of.wds.server
imgexec tftp://${netX/next-server}/boot/x86/wdsnbp.com
What I think I might have missed is in my guess is setting the network adapter 0:
set wdsserver:ipv4 192.168.1.88
set net0/next-server ${wdsserver}
Its interesting that the chain does work (kind of) that it does gram the wdsnnp.com file, but there is something in the referral that its missing to continue.
FWIW: All of the 7010 SFF Dells we have have “Intel
82579LM Gigabit Network Connection” according to our inventory tool.
Just thinking out loud here, but if target device doesn’t support PXE net booting in UEFI mode, might it support USB booting in UEFI mode. The thought is build a ipxe boot environment on a usb flash drive and boot off that. I’m pretty sure that ipxe boot environment can be setup to boot off usb flash. The question would be does the hardware support this…
^^^^ (just using a graphic to isolate ideas)
On some hardware platforms you need to enable the legacy ROMS to get support for both USB and PXE booting in UEFI mode. I don’t have any lenovos here to test that idea on.
@Jbob said:
@george1421 Centos 6 appears to be missing some of the modules I require. I’ve been trying to hunt down the exact dependencies I’d need, or if need be, a new policy with different rules / modules.
That’s why we are going through this. 
No worries on my part. We’ll get them worked out.
@Jbob said:
@george1421 there is a DHCP section in the post. I will include DNS as well. Right now I wish to keep those options separate. Eventually the installer should automatically configure the firewall based on installation preference.
Sorry I missed that. I copied the top sections and skipped the bottom.