iPXE boot problem
-
This sounds an awful lot like there may be another DHCP server doling out addresses within the scope of the network you’re trying to boot to fog in. I don’t think the HDD has any connection either as it’s not even loaded at that point (where you’re seeing the failure). Unless the HDD is passing some firmware and adjusting settings into the BIOS when it’s being turned on, which I don’t think is possible after initial POST goes through.
-
Thank you very much, I will check this
-
I tried all the stuffs on the wiki but it didn’t work … Still the same error message
-
Hello,
I had this message yesterday, the file default.ipxe was not present in /tftpboot (I changed the content of my /tftpboot), I just recreated it with the older one and it was ok
Perhaps it will help you
-
Thanks for your reply, but default.ipxe is present in my Fog server … You think it’s better if i recreate a /tftpboot directory and i transfer all the files of the old one ?
-
@Bcetinkaya You need to read the file, make sure the IP that’s listed in the file is pointing at the proper place.
-
I read it and no problem in this file … The IP address is correct
-
But can you download it using tftp client from another machine?? Why should iPXE say “No such file or directory” if it is there!? Please follow the troubleshoting guide and let us know if all the steps work.
-
@Sebastian-Roth
Hello,All the machines have this message error, I tried on 4-5 machines … I followed the troubleshooting guide, all the steps work but I still have the message error. I don’t understand why … The message error talks about a non-existent file that i have on the server.
-
Could you please take a picture of the error screen. Sometimes it’s somewhere in the details and we just cannot find the needle in the stack by asking questions.
-
-
Can you please try this undionly.kpxe? See here for more details about this binary: https://forums.fogproject.org/topic/4973/default-ipxe-connection-timeout-on-dell-only/6
-
Thank you very much, it works now but i have this message error before :
https://www.dropbox.com/s/20df005b7rzx6f7/IMG_3760.JPG?dl=0 (Sorry i can’t download the picture here, too big)
Is it important ?
-
@Bcetinkaya What happens after that?
-
The installation begins, but i have an error message : “no image in PartClone” but it continues and it fogs the machine
-
@Bcetinkaya Can you take a photo of that error, the “no image in partclone” message?
-
I took some pictures, i put the links below :
https://www.dropbox.com/s/omwhathmz63flij/Photo 28-01-16 15 15 49.jpg?dl=0
https://www.dropbox.com/s/kf930uxroz9apqr/Photo 28-01-16 15 19 20.jpg?dl=0
https://www.dropbox.com/s/yw23vjhrxgwwefp/Photo 28-01-16 15 19 26.jpg?dl=0
https://www.dropbox.com/s/j0n61wxh52754v9/Photo 28-01-16 15 19 32.jpg?dl=0
https://www.dropbox.com/s/d7b5i9yj2i4a5z4/Photo 28-01-16 15 19 40.jpg?dl=0
But after that it continues :
https://www.dropbox.com/s/bb5b9l0fig037qi/Photo 28-01-16 15 19 44.jpg?dl=0
-
The red and green messages you see when booting are iPXE debug messages. You can just ignore those for the moment! Works like a charm as we see.
The error “This is not partclone image” does not sound very healthy. I guess the image is corrupt. Can you run this command on the FOG server
ls -al /images/mikreleaseupand post the output here. Anyhow, I guess it would be a good idea to capture this image from your host again. When and how was this image created? -
I don’t have /images directory … The image is an upload of a master, you think the image is corrupted ?
-
Well at least the second partition seams to have an issue.
Where are you images stored then?? /images is the default path used by FOG.
