Latest posts made by orioliz
-
RE: Target computer booting from router not fog
@sebastian-roth yes, yes. Not boot problem is tftp
-
RE: Target computer booting from router not fog
@george1421 OK, sorry. CLient boot the FOG !! Good !!
This problem
Config /etc/dnsmasq.conf is heare:
# Don't function as a DNS server: port=0 # Log lots of extra information about DHCP transactions. log-dhcp # Set the root directory for files available via FTP. tftp-root=/tftpboot # The boot filename, Server name, Server Ip Address dhcp-boot=undionly.kpxe,,192.168.1.50 # Disable re-use of the DHCP servername and filename fields as extra # option space. That's to avoid confusing some old or broken DHCP clients. dhcp-no-override # inspect the vendor class string and match the text to set the tag dhcp-vendorclass=BIOS,PXEClient:Arch:00000 dhcp-vendorclass=UEFI32,PXEClient:Arch:00006 dhcp-vendorclass=UEFI,PXEClient:Arch:00007 dhcp-vendorclass=UEFI64,PXEClient:Arch:00009 # Set the boot file name based on the matching tag from the vendor class (above) dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,192.168.1.50 dhcp-boot=net:UEFI,ipxe.efi,,192.168.1.50 dhcp-boot=net:UEFI64,ipxe.efi,,192.168.1.50 # PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds. pxe-prompt="Booting FOG Client", 1 # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86, # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI # This option is first and will be the default if there is no input from the user. 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 dhcp-range=192.168.1.50,proxy```
-
Target computer booting from router not fog
@WAYNE-WORKMAN @SEBASTIAN-ROTH
Yes, run fsck /dev/sda1 this problem solution. Thanks !
My VM is VmWare (Bridged) (Fog Server and client). Client not run from the fog.
Client boot from 192.168.1.1 this router !
the client machine tries to boot from the router (192.168.1.1) if I set the network configuration to automatic (DHCP). If I configure the network manually (I put the FOG machine as gateway) then it starts from FOG and works fine. How do I start the kernel with FOG and not from the router by putting the client in DHCP mode? -
RE: Could not check expanded volume
@ wayne-obrero
hello, config the host and image is this…
-
Could not check expanded volume
OS Server: Ubuntu 16.04
OS client: Debian
SW Virt: Vm Ware WorkstationRun for the NETWORK :
where this error?