Could not boot: Input/Output error(http://ipxe.org/1d0c6539)
-
@ManofValor If you go to this address via a web browser, what is the output?
http://10.10.1.40/fog/service/ipxe/boot.php?mac0=48:0f:cf:27:72:6f
For you and future readers, you’ll see I have a MAC address at the end of that URL. This is how you can manually ask the fog web server to generate what WOULD be the iPXE boot script for whatever clent’s MAC you plug into that spot. Multiple MACs can be passed via standard POST syntax, like this for example (fake but valid example) http://10.0.0.4/fog/service/ipxe/boot.php?mac0=48:0f:cf:27:72:6f&mac1=14:fe:b5:df:fc:7e
-
@Wayne-Workman Just some clarification, using mac0/mac1 in the line will work, but you can also just use mac=
-
@Tom-Elliott can you give an example? I think the boot.php function combines them all together with pipe between but I’m not sure.
-
-
@Tom-Elliott I chose Quick image.
#!ipxe set fog-ip 10.10.1.40 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot} cpuid --ext 29 && set arch x86_64 || set arch i386 goto get_console :console_set colour --rgb 0x00567a 1 || colour --rgb 0x00567a 2 || colour --rgb 0x00567a 4 || cpair --foreground 7 --background 2 2 || goto MENU :alt_console cpair --background 0 1 || cpair --background 1 2 || goto MENU :get_console console --picture http://10.10.1.40/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console :MENU menu colour --rgb 0xff0000 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap Host is NOT registered! item --gap -- ------------------------------------- item fog.local Boot from hard disk item fog.memtest Run Memtest86+ item fog.reginput Perform Full Host Registration and Inventory item fog.reg Quick Registration and Inventory item fog.quickimage Quick Image item fog.multijoin Join Multicast Session item fog.sysinfo Client System Information (Compatibility) choose --default fog.local --timeout 3000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :fog.memtest kernel memdisk iso raw initrd memtest.bin boot || goto MENU :fog.reginput kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.10.1.40/fog/ conosoleblank=0 loglevel=4 mode=manreg imgfetch init_32.xz boot || goto MENU :fog.reg kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.10.1.40/fog/ conosoleblank=0 loglevel=4 mode=autoreg imgfetch init_32.xz boot || goto MENU :fog.quickimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.multijoin login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.sysinfo kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.10.1.40/fog/ conosoleblank=0 loglevel=4 mode=sysinfo imgfetch init_32.xz boot || goto MENU :bootme chain -ar http://10.10.1.40/fog/service/ipxe/boot.php##params || goto MENU autoboot
-
@Wayne-Workman Wait, do you need the output from the laptop I’m trying to image?
-
@ManofValor The output is fine.
I just wanted to find out if I could replicate.
Do you have an image defined on the FOG Server? When you chose quick image, did it first present you with a login page?
-
@Tom-Elliott Yes, I put in my user name and password and it gave me a list images then I chose the one I setup for this machine.
-
@ManofValor then it gave the error? Can you show me how the image is setup?
-
@Tom-Elliott Yes, but have to be Monday, sorry. Servers are getting shut down for a generator install. Thanks see ya’ll Monday.
-
@ManofValor No problem.
-
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?
-
@Tom-Elliott said:
@ManofValor then it gave the error? Can you show me how the image is setup?
-
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.
-
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?
-
@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!
-
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. -
@Sebastian-Roth Thx once again everybody.
-
@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.
-
@Tom-Elliott I understand, I posted that a couple posts up. Everything is working after manually registering at the client.