@Wayne-Workman
/thread hijack /offtopic /sorry.

Don’t forget that if you ARE running windows at all then hyper-v is (for less than 20 guest servers assuming a 2 host cluster) a better option, you get TWO virtual licenses for each server license purchased. thus a “free” host per hyper-v instance. If you were to license 10 virtual MS server guests on 2 hosts using centos as a clustered host then you would need to purchase 20 server licences (and you cant use enterprise licences as you aren’t licensing the host in this case). If you were using a pair of server 2012R2 hosts and had 10 server guests then you only need to purchase 10 licences as each license is worth 2 thus each host has 5 licenses each thus 10 total clustered servers.

And FWIW it is an ABSOLUTE NIGHTMARE to license desktop windows in a virtual environment - long story short don’t do it. Normal licenses do NOT cover W7 being installed in a virtual environment you need specialist licences (VDA). Seems mad? Yes it is.

Entering the password into a the group and update.

when viewed from the host the password is in clear.

Exported SQL and checked the raw insert into hosts entries - they are also in “clear”.

@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.

@Wayne-Workman yes. Not sure if it is the cleanest of solutions though, however it will work for me, if it gets to this point in the cloning process then I don’t care if I kill the partition table and give a nonsensical label - there maybe purists who aren’t happy with this.

There are probably countless pitfalls that might happen, such as wrong drive selected in multiple drive systems resulting in the wrong drive having its first 512 murdered - that isn’t an issue for me but at least it defaults to N

@cml didn’t know that. Thank you but it didn’t work. When I update the group of all it doesn’t “encode” the password. Going into any of the hosts and clicking the “eye” shows the password in clear. If this is saved on the host then it correctly gets encoded (after clicking the eye).

@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.

I have not yet found a way to mass update the NEW AD password (some of my units are in groups, some are not, some groups have active tasks for WOL etc so im not too keen on adding everyone to a group then removing back to their original) so for the time being im sticking with a legacy client.

Im not wiki editor so here are my notes on what I did to install SVN trunk on CENTOS 6.7 on hyper-v (2012R2) 2 cores with 2Gb RAM (htop says im using 300Mb so 2Gb is probably overkill, cores are not used hardly) I had a working 1.2.0 but in reality all I took from this was the config save SQL.

*Installed CENTOS from minimal install ISO. Follow the screens but importantly set network to AUTOMATICALLY CONNECT on your adapter - this makes things much easier now. Also make sure the hostname is correct now (and under 16 characters if you intend to join the domain, again it makes things easier).

• disable SELinux
• yum -y update and install nano, subversion
• I installed mariadb (MySQL) manually and ran the initial setup giving it a password
• get trunk and install
• change fog password to match the original exported settings, modify fog Class.class.php accordingly (for FTP and image purposes)
• modify init.xz for my own reasons, you might be fine https://forums.fogproject.org/topic/6117/svn-image-doesnt-push
• modify the exported save (if appropriate) and change anything (such as DOMAIN\USERNAME to USERNAME to avoid 2202 errors etc)
• run web GUI and import save, run GUI again in FRESH cache clear screen (I use inprivate). Upgrade settings and export settings. This is due to new “legacy” vs “new” AD component - upgraded goes into “new” so gives you 1326 domain errors, edit the exported settings and reimport - I used MySQL to truncate and reimport.

voila

Fixed.
Used https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image and modified /bin/fog.download

#fix for possible dodgy partitions on the disk
testdisk="";
testdisk=`fogpartinfo --list-devices 2>/dev/null`;
#this will either give us something or nothing
if [ -z "$testdisk" ]; then
  echo;
  read -r -p "Partition error. Do you want to murder the partition table for $hd? [y/N] " response
  if [[ $response =~ ^([yY][eE][sS]|[yY])$ ]]
  then
    #murder the partition table - this shouldnt need a restart
    dd if=/dev/zero of=$hd bs=512 count=1 conv=notrunc;
    #label the emptiness - should be enough to get the system to continue
    parted $hd --script -- mklabel msdos;
  fi
else
 echo "checked $testdisk for partitions (no need to kill partition table yet)";
fi

I put this before the imgtype checks

# Generates the partitions.  If singledisk resizeable, it generates
# based on default normal values.
# Otherwise it uses MBR/GPT to generate the partition table(s).

After that I get a VERY healthy speed increase (PIGZ 7 uploaded on a 4core 4gb @ about 1gb/min). This client is a modest 3ghz Core2Duo with 2gb RAM.

Testing was done on multiple brands of HDD and 2 brands of SSD reproducible. If the drive had already been cloned (some had been cloned from previous upgrades) then the system worked without my fudge. If the drive was brand spanking new out of the packet then there was a chance this would happen (both sandisk and Kingston SSDs were totally blank, the Seagate was blank but the WD was not and worked without the fudge)

Trunk still fails. Exactly the same error. I can fix it if I MANUALLY run the same bit of script I do below but im currently navigating my way around the new init.xz layout. Funcs.sh has changed completely so i’ll have to learn how the new structure works. Either way I am going to add my hack to get completely blank drives to work, when I do i’ll post it up. Trunk is almost working for me…

I used CENTOS 6.7 in a hyper-v host.

• Don’t forget to disable SELinux
• Domain 2202 errors (for me) was due to me upgrading from 0.32 - the domain password was correct but the username drops the DOMAIN portion of DOMAIN\USERNAME so basically drop the domain\ part
• Whilst the above is CORRECT for fixing 2202 errors what I didn’t do was update each host. It isn’t enough to simply change the master AD credentials - they will only affect NEW registrations. The existing registrations have one per host. We have 278 hosts and our apprentice wasn’t relishing the prospect of going into each one. What I did instead was save a configuration file, edit the SQL and copy the – Table structure for table hosts' and -- Dumping data for table hosts` into a new text (.SQL) file, I did a search and replace on my DOMAIN\ then reimported the SQL from command prompt (thus dropping and recreating the hosts with new AD information). Low and behold no more 2202 errors!
• Blank drives with no partition table barf partclone in 1.2.0 (apparently fixed in trunk). I created a dirty fix that DD the first 512 of the drive then added a simple label using parted partlabel. This fixed partclone for me.
• Multicast didn’t work for me until I truncated the two multicast tables (this is in the wiki).

Overall though 1.2.0 works just fine for me. Now to get trunk running…

I found Ubuntu was not very good in hyper-v although I have never tried it in virtualbox, I had NIC and SMP issues. Centos 6.7 installs as per the instructions in the wiki to the letter - I had no issues copying and pasting commands.

I do have a trunk VM server on stand by but needed to drop back to 1.2.0 - I ran out of time setting it up. My intention IS to use trunk and i’ll try to get some time later on this month. Luckily I have lots of empty drives I can use!

The biggest error I got was 2202 errors joining the domain using client 0.9.5 but I see that a new client is out - perhaps 0.9.6 fixes that. Allegedly 2202 errors are AD errors relating to username and passwords but I have no issues with 0.1 client on 1.2.0 (and I did try both “legacy” fogcrypt and the new “just type it in” passwords in trunk).

give me a week and i’ll get back onto trunk.

ok a simple fix that has worked for me. Using https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image as a reference to edit init.xz In funcs.sh I have altered gethardisk() as follows (since CAT works for me I have added it to the CAT function after fogpartinfo). I basically murder the partition table with “dd” then add a label, that should be enough to cure my blank drive issues anyway.

Lets check and see if the partition shows up in /proc/partitions

	for i in hda hdb hdc hdd hde hdf sda sdb sdc sdd sde sdf; do
		strData=`cat /proc/partitions | grep $i 2>/dev/null`;
		if [ -n "$strData" ]; then
			hd="/dev/$i";
                            #** this is the new bit **
			echo;
			read -r -p "Partition error. Do you want to murder the partition table for $hd? [y/N] " response
			if [[ $response =~ ^([yY][eE][sS]|[yY])$ ]]
			then
				#murder the partition table - this shouldnt need a restart
				dd if=/dev/zero of=$hd bs=512 count=1 conv=notrunc;
				#label the emptiness - should be enough to get the system to continue
				parted $hd --script -- mklabel msdos;
			fi	
                            #** end of the new bit **
			return 0;
		fi 
	done

I am going to butcher gethardisk() in funcs.sh and force it to remove and repartition (with a read case of course), rebooting as necessary and carry on. Not exactly friendly for other people but it will work for me (hopefully!).

whilst fogpartinfo --list-devices barfs the next CAT portion DOES return /dev/sda but the next partitioning section in fog.download doesn’t work (even with debugpause things don’t become clearer). I suspect that if I can clear partitions, create a “simple” FAT32 partition and reboot then things might work out. Watch this space…

I have just remoted in and you are correct. I used gparted live to create a simple fat32 partition and it worked, I now have a trunk upload and download working. Now I only have to sort out the 2202 error joining the domain using the trunk fog service client (hostname changer and domain join works fine in the 1.2.0 server and whatever fog service comes from that version) but since Ive been hogging the forums recently i’ll give someone else a go as I really cant give any more time at the moment!

Don’t worry, when I have all this up and running I will do a writeup on how I got Centos 6.7 working with fog trunk! (if only for my own notes when I search the forums in another year time…)

Luckily we have an apprentice who will love to run gparted live on the 114 SSDs we are priming for our 8.1 rollout next January

@Sebastian Roth I have moved back to 1.2.0 but can guess what the results would have been - the HDD would have had 2 partitions, 1xW7 reserved, 1x primary NTFS. The SSD was fresh out of the packet so I guess would have had nothing (no partitions). The hyper-v host was a freshly created VHDx so again would have had no partitions on there.

I’ll try and remote in tonight and play a little more, i’ll post back more concrete results if I can.

shut down my SVN trunk server host and booted my 1.2.0 back up. This images to a physical and hyper-V client fine so I’m knocking trunk on the head for the time being as I cant devote any more time to it. I agree that it makes no sense as I imagine the front end hasn’t actually changed much. I must have made some sort of mistake installing trunk, i’ll dig it out again at Christmas when I get more time and start (again) from scratch.

host VM is a freshly minted empty VHDX and the physical is its own existing HDD that has been imaged before (I keep reimaging over the top as necessary) and ive also tried a “removed from packet” SSD too. golden sample is made on an 80gb fixed disk size (image is about 40gb) and we only reimage to >80gb drives anyway. I have a script in windows that resizes the partition after OOBE.

Im reuploading the image now from the golden sample and will see if somehow the image was corrupted along the way or PIGZ was changed (does this invalidate the image? clutching at straws now)

Uploaded a fresh image from hyper-v ok. When attempting to push the image to a client (physical and hyper-v tested - same issue) the push doesn’t happen. This is the full screen as shown (there is slight 2 second pause at "stopping FOG status reporter)

I have checked permissions in the /images they are fog.root as expected. The /images contains my W7VBOX3 folder with d1xx.img inside again with fog.root permissions. CHMOD is 777 throughout /images

The upload went without a hitch. I even passwd fog to a different password (updating the Config.class.php and GUI as appropriate) with no difference (didn’t think so as it uploaded ok).

any ideas?