PXE-E32 error, unable to boot to fog from pxe
-
@K.Hays Have you tried updating to trunk?
-
First, all, this is 1.2.0 (Sorry it wasn’t asked before. And glancing over the posts, it wasn’t mentioned at all either).
-
@K.Hays Internal addressing is not available to the outside world and doesn’t harm anything to share. However I’d recommend not sharing external addressing.
-
@Wayne-Workman Isn’t there suppose to be text to the left of /default.ipxe? I just tried on my system and its too fast for me to catch.
-
@george1421 No, because it’s 1.2.0
-
@Tom-Elliott said in [PXE-E32 error:
First, all, this is 1.2.0 (Sorry it wasn’t asked before. And glancing over the posts, it wasn’t mentioned at all either).
Wow, how’d I miss asking that question. Well same on me.
-
@Tom-Elliott i have not tried updating to trunk, is that necessary?
-
@K.Hays said in [PXE-E32 error:
@Tom-Elliott i have not tried updating to trunk, is that necessary?
It’s not necessary, but I think you’d benefit a great deal from it.
-
@george1421 the owner is fog.root but how do i check the access level?
-
@george1421 said in [PXE-E32 error:
@Wayne-Workman Isn’t there suppose to be text to the left of /default.ipxe? I just tried on my system and its too fast for me to catch.
Good catch, George. It is supposed to have an address before it.
-
@K.Hays said in [PXE-E32 error:
@george1421 the owner is fog.root but how do i check the access level?
ls -lawill do that for you. it should be-rw-r--r-- 1 fog rootBut as Tom said you would be better off upgrading to the trunk. Don’t let the not stable term scare you off.
-
@Wayne-Workman No it’s not, not if the user is using FOG 1.2.0.
-
@george1421 ill do whatever to fix the issue at hand. If you think updating it to trunk will do that, then so be it
-
@K.Hays said in [PXE-E32 error:
@george1421 ill do whatever to fix the issue at hand. If you think updating it to trunk will do that, then so be it
I don’t want to lead you on that it will for sure fix your issue. But you will then have a consistent build that we can support. While the 1.2.0 build is still supported I don’t have a 1.2.0 stable system any more to compare your system against. That is the case with most of the Mods here. I have been running the trunk build for almost a year now. My memory of 1.2.0 stable is getting pretty weak these days.
-
@george1421 ok so how would i upgrade to trunk then? preferably without losing my current configs.
-
@K.Hays said in [PXE-E32 error:
@george1421 ok so how would i upgrade to trunk then? preferably without losing my current configs.
If course make sure you have a solid backup of your FOG server and then follow this post https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
Just for clarity, you made reference to having an older version of FOG installed at your site. What version was that? If it was before 1.2.0 it may be a better idea to spin up a new FOG server instead of upgrading.
-
@george1421 The system has since been removed. I believe it was 0.32, but this fog server is not on the same machine.
-
@K.Hays OK as long as this was a fresh install of 1.2.0 then you are ok to upgrade.
-
@george1421 ok, Currently doing that now
-
@george1421 * Installing package: php5-json…Failed!