The cause of the problem, like explained in the second link, it's related to the value of the -b parameter blocksize option of the tftp command. It looks like it gets to the point of trying to load the filesystem. Listed below are the different PXE menu option configurations that I have used so far.Įach of them have resulted in a no go with the following error: "Unable to find a live file system on the network". I believe that I am pretty close in getting it to work, but am not sure where to go next. Deploying Clonezilla with PXE Linux on Ubuntu 16.04 Server Server Fault is a question and answer site for system and network administrators.
UEFI pxe booting clonezilla.By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. My tftp server is an ubuntu Still having a problem with my XPS but it deserves it's own thread and I'll try and use a usb stick and see if I have any better luck. If the issue is reproducible, then it can be fixed. I'd rather try and set this up on my existing tftp server I have copied the grubx Which version of Clonezilla live did you use? How did you start the lite server? Please tell us in detail, step by step so that we can reproduce this issue here. I know the ip but not sure of the filename.
I picked interactive mode as each computer I connect I want to select images. I started the lite-server option and select existing dhcp server. I am not understanding the options when starting clonezilla in lite server mode. You can find them when lite server is enabled. Actually the lite server of Clonezilla supports uEFI network booting.
I had pxelinux working so nice and then Dell throws this at me.
I think I might just be able to use grub but not sure how to give it network options to get files like I do with pxelinux. I'll do some more research but documents on such seem few and far between. I see some posts about it but no notable configuration files. So I'll have to learn the new ways of booting clonezilla using something other than pxelinux. # at the moment all non-BIOS clients are consideredĭhcp-boot=tag:!ipxe,tag:!BIOS,ipxe.efi,10.1.0.Ok Dell finnally stopped shipping XPS's with legacy support. # inspect the vendor class string and tag BIOS clientĭhcp-vendorclass=BIOS,PXEClient:Arch:00000ĭhcp-boot=tag:!ipxe,tag:BIOS,undionly.kpxe,10.1.0.1 # Enable only when your network supports it # Set interface MTU to 9000 bytes (jumbo frame) Step by step guide Part 1: Setup the bare bone PXE boot server A VMware VM set to PXE boot from network. I strongly suggest to use isolated network for PXE boot to prevent it from interfering with existing DHCP servers on the network. This is an isolated network created just for booting new servers on the network. Interface 'eth1' is connected to the PXE boot subnet. Interface 'eth0' is for sysadmin to login and manage the server. PXE Boot server ( Centos 7.5) with two interfaces.I use iPXE as the boot image and dnsmasq as DHCP & TFTP server and I found it's dead simple to setup those two software. There are many articles on the Internet for building PXE boot infrastructure however I found most of them does not work for EFI based hardware. This article is a step by step guide for building your own PXE boot infrastructure which can be used to boot both legacy BIOS and EFI based hardware from network.