Ghost Solution Suite

Reading through the forum, seeing that lots of other people are getting the same error using the GSS 2.0 console and clients using Broadcom 57xx drivers, is there a solution to fix this? I've tried older versions of the drivers, different vendors drivers, the same as everyone else without any luck at all. Is Symantec aware of this problem?

Error from the client when it boots into the Ghost partition:
"Initializing Packet drive and IP address" then stop with error
Abort 19913, unable to start TCP/IP
can't find DHCP server
possible network setup problem.

In order to find a solution we need to understand more about your system, and methodically distinguish between the different kinds of hardware issues which can cause this symptom.

The first thing to clarify is model (or models) of client machine is having this problem?

Secondly, exactly what network hardware is present in these machines - there are a lot of different chipsets in that Broadcom product range, and it's possible that there is an issue with a specific one, but we need to collate reports from a number of customers if we are going to find a common pattern.

Probably the easiest way for you to find this for us is to open the device properties in a client machine, and find the "Device Instance Id" string and copy it out. Here's a screenshot of where you find this information, and you can copy and paste the value into a forum post so we can look it up; http://nigel.bree.googlepages.com/instance.PNG - so, for my example Marvell NIC, the instance ID is PCI\VEN_11AB&DEV_4320&SUBSYS_811A1043&REV_13\4&13699180&0&6048

Thirdly, we need to determine whether your hardware is suffering from IRQ conflicts in the DOS drivers. In GSS2, we have a tool call irqcfg.exe which you can find in the driver templates directory; this executable can do several things, but for diagnosis you can manually run it on an affected client with the command "irqcfg /summarize" to print out a detailed description of the interrupt configuration in your hardware. If you can direct that to a file and then post it here, we could take a look at that.

Finally, depending on the BIOS, you may be able to configure the machines such that you can use the Universal Network Driver that uses a BIOS-level driver supplied for PXE booting purposes with Ghost. There are several versions of this driver template, one of which also runs the irqcfg.exe tool to try and work around BIOSes that configure clashes between the network and hard disk interrupts. You may have to enable PXE specifically in your client machine BIOS to be able to use the UNDI driver, but this is something additional you can try.

Thank you for your reply. I have found I get the same error on two different Dell models using two different network cards. One is a Dell GX270 using a Intel(R) PRO/1000 MT ethernet card, and the other a Dell GX280 using a Broadcom NetExtreme 57xx ethernet controller. The following is the summary I get from the "irqcfg /summarize" on both Dell models:

Error on both models:
"Initializing Packet drive and IP address" then stop with error
Abort 19913, unable to start TCP/IP
can't find DHCP server
possible network setup problem.

Dell GX270, Pentium IV 2.8GHz, 1 GB RAM

Intel(R) PRO/1000 MT Network Connection
PCI\VEN_8086&DEV_100E&SUBSYS_01511028&REV_02\4&1C660DD6&0&60F0

IRQ configuration utility 1.0.
Copyright (C) 2006 Symantec Corp. All rights reserved.

Summarizing interrupts...

The following devices do not use an IRQ:
(0x00, 0x00, 0x00): IRQ: 0x00, INT#: 0x00, Link: 0x00
Class: Bridge, , SubClass: Host/PCI
Vendor: 0x8086, Device: 0x2570, RoutePINS: 0x00, 0x00, 0x00, 0x00,
(0x00, 0x1E, 0x00): IRQ: 0x00, INT#: 0x00, Link: 0x00
Class: Bridge, , SubClass: PCI/PCI
Vendor: 0x8086, Device: 0x244E
(0x00, 0x1F, 0x00): IRQ: 0x00, INT#: 0x00, Link: 0x00
Class: Bridge, , SubClass: PCI/ISA
Vendor: 0x8086, Device: 0x24D0, RoutePINS: 0x62, 0x61, 0x00, 0x00,

The following hard wired devices share IRQ 11:
(0x00, 0x02, 0x00): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Display, , SubClass: VGA compatible
Vendor: 0x8086, Device: 0x2572, RoutePINS: 0x60, 0x00, 0x00, 0x00,
(0x00, 0x1D, 0x00): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x24D2, RoutePINS: 0x60, 0x63, 0x62, 0x6B,
(0x00, 0x1D, 0x03): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x24DE, RoutePINS: 0x60, 0x63, 0x62, 0x6B,

The following hard wired devices share IRQ 3:
(0x00, 0x1F, 0x03): IRQ: 0x03, INT#: 0x0B, Link: 0x61
Class: Serial Bus, , SubClass: SMBUS
Vendor: 0x8086, Device: 0x24D3, RoutePINS: 0x62, 0x61, 0x00, 0x00,
(0x00, 0x1F, 0x05): IRQ: 0x03, INT#: 0x0B, Link: 0x61
Class: Multimedia, , SubClass: Audio
Vendor: 0x8086, Device: 0x24D5, RoutePINS: 0x62, 0x61, 0x00, 0x00,

The following hard wired devices share IRQ 9:
(0x00, 0x1D, 0x02): IRQ: 0x09, INT#: 0x0C, Link: 0x62
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x24D7, RoutePINS: 0x60, 0x63, 0x62, 0x6B,
(0x00, 0x1F, 0x01): IRQ: 0x09, INT#: 0x0A, Link: 0x62
Class: Mass Storage, , SubClass: IDE Controller
Vendor: 0x8086, Device: 0x24DB, RoutePINS: 0x62, 0x61, 0x00, 0x00,
(0x00, 0x1F, 0x02): IRQ: 0x09, INT#: 0x0A, Link: 0x62
Class: Mass Storage, , SubClass: IDE Controller
Vendor: 0x8086, Device: 0x24D1, RoutePINS: 0x62, 0x61, 0x00, 0x00,
(0x01, 0x0C, 0x00): IRQ: 0x09, INT#: 0x0A, Link: 0x62
Class: Network, , SubClass: Ethernet
Vendor: 0x8086, Device: 0x100E, RoutePINS: 0x62, 0x00, 0x00, 0x00,

The following hard wired devices share IRQ 10:
(0x00, 0x1D, 0x01): IRQ: 0x0A, INT#: 0x0B, Link: 0x63
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x24D4, RoutePINS: 0x60, 0x63, 0x62, 0x6B,

The following hard wired devices share IRQ 5:
(0x00, 0x1D, 0x07): IRQ: 0x05, INT#: 0x0D, Link: 0x6B
Class: Serial Bus, , SubClass: USB EHCI
Vendor: 0x8086, Device: 0x24DD, RoutePINS: 0x60, 0x63, 0x62, 0x6B,

>> Found Mass storage & network controller hard wired together !!
>> Found Mass storage & network controller sharing IRQ
>> Recommend that the network device is moved to irq 3
>> Found Mass storage & network controller hard wired together !!
>> Found Mass storage & network controller sharing IRQ
>> Recommend that the network device is moved to irq 3

IRQs enabled on the PIC: 0, 1, 2, 6, 8, 9, 12, 13, 14, 15,





Dell GX280 3GHz, 1GB RAM

Broadcom NetExtreme 57xx Gigabit Controller
PCI\VEN_14E4&DEV_1677&SUBSYS_01791028&REV_01\4&1D7EFF9E&0&00E0

IRQ configuration utility 1.0.
Copyright (C) 2006 Symantec Corp. All rights reserved.

Summarizing interrupts...

The following devices do not use an IRQ:
(0x00, 0x00, 0x00): IRQ: 0x00, INT#: 0x00, Link: 0x00
Class: Bridge, , SubClass: Host/PCI
Vendor: 0x8086, Device: 0x2580, RoutePINS: 0x00, 0x00, 0x00, 0x00,
(0x00, 0x1E, 0x00): IRQ: 0x00, INT#: 0x00, Link: 0x00
Class: Bridge, , SubClass: Sub Decode PCI/PCI
Vendor: 0x8086, Device: 0x244E, RoutePINS: 0x6B, 0x00, 0x00, 0x00,
(0x00, 0x1F, 0x00): IRQ: 0x00, INT#: 0x00, Link: 0x00
Class: Bridge, , SubClass: PCI/ISA
Vendor: 0x8086, Device: 0x2640, RoutePINS: 0x60, 0x61, 0x68, 0x00,
(0x01, 0x00, 0x01): IRQ: 0xFF, INT#: 0x00, Link: 0x00
Class: Display, , SubClass: Other Display
Vendor: 0x1002, Device: 0x5B70, RoutePINS: 0x60, 0x00, 0x00, 0x00,

The following hard wired devices share IRQ 11:
(0x00, 0x01, 0x00): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Bridge, , SubClass: PCI/PCI
Vendor: 0x8086, Device: 0x2581, RoutePINS: 0x60, 0x61, 0x62, 0x63,
(0x00, 0x1C, 0x00): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Bridge, , SubClass: PCI/PCI
Vendor: 0x8086, Device: 0x2660, RoutePINS: 0x60, 0x61, 0x62, 0x63,
(0x00, 0x1F, 0x01): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Mass Storage, , SubClass: IDE Controller
Vendor: 0x8086, Device: 0x266F, RoutePINS: 0x60, 0x61, 0x68, 0x00,
(0x01, 0x00, 0x00): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Display, , SubClass: VGA compatible
Vendor: 0x1002, Device: 0x5B60, RoutePINS: 0x60, 0x00, 0x00, 0x00,
(0x02, 0x00, 0x00): IRQ: 0x0B, INT#: 0x0A, Link: 0x60
Class: Network, , SubClass: Ethernet
Vendor: 0x14E4, Device: 0x1677, RoutePINS: 0x60, 0x00, 0x00, 0x00,

The following hard wired devices share IRQ 10:
(0x00, 0x1C, 0x01): IRQ: 0x0A, INT#: 0x0B, Link: 0x61
Class: Bridge, , SubClass: PCI/PCI
Vendor: 0x8086, Device: 0x2662, RoutePINS: 0x60, 0x61, 0x62, 0x63,
(0x00, 0x1F, 0x03): IRQ: 0x0A, INT#: 0x0B, Link: 0x61
Class: Serial Bus, , SubClass: SMBUS
Vendor: 0x8086, Device: 0x266A, RoutePINS: 0x60, 0x61, 0x68, 0x00,

The following hard wired devices share IRQ 3:
(0x00, 0x1D, 0x02): IRQ: 0x03, INT#: 0x0C, Link: 0x62
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x265A, RoutePINS: 0x69, 0x6A, 0x62, 0x6B,

The following hard wired devices share IRQ 5:
(0x00, 0x1F, 0x02): IRQ: 0x05, INT#: 0x0C, Link: 0x68
Class: Mass Storage, , SubClass: IDE Controller
Vendor: 0x8086, Device: 0x2651, RoutePINS: 0x60, 0x61, 0x68, 0x00,

The following hard wired devices share IRQ 9:
(0x00, 0x1D, 0x00): IRQ: 0x09, INT#: 0x0A, Link: 0x69
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x2658, RoutePINS: 0x69, 0x6A, 0x62, 0x6B,
(0x00, 0x1D, 0x07): IRQ: 0x09, INT#: 0x0A, Link: 0x69
Class: Serial Bus, , SubClass: USB EHCI
Vendor: 0x8086, Device: 0x265C, RoutePINS: 0x69, 0x6A, 0x62, 0x6B,

The following hard wired devices share IRQ 5:
(0x00, 0x1D, 0x01): IRQ: 0x05, INT#: 0x0B, Link: 0x6A
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x2659, RoutePINS: 0x69, 0x6A, 0x62, 0x6B,

The following hard wired devices share IRQ 10:
(0x00, 0x1D, 0x03): IRQ: 0x0A, INT#: 0x0D, Link: 0x6B
Class: Serial Bus, , SubClass: USB UHCI
Vendor: 0x8086, Device: 0x265B, RoutePINS: 0x69, 0x6A, 0x62, 0x6B,
(0x00, 0x1E, 0x02): IRQ: 0x0A, INT#: 0x0A, Link: 0x6B
Class: Multimedia, , SubClass: Audio
Vendor: 0x8086, Device: 0x266E, RoutePINS: 0x6B, 0x00, 0x00, 0x00,

>> Found Mass storage & network controller hard wired together !!
>> Found Mass storage & network controller sharing IRQ
>> Recommend that the network device is moved to irq 3

IRQs enabled on the PIC: 0, 1, 2, 5, 6, 8, 9, 12, 13, 14,

Ah, our old friend the GX270. What irqcfg is telling you here is the root cause of most problems with this machine:

>> Found Mass storage & network controller hard wired together !!
>> Found Mass storage & network controller sharing IRQ
>> Recommend that the network device is moved to irq 3

The designers of this machine at Dell chose to make it so that the hardware interrupt lines for these two devices cannot be separated, and the consequence that you can choose to either run an interrupt-based driver for one or the other, but not both at the same time if you run standard DOS drivers for your network card.



The main workaround for this situation is that you use a custom command-line option to Ghost, "-fni". In order to make Ghost's performance higher for machines with slow BIOSes, Ghost has uses by default its own, interrupt-driven IDE drivers, and this switch disables those built-in drivers so that the hard-disk and NIC access don't conflict. Instead this generally causes Ghost to use the hard-disk driver in the system BIOS, which costs performance but should allow things to work a little better.

Try this first, and see if it helps. It may on some of your machines also be necessary to use the network driver provided by the PXE BIOS option in these machines, but try -fni first.

Alternatively for manual Ghosting you can use the 32-bit Windows version of Ghost under Windows PE, since drivers hosted by an ACPI-aware operating system aren't subject to the same IRQ restrictions as the DOS drivers. Unfortunately you can't use Windows PE for console-based cloning in current editions of GSS.

Thank you again for your reply.

In the previous version of Ghost (GSS 1.2) I didn't have any issues with our Dell GX series workstations (GX240, GX260, GX270, GX280 and GX620). I did an "in-place" upgrade to version 2.0, and now all of these machines give me the same error. What changed in version 2.0? Would I have been better of doing a fresh install of the software?

I also tried the "-fni" switch and got the same error, is there any other switches that I can try in combination to help resolve this?

That's been the solution in the cases that I know of, but let me check with one of the QA guys - they have one of these machines in their lab for testing, and I'll ask them to chip in with how they have their one set up.

Okay, today I uninstalled the Symantec GSS 2.0 software and reinstalled it, hoping that a "fresh" install would eliminate my problem. Now the ngserver.exe will run for about 30secs, then it will crash with the following error:

"Faulting application ngserver.exe, version 11.0.0.1502, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x0002f344"

I uninstalled the program and tried to reinstall it a few times, but get the same error.

I was reading in the following Symantec forum (http://forums.symantec.com/discussions/thread.jspa?messageID=4478729) that a new.dll was needed to correct the problem, is this the same issue? Do I need to open another thread? Thanks for all your help!

Unfortunately Bryan, it looks like your install has been damaged somehow; the error isn't the same one as in that other thread, and I'll need to dig a little deeper into figuring out what the problem is.

When the service fails, it should be writing out a file called NGERROR.TXT into the Ghost install directory, and that file should have more detail than the report you quoted (which looks like the Windows error reporting), and if so it would be good if you could post part of that - it records every fault that happens so it should have a copy of the same data repeated a few times.

From that, it should be possible to work out why the server is unhappy and what we can do about repairing your installation.