Ghost error during restoring

I need a solution

Good morning, Inside the company i work for we got many cnc siemens machines with a pc windows 7 and the ghost suite integrated. After a blackuot i made a backup of the 2 partitions contained inside the ssd and after that i tried to restore an old partition backup. Here i made an error, i pressed restore entire hdd and i choose the partition file. After 2 seconds i got an error from the ghost console. Now, i got the hdd without anything inside. I think the procedure canceled some configuration files but no real files. Windows does not start and during the boot up i only got a black screen. Do you know any way to try to recover the hdd?



  • No Related Posts

Missing partition resize options

I need a solution

Hi guys,

We’re trying to update our win10 master and captured our customized installation. We don’t have any problem with the capture, no errors or warning. When I try to create a deployment task (using a copy of the one we use for our 1803 master), I can add the *.gho I’ve just created. But when I go to the advanced options for resizing partitions, none are listed (I should have 3 listed). The 3 partitions are created if I use the *.gho but I really need to resize them.

Does someone here ever encountered this problem ? What am I missing ? Thanks for your help !



  • No Related Posts

Difference between partition admin users configured on Default partition and Admin Partition

Question: What is the difference between partition admin users configured on Default partition from the ones created on Admin Partition?


1) AP users configured from Default partition are first created on Default partition and then bound to a Admin partition.

But for the other case, you need to first switch to the admin partition and create the user in that partition itself.

2) You can only login to ADC through NSIP and SNIP of default partition using the default partition user admin . Whereas you can only login to ADC through SNIP of Admin partition using admin partition created user.

3) You can bind user defined command policies for default partition user. But for admin partition specific user can have only 4 pre-defined command policies to choose from.


  • No Related Posts

Admin Partitions | Partition ID Gets Skipped

Q: On “show ns partition” output, we sometimes see partition ID assignment is not sequential / IDs getting skipped. Is this a problem ?

A:Subject to memory availability one can create up to 511 admin partitions manually.

A partition ID is assigned to each partition upon creation and is used for internal tracking (this is not a user defined parameter).

Partition IDs are assigned from 1 to 511, however if there is an error (for any reason) during partition creation or a partition is deleted then partitioned will be skipped, these are reused later once 511 is reached.


Add partition parta … success | partition:ID1

Add partition partb … success | partition:ID2

Add partition partc… failed | partition:ID3 (Skipped)

Add partition partd… success | partition:ID4

//Assume the one below is 510th partition created it will be assigned partitionID:511

Add partition partx success | partitionID:511

//So, the actual 511th partition will now be assigned partitionID:3 as that was skipped previously

Add partition party .. will be assigned partitionID3

Q: Do these skipped partition IDs have any resource consumption until freed / reused.

A:Resources are only consumed by active partitions, skipped partition IDs do not have any bearing on resource consumption.



In the following output partitionID 1 to 30 and 34 is skipped (for any reason)

> show ns partition

1) Name: a

Partition ID: 31

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 700 MB

2) Name: b

Partition ID: 32

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 700 MB

3) Name: c

Partition ID: 33

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 700 MB

4) Name: d

Partition ID: 35

Max BW : 10240 Kbps

Max Conn :1024 Max Mem: 5 MB



Now if you check using nsconmsg you can see memory use is only by the active partitions, no memory is in use for skipped partition IDs (1-30 or 34)

> shell

Copyright (c) 1992-2013 The FreeBSD Project.

Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

The Regents of the University of California. All rights reserved.

root@ns# nsconmsg -d finalstatswt0 -K /var/nslog/newnslog -g mem_cur_usedsize | grep partition

3 0 3193912 mem_cur_usedsize partition_ctx(a) (PART-31)

5 0 3193912 mem_cur_usedsize partition_ctx(b) (PART-32)

7 0 3193912 mem_cur_usedsize partition_ctx(c) (PART-33)

9 0 3193912 mem_cur_usedsize partition_ctx(d) (PART-35)



  • No Related Posts

How to set the default size of the Elastic Layering writable volume

When Elastic Layering is enabled (with or without User Layers), the boot disk is created with an extra 20GB as a second partition where the user writes will be stored.

This is necessary to keep writes at a layer above the boot disk and any elastically assigned layers that might show up later.

That 20GB is the default and cannot be changed by editing the Image Template.

If you need to adjust the volume size, you can either manually edit the disk after publishing to expand it, and then expand the second partition, or you can change the writable partition size for all published images.


Symantec does not detect EICAR on big partition

I need a solution


we have a Windows fileserver with SEP 14RU1MP2 installed on it. The fileserver has 6 partitions with different sizes. On 5 partitions SEP works great. But on the biggest partition it does not detect EICAR files which is really strange. The partition is 11 TB large.

I already repaired SEP together with the Symantec support and after that SEP works again good for a few days. The exeptions are also ok. But now we have that issue again.

Does anyone have an idea how to solve that issue?

Thank you!



  • No Related Posts

How to Free Space From /var Directory of NetScaler Appliance When Unable to Log on to NetScaler GUI

  • Run the following commands to view the contents of the /var directory:

    cd /varls -l

    The directories that are usually of interest are as follows:

    /var/nstrace – This directory contains trace files.This is the most common reason for HDD being filled on the NetScaler. This is due to an nstrace being left running for indefinite amount of time. All traces that are not of interest can and should be deleted. To stop an nstrace, go back to the CLI and issue stop nstrace command.

    /var/log – This directory contains system specific log files.

    /var/nslog – This directory contains NetScaler log files.

    /var/tmp/support – This directory contains technical support files, also known as, support bundles. All files not of interest should be deleted.

    /var/core – Core dumps are stored in this directory. There will be directories within this directory and they will be labeled with numbers starting with 1. These files can be quite large in size. Clear all files unless the core dumps are recent and investigation is required.

    /var/crash – Crash files, such as process crashes are stored in this directory. Clear all files unless the crashes are recent and investigation is required.

    /var/nsinstall – Firmware is placed in this directory when upgrading. Clear all files, except the firmware that is currently being used.

  • Related:

    • No Related Posts