Could not boot: Input/Output error(http://ipxe.org/1d0c6539)

[Tom Elliott]

Also, please try updating to the latest version then seeing if this problem is still present. It’s more likely an issue with the version you’re running, I think 6623?

[ManofValor]

@Tom-Elliott said:

@ManofValor then it gave the error? Can you show me how the image is setup?

[Wayne Workman]

One of the sites in my organization is getting a similar error. They are on 6677, and working with an Optiplex 9020 in BIOS mode. Here’s a screenshot.

I asked that building tech to update to the latest, I’ll report back with what happens.

[ManofValor]

So I’m not sure if I’ve just been missing a step or if it works differently with different machines, but when I registered it through the client it started working. I put up a screen shot that showed it saying “Host Not Registered” and I haven’t seen that before. I haven’t had to do that yet, not that I shouldn’t have been, so maybe someone could help me understand here. Am I supposed to register through the client every time?

[Sebastian Roth]

@ManofValor said:

Am I supposed to register through the client every time?

Well, new/unknown clients need to register (themselves) or be registered (via web gui) once! New client/MAC address new registration. But you don’t need to re-register clients once per task or once a day or whatever!

[Wayne Workman]

Following up - the update did not fix it.

Upon further investigation, the problematic hosts had a “Auto-Reg” task that was stuck in task management, preventing a full iPXE boot script being generated for them from boot.php. The task was spinning, as if it was “In Progress”. We canceled these and the hosts began working.

[ManofValor]

@Sebastian-Roth Thx once again everybody.

[Tom Elliott]

@ManofValor Are things working now?

Are you still getting “Could not boot: Input/output error(http://ipxe.org/1d0c6539)”?

I’m only asking because thanking doesn’t really confirm things. For example, it leaves out if things are working. Thanks are perfectly fine, but please do share what you did that helped fixed it. If it’s just understanding of things, express that. That way the post doesn’t go by the wayside with other people running into similar issues going (How did it get fixed?).

Hopefully you understand.

If things are fixed, please try to explain what was done to fix them.

[ManofValor]

@Tom-Elliott I understand, I posted that a couple posts up. Everything is working after manually registering at the client.

[Wayne Workman]

@ManofValor so what’s not working if the client isn’t registered? Nothing? Without registering, It’s my understanding that you should at least be able to quick-image.

[ManofValor]

@Wayne-Workman I was getting that boot error. That’s what wasn’t working. It wouldn’t let me do a quick image. For some reason it worked after registering at the client pc.

[Wayne Workman]

@ManofValor
Can you reliably replicate the issue?

[ManofValor]

@Wayne-Workman To do that I would have to delete the image I captured wouldn’t I?

[Wayne Workman]

@ManofValor No I think all you would need to do is delete the host.

[ManofValor]

@Wayne-Workman Well, I deleted the host and got the “host not registered” message but when I chose quick image it started the image. Is there a way to cancel in progress or do I have to just let it do it again? Not sure what changed other than registering it before. That’s the only thing I did different.

[Wayne Workman]

@ManofValor Weird. I don’t know what happened or what went wrong then.

And to stop imaging… I guess the power button on the computer. I’d just let it image.

[ManofValor]

@Wayne-Workman ok. I wish we could have come out with an answer. I guess it was just a PMS moment.