Next i would test that the WOL script is being called correctly.
On the FOG server 172.17.14.206, run:
[code]tail -f /var/log/apache2/access.log[/code]
Now execute a WOL, you should see the WOL call in this access log. If you dont, then the call is never getting to Apache.
[I]NOTE: You will see other URL calls here from FOG / FOG Clients… make sure you are looking at the right IP[/I]
[I]Please note: This is an advanced topic and requires basic Linux knowledge. These examples only provide information on how my system was configured.[/I]
Using the following setup i can unicast 15-20 machines at full speed (per node, 40 in total with 2 nodes). Unicast speeds range from 5.5gb/minute (~90mb/sec) to 3gb/minute (~50mb/sec). Normally it is much faster to unicast over multicast due to multicast’s fiddly deployments.
[SIZE=4][B]FOG VM Controller[/B] - FOG-1[/SIZE]
[LIST]
[]Stores no images, only used for a controller
[]Debian
[]5gb HDD
[]1gb RAM
[/LIST]
[SIZE=4][B]FOG Storage Nodes[/B] - FOG-2 & FOG-3[/SIZE]
[LIST]
[][B]General[/B]
[LIST]
[]These machines are custom white boxes, they were left over workstations which were turned into FOG storage nodes. Nothing fancy here.
[]CPU: E8400 Core2Duo
[]Motherboard: Intel DG35EC
[]RAM: DDR2 4gb - overkill really
[]OS Drive: 80gb Western Digital Green - Image storage is on the RAID array below
[/LIST]
[][B]Network[/B]
[LIST]
[]2x Intel 82574L PCIe 1gb network cards - bonded
[]Uses package ‘ifenslave’ (apt-get install ifenslave)
[]Bond Mode 0 - mode 4 (802.3ad) works [I]slightly[/I] better, but requires switch support
[]eth1 & 2
[]eth0 still has a cable in case something happens to the bond, the server can still be accessed remotely
[*]interfaces
[code]fog-2:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface eth0 inet dhcp
allow-hotplug bond0
auto bond0
iface bond0 inet static
address 10.10.8.55
netmask 255.0.0.0
gateway 10.10.10.10
slaves eth1 eth2
bond-mode 0
bond-miimon 100
pre-up ifdown eth0
post-down ifup eth0
[/code]
[*]module setup - not sure if this is still required with the new ifenslave method
[code]fog-2:~# cat /etc/modprobe.d/arch-aliases
alias bond0 bonding
options bonding mode=0 miimon=100
[/code]
[*]ifconfig (lo removed)
[code]fog-2:~# ifconfig
bond0 Link encap:Ethernet HWaddr 00:1b:21:53:c0:e5
inet addr:10.10.8.55 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::21b:21ff:fe53:c0e5/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:11906 errors:0 dropped:0 overruns:0 frame:0
TX packets:6105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2167156 (2.0 MiB) TX bytes:1736174 (1.6 MiB)
eth1 Link encap:Ethernet HWaddr 00:1b:21:53:c0:e5
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:10145 errors:0 dropped:0 overruns:0 frame:0
TX packets:3053 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1912960 (1.8 MiB) TX bytes:869040 (848.6 KiB)
Memory:e3280000-e32a0000
eth2 Link encap:Ethernet HWaddr 00:1b:21:53:c0:e5
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:1761 errors:0 dropped:0 overruns:0 frame:0
TX packets:3052 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:254196 (248.2 KiB) TX bytes:867134 (846.8 KiB)
Memory:e3180000-e31a0000[/code]
[/LIST]
[][B]Storage[/B]
[LIST]
[]2x 2TB Western Digital Black
[]Non raid edition drives, just the standard blacks
[]RAID 0
[]Software RAID using MDADM
[]Create file systems
[code]mke2fs -t ext4 -b 4096 -m 0 -i 65536 -E stride=64,stripe-width=128 /dev/md0[/code]
Create a partition on md0 as EXT4, 4k block sizes, no root reserved space, 65k inode block sizes
The images will be 1 big massive block of data. Maximizing block and inode sizes reduces overhead at the expense of a little wasted space (if the file partly uses a block).
stride = This is the number of blocks read or written to disk before moving to next disk
stripe_width = This is typically be stride-size * N, where N is the number of data disks in the RAID
If you are unsure of how to calculate stride and stripe_width, there is a handy calculator here: [url]http://busybox.net/~aldot/mkfs_stride.html[/url]
[*]Create MDADM Array
chunk size = 256kb # this could be 512kb, but i have seen no performance increase on this hardware set
A larger chunk size results in less overhead (faster performance) at the expense of wasted disk. The amount of waste will be minimal was we are using EXT4 with preallocate enabled. EXT preallocate has no overhead, where EXT3 must manually zero the files. Get EXT4!!
[code]mdadm --create --verbose /dev/md0 --level=stripe --raid-devices=2 --chunk=256 /dev/sdb1 /dev/sdc1[/code]
[*]MDADM config
[code]
fog-2:~# mdadm --detail --scan >> /etc/mdadm/mdadm.conf
fog-2:~# cat /etc/mdadm/mdadm.conf
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST <system>
MAILADDR root
ARRAY /dev/md0 metadata=1.2 name=fog-2:0 UUID=7ca3e285:ced98dbe:5fb7d2f1:46804423
[/code]
[*]Array status
[code]fog-2:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid0 sdb[0] sdc[1]
3907026944 blocks super 1.2 256k chunks
unused devices: <none>
fog-2:~# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Wed Jun 22 08:14:10 2011
Raid Level : raid0
Array Size : 3907026944 (3726.03 GiB 4000.80 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Wed Jun 22 08:14:10 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 256K
Name : fog-2:0 (local to host fog-2)
UUID : 7ca3e285:ced98dbe:5fb7d2f1:46804423
Events : 0
Number Major Minor RaidDevice State
0 8 16 0 active sync /dev/sdb
1 8 32 1 active sync /dev/sdc
[/code]
[*]Performance - 225.30 MB/sec - cached reads (from the drives cache) will be about 30-40x this speed.
[code]fog-2:~# hdparm -t /dev/md0
/dev/md0:
Timing buffered disk reads: 676 MB in 3.00 seconds = 225.30 MB/sec
[/code]
[/LIST]
[/LIST]
Please note that there is NO data redundancy in this setup. All images in this system are backup via DPM nightly.
Watching each node with ‘vnstat -l -ru’ i can see that each node maxes out around [B]240-260 MB (megabytes)/sec[/B]. This setup easily uses the 2 hard drives to their full potential and would require faster disks and a hardware RAID controller to get more.
This how-to will be left open for questions. Please let me know if you have any questions, or if i have missed something.
Those WOL variables are not in use anymore.
The settings are in: Web UI > Other Information > FOG Settings
Scroll down and look for the WOL settings.
If they are correct, then manually test WOL works.
http://[COLOR=#3366ff]FOG_WOL_HOST[/COLOR]/[COLOR=#3366ff]FOG_WOL_PATH[/COLOR]?wakeonlan=[COLOR=#3366ff]MAC[/COLOR]
Let me know if that works, ive got more things to try.
Did you remove the extended partition? From “Deploy Debug” run & post the results here: [B]fdisk -l[/B]
We (and users) can always post into the ‘How-to’ forum as well.
I’m looking at writing something to scrap the information.
Can you verify that the file exists on your FOG server.
/tftpboot/fog/GM/FLOPPY.IMG
Keep in mind that Linux is case sensitive.
Running this:
[code]ls -la /tftpboot/fog/GM/FLOPPY.IMG[/code]
Should return something like this:
[code]-rw-r–r-- 1 root root 1474560 2007-03-23 00:00 /tftpboot/fog/GM/FLOPPY.IMG[/code]
FOG is a network based solution, where clonezilla is more a media based (CD, USB, etc) solution.
That being said, Clonezilla does have network support.
I’m not sure if a trailing slash is meant to be there or not.
I will look into the standards and hopefully have a change for 0.33. By the sounds of it, the trailing slash should not be there.
Very strange. Can you provide any more information?
If you look in /opt/fog/log/ there is a file called ‘multicast.log’. Also, if a multicast task is running, there will be another log with more information.
Check here for information on multicast troubleshooting: [url]http://fogproject.org/forum/threads/wiki-troubleshooting-multicast.22/[/url]
Is it Windows 7 32bit or 64bit?
Can you please provide a [B]fdisk -l[/B] dump of your images partition setup? Do this in ‘Deploy Debug’
Just to clarify. If you Unicast Image (regular ‘Deploy’) the machines, they will all image simultaneously; using up all available slots.
[url]http://fogproject.org/wiki/index.php?title=Cisco_Multi_Cast[/url]
[SIZE=6]Cisco Multicast[/SIZE]
[url]http://fogproject.org/wiki/index.php?title=Troubleshooting_a_multicast[/url]
[SIZE=6]Troubleshooting Multicast[/SIZE]
On your server open up terminal and kill any running udpcasts by typing
[code]sudo killall udp-sender[/code]
now run this command
[code]udp-sender --file /opt/fog/log/multicast.log --ttl 1[/code]
you should see [I]broadcasting control to:[/I] and it should be the highest address of the subnet your fogserver is on
the line before that should say your fogserver ipaddress and the interface
Now boot up 1 client go to your pxe menu and select debug mode. Do this on the same subnet if possible. Type in:
[code]udp-receiver --mcast-rdv-address yourfogserver[/code]
On your server you should see that 1 client connected and then you can press any key to start the transfer
On your client you should see the contents of your multicast log file scrolling by the screen. You can press ctrl-C to stop it.
Hopefully that worked. Now we need to test 2 clients.
Run the command on your server again but this time change the [I]–ttl 1[/I] to [I]–ttl 32[/I]
You will see that this time your broadcast control is 224.0.0.1 this is the multicast address
Boot both clients in debug mode and run the client command on each. Once you see that both clients have connected to the server press any key and see if the log file transfers again to both machines this time.
If it does not then chances are something is not setup properly in your router possibly routing tables or multicast settings.If it does work then good lets try one more step
On your server run this:
[code]gunzip -c “/images/anyimagename” | /usr/local/sbin/udp-sender --min-receivers 2 --portbase 9000 --interface yourInterface --half-duplex --ttl 32[/code]
Now boot up 2 clients in debug mode and enter
[code]udp-receiver --portbase 9000 --mcast-rdv-address fogserverIP | partimage -f3 -b restore /dev/sda stdin[/code]
You might need to change /dev/sda to your correct harddrive if it’s different use fdisk -l to find out
If the clients start imaging then it seems that all of your multicast settings are correct and the problem may lie within fog configuration if it doesn’t work then you need to check your router settings
[url]http://fogproject.org/wiki/index.php?title=Troubleshooting_an_image_upload[/url]
To make this process easier, we are going to use an Windows XP image.[B] Note that this process has not been tested on Windows 7[/B]. Please also note that this process will change your partitions on the client computer. This tutorial assumes that your disk is /dev/sda1.
[LIST=1]
[]In the management portal, start a debug task for the client computer in question. Allow the client to boot and at the bash prompt type the following commands.
[]mkdir /images
[]mount -o nolock x.x.x.x:/images/dev /images (where x.x.x.x is the server ip)
[]cd /images
[]dd if=/dev/sda of=/mbr.backup count=1 bs=512
[]/usr/local/sbin/ntfsresize -f -i -P /dev/sda1
[]Look for You might resize you will need this number, so write it down. We will call this number NTFSSize.
[]Take NTFSSize and divide it by 1000
[]Now add 300000 to that number and write down as N
[]Now take NTFSSize again and multiply it by 1.1 and then round that to the nearest whole number and write it down as F
[]/usr/local/sbin/ntfsresize -f -n -s Nk /dev/sda1
[](where N is the value calculated above with a k after it.
[]If the test above ends successfully then run:
[]/usr/local/sbin/ntfsresize -f -s Nk /dev/sda1
[]fdisk /dev/sda
[]Press “d”, then Enter
[]Press “w”, then Enter
[]fdisk /dev/sda
[]Press “n”, then Enter
[]Press “p”, then Enter
[]Press “1”, then Enter
[]Press “1”, then Enter
[]Press “+FK”, then Enter (where F is the value calculated above; K must be capital)
[]Press “t”, then Enter
[]Press “7”, then Enter
[]Press “a”, then Enter
[]Press “1”, then Enter
[]Press “w”, then Enter
[]partprobe
[]/usr/local/sbin/partimage save /dev/sda1 /images/dev/[somefile] --volume=9900000000 -z1 -o -d -f3 -b
[]dd if=/mbr.backup of=/dev/sda
[]Press “w”, then Enter
[]partprobe
[]/usr/local/sbin/ntfsresize /dev/sda1 -f -b -P
[*]mv /images/dev/[somefile] /images/[somefile]
[/LIST]
[url]http://fogproject.org/wiki/index.php?title=Troubleshooting_an_image_push_to_a_client[/url]
[SIZE=6]Troubleshooting an Image Deploy[/SIZE]
This process will wipe out whatever is currently present on the client computer.
This tutorial is for FOG .30 pushing Windows XP and assumes that your primary disk is /dev/sda. [B]Note that this process has not been tested on Windows 7.[/B]
[LIST=1]
[]In the management portal, start a debug task for the client computer in question. Allow the client to boot and at the bash prompt.
[](Everything below is done within the bash prompt [B]on the client’s console[/B])
[LIST=1]
[]From your client, mount the remote /images folder on your FOG server onto a local /images folder using nfs:
[]mkdir /images (type this on the client’s keyboard, as explained above)
[/LIST]
[]mount -o nolock x.x.x.x:/images /images (where x.x.x.x is the server ip)
[LIST=1]
[]you may try also mount -t nfs -o nolock x.x.x.x:/images /images
[]Copy the master boot record to the first 512 bytes of the local disk. Take a look into /usr/local/fog/mbr/ to determine the correct MBR for your system. This example uses XP:
[/LIST]
[]cd /images
[LIST=1]
[]dd if=/usr/share/fog/mbr/xp.mbr of=/dev/sda1 bs=512 count=1
[](For previous versions, find the fog directory under:/usr/local/)
[]Start fdisk and remove all previous partitions:
[/LIST]
[]fdisk /dev/sda (Note there is no 1 at the end of the device name)
[LIST=1]
[]Press “d”, then “Enter” - select a partition if prompted and repeat pressing “d”
[]Press “w”, then “Enter” to save and exit fdisk
[]Create a new partition:
[]fdisk /dev/sda
[]Press “n”, then “Enter”
[]Press “p”, then “Enter”
[]Press “1”, then “Enter”
[]Press “1”, then “Enter” or just “Enter” to accept the default starting sector
[]Note: Windows 7 users may want to create a 100M partition, then repeat these steps to create the system partition and assign the rest of the disk to the OS.
[]Press “Enter” to accept the default ending sector
[]Press “t”, then “Enter” to change the partition type
[]Press “7”, then “Enter” for NTFS
[]Press “a”, then “Enter” to toggle the bootable flag
[]Press “1”, then “Enter”
[]Press “w”, then “Enter” to save and exit fdisk
[/LIST]
[]Update the partition info:
[LIST=1]
[]partprobe
[/LIST]
[]Use partimage to copy image from FOG server to local partition:
[LIST=1]
[]/usr/sbin/partimage restore /dev/sda1 /images/[imagename] [B]-f3 -b[/B]
[/LIST]
[]Use ntfsresize to expand partition:
[LIST=1]
[*]/usr/sbin/ntfsresize /dev/sda1[B] -f -b -P[/B]
(For previous versions, find sbin under: /usr/local/)
[/LIST]
[/LIST]
An alternate way to do partimage (which gives more feedback) is to load the gui version of partimage with:
/usr/sbin/partimage, then manually fill in the fields/choose options.