Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Virtual Partition: Failed to reboot client to recovery partition

Created: 14 May 2006 • Updated: 22 May 2010 | 11 comments

When I tried to create or clone image remotely from a domain PC, it always came up with the error: "Virtual Partition: Failed to reboot client to recovery partition".

I have selected the correct NIC driver for the client as it worked when I booted up with Network Boot Disk using that driver on that client.

Is there anything else I need to do to be able to clone or create image remotely ?

Thanks

Discussion Filed Under:

Comments 11 CommentsJump to latest comment

Hiep Pham's picture

Additional information:

- I use Ghost 8.0 (Enterprise Edition) on Windows XP and Windows 2003 server
- The client PC is running on Windows XP SP 2

Thanks for any help.

Chris Anderson 7's picture

Does your client PC have more than 3 primary partitions defined on the OS disk?

According to Ghost Implementation Guide,


A free primary slot in the partition table is required.

The partition table in the MBR shows if a disk is partitioned into up to 4 primary

partitions, or 3 primary partitions and 1 extended partition. If 4 primary

partitions already exist then the virtual partition cannot be created.

Compressed NTFS drives on Windows NT/2000/XP are not supported.

Support of dynamic disks is limited to simple dynamic disks. The virtual
partition is not supported on spanned, striped, and RAID-5 volumes.




Hope that helps

Hiep Pham's picture

It has only 2 primary partitions - one in FAT (55MB) and one in NTFS (C:). The FAT partition is properly created when the Ghost Console client is installed remotely.

So what else I need to look at ?

Much thanks.

Chris Anderson 7's picture

> It has only 2 primary partitions - one in FAT (55MB)
> and one in NTFS (C:). The FAT partition is properly
> created when the Ghost Console client is installed
> remotely.

What do you mean The FAT partition is properly created when the Ghost console client is installed remotely? Do you mean the FAT partition is a Ghost Boot Partition?

How are your partitions laid out? Is it like the following?
Partition 1 (NTFS)
Partition 2 (FAT)

Do you have a heavily fragmented OS partition? You might want to try defragmenting your partition if that is the case.

Andrew Stephens's picture

The virtual partition file is created within the system partition, which is the partition that windows booted from (which is not always the same as the partition that contains the actual OS files). If your client machine has a small partition that contains the NT loader then runs Windows from the second, larger partition then it is possible that the first partition is too small to create the virtual partition file.
If the FAT partition is a Ghost Boot Partition then everything should be fine. Are you able to watch the client machine while the task is running to see if it attempts to restart? If it does restart into DOS and then immediately reboot back to windows then the network driver is probably not working.
If this is the case, you could try turning off the "Plug'n'play OS" setting in the machine's BIOS. Some DOS network drivers require this setting to be off when used from a hard drive.

Hiep Pham's picture

> The virtual partition file is created within the
> system partition, which is the partition that windows
> booted from (which is not always the same as the
> partition that contains the actual OS files). If your
> client machine has a small partition that contains
> the NT loader then runs Windows from the second,
> larger partition then it is possible that the first
> partition is too small to create the virtual
> partition file.
> If the FAT partition is a Ghost Boot Partition then
> everything should be fine. Are you able to watch the
> client machine while the task is running to see if it
> attempts to restart? If it does restart into DOS and
> then immediately reboot back to windows then the
> network driver is probably not working.
> If this is the case, you could try turning off the
> "Plug'n'play OS" setting in the machine's BIOS. Some
> DOS network drivers require this setting to be off
> when used from a hard drive.

It happens exactly like what you said. It starts up in DOS environment and then restarts back to Windows XP immediately.

The client PC is a Dell Optiplex GX280. It has Broadcom NetXtreme 57XX Gigabit Controller Ethernet card. Also in BIOS setting I can't find the option to disable Plug-n-Plug OS.

I try both Packet Driver and NDIS2 Driver to create network templates for the client. The NDIS2 driver works perfectly to boot the client in Network Broadcast session.

The order of the primary partitions is:
(1) FAT partition (55MB) - Ghost Boot Partition
(2) NTFS partition

So is it coming down to find the right network driver for the NIC ?

Much thanks for any help.

Hiep Pham's picture

I just upgraded to Ghost 10 and it automatically selects the right driver for the NIC. Now it works perfectly. Much thanks for everyone's help.

Chris Anderson 7's picture

Just curious. How did you upgrade from Ghost 8.0 to Ghost 10? Or do you mean Ghost Solution Suite 1.0?
Isn't Ghost 10 a consumer product?

Hiep Pham's picture

You are right. It's actually Ghost 8.3 or Ghost Solution Suite 1.0. Thanks

Joe Chittick's picture

I have ghost 8.3 and am receiving this error on an new HP DC5700 small form factor PC. I do have the correct nic and 2 partitions. Any ideas?

David Swinton's picture

I recently upgraded form GSS 1.1 to GSS 2.0.  I am reciveing this error message on 2 machinces; Virtual Partition: Failed to reboot client to recovery partition.

I have checked drivers for NIC cards ensured that they are working and that they are up to date.  Replaced the Nic card to no resolve.

Any suggestions on what to try next would be great.  I am using Intel Pro 100 card template.  The template is working on 3 other machines but on these 2 no success.