Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to fetch tftp image: TFTP Error, start_image returned tftp error #111

Open
xutian opened this issue Jan 25, 2018 · 5 comments
Open

Comments

@xutian
Copy link

xutian commented Jan 25, 2018

When I boot my host from pxe server, pxe client download shim from tftp server successful, but shim failed to fetch netimage with error message like:

Unable to fetch tftp image: TFTP Error, start_image returned tftp error

@lcp
Copy link
Collaborator

lcp commented Jan 26, 2018

Per UEFI SPEC, EFI_TFTP_ERROR from EFI_PXE_BASE_CODE_PROTOCOL.Mtftp() means "A TFTP error packet was received during the MTFTP session". Unfortunately, shim currently won't show the details of TFTP error code. According to RFC1350, the possible error codes are:

0 Not defined, see error message (if any).
1 File not found.
2 Access violation.
3 Disk full or allocation exceeded.
4 Illegal TFTP operation.
5 Unknown transfer ID.
6 File already exists.
7 No such user.

Maybe we can fetch the error code after getting EFI_TFTP_ERROR to help the user to identify the issue.

lcp added a commit to lcp/shim that referenced this issue Jan 26, 2018
Since the TFTP error code is cached in EFI_PXE_BASE_CODE_MODE.TftpError,
print the error code to help the user to identify the issue.

rhboot#111

Signed-off-by: Gary Lin <glin@suse.com>
@lcp
Copy link
Collaborator

lcp commented Jan 26, 2018

Could you try this patch and paste what it shows?
lcp@7a90c2a

@xutian
Copy link
Author

xutian commented Jan 31, 2018

@lcp
Thanks your patch and quick response, I will try on my host.
Thanks,
Xu

@daberkow
Copy link

I have been having issues for a while trying to get this to work, I may have an idea of your issue. The shim REQUIRES your DHCP server to be giving out "next-server" pointing to your TFTP host, if you are running proxyDHCP and dont have your primary server giving out a next-server address it will fail this way.

@AdamWill
Copy link
Contributor

note for anyone else googling around forlornly: another possible cause of this is that shim always seems to want the grub executable to be in the TFTP root - even if shim itself is in a subdirectory. If it can't find the grub executable, you get this error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants