init.xz issue?
-
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
Right now what the OP is saying is a bit conflicting in my mind. So we need to get to a known good place with the SVN trunk. I can say, absolutely that FOG SVN trunk works on Centos 6.7 with 0 alternations or messing around. Follow the documented install instructions (even on the svn trunk) and it will work, period. Understand that I’m not saying that Centos 7 (rhel7) is not a viable candidate. Personally I don’t have quite enough experience with Centos 7 to say absolutely there will be no issue. It appears that the OP is having issues that could or could not be related to the OS, or the way the FOG interacts with the OS. To go to a known good state I recommended Centos 6.7 on alternate hardware. If it works there and not on the main system then we can start to pick the OS apart. If FOG acts exactly the same between the production system and this test system on a known stable OS then we have more justification to point to something in the FOG SVN trunk is amiss.
Also for 6.7 its still a viable option since LTS ends in 2020 with full system updates ending in summer 2017 (it kind of parallels the question of Win7 vs Win10, what do you install today?). The answer will be different if you ask me the same question next July. FWIW: LTS for Centos 7 ends in 2024.
-
@Tom-Elliott Thank you for your input… I waited for quite some time, and the issue persisted.
@StahnAileron @george1421 @Wayne-Workman After not getting further with Fedora 22, I set up the SVN trunk FOG server on the same machine, with Centos 6.7. Outside of correcting a reboot parameter on Centos itself (Optiplex 990 issue), it all works as expected and I am playing with the imaging capture/deploy.
@george1421 Thank you for the Centos suggestion, it has been sometime since I’ve used that but it is coming back to me
I will most likely try Centos 7 at some point, but I have enough playing to do for now
Thank you all for your assistance, and thanks for making FOG available!
-
For what its worth. I just spun on a centos 7 fog server. With the exception of a few commands that are different between 6.7 and 7. The current FOG trunk installs and operates on Centos 7 without issue. Understand at this point I haven’t uploaded or downloaded an image yet. But basic functions on Centos 7 are working.
Right now you appear to be in a good place with Centos 6.7 so hang there for a bit and then focus on make your fog configurations perfect for your tasks.
-
@bjmarowitz said:
@Wayne-Workman After not getting further with Fedora 22, …
That’s it, I’m writing a Fedora 22 article.
-
@bjmarowitz Do you still see the init.xz hang issue or should we mark this solved?
-
@george1421 regards to centos 6.7 I had difficulty installing sql using the trunk install. I needed to install sql separately, sql wouldn’t start without a separate installation (for me), I didn’t bother debugging as it took seconds to spool up a separate yum. I used the minimal 6.7 install ISO on a freshly minted hyper-v host. I did try with 7 at one point but stuck to 6 as the instructions were more verbose.
obviously mariadb was used.
-
@KKTwenty101 Interesting, I also do a minimal install for Cento 6 and 7 and fog installs no problem. As long as you remember to disable iptables and selinux. I know that FOG installs mysql during the initial install because the password for mysql root user is blank. If you are doing something outside of the normal FOG install then something is broken either with the system or the FOG installer.
My FOG server is behind a proxy server so I have to create a few envron variables and update wgetrc and subversion with the proxy server settings, but the basic workflow is
- Install centos 6.5
- yum upgrade -y
- yum install subversion wget -y
- reboot
- disable selinux and iptables
- reboot
- mkdir /opt/fog_trunk
- cd to the fog_trunk and use subversion to copy the current build
- cd /opt/fog_trunk/bin
- ./install.sh
That’s all I’ve done and it works correctly right out of the box, so to speak.
-
@george1421 I wonder if there is something different in 6.7? Originally I used Ubuntu where the documentation was followed to the letter, I only recently rebuilt as Centos in the last week due to SMP and NIC issues in the Ubuntu integration services. It could be that a hyper-v centos installs/activates “something else”. I have done the same as you above except that I install sql (and nano- I really cant use VI) at point 3 (and I disable selinux and iptables before point 2).
Either way, the system does work for me and any errors AFTER base installation are usually down to importing settings from a previous versions (FOG user password differences, large log files, hosts with incorrect usernames/passwords, AD activation differences etc etc).
I have no doubt it will be something I have done as I am primarily a windows sysadmin with enough Linux experience to get me by.
-
Sorry to reply to a rather old topic, but I’m having the exact same issue…
History:- fog 1.20 on Ubuntu 12.04 (which served us well for a couple of years now)
- a “special” computer arrived this week that we need to image: a Thor VM3 (https://www.honeywellaidc.com/en-US/Pages/Product.aspx?category=vehicle-mount-computers&cat=HSM&pid=thorvm3)
- Since this uses uefi, it doesn’t work with fog 1.20. So I upgraded to the trunk version, hoping this would fix all my issues
- it boots to the fog menu, but when I choose the quick registration task, the machine hangs on “init.xz … ok” (no reboot, it just hangs there).
- memtest doesn’t work either: it says “memdisk… ok” followed by “Could not select: Exec format error” and “Could not boot: Exec format error”
I read in this topic that installing fog on a fresh Centos 6.7 helped for @bjmarowitz. I tried that today, but it behaves the exact same way in our situation here
PS: Last attempt was with trunk version 8099 (or is it the SVN revision 5678 that is important? I’m confused
)Any help is very welcome! Thanks!
-
@bmaster001 I strongly suggest that you start your own thread since your conditions are probably different.
If this is your first uefi system, what are you sending for dhcp option 67? This uefi system needs the uefi boot iPXE kernel. So you will need ipxe.efi being sent to “this” target computer.
-
I understand, I created a new topic: https://forums.fogproject.org/topic/7767/another-init-xz-issue
PS: dhcp settings seem to be ok (see the new topic).
