Ghost Solution Suite

Hello,

I have searched everywhere but cannot resolve this annoying issue I am having here.

I run symantec ghost 8.3 on it's own dedicated server. I do all of my imaging over the network PXE booting into ghostcast server.

I have a win2k3 standard image for an HP dl145g2 server. I've pushed it to 5-6 other servers with no issues.

The dl145 boots into the ghost session fine. I select unicast and the server info, click send from the server and it starts going nice and fast. Once the dl145 gets to around 15% it completely freezes and i Have to do a hard reset on the server via iLo.

The bottom of the client screen says "Restoring... remaining NTFS MFT files."

The message I receive in ghostcast server is "Connection timed out." and all I can do is click OK.

-I have verified that image is not corrupt
-I tried pushing another image to the client and it "froze" at the exact same progress point
-I tried pushing another image to a different client and it worked beautifully

Any help would be greatly appreciated.

Thanks.

Hi Jordan,

Can you please give me more information about the type of hard disk (SCSI, SATA, IDE) and the network card you have on the client?


Adina

It has a single 80GB Maxtor 6Y080M0 drive. The NIC is a Broadcom NetXtreme Gigabit Ethernet.

Have 10 identical servers that I have pushed this image to with no problem.

Thanks.

Hi Jordan, I'm not expert in this particular area, but I'll give it a single shot in case its useful to you. Its a long shot, I realise you have successfully configured several identical machines.

I have found the broadcom netxextreme series to be sensitive to the driver version used. In the past I've had similar issues when using a unified driver from the broadcom site which were later resolved by using the driver obtained from the OEM hardware manufacturers site.

Eg; If the machine is an HP123 obtain the network driver for the HP123 machine from hp.com.

Hi Jordan,

We have seen that in certain situations the hard disk and the network card use the same IRQ and this generates a conflict.

Other than that, some suggestions would be:
1) try to boot the computers that have this problem using a different method other than PXE (a USB key, for example);
2) can you try to use a different switch port?
3) check if the BIOS settings are the same for the computers that complete the clone and for those that don't.


Adina

Thanks for both of your replies. I actually was about to do a side-by-side comparison of the bios settings and just decided to try imaging the server again (for the 15th time at least). It worked beautifully.....I guess all it needed was a weekend of not being touched, haha.

Thank you.