@Wayne-Workman said:

Tom, I think you’re mistaking fast startup for something else. see in this picture:

I have seen this as a BIOS setting as well in Dells, Lenovo or Toshiba. Sorry I can’t be specific. It MUST be turned off or hair is pulled.

Is that a 512e drive?

You need to break your request down to two things.

1. Creating or `Mastering’ an OS for distribution.
2. Capturing an image for distribution

If you’re looking for the first, I recommend starting your journey with Microsoft documentation ( http://go.microsoft.com/fwlink/?LinkId=162739 ), and the Windows 7 Resource Kit.

For the second, start with what Wayne said.

Have you tried zeroing the disk entirely with DBAN? (Darik’s Boot and Nuke - just use the quick method)

Is it possible the disk is failing?

So it doesn’t seem to present any issues whatsoever for how we use FOG 4820 .

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.

Confirmed! Ty again.

After waiting the entirety of the song Axel F by Harold Faltermeyer… still nothing happening on 4818 either.

Trying 4818 now.

During installation when instructed to visit the web management page ( eg: http://172.19.244.38/fog/management
) for the first time to install/upgrade the Database Schema Installer, clicking [Install/Upgrade Now] on that page sends up a page consisting of:

1. The Cloud
2. Open Source Computer Cloning Solution
3. Database Schema Installer / Updater title … and nothing else.

Viewed on Edge and IE11.

You’re being modest.

Thank you for the quick response.

Any changes made to Storage Group or Storage Node are not written.

Web interface pushes back with:

“Storage Group/Node already exists”

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.

1. Install the Minimal Server to a VM, nothing else, no updates
2. Purpose the VM (in this case for FOG and all that entails, no updates)
3. Master the image (every update and generalizing code)
4. Capture the image
5. Distribute the image
6. 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

I thought of that too. I just installed an infrastructure server with a bunch of file storage drivers. I will know tomorrow how it is.

FOG of course. Build 4752 to be precise.

Could a moderator move this thread into Linux problems for me please?

So I found this very specific page: How to install the AHCI mode drivers in an existing installation of CentOS that only has IDE support … but it didn’t work.

1. Add the line: “alias scsi_hostadapter ahci” to /etc/modprobe.conf

2. Rebuild your initrd with this command:
   mkinitrd -f -v /boot/initrd-$(uname -r).ahci.img $(uname -r)

3. Rename the old init.rd to a backup and mv the new one where the old one was:
   mv /boot/initrd-$(uname -r).img /boot/initrd-$(uname -r).img.bak
   mv /boot/initrd-$(uname -r).ahci.img /boot/initrd-$(uname -r).img

That first part of #3 can’t find the file on my LVM sample.

Okay, so that’s the deal. The controller.

The changing disk controller tripped it up.

I turned off AHCI mode on the physical box and it now works.

The next step is, how can I fix this so I can retain the benefits of AHCI over compatibility mode?

I’m going to try a different box and see if it may be a hardware compatibility issue.

BTW, on the completed VM with FOG, SELinux is disabled.

I would like to clone my CentOS 7 and my CentOS 7+ Fog 4752 Hyper-V VMs onto a physical machines.

It is a minimal installation on a single disk. I’m just installing the OS, then shutting down to capture then deploy, and for the FOG install, doing my usual thang.

Each time, build 4752 captures the way it’s meant to, then deploys without issue, but when Centos tries to boot, it dumps to Dracut.

I have tried installing it with LVM and the XFS File System, with Standard Partitions, and ext4 File System.

This is the dump from a pure LVM attempt:

Reached: Target Paths
Reached: Target Basic System
Warning: Could not boot
Warning: /dev/centos_centos7/root does not exist
Warning: /dev/centos_centos7/swap does not exist
Warning: /dev/mapper/centos_centos7-root does not exist
Starting Dracut Emergency Shell...
...
Entering emergency mode.

What have I done wrong this time?