Topics created by sudburr

You’re being modest.

So the problem isn’t the cloning but that I was transferring from an IDE/Compatible VM to an Physical system with AHCI enabled. Setting the physical to IDE/Compatible mode fixed that. However IDE mode is not a solution. I required building AHCI into the kernel prior to deployment.

Thanks to some help from centos.org forums I have a working solution.

I’ve moved the OS update and some other new code that forces the recompiled kernel to include AHCI drivers to the final mastering.

Server building occurs for me in several steps.

Install the Minimal Server to a VM, nothing else, no updates Purpose the VM (in this case for FOG and all that entails, no updates) Master the image (every update and generalizing code) Capture the image Distribute the image Align the Deployed system

I’ve added the following code to the Mastering:

03> Master the Image ## Login REMOTELY with Kitty ( http://kitty.9bis.net/ ) ## Elevate Access Level ## -- ## Disable root access via SSH (CentOS only) ## Direct next Kernel recompilation update to include AHCI drivers & be HW generic ## Clean & Update the OS ## Shutdown sudo su if [ -f /etc/centos-release ]; then sed -i "s|#PermitRootLogin yes|PermitRootLogin no|g" /etc/ssh/sshd_config systemctl restart sshd.service sed -i 's|#add_drivers+="|add_drivers+="ahci|g' /etc/dracut.conf sed -i 's|#hostonly="yes|hostonly="no|g' /etc/dracut.conf yum clean all yum makecache yum update -y shutdown now fi

@Tom-Elliott CrucibleWDS has resizeable LVM working.

Thought I did … setting it again.

@sudburr Hi, not sure but I think it’s for FOG 2.0 : core installation and plugins to add dhcp, …

@Wayne-Workman, @sudburr you both realize you can use relative paths in the location parameter? This removes the hardcoding and is safer than trying get a good Apache configuration using a series of sed statements.

I’ve fixed this in the code so fresh installs should no longer have this issue. That said this would not have caused any issues.

Because, the other installers did NOT require setting of the password. Arch and Redhat. I made a large move to commonize the installer so things were more or less presented the same way across the board.

By build 4728, it is fixed. Ty!

@Tom-Elliott said:

@Wayne-Workman I don’t know what you mean.

They are currently synced properly.

gah… I had it backwards… I do apologize, that was confusing.

Change the FOG number every other time - till it’s in sync with the SVN number.

Success on all fronts.

I have successfully created a generalized virtual server running CentOS 7.1 with FOG Build 4820. I can dump an image of it onto any hardware we use, mobile, desktop or virtual and it works exactly as desired.

I like it so much I’m making it my new standard.

There were some new hoops to jump through, but the CentOS community and online documentation provided solutions using native commands and features.

I even succeeded with no issues whatsoever in converting my vm development fog from Debian8.2 to CentOS7.1 in about 15 minutes.

I love slaying dragons. 😎

@sudburr said:

What didn’t make sense?

I was rushing, it makes more sense now. Today was really hectic, apologies.

Since sourceforge’s issues, I decided to use git’s versioning system. This is expected.

As a failsafe, I added the same version checking to check, latest stable, svn, and git.

GIT 4274 has everything back in running order.

Welp, SF is working enough again that I was able to pull down 3.18.5 . 3.0.1 is weirding out though.

@Wayne-Workman I actually created a fog database from MySQL Workbench with no problem, however, I didn’t realize my account doesn’t have a MySQL password, but the mysql and root accounts do and fog was using one of those! So, that’s why there was a permissions problem. I installed the trunk and built it and it worked! I did however, have to comment out the configureMySql call because it wasn’t defined in the trunk. I guess someone removed its definition so it failed because the installation.sh script still called it!
"I’m so happy… " I can now go on with my PXE thing and proceed with the software phase of my new server.

Fixed in 3410 ty.

Fixed with svn 3388 thank you!