Ghost Solution Suite

 View Only

  • 1.  (40020): "Virtual Partition System Data overlaps with critical data"...

    Posted Mar 23, 2007 06:43 PM
    In GSS 2.0, I'm trying to clone an image with a somewhat complex disk layout (Dell utility partition - primary; Dell recovery partition / Vista boot loader / NTLDR - primary; extended partition => logical partition: Vista boot; logical partition: XP SP2 boot; logical partition: blank) onto a disk of the same size, and keep getting this in ghosterr.txt:
     
    Date   : Fri Mar 23 23:33:54 2007
    Error Number: (40020)
    Message: Virtual Partition System Data overlaps with critical data in the destination partitions
    Version: 11.0.0.1502 (Dec  4 2006, Build=1502)
    OS Version: DOS v7.10
    Command line arguments: -clone,dst=1,mode=restore,src=@MCQAVMWAREpush10 -batch -sgb -sgt
    It seems like it's trying to preserve something it thinks is important on the destination drive, and I'm not sure why - I want it all to look like the drive image. Can I force an override of this?


  • 2.  RE: (40020): "Virtual Partition System Data overlaps with critical data"...

    Posted Mar 24, 2007 06:20 PM
    It seems like it's trying to preserve something it thinks is important on the destination drive, and I'm not sure why - I want it all to look like the drive image. Can I force an override of this?

    Since you're doing this through the console, Ghost (along with all the other console tools) is running out of a specially constructed temporary partition. In this situation, because there are other things that need to be done once Ghost finishes such as run Ghost Walker and apply any post-configuration settings with GhConfig, it needs to preserve this temporary partition.

    Ghost normally tries to move the temporary virtual partition out of the way of anything important that's coming in, but there may be a subtle difference in the rules used by the code that does that versus the overlap check that results in the 40030 error. I'll need to consult with the cloning engine lead on that.

    In the meantime, something that would really help is a GHOSTERR.TXT from this situation; that will give us a lot more details about where everything is on your current disk and where the image you're trying to use needs everything to be.

    There isn't, unfortunately, an easy way to force this except to run the clone manually. However, if you can supply us with the GHOSTERR.TXT then perhaps we can work out why the automatic relocation isn't working for you.


  • 3.  RE: (40020): "Virtual Partition System Data overlaps with critical data"...

    Posted Mar 27, 2007 10:06 PM
    Pasted below (couldn't figure out a way to attach, so sorry about the length).
     
    If you need any other information about the layout or configuration, let me know.
     
    Thanks for the quick response!
     
    *********************************
    Date   : Wed Mar 28 06:40:59 2007
    Error Number: (40020)
    Message: Virtual Partition System Data overlaps with critical data in the destination partitions
    Version: 11.0.0.1502 (Dec  4 2006, Build=1502)
    OS Version: DOS v7.10
    Command line arguments: -clone,dst=1,mode=restore,src=@MCQAVMWAREpush15 -batch -sgb -sgt
    Active Switches :
          AutoName
    PathName            :
    DumpFile            : @MCQAVMWAREPUSH15
    DumpPos             : 11264
    FlagImplode         : 0
    FlagExplode         : 2
    CloneSrc            : @MCQAVMWAREPUSH15
    BatchPartSrc        : 0
    BatchPartMSrc       :
    CloneDst            : 1
    BatchPartDst        : 0
    Operation Details :
     Total size.........0
     MB copied..........0
     MB remaining.......0
     Percent complete...0%
     Speed..............0 MB/min
     Time elapsed.......0:00  
     Time remaining.....0:00  
    Program Call Stack
    AbortLog
    Generic_Abort
    checkVirtualPartitionData
    CopyFileToDisk
    CopyMainline
    AttemptOperation
    sub_main
    main
    Call Stack
     0x0039623c
     0x0009cbd1
     0x0009c40c
     0x0009bae7
     0x0009d6b2
     0x000e259a
     0x000c6e9e
     0x0000220f
     0x00002374
     0x0000502f
     0x00003f2f
     0x0039f468
    End Call Stack

    Start heap available: 995098624
    Cur   heap available: 994836480
    Total Memory:         1004404736
    Allocated
      1024 DpmiDjgpp.cpp:56
     33504 ghost.cpp:1394
        48 DiskDriveAccessExInt13.cpp:139
       528 IdeDmaServerPci.cpp:127
       528 IdeDmaServerPci.cpp:127
       528 IdeDmaServerPci.cpp:127
       528 IdeDmaServerPci.cpp:127
    Free
        64 GetDriveType.cpp:111
       512 DiskDriveAccessInt13.cpp:184
     32768 MsdosFile.cpp:368
    Fat details:
    NTFS details:
    ----------------
    NTFS Global Flags:
    ----------------
     contiguousWrite=1 forceDiskClusterMapping=0
     inhibitCHKDSK=1 ignoreBadLog=0 ignoreCHKDSKBit=0
     enable_cache=0 xfrbuflen=0
     last_attr_type = 0
     loadExact = 0
    ----------------
    Disk Info :
     remote.............0
     drive..............0
     sectorsUsedCount.......312486821
     estimatedUsedCount.....45270688
     numPartitions..............5
     Version............1100
     # Ord Boot Id Ext     First        Num       Last       Used NTFS
     0  0    0  de No         63      80262      80325      14231 No
     1  1    1  27 No      81920   20971520   21053440   20971520 No
     2  2    0   7 Yes   21061215   41929650   62990865   19395320 Yes
     3  3    0   7 Yes   62990928   41945652  104936580   12225472 Yes
     4  4    0   7 Yes  104936643  207559737  312496380     201544 Yes
    Disk Info :
     remote.............0
     drive..............0
     sectorsUsedCount.......312496380
     estimatedUsedCount.....0
     numPartitions..............5
     Version............0
     # Ord Boot Id Ext     First        Num       Last       Used NTFS
     0  0    0  de No         63      80262      80325      14231 No
     1  1    1  27 No      81920   20971520   21053440   20971520 No
     2  2    0   7 Yes   21061215   41929650   62990865   19395320 Yes
     3  3    0   7 Yes   62990928   41945652  104936580   12225472 Yes
     4  4    0   7 Yes  104936643  207559737  312496380     201544 Yes
    Fixed Drives
    Drive 128 ST3160812AS             9LS4YQY5
    Int 13h
    Total Sectors            16434495
    Bytes per Sector         512
    MB                       8024
    Cylinders                1023
    Heads                    255
    Sectors per Track        63
    Successful IO Count      0
    Extended Int 13h
    Total Sectors            312500000
    Bytes per Sector         512
    MB                       152587
    Successful IO Count      0
    IDE using PIO
    Total Sectors            312500000
    Bytes per Sector         512
    MB                       152587
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      0
    IDE using UDMA (Active)
    Total Sectors            312500000
    Bytes per Sector         512
    MB                       152587
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      27
    Floppy Drives
    Drive 0
    Int 13h (Active)
    Total Sectors            2880
    Bytes per Sector         512
    MB                       1
    Cylinders                80
    Heads                    2
    Sectors per Track        18
    Successful IO Count      1
    Remote Drives
    AsyncIo : 0
    ConvMemoryAllocationFactoryDpmi diagnostic...
    =============================================
    Conventional Memory
    Initial Conventional Memory Size = 362816
    Current Conventional Memory Size = 226832
    Allocated
      1024 DpmiDjgpp.cpp:56
     33504 ghost.cpp:1394
        48 DiskDriveAccessExInt13.cpp:139
       528 IdeDmaServerPci.cpp:127
       528 IdeDmaServerPci.cpp:127
       528 IdeDmaServerPci.cpp:127
       528 IdeDmaServerPci.cpp:127
    Free
        64 GetDriveType.cpp:111
       512 DiskDriveAccessInt13.cpp:184
     32768 MsdosFile.cpp:368

    DiskManager diagnostic...
    =========================
    Fixed Drives
    Drive 128 ST3160812AS             9LS4YQY5
    Int 13h
    Total Sectors            16434495
    Bytes per Sector         512
    MB                       8024
    Cylinders                1023
    Heads                    255
    Sectors per Track        63
    Successful IO Count      0
    Extended Int 13h
    Total Sectors            312500000
    Bytes per Sector         512
    MB                       152587
    Successful IO Count      0
    IDE using PIO
    Total Sectors            312500000
    Bytes per Sector         512
    MB                       152587
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      0
    IDE using UDMA (Active)
    Total Sectors            312500000
    Bytes per Sector         512
    MB                       152587
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      27
    Floppy Drives
    Drive 0
    Int 13h (Active)
    Total Sectors            2880
    Bytes per Sector         512
    MB                       1
    Cylinders                80
    Heads                    2
    Sectors per Track        18
    Successful IO Count      1
    The following devices do not use an IRQ:
      (0x00, 0x00, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x02f0
      (0x00, 0x00, 0x01):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x02fa
      (0x00, 0x00, 0x02):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x02fe
      (0x00, 0x00, 0x03):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x02f8
      (0x00, 0x00, 0x04):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x02f9
      (0x00, 0x00, 0x05):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x02ff
      (0x00, 0x00, 0x06):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x027f
      (0x00, 0x00, 0x07):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x027e
      (0x00, 0x02, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Bridge, SubClass: PCI/PCI
         Vendor: 0x10de, Device: 0x02fc, RoutePINS: 0x06, 0x07, 0x08, 0x05,
      (0x00, 0x03, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Bridge, SubClass: PCI/PCI
         Vendor: 0x10de, Device: 0x02fd, RoutePINS: 0x05, 0x06, 0x07, 0x08,
      (0x00, 0x04, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Bridge, SubClass: PCI/PCI
         Vendor: 0x10de, Device: 0x02fb, RoutePINS: 0x05, 0x06, 0x07, 0x08,
      (0x00, 0x09, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x0270
      (0x00, 0x0a, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Bridge, SubClass: PCI/ISA
         Vendor: 0x10de, Device: 0x0260, RoutePINS: 0x0a, 0x0d, 0x00, 0x00,
      (0x00, 0x0a, 0x02):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Memory, SubClass: RAM
         Vendor: 0x10de, Device: 0x0272, RoutePINS: 0x0a, 0x0d, 0x00, 0x00,
      (0x00, 0x10, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
         Class: Bridge, SubClass: Sub Decode PCI/PCI
         Vendor: 0x10de, Device: 0x026f, RoutePINS: 0x00, 0x13, 0x14, 0x15,
      (0x00, 0x18, 0x00):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Bridge, SubClass: Host/PCI
         Vendor: 0x1022, Device: 0x1100
      (0x00, 0x18, 0x01):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Bridge, SubClass: Host/PCI
         Vendor: 0x1022, Device: 0x1101
      (0x00, 0x18, 0x02):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Bridge, SubClass: Host/PCI
         Vendor: 0x1022, Device: 0x1102
      (0x00, 0x18, 0x03):   IRQ: 0x00, INT#: -, Link: 0x00
         Class: Bridge, SubClass: Host/PCI
         Vendor: 0x1022, Device: 0x1103
    The following hard wire-ord devices share IRQ 5:
      (0x04, 0x07, 0x00):   IRQ: 0x05, INT#: A, Link: 0x04
         Class: Network, SubClass: Ethernet
         Vendor: 0x14e4, Device: 0x170c, RoutePINS: 0x04, 0x04, 0x04, 0x04,
    The following hard wire-ord devices share IRQ 7:
      (0x00, 0x05, 0x00):   IRQ: 0x07, INT#: A, Link: 0x07
         Class: Display, SubClass: VGA compatible
         Vendor: 0x10de, Device: 0x0241, RoutePINS: 0x07, 0x08, 0x05, 0x06,
    The following hard wire-ord devices share IRQ 10:
      (0x00, 0x0a, 0x01):   IRQ: 0x0a, INT#: A, Link: 0x0a
         Class: Serial Bus, SubClass: SMBUS
         Vendor: 0x10de, Device: 0x0264, RoutePINS: 0x0a, 0x0d, 0x00, 0x00,
    The following hard wire-ord devices share IRQ 7:
      (0x00, 0x0b, 0x01):   IRQ: 0x07, INT#: B, Link: 0x0b
         Class: Serial Bus, SubClass: USB EHCI
         Vendor: 0x10de, Device: 0x026e, RoutePINS: 0x10, 0x0b, 0x00, 0x00,
    The following hard wire-ord devices share IRQ 10:
      (0x00, 0x0f, 0x00):   IRQ: 0x0a, INT#: A, Link: 0x0e
         Class: Mass Storage, SubClass: IDE Controller
         Vendor: 0x10de, Device: 0x0267, RoutePINS: 0x0e, 0x00, 0x00, 0x00,
    The following hard wire-ord devices share IRQ 11:
      (0x00, 0x0e, 0x00):   IRQ: 0x0b, INT#: A, Link: 0x0f
         Class: Mass Storage, SubClass: IDE Controller
         Vendor: 0x10de, Device: 0x0266, RoutePINS: 0x0f, 0x00, 0x00, 0x00,
    The following hard wire-ord devices share IRQ 15:
      (0x00, 0x0b, 0x00):   IRQ: 0x0f, INT#: A, Link: 0x10
         Class: Serial Bus, SubClass: USB OHCI
         Vendor: 0x10de, Device: 0x026d, RoutePINS: 0x10, 0x0b, 0x00, 0x00,
    The following hard wire-ord devices share IRQ 11:
      (0x00, 0x10, 0x01):   IRQ: 0x0b, INT#: B, Link: 0x13
         Class: Multimedia, SubClass: Unknown Multimedia
         Vendor: 0x10de, Device: 0x026c, RoutePINS: 0x00, 0x13, 0x14, 0x15,
     
    FilesystemManager diagnostic...
    ===============================
    Volume 1
    VolumePos: 1.1:
    DriveLetter:
    Description:  149.01GB Primary Disk 0 Offset   31.50KB  149.01GB ST3160812AS             9LS4YQY5
    Type:        fsfNtfsWindowsXP
    Name:        OS

    FilesystemMounter diagnostic...
    ===============================

    LfoFilesystemManager diagnostic...
    ==================================
    Filesystem Index: 0
    Filesystem Descriptor:
     ID's:
       ID Type: 2
       ID: A:
     DriveType: 2
     No FilesystemInfo structure.
     Filesystem has no VolumePtr
    Filesystem Index: 1
    Filesystem Descriptor:
     ID's:
       ID Type: 2
       ID: C:
     DriveType: 4
     No FilesystemInfo structure.
     Filesystem has no VolumePtr
    Filesystem Index: 2
    Filesystem Descriptor:
     ID's:
       ID Type: 1
       ID: 1.1:
       ID Type: 4
       ID: OS:
     DriveType: 4
     FilesystemInfo:
       formatType: 8
       volumeName: OS

    *********************************


  • 4.  RE: (40020): "Virtual Partition System Data overlaps with critical data"...

    Posted Mar 28, 2007 05:22 AM
    Thanks for that, I'll spend some time discussing it with the cloning lead tomorrow. My reading of the code is that as the code stands right now, you will need to run Ghost interactively to lay down that specific image initially, although after doing that once you should be fine - once your complex image is down there, when Ghost subsequently creates the Virtual Partition it will be fine.

    The -sgb and -sgt options that appear on the command line in the GHOSTERR.TXT are put there by the console client when it runs Ghost to let it know to preserve the virtual partition, but if you run Ghost yourself using a "command execute" kind of task to get the client to run GHOST.EXE without those flags, at the end of the clone Ghost should reboot immediately into the target OS.

    Now, the console won't be completely happy about this - it will know that the transfer into the new image running Windows happened when it was expecting the DOS client to get control for the rest of the task to run, and the task will probably be marked as "failed", but as long as you aren't expecting to combine the task with post-configuration that will be better than nothing.

    However, that's my interim reading of things; when I go over the log data with the cloning lead tomorrow he might be able to suggest something that I've missed.


  • 5.  RE: (40020): "Virtual Partition System Data overlaps with critical data"...

    Posted Mar 29, 2007 04:42 AM
    After working through this and your error file with the cloning lead, it turns out that as I suspected the code that decides where to move the VP and the code that decides there is an overlap aren't quite using the same rules. In particular, it turns out that partition number 2 is being considered a legal place to put the VP by the relocation code, even though some of the rest of the code thinks that it should be off-limits.

    If you drop me a line at nigel dot bree at gmail dot com we can send you a test build of Ghost that should work better with your image and not produce this error.