Could not boot: Input/Output error(http://ipxe.org/1d0c6539)
-
I am trying to image my first machine(Lenovo Thinkpad T430) and when the machine PXE(after adding it to the inventory and scheduling a task to capture the image) I get the “Could not boot: Input/Output error(http://ipxe.org/1d0c6539)”.
I have checked
https://forums.fogproject.org/topic/6910/could-not-boot-input-output-error-http-ipxe-org-1d0c6539
and
https://forums.fogproject.org/topic/7447/could-not-boot-input-output-error-http-ipxe-org-1d0c6539
topics and it looks like I need to upgrade the fog deployment.I am on Ubuntu 16.04.1 LTS
FOG: 1.3.0-RC10
Schema: 234
Git:5955
SVN:5954Is there something that should be updated on my end?
Thanks in advance.
-
Unfortunately that machine is in a devel environment. But I see what the problem is. During install it said the IP of the server was 192.168.76.169\n10.254.254.10. It is giving me a login error with the username of “192.168.76.169\n10.254.254.10”. I thought I fixed all of those entries in the database. Let me see if there is another location with that crufy data
-
Ok just so I understand you can pxe boot the target computer into the FOG iPXE menu, from there you can register/inventory the target computer. From there when you schedule a capture or deploy task you get the above error message?
-
@george1421 That is correct. I have done this from two different machines, both different hardware.
-
@george1421 Also I am not sure how this got added to the General Topics. I meant for it to be in the Tech Help
-
@sbenson I can move it to the right section for you.
So from the FOG iPXE menu have you tested the hardware compatibility? I think its the last menu item on the iPXE menu.
-
@george1421 Yeah, the compatibility said the disk/network was fine. I don’t think there was anything else it needed to do. I can run it again if you would like
EDIT: Yes it says Network/Disk PASS
-
@sbenson Hmm it should be working (obvious statement).
lets see if what you get when you do this from a browser.
http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=<mac_address_of_target>
What that will do is tell FOG to create the iPXE menu specifically for that target computer (where you’ve told it to capture/deploy). You need the mac address of that specific target in the form of 00:00:00:00:00:00 post the output here.
-
@george1421 said in Could not boot: Input/Output error(http://ipxe.org/1d0c6539):
What that will do is tell FOG to create the iPXE menu specifically for that target computer (where you’ve told it to capture/deploy). You need the mac address of that specific target in the form of 00:00:00:00:00:00 post the output here.
#!ipxe
set fog-ip 192.168.76.169
set web-root fog
set boot-url http://${fog-ip}/${web-root} -
@sbenson Well we both know that’s not right. The page is complete.
Can you check the apache error log. Since you are using ubuntu the file should be titled error.log Tail that file and see if apache threw an error when that happened. I do have to say I’ve seen this before, but I can’t remember off the top of my head the cause. Hopefully the apache error log will give us the path.
-
Unfortunately that machine is in a devel environment. But I see what the problem is. During install it said the IP of the server was 192.168.76.169\n10.254.254.10. It is giving me a login error with the username of “192.168.76.169\n10.254.254.10”. I thought I fixed all of those entries in the database. Let me see if there is another location with that crufy data
-
@george1421 Confirmed it was the cruft left over when the machine was being installed(it didn’t like 2 IP’s assigned to one interface I guess).
Next quick question. Is there a way to convert a clonezilla image to work with FOG?
-
@sbenson The easiest way may not be the direct way. The easiest way is to deploy your clonezilla image to a target computer then immediately pxe boot that system and capture it with fog. This will be the quickest and surest way to ensure the files are in the correct format.
-
Crosslinking similar threads:
https://forums.fogproject.org/topic/8601/ipxe-boot-php-hanging-on-capture