Tftp file is too big

With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need. Who are the certified experts? How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk.

We're a community of IT professionals committed to sharing knowledge. Our experts volunteer their time to help other people in the technology industry learn and succeed.

Plans and Pricing. But it does not serve the file and dies with "Error on server : Access violation". What would that mean? Stop the service and back to properties Click Log On tab and uncheck "Allow Service to interact with desktop" Start the service again, all should work. When attempting to boot into Clonezilla the issue arises when the file filesystem.

The following error is thrown from Python:. This didn't throw any exceptions in Python as the initrd. However, while Python doesn't see anything wrong, the system doesn't fully load or initialize: At the above referenced point, the system just sits there indefinitely.

What's interesting is that it never gets to that point exactly it gets to roughly that point sometimes a little earlier, sometimes a little later but at roughly that point it hangs.

PyPXE continues to run because it doesn't think anything is wrong but it appears that the system never received the full filesystem. Note that the above VM has been set to use 2 processor cores and 4GB of RAM plenty of space in the memory to hold these files with a 60GB virtual hard disk although it never gets used or is touched.

The text was updated successfully, but these errors were encountered:. In short, TFTP sucks for large files. However, this does not explain the error you are receiving. This error would imply that the TFTP packets are not being correctly created, and the data we're reading from the file is too large. Are you able to get an approximate byte boundary for where the error is caused? This can be done with wireshark. If you can't do this, then would you be able to create a packet capture of the whole boot and send it to me?

Sorry, something went wrong. In TFTP, the block id is a 2 byte int. This is the source of the error code I believe. I wonder why it isn't booting properly? Not so much fix as bypass. I don't think you'll be able to change blksize in a bootrom though. Give me a few minutes to set up the same environment and test. Sorry about the message spam. Using the pxelinux config copied from you, just changing the 'fetch' param, I get a complete boot.

The command I'm using is sudo python2 server. Perhaps that's the issue, then? I was using the pxelinux. I'll try with the one from the Clonezilla package and see what happens. I used everything we provide, just the config is different. And I added the following files to the netboot dir from clonezilla-live I can't seem to find physical hardware to test with, I'll have to test with physical hardware at another time. Can we keep this open for now? I think it's an issue with VMWare; in this discussion another user is having a similar problem and it appears to be an issue with a kernel mismatch or something.

I'm going to try with Virtualbox and see if I can get a clean boot on that. After hours upon hours of banging my head against the wall with this I finally was able to test with physical hardware and confirmed that it boots just fine via HTTP.

There must be something about the kernel in that image that VMWare doesn't like. I tried VirtualBox and it won't even initialize the adapter, I'm not sure if that's an issue with the hardware on my Mac or a bad config I had in VirtualBox; either way, the physical hardware test confirms that you can boot Clonezilla using PyPXE as long as you specify the filesystem.