@jdd49 The image seems to have worked now after rebooting the Hypervisor this morning, though I’m now getting the following error message when trying to boot the VM:
I’ve recreated the VHD on a different Hypervisor and still run into the same issue. Annoyingly (but also thankfully), the actual physical machine I’m trying to virtaulise runs perfectly fine and doesn’t have this issue.
Below are the results for running smartctl -a /dev/sda:
You can also see what kernel I’m using on the FOG server in that screenshot.
The /images directory is on the one drive, so that’s probably why I couldn’t couldn’t unmount the device.
Hyper-V is currently running on a Dell Windows Server 2012 R2 server with the latest updates.
@sebastian-roth Thanks!
How do I go about using smartctl?
It complains it can’t detect the device type, and when selecting the -d option, I get a load of options. I’ve tried setting this to -ata and scsi, but these all come back saying there is no such device.
I have also tried running fsck after unmounting the drive, but then that complains the drive is still mounted (it isn’t… it’s clearly lying or being stupid), and says that continuing will destroy data, etc.
FOG Details:
Running Version 1.5.0-RC-8
SVN Revision: 6080
Hi all,
I have a problem at the moment where I’m trying to image a Hyper-V VM, and it gets to about 40/45% and then suddenly the rate of the network connection starts going down, with no percentage increase at all. I’ve checked the FOG server itself and it reports it’s not sending out any packets (this is looking at the home page graph).
I’ve tried this numerous times and keep running into the same thing. There are no network connection issues in our network at the moment aside from this.
Has anyone else experienced a similar issue? What would be the recommended way of diagnosing this?
Any help would be greatly appreciated as usual 
Thanks all - will hopefully get back to you next week with some of my findings (busy days…)
Hi all,
I have an issue with one of my scripts called fog.postclient which will create the directory “/ntfs/Windows/Setup/Scripts/” and then copy across the FogService.msi into it, as well as various other things (like moving the Sophos installer across, etc.). This has worked perfectly fine in the past with no issues whatsoever, and nothing has been changed in the script. Fog.Postdownload calls two scripts: fog.postclient, and fog.postdrivers. The drivers script works great.
However, I’ve found recently that nothing in the fog.postclient works. Going by past experience and the recommendations here, I set a spare laptop to image as a debug task. When in debug mode, I call fog.postdownloads and it complains that it can’t see the postdrivers script. I get the error:
./fog.postdownload: line 7: .: fog.postdrivers: file not found
Yet when running the fog.postclient script, it seems to work as it echoes ‘Non-Windows Deployment’ (which is a part of the script), but nothing else works - it doesn’t create the directory, or copy across the .msi file.
The aforementioned scripts are below. I would appreciate any assistance/guidance on this issue.
fog.postdownload:
#!/bin/sh
## This file serves as a starting point to call your custom postimaging scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post download scripts are
#. ${postdownpath}<SCRIPTNAME>
. ${postdownpath}fog.postdrivers
. ${postdownpath}fog.postclient
fog.postclient:
#!/bin/bash
. /usr/share/fog/lib/funcs.sh
case $osid in
5|6|7|9)
clear
[[ ! -d /ntfs ]] && mkdir -p /ntfs
getHardDisk
if [[ -z $hd ]]; then
handleError "Could not find hdd to use"
fi
getPartitions $hd
for part in $parts; do
umount /ntfs >/dev/null 2>&1
fsTypeSetting "$part"
case $fstype in
ntfs)
dots "Testing partition $part"
ntfs-3g -o force,rw $part /ntfs
ntfsstatus="$?"
if [[ ! $ntfsstatus -eq 0 ]]; then
echo "Skipped"
continue
fi
if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then
echo "Not found"
umount /ntfs >/dev/null 2>&1
continue
fi
echo "Success"
break
;;
*)
echo " * Partition $part not NTFS filesystem"
;;
esac
done
if [[ ! $ntfsstatus -eq 0 ]]; then
echo "Failed"
debugPause
handleError "Failed to mount $part ($0)\n Args: $*"
# Give the reader a chance to see what the error was
sleep 12;
# Terminate the post install script
exit 1;
fi
# This next section determines the IP of the host system, cuts the last two octects and sets the FOGIP variable to
# the correct IP address of the FOG server depending on the location (as the subnets are designed by location - i.e.
# 10.1 is for the UK, 10.2 is for the US, etc.)
myip=$(ip route get 8.8.8.8 | awk 'NR==1 {print $NF}' | cut -d "." -f1-2)
case "${myip}" in
10.1)
sitecode="UK";
timezone="GMT Standard Time";
FOGIP="10.1.0.102";
sitelocal="en-GB";
uilang="en-US";
;;
10.2)
sitecode="US";
timezone="Eastern Standard Time";
FOGIP="10.2.1.103";
sitelocal="en-US";
uilang="en-US";
;;
*)
# Default code for the unknowns - we set the FOGIP to the development server in the UK.
sitecode="CompanyName";
timezone="Greenwich Mean Time";
FOGIP="10.1.0.102";
sitelocal="en-GB";
uilang="en-GB";
;;
esac
# Check if the direcotry /ntfs/Windows/Setup/Scripts exists, and if not then create it.
if [ ! -d "ntfs/Windows/Setup/Scripts" ]
then
mkdir /ntfs/Windows/Setup/Scripts
fi
# Copy the FOGService.msi across to the target computer.
[[ -f ${postdownpath}FOGService.msi ]] && cp ${postdownpath}FOGService.msi "/ntfs/Windows/Setup/Scripts/FOGService.msi"
# Check if the file SophosInstaller.exe exists in the source folder and then copy it to the destination on
# the C: drive.
if [ -f "/images/drivers/Common/SophosInstall.exe" ]; then
cp /images/drivers/Common/SophosInstall.exe /ntfs/Windows/Setup/SophosInstall.exe
fi
# Check if the file SetupComplete.cmd exists in the source folder and then copy it to the destination on
# the C: drive.
if [ -f "/images/drivers/Common/SetupComplete.cmd" ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
# append the msiexec command to the end of the setupComplete.cmd file
echo "msiexec.exe /i %windir%\Setup\Scripts\FOGService.msi /quiet USETRAY=\"0\" WEBADDRESS=\"${FOGIP}\" " >> /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
# Re-enable the FOGService
echo "sc config FOGService start= auto
del /Q /F c:\windows\system32\sysrep\unattend.xml
del /Q /F c:\windows\panther\unattend.xml
shutdown -t 0 -r" >> /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
# just in case we edited the setupcomplete.cmd file in unix lets filter it to make it DOS compatible
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
# now lets use the timezone variable and update the unattend.xml file. You may need to edit the variable to
# point to where your unattend.xml file exists. Remember case IS important.
unattendfile="/ntfs/Windows/Panther/unattend.xml";
sed -i -e "s#<TimeZone>\([^<][^<]*\)</TimeZone>#<TimeZone>$timezone</TimeZone>#gi" $unattendfile
# now lets deal with the internationalization stuff in the unattend.xml file
sed -i -e "s#<InputLocale>\([^<][^<]*\)</InputLocale>#<InputLocale>$sitelocal</InputLocale>#gi" $unattendfile
sed -i -e "s#<SystemLocale>\([^<][^<]*\)</SystemLocale>#<SystemLocale>$sitelocal</SystemLocale>#gi" $unattendfile
sed -i -e "s#<UILanguage>\([^<][^<]*\)</UILanguage>#<UILanguage>$uilang</UILanguage>#gi" $unattendfile
sed -i -e "s#<UserLocale>\([^<][^<]*\)</UserLocale>#<UserLocale>$sitelocal</UserLocale>#gi" $unattendfile
;;
*)
echo "Non-Windows Deployment"
debugPause
return
;;
esac
Edit: Also, before I get asked, the FOG version is the following:
Running Version 1.5.0-RC-8
SVN Revision: 6080
@george1421 Thanks, George.
This turned out to be an issue with the dnsmasq update. We have now updated to the latest version (following a full removal of dnsmasq), and had to edit the /etc/dnsmasq.conf file to include the DHCP range again.
@george1421 Even after updating I still have the same thing, despite maintaining the exact same settings as before, and it is now affecting the hardware also, unfortunately.
When attempting to boot from the network in either UEFI or Legacy mode, I see the following:
Auto-Select:
Boot BIOS PXE
PCE-E78: could not locate boot server
@george1421 Ah, that could be it… it’s showing as 2.68. I’ll try updating it and see how it goes.
FOG Version: 1.5.0-RC-8.
SVN Revision: 6080
Hi all,
We’re currently having a problem with our FOG server where we can’t boot Generation 2 VMs over the network. We’ve turned off secure boot, and strangely enough, it did work the other night when we wanted to upload a newly built image. Now, however, it doesn’t work, and we’re not entirely sure why. We’ve reviewed what has changed and the answer is nothing - we had to restore FOG from a Veeam Backup the other day as a similar thing happened, but no machine could boot from the network. It only appears to be effecting Generation 2 VMs in Hyper-V, rather than everything.
We see the following message:
I wonder if this has something to do with DNSMasq somehow breaking? I know there was a major update for it the other day, but we haven’t run any updates. Is there anything we could check?
Any help with this would be appreciated.
@george1421 It all uploaded perfectly fine the other day - thanks
@george1421 It turned out there was a space in my Unattend.xml file where I was setting the computer name to: RENAME.
I’ll have to create a generation 2 Hyper-V VM to see if I can get it to upload to UEFI.
@george1421 Thanks, George.
The Specialize section is as follows:
<settings pass="specialize">
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-SQMApi" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<CEIPEnabled>0</CEIPEnabled>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<WindowsFeatures>
<ShowMediaCenter>false</ShowMediaCenter>
<ShowWindowsMail>false</ShowWindowsMail>
</WindowsFeatures>
<ShowWindowsLive>false</ShowWindowsLive>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<BluetoothTaskbarIconEnabled>true</BluetoothTaskbarIconEnabled>
<ComputerName>RENAME </ComputerName>
<CopyProfile>true</CopyProfile>
</component>
I can’t see anything immediately obvious… unless there’s an issue with the copy profile being set to true.
@george1421 Thanks very much!
So I’ve just tried this today and I’ve found that something has gone weird with my Unattend.xml file. I suspect it’s something to do with the Windows 10 Creator’s Update, and I need to update some of my settings, but after running sysprep and rebooting the VM, I get the following error message:
“Windows could not parse or process the unattend answer file for pass [specialize]”.
Has anyone else run into this? I can post my Unattend.xml file if that helps.
@george1421 Ah, thanks. I’m building it in hyper-v, so I don’t think there is anything like that I need to change, though I could be wrong (it did work before without any changes to systems running in UEFI mode).
@george1421 Thanks for running those tests, George - interesting conclusions. I found that I was able to boot into the system when I changed into Legacy mode, so perhaps something went wrong when uploading the image in the first place. I’m currently applying the Creator’s update to the image on a VM, after which I shall sysprep and upload it once more to FOG. I should be able to test the deployment again later today.
@george1421 Sorry to resurrect this thread - unfortunately, this is still an issue.
To update everyone, I’m currently running: Ubuntu 14.04 server hosting FOG.
The FOG version is 1.5.0-RC-8.
The SVN Revision is: 6080.
There seems to be something wrong on the BIOS level after applying the image: it no longer detects the UEFI hard drive. It detects it perfectly fine before the image in UEFI mode, but then I only see two options: “Onboard NIC (IPV4)”, and “Onboard NIC (IPV6)”. If I plug in the Windows 10 USB that came with the laptop, I see a third also: “UEFI: Dell Recovery USB 1100, Parititon1”.
So, what can I check/test or run to prevent this from happening in the future? Why does the hard drive disappear after applying the image? Are there any logs I can get to help determine the cause of this issue.
As always, any help with this would be greatly appreciated.
@george1421 Still no joy, even after updating again and running through the steps previously linked. I’ll try and boot from the CD and go from there.
@george1421 Yep, that’s what I thought but wanted to check I wasn’t going insane.
I’ll take a snapshot of my FOG server and try the above mentioned fix in the article you linked.
@george1421 Thanks, George. I’m just reviewing this now, and I’ve created a test image with all of the drivers (Dell 7280 and Win10PE) installed. I haven’t sysprepped it either (though I don’t expect that to make much of a difference).
After the system has been imaged, it still says there are no boot devices. Interestingly, when I press F12 to go into the one-time boot menu, the hard drive isn’t even listed! I just have IPV4, IPV6 and the DVD USB drive with the Windows 10 disc (in preparation for your aforementioned steps).
It’s using UEFI mode to boot and I can see the drive is enabled in the BIOS (though it also doesn’t appear when choosing the boot sequence). I’ve set the SATA Operation to AHCI mode (it was on RAID on before). Is there anything else I could check? Or am I chasing a red herring and the hard drive shouldn’t appear in the UEFI one-time boot menu?