Welcome, Guest. Please Login
 
  HomeHelpSearchLogin FAQ Radified Ghost.Classic Ghost.New Bootable CD Blog  
 
Pages: 1 2 
Send Topic Print
Invalid Partition Offset Error during Integrity Ck (Read 26747 times)
barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #15 - Jan 24th, 2007 at 3:02pm
 
Hi Nightowl and Ghost4me,

Nightowl,

I am doing  a partition backup (Local > Partition > to Image), have never tried (Local > Disk > to Image).

I had per previous post already used Partition Magic to follow Dan's suggestion--I made C: smaller, and after a couple of reboots and using the computer for a couple of hrs, had Partition Magic do its thing and resize C: to the exact size of D: & G:

Here is the current situation and boy am i confused. Last night after posting here, I was writing another forum about my situation, and had to open ghost so that i could quote something accurately.

I noticed that when I went to Advanced-Run Ghost Interactively, that instead of being immediately taken to the blue and gray screen, a wizard window opened up to take me through the creation process, and after a couple of mouse clicks I then got the blue and gray screen. It was late, I finished the email and hit bed.

This morning I ran ghost (Local > Partition > to Image) in Advanced--Run Ghost Interactively, and to my TOTAL shock, made the ghost and was able to run a successful integrity check on top of it! I repeated the process successfully a second time just to be sure, it worked just fine making the ghost and doing the integrity check, and here is where things get weird......

I decided that I should try making a ghost and doing an integrity check in Basic mode (Local > Partition > to Image), and the backup procedure failed almost instantly. The failure log either follows below this or if it doesn't fit, is in my next post.

After the failure, I again tried  (Local > Partition > to Image) in Advanced--Run Ghost Interactively, and the procedure worked perfectly including a successful integrity check. This state of events is very confusing and I will wait for your comments about the details of the failure log before doing anything else.

I have taken Ghost4me's tip and downloaded the Partition Table Doctor software, but will not do anything more till I hear back from you.

Log is too big, follows in next post

 

Sometimes the light's just shining on me, other times I barely can see...... what a long strange trip its turning out to be
 
IP Logged
 

barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #16 - Jan 24th, 2007 at 3:06pm
 
Nightowl,
Here is failed basic mode backup log; will wait for your advice before doing anything else. Has to come in 2 parts- is too big

Basic mode failure log part 1

BackupOperation 0

-- GHOST\GHOSTERR.TXT ---------------------------------------------------------

*********************************
Date   : Wed Jan 24 12:01:12 2007
Error Number: (40207)
Message: Invalid partition offset
Version: 2003.793 (Dec 17 2003, Build=793)
Command line arguments: -igb -imgdescfile=\ghost\imgdescp.txt -wizard -clone,mode=create,src=@GFfb9299eb-08f9-405b-a389-f3ff645c208a,dst=@GFfb9299eb-0
8f9-405b-a389-f3ff645c208a:16128\My Documents\1 24 07 basic mode\1 24 07.gho -ghwrap
Active Switches :
      AutoName
      Sure
ProgMode            : PROG_LOCAL
PathName            :
DumpFile            :
DumpPos             : 0
File64 buffersize   : 0
FlagImplode         : 0
FlagExplode         : 0

CloneSrc            : 1
BatchPartSrc        : 0
BatchPartMSrc       :

CloneDst            : @GFFB9299EB-08F9-405B-A389-F3FF645C208A:16128\MY DOCUMENTS\1 24 07 BASIC MODE\1 24 07.GHO
BatchPartDst        : 0

Operation Details :
  Total size.........0
  MB copied..........0
  MB remaining.......0
  Percent complete...0%
  Speed..............0MB/min
  Time elapsed.......0:00   
  Time remaining.....0:00   

Program Call Stack
Generic_Abort
processDriveMatchingArguments
sub_main
main

Call Stack
  0x0023f3c7
  0x0006b29f
  0x0006a54c
  0x0006a3c1
  0x0006ba63
  0x00003cf6
  0x000043a5
  0x0000370b
  0x0024cac8
End Call Stack


Start heap available: 1066598400
Cur   heap available: 1066532864
Total Memory:         1072627712

Conventional Memory
Inital Conventional Memory Size = 315824
Current Conventional Memory Size = 240816
Allocated
   1024 DpmiDjgpp.cpp:59
  33504 ghost.cpp:913
   2048 IdeDmaServerPci.cpp:132
    528 IdeDmaServerPci.cpp:132
   2048 AspiAdapterDos.cpp:87
    176 AspiAdapterDos.cpp:88
     32 DiskDriveAccessExInt13.cpp:107
    512 DiskDriveAccessExInt13.cpp:107
    512 DiskDriveAccessExInt13.cpp:107
Free
     16 MsdosFile.cpp:92
     80 AspiServerDos.cpp:103
    512 DiskDriveAccessInt13.cpp:181
   1024 AspiAdapterDos.cpp:323
  32768 AspiAdapterDos.cpp:323

Fat details:

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

NTFS Global Flags:
----------------
contiguousWrite=1 forceDiskClusterMapping=0
inhibitCHKDSK=1 ignoreBadLog=1 ignoreCHKDSKBit=1
enable_cache=0 xfrbuflen=0
last_attr_type = 0
loadExact = 0
----------------
=======================================================
NTFS volume 0:
----------------
initialised..............1
read cached..............N
Selective caching........N
flags....................Volume OK
drive....................0x02
part order...............0
version..................0x0400
volsize..................156280256
blocksize................512
clusterfactor............8
clustersize..............4096
mftrecordsize............1024
indexrecordsize..........4096
indexclustperrecord......1
bootSectorCopyOffset.....156280256
pagefileSys..............4294967295
bootIni..................3234
volumeLabel..............[]
sectorsInUse.............150012736
totalNonCopiedBytes......0
bytesToCopy..............0
bitmapClusters...........597
bitmapUsedBytes..........2441880
estimatedClusters........597
estimatedUsedBytes.......2441880
clustersizeShift.........12
blocksizeShift...........9
mftrecordsizeShift.......10
indexrecordsizeShift.....12
totalRootMftRecs.........0
clustermap failover......N
Boot sector details
name....................[NTFS    ]
blocksize...............512
clusterfactor...........8
reservedSectorsUnused...0
mediaType...............0xf8
secPerTrack.............63
numHeads................255
hiddenSectors...........16128
volsize_lo..............156280256
volsize_hi..............0
mftcluster.(lo).........786432
mftcluster.(hi).........0
mftmirrorcluster.(lo)...16
mftmirrorcluster.(hi)...0
clustersPerMFTRecord....246
clustersPerIndexBuffer..1

---------------------------------------------------
Cluster Allocation Map
---------------------------------------------------
Start:  19535032 Length:         0 Next:  19535032


=======================================================
=======================================================
NTFS volume 1:
----------------
initialised..............1
read cached..............N
Selective caching........N
flags....................Volume OK
drive....................0x01
part order...............0
version..................0x0400
volsize..................156280256
blocksize................512
clusterfactor............8
clustersize..............4096
mftrecordsize............1024
indexrecordsize..........4096
indexclustperrecord......1
bootSectorCopyOffset.....156280256
pagefileSys..............4294967295
bootIni..................4294967295
volumeLabel..............[]
sectorsInUse.............88425424
totalNonCopiedBytes......0
bytesToCopy..............0
bitmapClusters...........597
bitmapUsedBytes..........2441880
estimatedClusters........597
estimatedUsedBytes.......2441880
clustersizeShift.........12
blocksizeShift...........9
mftrecordsizeShift.......10
indexrecordsizeShift.....12
totalRootMftRecs.........0
clustermap failover......N
Boot sector details
name....................[NTFS    ]
blocksize...............512
clusterfactor...........8
reservedSectorsUnused...0
mediaType...............0xf8
secPerTrack.............63
numHeads................255
hiddenSectors...........16128
volsize_lo..............156280256
volsize_hi..............0
mftcluster.(lo).........786432
mftcluster.(hi).........0
mftmirrorcluster.(lo)...9768520
mftmirrorcluster.(hi)...0
clustersPerMFTRecord....246
clustersPerIndexBuffer..1

---------------------------------------------------
Cluster Allocation Map
---------------------------------------------------
Start:  19535032 Length:         0 Next:  19535032
 

Sometimes the light's just shining on me, other times I barely can see...... what a long strange trip its turning out to be
 
IP Logged
 
barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #17 - Jan 24th, 2007 at 3:09pm
 
Nightowl,
Basic mode failure log part 2; wait to hear from you

=======================================================
NTFS volume 2:
----------------
initialised..............1
read cached..............N
Selective caching........N
flags....................Volume OK
drive....................0x00
part order...............0
version..................0x0400
volsize..................156280256
blocksize................512
clusterfactor............8
clustersize..............4096
mftrecordsize............1024
indexrecordsize..........4096
indexclustperrecord......1
bootSectorCopyOffset.....156280256
pagefileSys..............4294967295
bootIni..................3231
volumeLabel..............[]
sectorsInUse.............24112032
totalNonCopiedBytes......0
bytesToCopy..............0
bitmapClusters...........597
bitmapUsedBytes..........2441880
estimatedClusters........597
estimatedUsedBytes.......2441880
clustersizeShift.........12
blocksizeShift...........9
mftrecordsizeShift.......10
indexrecordsizeShift.....12
totalRootMftRecs.........0
clustermap failover......N
Boot sector details
name....................[NTFS    ]
blocksize...............512
clusterfactor...........8
reservedSectorsUnused...0
mediaType...............0xf8
secPerTrack.............63
numHeads................255
hiddenSectors...........63
volsize_lo..............156280256
volsize_hi..............0
mftcluster.(lo).........786432
mftcluster.(hi).........0
mftmirrorcluster.(lo)...16
mftmirrorcluster.(hi)...0
clustersPerMFTRecord....246
clustersPerIndexBuffer..1

---------------------------------------------------
Cluster Allocation Map
---------------------------------------------------
Start:  19535032 Length:         0 Next:  19535032


=======================================================

Disk Info :
  remote.............0
  drive..............0
  sectors_used.......156280257
  estimated_used.....24112032
  pemax..............1
  Version............0

# Ord Boot Id Ext First    Num      Last     Used     NTFS
0   0   80 7  No  00000063 156280257 156280320 24112032 Yes

Disk Info :
  remote.............0
  drive..............0
  sectors_used.......0
  estimated_used.....0
  pemax..............0
  Version............0

# Ord Boot Id Ext First    Num      Last     Used     NTFS

Drive 128 WDC WD800JB-00ETA0 WD-WCAHL2639422

Int 13h
Total Sectors     16450560
Bytes per Sector  512
MB                8032
Cylinders         1024
Heads             255
Sectors per Track 63

Extended Int 13h
Total Sectors     156301488
Bytes per Sector  512
MB                76319

IDE using PIO
Total Sectors     156301488
Bytes per Sector  512
MB                76319
Cylinders         16383
Heads             16
Sectors per Track 63

IDE using UDMA (Active)
Total Sectors     156301488
Bytes per Sector  512
MB                76319
Cylinders         16383
Heads             16
Sectors per Track 63

Drive 129 WDC WD800JB-00ETA0 WD-WCAHL4690059

Int 13h
Total Sectors     16450560
Bytes per Sector  512
MB                8032
Cylinders         1024
Heads             255
Sectors per Track 63

Extended Int 13h
Total Sectors     156301488
Bytes per Sector  512
MB                76319

IDE using PIO
Total Sectors     156301488
Bytes per Sector  512
MB                76319
Cylinders         16383
Heads             16
Sectors per Track 63

IDE using UDMA (Active)
Total Sectors     156301488
Bytes per Sector  512
MB                76319
Cylinders         16383
Heads             16
Sectors per Track 63

Drive 130 WDC WD80 0JB-00ETA0 77.0

Int 13h
Total Sectors     16434495
Bytes per Sector  512
MB                8024
Cylinders         1023
Heads             255
Sectors per Track 63

Extended Int 13h
Total Sectors     156301488
Bytes per Sector  512
MB                76319

ASPI (Active)
Total Sectors     156301488
Bytes per Sector  512
MB                76319

Remote Drives
AsyncIo : 0
Image Devices

Key      A:
Path     A:
Desc    
Type     Floppy

Key      C:
Path     C:
Desc     [-VPSGHBOOT-]
Type     Disk
Disk     0
Offset   27262305

Key      D:
Path     D:
Desc     []
Type     CD

Key      E:
Path     E:
Desc     []
Type     CD

Key      @LFO1:1
Path     1:1
Desc     []
Type     NTFS
Disk     0
Offset   63

Key      @LFO2:1
Path     2:1
Desc     []
Type     NTFS
Disk     1
Offset   16128

Key      @LFO3:1
Path     3:1
Desc     []
Type     NTFS
Disk     2
Offset   16128

Key      @CD-R1
Path     @CD-R1
Desc     PLEXTOR DVDR   PX-708A 
Type     DVD

Key      @CD-R2
Path     @CD-R2
Desc     TDK     CDRW4800B      
Type     CD


*********************************
-- GHOST\GSCRIPT.TXT ----------------------------------------------------------

[BackupOperation]
AlreadyProcessedFile = YES
BeginTimeParam = Wed Jan 24 12:01:06 2007
DestFingerprintParam = fb9299eb-08f9-405b-a389-f3ff645c208a
DestPartitionOffsetParam = 16128
EndTimeParam = Wed Jan 24 12:01:13 2007
ExecutionStateParam = ExecutionFailed
FileIdParam = 244281
PathParam = \My Documents\1 24 07 basic mode\1 24 07.gho
SourceFingerprintParam = fb9299eb-08f9-405b-a389-f3ff645c208a
UseImageDescriptionParam = YES
UseLFOParam = YES
WindowsPathParam = D:\My Documents\1 24 07 basic mode\1 24 07.gho

[ImageCheckOperation]
AlreadyProcessedFile = YES
DestFingerprintParam = fb9299eb-08f9-405b-a389-f3ff645c208a
DestPartitionOffsetParam = 16128
ExecutionStateParam = ExecutionNotStarted
FileIdParam = 244281
PathParam = \My Documents\1 24 07 basic mode\1 24 07.gho
UseLFOParam = YES
WindowsPathParam = D:\My Documents\1 24 07 basic mode\1 24 07.gho

-- GHOST\ARGS.TXT -------------------------------------------------------------

-igb -imgdescfile=\ghost\imgdescp.txt -wizard "-clone,mode=create,src=@GFfb9299eb-08f9-405b-a389-f3ff645c208a,dst=@GFfb9299eb-
08f9-405b-a389-f3ff645c208a:16128\My Documents\1 24 07 basic mode\1 24 07.gho" -ghwrap
-- AUTOEXEC.BAT ---------------------------------------------------------------

@echo off
SET PATH=C:\GHOST;C:\
SET PROMPT=To return to Windows, type ghreboot and press Enter.$_$p$g
SET TZ=GHO+08:00
if "%CONFIG%" == "WINDOWS" goto WINDOWS
\GUEST.EXE
LH \MSCDEX.EXE /D:cd1 /D:cd2
MOUSE.COM
CD \GHOST
GHWRAP.EXE
goto EOF

:WINDOWS
\GHOST\GHREBOOT.EXE

:EOF
-- CONFIG.SYS -----------------------------------------------------------------

[MENU]
menuitem=GHOST,Run Norton Ghost Dos Operation
menuitem=WINDOWS,Return to Windows without running Norton Ghost
menudefault=GHOST,3

[GHOST]
LASTDRIVE=Z
DEVICE = \USB\ASPIOHCI.SYS /int /all
DEVICE = \USB\ASPIOHCI.SYS /int /all /D1
DEVICE = \USB\ASPIUHCI.SYS /int /all
DEVICE = \ASPICD.SYS /D:cd2
DEVICE = \OAKCDROM.SYS /D:cd1

[WINDOWS]
 

Sometimes the light's just shining on me, other times I barely can see...... what a long strange trip its turning out to be
 
IP Logged
 
John.
Übermensch
*****
Offline



Posts: 2072


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #18 - Jan 24th, 2007 at 3:44pm
 
barebear wrote on Jan 24th, 2007 at 3:02pm:
I have taken Ghost4me's tip and downloaded the Partition Table Doctor software, but will not do anything more till I hear back from you.

I think you can run Partition Table Doctor to analyze your partition, without it changing anything.  As I recall, you don't even have to purchase it to run the demo version:

http://www.ptdd.com/download.htm

 

Ghost4me  Ghost 9, 10, 12, 14, 15.  Windows XP, Vista, Windows 7
 
IP Logged
 
barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #19 - Jan 24th, 2007 at 5:08pm
 
Hi Ghost4me,

The free version is already downloaded --I'm just waiting to hear from Nightowl before doing anything more.

I'm really puzzled by the current state of affairs ie I can back up, do an integrity check , and restore via  (Local > Partition > to Image) in Advanced--Run Ghost Interactively, but when I try  (Local > Partition > to Image) in Basic >Backup the operation fails immediately.......very spooky (pun intended LOL)

I do want to thank you for your help/advice; PLEASE stay tuned to this thread and continue to post with any further help you may happen to think of !  Best, Peter
 

Sometimes the light's just shining on me, other times I barely can see...... what a long strange trip its turning out to be
 
IP Logged
 
NightOwl
Radministrator
*****
Offline


"I tought I saw a puddy
tat..."

Posts: 5801
Olympia, WA--Puget Sound--USA


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #20 - Jan 25th, 2007 at 12:56am
 
barebear

I'm not familiar with the program Ghost4me is suggesting to use, and I'm no expert on *partition offset* errors--so I don't know exactly what to look for.

But, you have used PartitionMagic to shrink and then you have used it to expand your HDD's partition to its maximum size again, as Dan Goodell suggested in the other thread--and that has not helped?

The reason I asked about if you are doing *whole* drive backups vs just *partition* backups is that you may be able to solve the problem by making sure you have a whole drive backup image, wipe the drive that is giving the problem (C:\--correct?), and then restoring the image to a clean/wiped HDD to see if that solves the problem.

You stated that you successfully restored your image to the HDD previously--did you boot with a floppy boot disk to do that--because if I followed your steps, the C:\ drive is the OS drive and that's the drive you restored--so you could not have been booted to the Windows OS--is that correct?

So, your C:\ partition is the only partition on that HDD?

Based on what you have reported--it sound like the Windows interface for Ghost is the only place that the *offset* problem occurs--when you run Ghost *interactively*, that ends up being as if you booted to DOS with a floppy disk--and Ghost is then using the drive letter assignments in DOS to access the various partitions--but, when you set things up in Windows, Ghost uses  a completely different way to access and identify the HDD's and the start and ending points of a HDD's partitions--i.e. the *offset* which identifies the exact place on the HDD's surface where partition boundaries begin and end.  And in some way, the HDD size as reported by the HDD and what's in the partition table are mis-matched.

Do you have a spare HDD to work with so as to protect your current original HDD--just in case anything goes wrong?
 

____________________________________________________________________________________________

No question is stupid ... but, possibly the answers are Wink !
 
IP Logged
 

barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #21 - Jan 25th, 2007 at 2:27am
 
Hi Nightowl,

I have "....used PartitionMagic to shrink and then you have used it to expand your HDD's partition to its maximum size again, as Dan Goodell suggested in the other thread" ---- it has helped to the point that now Ghost does what it should in  (Local > Partition > to Image) in Advanced--Run Ghost Interactively, whereas before resizing down and then back up I was only able to restore a ghost but not to do an integrity check.

As for your other questions:

C: is the only partition on that drive.

I have 3 drives all identical per my first post. In order to do a whole drive image and restore, I would have to move everything off my USB G: to my secondary IDE slave D: (can't do D; to G: because D: has much more on it--its my data drive). I then would have to ghost the whole C: drive to G:----I've never done a whole drive image; would I need to "wipe" G: before ghosting the C: drive to it??-- PLEASE advise

The C: is my OS drive and I have restored ghosts from D: to C: BOTH by:
1. starting with Ghost>Advanced>Restore and then Local>Partition>From Image in the blue/grey screen that pops up after clicking "Restore" ( the program tells you that it needs to relocate the virtual partition and then reboot, after rebooting you get the blue/grey screen again and do Local>Partition>From Image)           and
2. Booting from the floppy

I totally agree with your analysis " Based on what you have reported--it sound like the Windows interface for Ghost is the only place that the *offset* problem occurs--when you run Ghost *interactively*, that ends up being as if you booted to DOS with a floppy disk--and Ghost is then using the drive letter assignments in DOS to access the various partitions--but, when you set things up in Windows, Ghost uses  a completely different way to access and identify the HDD's and the start and ending points of a HDD's partitions--i.e. the *offset* which identifies the exact place on the HDD's surface where partition boundaries begin and end.  And in some way, the HDD size as reported by the HDD and what's in the partition table are mis-matched."

I unfortunately don't have a spare  HD---I would have to move everything off my USB 1.1 connected G:, ghost C: to G: (again, do I have to "wipe" the G: before ghosting the whole drive image? --is there anything else I would need to do before ghosting?), and then restore the whole drive image from G:

Contemplating the preceding, I have another ? -----after doing a drive image from C: to G: and then restoring it per your idea, what about the C: partition image that is already stored on the D:?--would I be able to restore that partition to the restored drive w/o expecting problems, OR, would I have to delete the old partition ghost on D:, make a new Partition ghost from the restored C: drive and then see if it would both pass an integrity check and restore in both Basic and Advanced mode from the Windows interface??

Regardless of your answer to my ? in the preceding paragraph,
the time involved in transferring whats on the USB 1.1 connected G: to the secondary IDE slave D:, ghosting the C: drive to G:, restoring the whole drive  ghost from G: to C:, then deleting the drive ghost from G: and transferring back from D: to G: all of the stuff I moved off it so as to have been able to make the drive ghost in the first place......is ( at least for me ) a very complex and  time consuming task.

      Given the immediately preceding  AND
 
considering that at the current time I can make, integrity check, and restore a partition ghost from the Advanced>Run Ghost Interactively>Backup/Restore in the Windows interface , and can also restore a partition from the floppy ( I presume I could also successfully do an integrity check but haven't tried that---do you want me to ?? ), I am beginning to wonder IF, considering that everything else in the system seems to be working optimally, I EVEN NEED TO BE CONCERNED that I can't make , integrity check, and restore a ghost in Basic mode??--PLEASE comment your thoughts.

Just thought of something--I haven't tried this but will if you think its worth it: I know I can't make a ghost in Basic mode, but wonder if I can in Basic mode, restore a ghost that was made in Advanced mode?---I'm referring specifically to an Advanced mode partition ghost that currently is on D: ----- PLEASE advise if you want me to attempt this. ( I could do so with impunity because I took the precaution of making a duplicate ghost ---if things screwed up I could always restore from the floppy too)

Your time ,help, and eminently LOGICAL approach to analyzing/solving my dillema is both admireable and immensely appreciated! I thank you again and am looking forward to hearing back from you-----I will stay up for a while in hopes of still doing so tonight.

Best, Peter

PS to anyone else reading this besides Nightowl and Ghost4me---please don't be bashful about getting involved!
( Dan Goodell ) ??  Hopefully??!!
 

Sometimes the light's just shining on me, other times I barely can see...... what a long strange trip its turning out to be
 
IP Logged
 
NightOwl
Radministrator
*****
Offline


"I tought I saw a puddy
tat..."

Posts: 5801
Olympia, WA--Puget Sound--USA


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #22 - Jan 25th, 2007 at 10:14am
 
barebear

Quote:
I am beginning to wonder IF, considering that everything else in the system seems to be working optimally, I EVEN NEED TO BE CONCERNED that I can't make , integrity check, and restore a ghost in Basic mode??--PLEASE comment your thoughts.

Well, that's kind of what I meant by *not Panicking*  Wink !  It, of course, is your call whether to try and fix whatever is causing the problem.

But to quote Dan Goodell from the other thread:

Quote:
This is not a major problem, and I think this type of discrepancy shouldn't interfere with the integrity of the Ghost image.

Although the anomaly isn't critical, it's not advisable to leave it that way.


Quote:
I have 3 drives all identical per my first post. In order to do a whole drive image and restore, I would have to move everything off my USB G: to my secondary IDE slave D: (can't do D; to G: because D: has much more on it--its my data drive). I then would have to ghost the whole C: drive to G:----I've never done a whole drive image; would I need to "wipe" G: before ghosting the C: drive to it??-- PLEASE advise

If your HDD has only the one partition on it, then a *whole drive*
image
will be essentially the same size as the *partition*
image
--the key word here is *image*.  Ghost, in its default mode only saves the data that is necessary to restore the HDD back to an equivalent functional state as the original in an *image* file--it does not store all the *empty space*--it's when you do a *disk-to-disk* direct clone that Ghost will, in its default mode, fill the new disk to its full capacity.  So, you do not have to make any special preparations for that *whole disk* image file except there has to be enough room for the data size of the image file.

And, *No*, you do not have to wipe the drive where you are storing the image file--the wiping of the original HDD is to eliminate the *partition table* so that any new partitioning, either from a restored image or from partitioning from scratch, will have to write a new *partition table* which can not then be influenced by the previous *partition table*--basically starting clean and fresh as if you bought the HDD off the shelf this morning!

Quote:
after doing a drive image from C: to G: and then restoring it per your idea, what about the C: partition image that is already stored on the D:?--would I be able to restore that partition to the restored drive w/o expecting problems, OR, would I have to delete the old partition ghost on D:, make a new Partition ghost from the restored C: drive and then see if it would both pass an integrity check and restore in both Basic and Advanced mode from the Windows interface??

You should be able to use any Ghost image that is not corrupted to restore to any partition you choose--there's always the possibility that an OS partition will not boot if you have a complicated partition structure and you are restoring it to a position on the HDD that it did not originally exist--but you do not appear to have those issues.

Quote:
Just thought of something--I haven't tried this but will if you think its worth it: I know I can't make a ghost in Basic mode, but wonder if I can in Basic mode, restore a ghost that was made in Advanced mode?---I'm referring specifically to an Advanced mode partition ghost that currently is on D: ----- PLEASE advise if you want me to attempt this.

You could certainly try this to see if it helps solve the problem--and it would tell you if the Windows interface is having the *offset* error when doing this type of restore when using the *Basic Mode*--just as it is having attempting to do an *image creation* and *Integrity check*.

Quote:
( I presume I could also successfully do an integrity check but haven't tried that---do you want me to ??)

I never assume a Ghost image file is valid until it passes an Integrity check--if I'm hoping to rely on it for a future restore, I put it through an Integrity check!

If you are going to proceed in attempting to eliminate the *offset* error found in the Ghost Windows interface--there are two possible programs that you can use to *wipe* your HDD that I am familiar with--(I'm sure there are others--for instance in the past I had IBM HDD's and the company made a diagnostic DOS boot floppy disk that had utility programs on it--one of which was a wiping function):

1.  Because you already have Ghost--there is *gdisk.exe*, the Ghost DOS partitioning tool (there is *gdisk32.exe* also, but that only works from within Windows--and will not work on the OS HDD that you launch the program from).

2.  
MBRWizard - The MBR utility you've been looking for!


This is a free utility for down loading.  It has both a *Windows* version--*MBRWiz.exe* and a DOS version--*MBRWizd.exe*.  I simply copy the *mbrwizd.exe* to a floppy disk, use a boot floppy to get to a A:\ prompt and then switch floppy disks so the one with the *mbrwizd.exe* is in the drive.

With *GDisk*, you can only wipe the *whole* drive--great if you need to securely wipe your HDD for security reasons--but takes a long time.

MBRWizard can be used to wipe just the *boot tract*, absolute sectors 0-62--which will destroy the Master Boot Record and the Master Partition Table, and anything else that's in those first 63 sectors (which is exactly what you want to do to start *clean* as far as the partition structure of your HDD).  (If you have any special programs that use the *boot tract* for storage of special passwords or activation codes--you do not want to wipe that unless you have the ability to restore those codes--most folks do not have those issues--probably you do not--if you do, you should already know about that!)

When using a wiping program in DOS, I always remove any other HDD's that I'm not wishing to wipe first so there can be no accidental wiping of the wrong HDD!

So, if you plan on proceeding, 1.  you have to be *sure* that you have a backup that you can restore in the case of some failure during the process (a *whole disk* Ghost image that passes the Integrity check), 2.  we can discuss the command line to wipe your HDD with either GDisk or MBRWizard.
 

____________________________________________________________________________________________

No question is stupid ... but, possibly the answers are Wink !
 
IP Logged
 
barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #23 - Jan 25th, 2007 at 3:40pm
 
Hi Nightowl,

I read your last post and am feeling overwhelmed by lack of experience/knowledge on my part-----

I tried via Basic mode to restore a ghost made in Advanced; the procedure failed.

I read your post several times and am still unclear on this----if I'm going to do a whole C: drive image to USB 1.1 G:, do I need to wipe the data presently on G:, or when I do the ghost , is all the stuff on G: just automatically overwritten?, or does the C: drive image just fit in the present remaining free space of G:?

There is more than enough room on G: to accept all the data on C: w/o having to remove any data presently on G:  If I understand correctly, I don't need to do anything but make the drive image w/ no other preparation?---My C: data is a total of 11.5GB  on 80 GB drive, and I presently have 21GB free on G: (80GB HD) Please let me know if I've got the concept correct per my immediately preceding statements, and enlighten me if I'm wrong.

In light of Dan's comment  "This is not a major problem, and I think this type of discrepancy shouldn't interfere with the integrity of the Ghost image. Although the anomaly isn't critical, it's not advisable to leave it that way."  ----- if this were your system and Ghost Advanced from Windows and the boot floppy both did everything needed (backup, integrity check, restore), would you consider it necessary to go thru the process of  doing a drive image to G:, using MBR wizard, and then restoring the drive image from G:, or just leave things the way they are now and not worry about GHost Basic not working??
I ask this because I know I'm way too anal and have a big problem w/ trying to have everything just perfect all the time. I know you're you and I'm me and tastes differ--what I think I'm really asking is whether doing the drive image, MBR wizard and then an image restore is really essential to my system stability, or whether I can safely ignore the malfunctioning of Ghost Basic and just stick to, as I have been all along, Ghost Advanced and/or my ghost boot floppy?

I will wait for your comments and then based on your feedback  either bite the bullet and do the drive image, run MBR wizard and restore, or stick w/ the status quo. ( I am most apprehensive since I've never done a whole drive image and am utterly unfamiliar w/ MBR wizard. By the time you reply to this, though, I will have MBR wizard downloaded and waiting --I will NOT run it w/o step by step detailed guidance from you--I am utterly petrified of making a catastrophic  error).

One more ?--you mention "using a boot floopy to get to a A:\ prompt and then switch floppy disks so the one with mbrwizd.exe is in the drive"--am I correct that I could use the ghost boot floppy to get to the A:\ prompt by just going to "Quit"?--I think I've gotten there before when restoring a Ghost via boot floppy?

Thanks again for your great patience and understanding!!

Best, Peter
 

Sometimes the light's just shining on me, other times I barely can see...... what a long strange trip its turning out to be
 
IP Logged
 
Dan Goodell
Special Guest
*****
Offline



Posts: 552
N California


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #24 - Jan 25th, 2007 at 7:33pm
 
(... Puff ... puff ... puff ...)  Okay, I'm back--did anything happen while I was gone?  Grin

I was preoccupied for a few days, mostly with repairing and backing up a laptop with a bad hard disk.  I see Ghost4me posted in another thread about Spinrite, so let me embellish the plug.  This laptop would POST but wouldn't boot, and running the disk manufacturer's diagnostic utility returned, "disk failure, return to manufacturer for replacement."  I couldn't ghost it (nor Drive Image, nor BootIt) because the image creation would fail when it hit an unreadable sector.  So I ran Spinrite 6 on it.  It breezed through the sectors until it hit an unreadable sector, then it worked on the sector for the better part of an hour.  When Spinrite was done, everything was back, and even the manufacturer's utility gave the disk a clean bill of health.  So yes, Spinrite works!

Now to barebear's issue ...

I don't use Ghost from within Windows, so I'm not going to comment on why it behaves differently from DOS.  I also am not that familiar with reading the Windows log files, but ...

Peter says it's an "Invalid Partition Offset" error, and I think I can see where in the error logs that is showing up.  Unfortunately, the logs never show what's in the partition tables, but near the end of the log are these lines, which give a hint of what the partition tables probably contain:
    Key @LFO1:1
    Path     1:1
    Desc     []
    Type     NTFS
    Disk     0
    Offset   63

    Key @LFO2:1
    Path     2:1
    Desc     []
    Type     NTFS
    Disk     1
    Offset   16128

    Key @LFO3:1
    Path     3:1
    Desc     []
    Type     NTFS
    Disk     2
    Offset   16128

A normal single-partition disk should have its one-and-only partition start on Cyl/Head/Sector = 0/1/1, which translates to Offset 63.  Note that Disk 0 looks okay, but Disks 2 and 3 show Offset 16128.  That translates to CHS = 1/0/2.  Partitions are supposed to begin on cylinder boundaries, not two sectors into one of the sides.  That means the partition is misaligned.  I'm not going to guess how this might have happened, but the prime suspect would have to be whatever utility created those partitions in the first place.  They don't just "shift" on their own.

To confirm this diagnosis, Peter should download ptedit32.  Run it from within Windows, and look at the actual partition tables on each disk.  Post screenshots or report here what ptedit32 shows for the partition table numbers.


 
 
IP Logged
 
John.
Übermensch
*****
Offline



Posts: 2072


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #25 - Jan 25th, 2007 at 7:49pm
 
barebear wrote on Jan 25th, 2007 at 3:40pm:
I will wait for your comments and then based on your feedback  either bite the bullet and do the drive image, run MBR wizard and restore, or stick w/ the status quo.

Before you do something drastic, have you run the demo mode from Partition Table Doctor?  Click on the "check" icon and you should get a report which you can post back here.

...
 

Ghost4me  Ghost 9, 10, 12, 14, 15.  Windows XP, Vista, Windows 7
 
IP Logged
 

barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #26 - Jan 25th, 2007 at 8:58pm
 
Hi Dan and Ghost4me,

Am I glad to hear from both of you!

I have downloaded both PTdemo and PTEdit32; I will run them and post the results here, but don't know how to get a picture in here like Ghost4me did--do I just drag and drop a .jpg capture or what? I just tried to drag/drop a Partition Magic Screenshot in here and it didn't work.
HOW DO I GET A PICTURE IN HERE LIKE Ghost4me DID??

Please advise and in the meanwhile I will run those 2 progs

Dan, All my drives were done by Partition Magic and I have the same question for you and Ghost4me per my last post-- " if this were your system and Ghost Advanced from Windows and the boot floppy both did everything needed (backup, integrity check, restore), would you consider it necessary to go thru the process of  doing a drive image to G:, using MBR wizard, and then restoring the drive image from G:, or just leave things the way they are now and not worry about GHost Basic not working?? What I think I'm really asking is whether doing the drive image, MBR wizard and then an image restore is really essential to my system stability, or whether I can safely ignore the malfunctioning of Ghost Basic and just stick to, as I have been all along, Ghost Advanced and/or my ghost boot floppy"

Dan , I know that in the thread which I originally scroogled and led to my first post you wrote "This is not a major problem, and I think this type of discrepancy shouldn't interfere with the integrity of the Ghost image. Although the anomaly isn't critical, it's not advisable to leave it that way." ----- is there a specific danger to my system that I need to be aware of and deal with?!!
For now let me restate C: is Primary IDE master, D: is secondary IDE slave, and G: is USB 1.1--all are the only partitions on each of the respective exactly identical drives they are on and all the partitions were originally created and later modified by Partition Magic  ( D: and G: both used to be active primary partitions, and I then used Partition Magic to convert them to logical extended, and you can read about what I recently did to C: in an earlier post in this thread).

As soon as I know how to stick a picture in here like Ghost4me did, I should be able to make things much clearer.

Dan, If you can take the time PLEASE read through this thread from my original post (if you haven't already) --- maybe there is some other detail that will be of help from an earlier log?

Eagerly waiting to hear back from you and in the meantime will get those 2 progs and screenshots going and made.

As I wrote in an earlier post, this is the only forum I've ever been on where I couldn't post files,.jpg's, etc as attachments to a post--would sure make it easier for an unsophisticated user like me!

Best, Peter
 

Sometimes the light's just shining on me, other times I barely can see...... what a long strange trip its turning out to be
 
IP Logged
 
Ex Member




Back to top
R
Reply #27 -
 
 
 
IP Logged
 
Pages: 1 2 
Send Topic Print