@FeasiblePear Have your admin update to the 1.4.0RC release over 1.3.5 stable. 1.3.5 stable had a bug with resizing hard drives under certain conditions. 1.4.0RC1 addressed this issue. I think the devs are up to 1.4.0RC8 which address a few other bugs from 1.3.5 stable. Its well worth the update to the current RC release.
Posts made by george1421
-
RE: Keyboard not working in Fog on client
-
RE: FOG Server TFTP timing out
@tom.langenfeld I also agree it sounds like an IP address conflict with the FOG server.
Once you determine one way or the other on the IP address conflict I want you to do the following from the FOG server linux console.
(you may need to install the traceroute utility if its not installed by default).
Run a traceroute from the FOG server to a device on this remote vlan where you are getting the tftp timeout. If you have success on a traceroute back to the remote vlan then…From a windows computer on that remote vlan, see if you can ping the fog server IP address.
If success then install the tftp client program on the windows computer from Program and Features. See if you can
tftp get
undionly.kpxe from the FOG server.If success then you must confirm that you have dhcp options 66 and 67 set correctly for this client vlan.
-
RE: Booting ISO issue / Mount /dev/cdrom
I agree with Wayne.
What is going on is the iso image kernel has it hard coded to connect to the physical cdrom (which doesn’t exist because the kernel was pxe booted). You will need to unpack the iso image and then look for the syslinux config files.
I’m in the process of downloading the liniso.iso for the 1950 to see what the iso image looks unpacked.
-
RE: networks and multicast
multicasting works really well when the target and fog server are on the same subnet (vlan). If you have multiple vlans isolated with a router, then for multicasting you need to have a multicast router setup to. This will forward the multicast streams through your core router. Also you will want to turn on igmp snooping on the vlan where your target computers are. This will allow only the systems who request the multicast stream to use them (multicast sparse mode vs dense mode)
-
RE: Share /images on NAS Synology
You might want to read over this: https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node
You can not reshare a mounted external file system, i.e. share a mounted share. Your only option is to turn synology nas into a fog storage node.
-
RE: PXE-T01: File Not Found Error
@easybizit That is an excellent question!!
Has selinux been set to permissive? The sym link should work no problem…
-
RE: PXE-T01: File Not Found Error
@easybizit Well that one is a bit confusing. I’m not seeing anything wrong.
Lets replace the link with a real file.
cp /tftpboot/undionly.kpxe /tftpboot/undionly.0
And then try with the tftp again from a remote windows client.
-
RE: PXE-T01: File Not Found Error
@easybizit can you download the file manually via tftp?
-
RE: PXE-T01: File Not Found Error
@easybizit You do need to create the symbolic link between undionly.0 and undionly.kpxe for that bit to work.
ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0 ln -s /tftpboot/ipxe.efi /tftpboot/ipxe.0
-
RE: Dell Inspiron 15 7559
@Sebastian-Roth said in Dell Inspiron 15 7559:
Looks like our iPXE script (see here) is not behaving the way we intended it to.
Well that may explain why I didn’t see the main dhcp server responding with next server. I was going to have the OP post his ltsp.conf again on monday to see if we had something in the wrong spot and/or capture another pcap file. We might want to do that just to be clear that dnsmasq isn’t doing something unexpected.
-
RE: Configuring Boot with Off-board ISA Intel Pro/100
@wanderbread Ah yes ISA cards. Glad I left them behind back in the 1990’s…
Watch the IRQ number, make sure its not shared with another device in the computer. The ISA cards had a jumper to select the irq port. irq 3 and 4 were for the serial ports. irq 2 was for the printer (I think). That left irq 5 and 7 open for add in cards (confirm with ancient text documents to be sure). Could the on board nic be interfering with the add in one?
-
RE: Pxe timeout error after upgrade to 1.4.0 rc7
@Smokinjoe68 Is your fog server and the pxe booting clients on the same subnet/vlan? If so lets grab a pcap of the pxe booting process.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
There is no need to hide the private IP address inside your network. There is no useful information there, I can’t connect to 192.168.x.x over the network to hack your computer. If this was a public IP address I would feel differently. But then you would have bigger issues than me trying to hack your network.
-
RE: Dell Inspiron 15 7559
@Merilious Some environments require the pxe-service code and some do not. I don’t have a solid answer for you, but we start and step 1 and move to step 4 testing at each step. Your pcap file was flowing perfectly until it got to the proxydhcp dialog. dnsmasq didn’t supply what your PXE rom needed so it abort the pxe boot. This is all different pxe rom requirements. Once you are in iPXE then fog has a better chance of controlling the pxe booting process.
Ah ok, I just reread what iPXE posted, duplicate option 66… your dhcp server gave it one IP address for the boot server and dhcp proxy gave it another so it talked to the proxy to find out what to do. I need to look at your pcap file again a bit closer to see where your main dhcp server was sending the client. Do you have another imaging system in your environment?
-
RE: Dell Inspiron 15 7559
@Merilious ok that tells me a bit more about the booting process. Everything looks good until it talks to the ProxyDHCP server (dnsmasq). So we need to move to step 3 for dnsmasq config.
after this section in your ltsp.conf
# PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds. pxe-prompt="Booting FOG!", 10
Actually take the prompt timeout from 10 to 1. Its not needed since you can’t pick anything different in this configuration.
add in
pxe-service=X86PC, "Boot to FOG", undionly.kpxe pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi
I guessed at the context since I can’t find it quickly. I have the answer on my dev server at home, but well that’s at home and I’m not.
If that doesn’t work then move to step 4
pxe-service=X86PC, "Boot to FOG", undionly.kpxe,10.200.10.20 pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi,10.200.10.20 pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi,10.200.10.20
We don’t want to jump right to 4 because it may create other issues. So one step at a time. This should tell proxy dhcp to send the right file name per the client request.
-
RE: Pxe timeout error after upgrade to 1.4.0 rc7
@Smokinjoe68 what is the error message you get?
Is the FOG server supplying the dhcp info to the target computers?
If you have a clear screen shot of what the pxe client is not doing, it might give us a direction to move in.
-
RE: Dell Inspiron 15 7559
@Merilious is the uefi iPXE kernel making it to the target computer (i.e. are you seeing the iPXE banner)?
If you are unsure where to turn next, then follow and do what the tutorial says in the previous post. What we need to do is capture the pxe bootup of one of these uefi systems. This works really well if the fog server and the pxe booting client is on the same subnet. Post the pcap here for review.
I can boot and image a BIOS system no problem. It’s UEFI/EFI systems that don’t want to work
for clarity a clear picture taken with a mobile phone helps understand what don’t work means. If we can see the error we may understand what’s wrong. The context of the error is almost as important as the error itself.
-
RE: Dell Inspiron 15 7559
@george1421 So with 2.76 is your pxe booting for uefi working as you need it?
Don’t follow this just yet, posting it cause I’m doing 4 things right now and don’t want to loose the link.
ref: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue -
RE: Dell Inspiron 15 7559
@Merilious That one looks good. There is the next step if that one doesn’t boot correctly. The dnsmaq configuration is built in layers, you start basic and then build up until it works in your environment. Right now you are on step 2 of 3.
-
RE: Dell Inspiron 15 7559
@Merilious That is the version you need. Now post your ltsp.conf file and we can take a look at that.