Ghost Solution Suite

The step that continues to fail is

"To virtual partitition".

The details for the error are

Details for: To Virtual Partition
Disk is either full or heavily fragmented.
Unable to create Virtual Partition file.


Just to make sure I
Defragmented both Client and Server hard drives (storage)
Have the virtual partion on the client set to 50MB (largest size)
Currently have over 50% of free space on both the client and server

What should I now be looking at?

I am also receiving this on another machine:

Details for: To Virtual Partition
Failed to reboot client to recovery partitionMessage was edited by:
Richard Ballard

Hi Richard,

This error indicates an issue it encountered in the client when try to create the virtual partition. So we are looking at some thing in the client, not the server.

When try to boot to virtual partition, it needs to create a contiguous file in the boot drive. If it fails to do so, it might think that the reason is not having an enough contiguous space to create the file. One common situation is disk structure errors, which could be corrected running chkdsk. You can try running chkdsk but I believe that most of defrag software does not run if there are chkdsk errors. As you defrag the disk, probably chkdsk would not find any issues.

Using a bigger VP size will make the problem worst as it need more space. Seems you have enough free space; by any chance do you have multiple partitions? If you use a smaller partition to boot, could it have a space problem?

Is there any disk management related software running in your client?

Krish

I have taken another look and defraged the drives in question. Now I am receiving a different error message. (Two machines)

The step it still fails on with both machines is:

To Virtual Partition

The event detail for # 1reads:

Details for: To Virtual Partition
Client timed out

The event detail for # 2reads:

Details for: To Virtual Partition
Failed to reboot client to recovery partition

In #1, does the client show as connected in the console? If you run a refresh task, does it execute successfully?
Because this error indicates that console was waiting for client to respond but it did not. Default time is about 20 minutes, possibilities are either client was not responding to start with or it encountered a problem during VP creation.

In #2, did you see if the client booted to VP?
Usually this error indicates that console did not detect that if the client booted to DOS or not, though there are no errors creating virtual partition. One common possibility is DOS network driver not correct. Client boot to DOS, but network driver does not work so it fails to tell the console that it is in DOS. In this situation client boot to Windows again, and then Console thinks that it did not boot to Virtual Partition.

Krish

In # 1. the client does not show to be connected in the console. I see the "Session Name" and the "Image File" destination. It reads "Waiting for clients to connect..." in the bottom left hand side of the "Symantec GhostCast Server console".

In # 2. Yes the client did boot to the VP. I will check the network driver.

Hi Richard,

When you start the task, did the Client #1 show in the console as connected? If not that means the client is not communicating with the console at all.

Krish

I had the same issue until I rebuilt my virtual partion after a live update and then had to defrag the box to get the VP to take.