Ghost Solution Suite

I am building some dual-boot Windows XP SP2 PRO and Red Hat Enterprise Linux 4 WS PCs. Each PC has two hard drives: one drive has XP2 installed (/dev/sda) and the other has RHEL4 (/dev/sdb).

I am using Ghost Solution Suite 2.0.1.

I can successfully clone the XP2 drive, but when I try to clone the RHEL4 drive the clone task always fails with the following error message:

Error Number: (40020)
Message: Virtual Partition System Data overlaps with critical data in the destination partitions
Version: 11.0.2.1573 (Nov 14 2007, Build=1573)
OS Version: DOS v7.10
Command line arguments: -ia -nolilo -clone,dst=2,mode=restore,src=@MCCASTORpush256 -batch -sgt

[I'll post the full text of the error log in a follow-on message...]

FWIW, GSS does not emit any error / warning messages when I perform the “Image Create” task to pull the disk image from the RHEL4 drive onto the server. That step seems to work okay.

FWIW2, if I drastically reduce the partition sizes on the RHEL4 disk and then perform a “minimal” RHEL4 installation,

/dev/sdb1    /boot      100 MB
/dev/sdb2    /         1500 MB
/dev/sdb3    <swap>    1024 MB

then I can successfully clone the RHEL4 disk using GSS. But if I wipe the disk and reinstall RHEL4 onto a relatively large root file system (/) partition, e.g., 60 GB, the clone task always fails with the error message shown above. [n.b. The RHEL4 disk has a capacity of 160 GB and I'm only using about 62 GB total in the three primary partitions I've created. There is one unused primary partition, and there should be plenty of unused disk space available for the cloning operation.]

If I clone the partitions individually (versus cloning the entire disk), the 100 MB “/boot” partition always clones correctly, but the 60GB “/” partition always fails with the error message shown above. I’ve tried everything I can think of to make this work, but no luck.


FWIW3: In the error log I noticed something odd:

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    1  83 No         63     208782     208845     208782 No
 1  1    0  83 No     208845  122881185  123090030  122881185 No
 2  2    0  82 No  123090030    2104515  125194545    2104515 No

Note that the last block(?) on sector #0 is listed as the first block on sector #1. Likewise, the last block of sector #1 is listed as the first block of sector #2. Is this an off-by-one error? IOW, how can two different partitions share the same block (208845, or 123090030)?


Jim

Here is part 1 of the error log:


*********************************
Date   : Wed Apr 23 11:10:08 2008
Error Number: (40020)
Message: Virtual Partition System Data overlaps with critical data in the destination partitions
Version: 11.0.2.1573 (Nov 14 2007, Build=1573)
OS Version: DOS v7.10
Command line arguments: -ia -nolilo -clone,dst=2,mode=restore,src=@MCCASTORpush256 -batch -sgt
Active Switches :
       AutoName
PathName            :
DumpFile            : @MCCASTORPUSH256
DumpPos             : 8192
FlagImplode         : 0
FlagExplode         : 2

CloneSrc            : @MCCASTORPUSH256
BatchPartSrc        : 0
BatchPartMSrc       :

CloneDst            : 2
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
  0x0039846c
  0x0009d011
  0x0009c84c
  0x0009bf27
  0x0009daf2
  0x000e2bee
  0x000c74de
  0x0000220f
  0x00002374
  0x00005057
  0x00003f2f
  0x003a1698
End Call Stack


Start heap available: 516489216
Cur   heap available: 516292608
Total Memory:         525860864

Allocated
   1024 DpmiDjgpp.cpp:56
  33504 ghost.cpp:1396
     64 DiskDriveAccessExInt13.cpp:152
     48 DiskDriveAccessExInt13.cpp:152
    528 IdeDmaServerPci.cpp:127
    528 IdeDmaServerPci.cpp:127
    528 IdeDmaServerPci.cpp:127
    528 IdeDmaServerPci.cpp:127
Free
    512 DiskDriveAccessInt13.cpp:189
     48 MsdosLfoFilesystem.cpp:412
  32768 MsdosFile.cpp:368

Fat details:

NTFS details:
----------------

NTFS Global Flags:
----------------
     contiguousWrite=1 forceDiskClusterMapping=0
     inhi**bleep**KDSK=1 ignoreBadLog=0 ignoreCHKDSKBit=0
     enable_cache=0 xfrbuflen=0
     last_attr_type = 0
     loadExact = 0
----------------

Disk Info :
  remote.............0
  drive..............1
  sectorsUsedCount.......125194482
  estimatedUsedCount.....125194483
  numPartitions..............3
  Version............1102

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    1  83 No         63     208782     208845     208782 No
 1  1    0  83 No     208845  122881185  123090030  122881185 No
 2  2    0  82 No  123090030    2104515  125194545    2104515 No

Disk Info :
  remote.............0
  drive..............1
  sectorsUsedCount.......125194545
  estimatedUsedCount.....0
  numPartitions..............3
  Version............0

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    1  83 No         63     208782     208845     208782 No
 1  1    0  83 No     208845  122881185  123090030  122881185 No
 2  2    0  82 No  123090030    2104515  125194545    2104515 No

Fixed Drives

Drive 128 WDC WD800JD-75MSA3      WD-WMAM9AAP0364
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            156250000
Bytes per Sector         512
MB                       76293
Successful IO Count      0

IDE using PIO
Total Sectors            156250000
Bytes per Sector         512
MB                       76293
Cylinders                16383
Heads                    16
Sectors per Track        63
Successful IO Count      0

IDE using UDMA (Active)
Total Sectors            156250000
Bytes per Sector         512
MB                       76293
Cylinders                16383
Heads                    16
Sectors per Track        63
Successful IO Count      25

Drive 129 WDC WD1600AAJS-60PSA0      WD-WCAP94091996
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            312581808
Bytes per Sector         512
MB                       152627
Successful IO Count      0

IDE using PIO
Total Sectors            312581808
Bytes per Sector         512
MB                       152627
Cylinders                16383
Heads                    16
Sectors per Track        63
Successful IO Count      0

IDE using UDMA (Active)
Total Sectors            312581808
Bytes per Sector         512
MB                       152627
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 = 378208
Current Conventional Memory Size = 242160

Allocated
   1024 DpmiDjgpp.cpp:56
  33504 ghost.cpp:1396
     64 DiskDriveAccessExInt13.cpp:152
     48 DiskDriveAccessExInt13.cpp:152
    528 IdeDmaServerPci.cpp:127
    528 IdeDmaServerPci.cpp:127
    528 IdeDmaServerPci.cpp:127
    528 IdeDmaServerPci.cpp:127
Free
    512 DiskDriveAccessInt13.cpp:189
     48 MsdosLfoFilesystem.cpp:412
  32768 MsdosFile.cpp:368


DiskManager diagnostic...
=========================

Fixed Drives

Drive 128 WDC WD800JD-75MSA3      WD-WMAM9AAP0364
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            156250000
Bytes per Sector         512
MB                       76293
Successful IO Count      0

IDE using PIO
Total Sectors            156250000
Bytes per Sector         512
MB                       76293
Cylinders                16383
Heads                    16
Sectors per Track        63
Successful IO Count      0

IDE using UDMA (Active)
Total Sectors            156250000
Bytes per Sector         512
MB                       76293
Cylinders                16383
Heads                    16
Sectors per Track        63
Successful IO Count      25

Drive 129 WDC WD1600AAJS-60PSA0      WD-WCAP94091996
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            312581808
Bytes per Sector         512
MB                       152627
Successful IO Count      0

IDE using PIO
Total Sectors            312581808
Bytes per Sector         512
MB                       152627
Cylinders                16383
Heads                    16
Sectors per Track        63
Successful IO Count      0

IDE using UDMA (Active)
Total Sectors            312581808
Bytes per Sector         512
MB                       152627
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

Here is part 2 of the error log:


The following devices do not use an IRQ:
   (0x00, 0x00, 0x00):   IRQ: 0x00, INT#: -, Link: 0x00
      Class: Bridge, SubClass: Host/PCI
      Vendor: 0x8086, Device: 0x2580
   (0x00, 0x02, 0x01):   IRQ: 0x00, INT#: -, Link: 0x00
      Class: Display, SubClass: Other Display
      Vendor: 0x8086, Device: 0x2782, RoutePINS: 0x60, 0x00, 0x00, 0x00,
   (0x00, 0x1e, 0x00):   IRQ: 0x00, INT#: -, Link: 0x00
      Class: Bridge, SubClass: Sub Decode PCI/PCI
      Vendor: 0x8086, Device: 0x244e, RoutePINS: 0x6b, 0x00, 0x00, 0x00,
   (0x00, 0x1f, 0x00):   IRQ: 0x00, INT#: -, Link: 0x00
      Class: Bridge, SubClass: PCI/ISA
      Vendor: 0x8086, Device: 0x2640, RoutePINS: 0x60, 0x61, 0x68, 0x00,
The following hard wire-ord devices share IRQ 11:
   (0x00, 0x01, 0x00):   IRQ: 0x0b, INT#: A, Link: 0x60
      Class: Bridge, SubClass: PCI/PCI
      Vendor: 0x8086, Device: 0x2581, RoutePINS: 0x60, 0x61, 0x62, 0x63,
   (0x00, 0x02, 0x00):   IRQ: 0x0b, INT#: A, Link: 0x60
      Class: Display, SubClass: VGA compatible
      Vendor: 0x8086, Device: 0x2582, RoutePINS: 0x60, 0x00, 0x00, 0x00,
   (0x00, 0x1c, 0x00):   IRQ: 0x0b, INT#: A, Link: 0x60
      Class: Bridge, SubClass: PCI/PCI
      Vendor: 0x8086, Device: 0x2660, RoutePINS: 0x60, 0x61, 0x62, 0x63,
   (0x00, 0x1f, 0x01):   IRQ: 0x0b, INT#: A, Link: 0x60
      Class: Mass Storage, SubClass: IDE Controller
      Vendor: 0x8086, Device: 0x266f, RoutePINS: 0x60, 0x61, 0x68, 0x00,
   (0x02, 0x00, 0x00):   IRQ: 0x0b, INT#: A, Link: 0x60
      Class: Network, SubClass: Ethernet
      Vendor: 0x14e4, Device: 0x1677, RoutePINS: 0x60, 0x00, 0x00, 0x00,
The following hard wire-ord devices share IRQ 10:
   (0x00, 0x1c, 0x01):   IRQ: 0x0a, INT#: B, Link: 0x61
      Class: Bridge, SubClass: PCI/PCI
      Vendor: 0x8086, Device: 0x2662, RoutePINS: 0x60, 0x61, 0x62, 0x63,
   (0x00, 0x1f, 0x03):   IRQ: 0x0a, INT#: B, Link: 0x61
      Class: Serial Bus, SubClass: SMBUS
      Vendor: 0x8086, Device: 0x266a, RoutePINS: 0x60, 0x61, 0x68, 0x00,
   (0x04, 0x01, 0x00):   IRQ: 0x0a, INT#: A, Link: 0x61
      Class: Simple Com, SubClass: Other Com
      Vendor: 0x1093, Device: 0xc801, RoutePINS: 0x61, 0x62, 0x63, 0x60,
The following hard wire-ord devices share IRQ 3:
   (0x00, 0x1d, 0x02):   IRQ: 0x03, INT#: C, Link: 0x62
      Class: Serial Bus, SubClass: USB UHCI
      Vendor: 0x8086, Device: 0x265a, RoutePINS: 0x69, 0x6a, 0x62, 0x6b,
The following hard wire-ord devices share IRQ 5:
   (0x00, 0x1f, 0x02):   IRQ: 0x05, INT#: C, Link: 0x68
      Class: Mass Storage, SubClass: IDE Controller
      Vendor: 0x8086, Device: 0x2651, RoutePINS: 0x60, 0x61, 0x68, 0x00,
The following hard wire-ord devices share IRQ 9:
   (0x00, 0x1d, 0x00):   IRQ: 0x09, INT#: A, Link: 0x69
      Class: Serial Bus, SubClass: USB UHCI
      Vendor: 0x8086, Device: 0x2658, RoutePINS: 0x69, 0x6a, 0x62, 0x6b,
   (0x00, 0x1d, 0x07):   IRQ: 0x09, INT#: A, Link: 0x69
      Class: Serial Bus, SubClass: USB EHCI
      Vendor: 0x8086, Device: 0x265c, RoutePINS: 0x69, 0x6a, 0x62, 0x6b,
The following hard wire-ord devices share IRQ 5:
   (0x00, 0x1d, 0x01):   IRQ: 0x05, INT#: B, Link: 0x6a
      Class: Serial Bus, SubClass: USB UHCI
      Vendor: 0x8086, Device: 0x2659, RoutePINS: 0x69, 0x6a, 0x62, 0x6b,
The following hard wire-ord devices share IRQ 10:
   (0x00, 0x1d, 0x03):   IRQ: 0x0a, INT#: D, Link: 0x6b
      Class: Serial Bus, SubClass: USB UHCI
      Vendor: 0x8086, Device: 0x265b, RoutePINS: 0x69, 0x6a, 0x62, 0x6b,
   (0x00, 0x1e, 0x02):   IRQ: 0x0a, INT#: A, Link: 0x6b
      Class: Multimedia, SubClass: Audio
      Vendor: 0x8086, Device: 0x266e, RoutePINS: 0x6b, 0x00, 0x00, 0x00,

>> Found Mass storage & network controller hard wire-ord together !!
>> Found Mass storage & network controller sharing IRQ
>> Reckon you should move the irq to 3


FilesystemManager diagnostic...
===============================

Volume 1
VolumePos: 1.1:
DriveLetter:
Description:   74.28GB Primary Disk 0 Offset   31.50KB   74.28GB WDC WD800JD-75MSA3      WD-WMAM9AAP0364
Type:        fsfNtfsWindowsXP
Name:       

Volume 2
VolumePos: 2.1:
DriveLetter:
Description:  101.94MB Primary Disk 1 Offset   31.50KB  101.94MB WDC WD1600AAJS-60PSA0      WD-WCAP94091996
Type:        fsfExt3
Name:        /boot*********************************

In my previous post I wrote:

<quote>
FWIW3: In the error log I noticed something odd:

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    1  83 No         63     208782     208845     208782 No
 1  1    0  83 No     208845  122881185  123090030  122881185 No
 2  2    0  82 No  123090030    2104515  125194545    2104515 No

Note that the last block(?) on sector #0 is listed as the first block on sector #1. Likewise, the last block of sector #1 is listed as the first block of sector #2. Is this an off-by-one error? IOW, how can two different partitions share the same block (208845, or 123090030)?
</quote>

In the last paragraph, replace each occurance of 'sector' with 'partition'.

Jim

Hi Jim,

It's a long weekend here otherwise I would ask someone who knows more about the Virtual Partition, but here's what I think the problem is:

Ghost is trying to preserve the Virtual Partition, but it doesn't understand the ext3 filesystem so doesn't have anywhere to copy it. Changing from using a VP (Virtual Partition) to using a GBP (Ghost Boot Partition) would fix this.

BTW: Is there a reason you have the -ia (image all) and -nolilo (no boot loader fixup) flags set? Is /dev/sdb2 a LVM storage partition? Cloning will be much faster if you let Ghost clone only the data in the ext3 filesystems (but it does have some trouble with LVM).

When /dev/sdb2 is small it doesn't overlap the VP so there is no problem. Possibly if there was a FAT or NTFS partition on this drive the VP could be moved there. But even with FAT/NTFS it won't move the VP if the -ia flag is set. Also I think the FAT or NTFS partition might have to be located to overlap the VP, who's location we don't know, so that probably won't work. Might be worth trying though if you don't want to set up a GBP. NB: You'd have to drop the -ia flag though, if you still needed to image all the ext3 partition you could use -ial (image all Linux partitions).

> In the error log I noticed something odd... Is this an off-by-one error?

You're right this is an off by one error, but only in the logging code. When we print out the last sector it is calculated as (firstSector + sectorCount) when it should really be (firstSector + sectorCount - 1). So all those partitions really end one sector less than the log says. I'll fix this.

Hope this helps,
David.

Message Edited by David Moore on 04-25-2008 12:27 PM

Hi Jim,

Hard links are definitely preserved with Ghost 11.x (GSS 2.0.1). In earlier versions too I think, but I'm not sure when it was done.

The Lilo fix-up code won't work for a second drive (sdb), but with RHEL4 I'm pretty sure you're using Grub which should be OK. (You probably already know -nolilo disables Grub fix-up as well as Lilo fix-up).

Not having LVM will make things much simpler.


Cheers,
David.

Hi Jim,

Have talked to colleagues about Virtual Partition now and we've discovered a defect here. Ghost is checking if it can move the VP, but the VP isn't on your second disk so this check is not needed. Using a GPB as I suggested before would work, but shouldn't really be needed. I will message you about a diagnostic build you can try if you like.

Regards,

Okay, thanks. I would be interested in trying a diagnostic build.

By the way, I experimented a bit with using a Ghost boot partition. I created an "image create" task that images the entire hard drive that has Linux on it. The "master" Linux disk does not have a GBP. I then created a clone task that pushes the disk image onto a clone without deleting the GBP on the clone drive. The push succeeds but Linux now resides on partitions that don't correspond to the settings in the various config files in the /etc directory, requiring a manual fix-up of those config files after the cloning task (which of course is undesirable):

Before cloning:
/dev/sdb1   /boot
/dev/sdb2   /
/dev/sdb3   <swap>

After cloning:
/dev/sdb1   <GBP>
/dev/sdb2   /boot
/dev/sdb3   /
/dev/sdb4   <swap>

If I reconfigure the clone task so that the task deletes the GBP, thereby recreating the Linux partitions at their original locations on the disk, the clone task fails with the same "virtual partition" error message as before.

Jim