Ghost Solution Suite

Hi all,

I have a problem with ghosting at the moment.


I can create an image from a pc fine with ghostcast within about 30min.


When I try to restore the image to the same pc or to another pc with the same
hardware the transfer rate for the MB that it copies is so slow.


When I create the image it transfers, anyway from 200mb to 400mb.


But when I restore the image it only transfers from 0mb to 10mb max
then times out on the ghostcast server


Why am I able to create an image fine with no problems but cannot
restore the image.


I have included the report log for when i try to restore the image below (sorry its so long but i have shortened the log)

Log Level All
632947828 GhostSrv 8.3.0.1331
Mon Oct 23 16:57:49 2006

632953843 Initialising RML
rml_get_local_interfaces found these IP addresses:
192.168.0.12
RML Initialised
RML socket send buffer size set to 549504
Setting UDP socket receive buffer size to 20034
UDP socket receive buffer size set to 20034
RML socket receive buffer size set to 17172
632953859 Throttle value:0 mb/min
Length of tick in seconds:0.001000
Ticks per throttle bucket:15
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle value:0 mb/min
Length of tick in seconds:0.001000
Ticks per throttle bucket:15
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
RML socket send buffer size set to 4194304
Server multicast address set to 224.77.66.172
Throttle value:0 mb/min
Length of tick in seconds:0.001000
Ticks per throttle bucket:15
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Bound RML socket to 0.0.0.0:3244
Setting multicast scope to 16
State was 0, now 1
Bound TCP socket to 0.0.0.0:3245
Bound UDP socket to 0.0.0.0:6666
Interface 192.168.0.12 (0) ws2AddMembership succeeded
632959546 R: LEN: <277> SESSION: <test> FROM: <192.168.0.25:1025>
S: LEN: <260> SESSION: <test> TO: <192.168.0.25:1025>

632964546 Wait(0) returned (RW) after 0 ticks

R: SYN SEQ=0 ACK=0 WIN=17172 LEN=39 ADDR=192.168.0.25:7777
Recv would block
Setting UDP Socket to allow broadcasts
Telling client (192.168.0.25) to use Directed Broadcast data transfer mode

S: SYN ACK TAK SEQ=0 ACK=1 WIN=17172 LEN=41 ADDR=192.168.0.25:7777
Sent second packet unicast
State was 1, now 3

Wait(1000) returned (R) after 0 ticks

R: ACK TOK SEQ=1 ACK=1 WIN=17172 LEN=4 ADDR=192.168.0.25:7777
State was 3, now 4
State was 4, now 1
Recv would block

Wait(0) returned (R) after 0 ticks

R: ACK TOK SEQ=1 ACK=1 WIN=17172 LEN=266 ADDR=192.168.0.25:7777
Recv would block

632965531 Wait(0) returned (R) after 0 ticks

R: ACK TOK SEQ=1 ACK=1 WIN=17172 LEN=266 ADDR=192.168.0.25:7777
UDM Destination count now 1
Directed Broadcast: 192.168.0.255:7777 0.0.0.0

S: ACK SEQ=1 ACK=267 WIN=16906 LEN=0 ADDR=
Recv would block
632969546 State was 1, now 4

S: ACK SEQ=1 ACK=267 WIN=17172 LEN=10 ADDR=
Timing of 1 commenced

Wait(1000) returned (R) after 0 ticks

R: ACK TOK SEQ=267 ACK=11 WIN=17172 LEN=0 ADDR=192.168.0.25:7777
Congestion window 1441
RTT for 1 is 8 ticks
Retransmit timeout 32 = 8 + 4 * 4

R: ACK TOK SEQ=267 ACK=11 WIN=17172 LEN=22 ADDR=192.168.0.25:7777
Recv would block

S: ACK SEQ=11 ACK=289 WIN=17172 LEN=18 ADDR=
Timing of 11 commenced

Wait(32) returned () after 0 ticks

Wait(32) returned (R) after 16 ticks

632969562 R: ACK TOK SEQ=289 ACK=29 WIN=17172 LEN=14 ADDR=192.168.0.25:7777
Congestion window 1459
RTT for 11 is 24 ticks
Retransmit timeout 36 = 9 + 4 * 6
Recv would block

S: ACK SEQ=29 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 29 commenced

Wait(36) timed out after 47 ticks
632969609 Retransmit timeout
Slow start threshold 2862
Congestion window 2862

S: ACK SEQ=29 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 29 abandoned

S: ACK SEQ=1460 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 1460 commenced

Wait(72) returned (R) after 0 ticks

R: ACK TOK SEQ=303 ACK=1460 WIN=17172 LEN=0 ADDR=192.168.0.25:7777
Congestion window 3577
Recv would block

S: ACK SEQ=2891 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(36) returned (R) after 0 ticks

R: ACK TOK SEQ=303 ACK=4322 WIN=17172 LEN=0 ADDR=192.168.0.25:7777
Congestion window 4149
RTT for 1460 is 8 ticks
Retransmit timeout 32 = 9 + 4 * 5
Recv would block

S: ACK SEQ=4322 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 4322 commenced

S: ACK SEQ=5753 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(32) returned (R) after 0 ticks

R: ACK TOK SEQ=303 ACK=7184 WIN=17172 LEN=0 ADDR=192.168.0.25:7777
Congestion window 4642
RTT for 4322 is 8 ticks
Retransmit timeout 32 = 9 + 4 * 5
Recv would block

S: ACK SEQ=7184 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 7184 commenced

S: ACK SEQ=8615 ACK=303 WIN=17172 LEN=1431 ADDR=

S: ACK SEQ=10046 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(32) returned (R) after 0 ticks

R: ACK TOK SEQ=303 ACK=10046 WIN=14357 LEN=0 ADDR=192.168.0.25:7777
Congestion window 5083
RTT for 7184 is 8 ticks
Retransmit timeout 32 = 9 + 4 * 4
Recv would block

S: ACK SEQ=11477 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 11477 commenced

S: ACK SEQ=12908 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(32) returned (R) after 0 ticks

R: ACK TOK SEQ=303 ACK=11477 WIN=17172 LEN=0 ADDR=192.168.0.25:7777
Congestion window 5485
Recv would block

S: ACK SEQ=14339 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(32) timed out after 47 ticks
632969656 Retransmit timeout
Slow start threshold 2862
Congestion window 2862

S: ACK SEQ=11477 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 11477 abandoned

S: ACK SEQ=12908 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(64) timed out after 78 ticks
632969734 Retransmit timeout
Slow start threshold 2862
Congestion window 2862

S: ACK SEQ=11477 ACK=303 WIN=17172 LEN=1431 ADDR=

S: ACK SEQ=12908 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(128) timed out after 141 ticks
632969875 Retransmit timeout
Slow start threshold 2862
Congestion window 2862

S: ACK SEQ=11477 ACK=303 WIN=17172 LEN=1431 ADDR=

S: ACK SEQ=12908 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(256) returned (R) after 171 ticks

632970046 R: ACK TOK SEQ=303 ACK=14339 WIN=17172 LEN=0 ADDR=192.168.0.25:7777
Congestion window 3577

R: ACK TOK SEQ=303 ACK=15770 WIN=15756 LEN=0 ADDR=192.168.0.25:7777
Congestion window 4149

R: ACK TOK SEQ=303 ACK=15770 WIN=15756 LEN=0 ADDR=192.168.0.25:7777
Recv would block

S: ACK SEQ=15770 ACK=303 WIN=17172 LEN=1431 ADDR=
Timing of 15770 commenced

.......................................................................................................................

then at the end of the log i get this........


Wait(1000) timed out after 1000 ticks

633546156 Wait(1000) timed out after 1000 ticks

633547156 Wait(1000) timed out after 1000 ticks

633548156 Wait(1000) timed out after 1000 ticks

633549156 Wait(1000) timed out after 1000 ticks

633550156 Wait(1000) timed out after 1000 ticks

633551156 Wait(1000) timed out after 1000 ticks

633552156 Wait(1000) timed out after 1000 ticks

633553156 Wait(1000) timed out after 1000 ticks

633554156 Wait(1000) timed out after 1000 ticks

633555156 Wait(1000) timed out after 1015 ticks

633556171 Wait(1000) timed out after 1000 ticks

633557171 Wait(1000) timed out after 1000 ticks

633558171 Wait(1000) timed out after 1000 ticks

633559171 Wait(1000) timed out after 1000 ticks

633560171 Wait(1000) timed out after 1000 ticks

633561171 Wait(1000) timed out after 1000 ticks

633562171 Wait(1000) timed out after 1000 ticks

633563171 Wait(1000) timed out after 1000 ticks

633564171 Wait(1000) timed out after 1000 ticks

633565171 Wait(1000) timed out after 1000 ticks

633566171 Wait(1000) timed out after 1000 ticks

633567171 Wait(1000) timed out after 1000 ticks

633568171 Wait(1000) timed out after 1000 ticks

633569171 Wait(1000) timed out after 1000 ticks

633570171 Wait(1000) timed out after 1000 ticks

633571171 Wait(1000) timed out after 1000 ticks

633572171 Wait(485) timed out after 500 ticks
633572671 Retransmit timeout
Slow start threshold 2862
Congestion window 2862
Retransmit timeout 56 = 0 + 4 * 14

S: ACK SEQ=556688 ACK=303 WIN=17172 LEN=1431 ADDR=

S: ACK SEQ=558119 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(1000) timed out after 1000 ticks

633573671 Wait(1000) timed out after 1000 ticks

633574671 Wait(1000) timed out after 1000 ticks

633575671 Wait(584) timed out after 594 ticks
633576265 Retransmit timeout
Slow start threshold 2862
Congestion window 2862
Retransmit timeout 56 = 0 + 4 * 14

S: ACK SEQ=556688 ACK=303 WIN=17172 LEN=1431 ADDR=

S: ACK SEQ=558119 ACK=303 WIN=17172 LEN=1431 ADDR=

Wait(1000) timed out after 1000 ticks

633577265 Wait(1000) timed out after 1000 ticks

633578265 Wait(1000) timed out after 1000 ticks

633579265 Wait(1000) timed out after 1000 ticks

633580265 Wait(1000) timed out after 1000 ticks

633581265 Wait(1000) timed out after 1000 ticks

633582265 Wait(1000) timed out after 1000 ticks

633583265 Wait(168) timed out after 172 ticks
633583437 Retransmit timeout
State was 4, now 12
rml_wait failed: connection aborted
RMLSend failed: Software caused connection abort.
rml_wait failed: connection aborted

S: RST SEQ=559550 ACK=303 WIN=0 LEN=0 ADDR=192.168.0.25:7777
ConnectionState was 4, now 12


RML Statistics

Retransmits on Request: 21
Retransmits on Timeout: 120
No Response Timeouts: 8
Token Switches: 7
Token Switch Retries: 35

End RML Statistics

Shutting down RML
RML shutdown

Log Level None



please can someone tell me what i am doing wrong.

thanks in advance

Karl Thompson

Hi Karl,

From the attached log, it seems like if you are doing directed broadcast.
Can you see if unicast is also having the slowness problem?
You can force ghostcast server to use unicast through the options menu.

If unicast is slow too then I would say the problem is more likely to be related to the machine you are imaging.
What is the spec of the machine? Especially the network card?
What DOS network driver are you using?

Cheers

Chris

Hi Chris,

Thanks for getting back to me.

Yes the log is from doing a Directed Broadcast, but I have also tried unicast and multicast but still does the same. i have also force ghostcast server to use all 3 but still no difference.

The machine is a Lenovo, as for the spec of the machine,

P4 2.80GIG with 512mb.

Network card is a Realtek RTL8139

And I am using the drives for the Realtek RTL8139 that is already on the Ghost Boot Wizard.

Is there any more information that you need?

Regards

Karl

Hi Chris,

I think i have solved my problem.

With this pc been a client pc i didn't even take the cover off the machine.

I have taken the case off the pc and noticed that they have SATA drives.

I was looking through the switches for ghost and noticed that there is a switch for no ide. So i entered the switch and to my suprise it restores the image within 15 - 20 mins.

if i use the same process using unicast and the noide switch would this work to ghost the full network (30 - 50 pcs) or would i need to change something.

also please can you tell me what/difference is between directed broadcast, multicase and unicast.

Thanks for your help Chris,

Regards

Karl

Hi Karl,

Glad the switches worked for you. I've learnt something too. :)

If you have 30 to 50 pcs you want to image in one sitting, you probably wouldn't want to use unicast.

unicast is essentially a 1 to 1 transfer between server and client, another words, the image would be sent out once for each client machine participating in the restore operation.

If all your machines are on the same subnet, you can try directed broadcast. Directed broadcast broadcasts the image to an entire subnet (eg. 192.168.0.255), all the machines on the subnet will recieve it. So the upside is that the image is only broadcasted once for each subnet. The downside is that other machines on the same subnet that aren't participating in the restore operation will also see all the network traffic.

With multicast, the image is only sent out once, to a multicast address. Regardless of the number of clients connected and the number of different subnets that the image has to be sent to.
A multicast address is a designated IP address in the range of between 224.0.0.0 to 239.255.255.255, a machine has to "sign up" to receive this traffic, otherwise it wouldn't. The router is responsible for keeping a register of the computers that have signed up to receive multicast traffic at specific multicast addresses. It will decide how to forward the network packets so that all the "signed up" machines will receive the packet, even if they are on different subnets.
The downside to multicast is that if you have a slow router, your restore operation speed will be impacted.


I guess you should try either broadcast or multicast in your network environment, and decide which one works out better for you.

Hope that helps.

Cheers

Chris

Hi Chris,

Thanks for your help. This will come in very helpful in the future and glad you have learned something as well.

Again thanks for your help

Regards

Karl