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 26767 times)
barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Invalid Partition Offset Error during Integrity Ck
Jan 22nd, 2007 at 2:54am
 
I found and registered with this forum today after doing a Scroogle  (Google without you being spied on and having your info recorded  www.scroogle .org ) search for " Invalid Partition Offset message in Norton Ghost ".

My tale is slightly different than the one from the link I scroogled to that has led to my registering:

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=Full_Rad_Board;action=display;nu...

I run XP Pro SP2 fully updated, all drivers and software updated, no virus or malware issues (daily scans/updates). Processor is Athlon 2400 on Asus A7N8X deluxe, 1 GB Mushkin Black High performance DDR-SDRAM.
The system has 3 identical 80GB Western Digital 7200rpm 8MB cache HD's----my C:, D: which is a secondary IDE data drive where I keep the "My Documents" folder instead of using the Windows one on C:, and then G: which is an
external USB 1.1 connection.

When applicable,I make a ghost of C: to a folder inside D:\My Documents, and then overnite a backup utility sends the entire My Documents folder to a folder on G: simply called "Backup"

I run Norton Ghost 2003 about once a week and have "always perform an integrity check" checked in "options".
I realized,after what occurred tonite that led me on a Scroogle search to here,that I had never seen a verification of any sort that an integrity check had been performed.

What happened tonight was that I created a ghost and got the usual "successfully completed" screen, BUT I noticed that instead of transferring the usual 1.45 GB- 1.5GB of data per minute only about 760MB per minute was transferring. I went back to Windows, opened Ghost--advanced--image integrity check, and generated the error.

Now for the teaser: I keep the 3 most recent ghosts just because of "extra insurance" --my C drive has 63GB free space, D and G 32-33GB free. I therefore decided to attempt a restore of the image ( the restore ran at its usual speed of approx 1.6GB per minute ), and that procedure worked perfectly despite the integrity check failure. I then decided to try making the ghost again ( after deleting the image I restored from) and this time the ghost transferred at the usual speed of at least 1.45 GB per minute.

At that point I realized that per my option settings I should have been seeing an image integrity verification screen for not only this but all the other ghosts I have made previously, and therefore didn't even bother trying an image integrity check on this ghost

My partions are all done by Partition Magic, I run Diskeeper on "automatic defrag" for all 3 drives, and I'm not aware of any problems in the system whatsoever---everything seems to be running clean and fast.

I do notice that the little yellow "in use" light on the front of my removable bay enclosure for the D: drive is frequently on along with the green power light (always on of course) even though the drive isn't being used for anything. When I open Process EXplorer while the yellow light is on, I see that a significant ( often up to 50% of CPU usage ) is dedicated to "Hardware Interrupts". Could that be a clue to whats going on about image ntegrity checks not being automatically run?

After reading the post I referred to above, I did download the Findpart utility and have it in a folder on my desktop. If you need me to use it, please confirm that the folder contents should be copied too and run from a floppy.

Please advise how to go about resolving the issues of enabled post ghost creation integrity checks not being done, and the failure of user initiated integrity checks failing on a perfectly good ghost (proof being the ghost restored perfectly as earlier stated)

Thank you in advance for your assistance


 

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: good ghost but failed integrity check
Reply #1 - Jan 22nd, 2007 at 3:28am
 
Since my preceding post and re-reading of the post that got me here, I had a flash of inspiration, opened Partition Magic, and noticed to my surprise that my C: has a size of 76,316.6MB while my D: & G: are only 76308.7 each because they are each behind a 7.8 MB unallocated space.

I am going to resize C: to 76,305MB per the obvious.

Please advise what other actions to take.



 

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
 
Pleonasm
Übermensch
*****
Offline



Posts: 1619


Back to top
Re: good ghost but failed integrity check
Reply #2 - Jan 22nd, 2007 at 11:48am
 
Barebear, if you are interested in Scroogle, you’ll be interested in this thread:
     Anonymous Internet Surfing
 

ple • o • nasm n. “The use of more words than are required to express an idea”
 
IP Logged
 
barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: good ghost but failed integrity check
Reply #3 - Jan 23rd, 2007 at 12:26am
 
I still need help.
Partition Magic automatically resized My C: to the exact size of the other drives and I made a new ghost  to D: as described in my first post. The automatic integrity check didn't happen and the one I tried to do manually failed.
I then did a total uninstall/reinstall of Ghost, made sure " automatically verify " was checked, and made a new Ghost.
Again, the scheduled integrity check never happened and the one I then tried manually failed as before.
Since I have other ghosts, I  attempted a restore from this ghost; the procedure worked just fine despite the failed integrity check messages.
A log file was generated and since I couldn't see where/how to send it as an attachment, it follows just below.

PLEASE will someone look through this and try to help me resolve this integrity check issue----how is it that the image is good as proven by the successful restore, but the automatic integrity check never happens despite being checked in "options", and user prompted checks return the " Invalid Partition Offset-40207 "

I am getting seriously panicked that this means there is something terribly wrong with my system--despite the fact that it seems to be running as fast and clean as it ever has, and both made and restored ghosts in excellent speed of about 1.45 GB per minute

Please get back to me with any and all help you can provide.

I can't put the log in this message--I was rejected for too big a message. How can I send the log as an attachment?--I don't see a prompt anywhere for doing that. Please advise

[color=Blue][/color]
 

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: good ghost but failed integrity check
Reply #4 - Jan 23rd, 2007 at 9:10am
 
barebear

*Don't Panic*!--at least not yet--it's when your system will not boot, all your data has disappeared, or you smell electrical burning odors, and see smoke coming from your case--that's panic time  Wink !

Quote:
I can't put the log in this message--I was rejected for too big a message. How can I send the log as an attachment?--I don't see a prompt anywhere for doing that. Please advise

Will it fit in a separate post without additional comments?

Break it up into two segments and post segment one and then segment 2 in separate posts.

Most of the important information as to what Ghost did in the log is in the first part of the log--any error messages will usually be there--the last part is usually details about the individual drives and their configuration--may or may not be of value in troubleshooting.

Quote:
I then did a total uninstall/reinstall of Ghost, made sure " automatically verify " was checked, and made a new Ghost.
Again, the scheduled integrity check never happened and the one I then tried manually failed as before.

Are you watching the Ghost procedure take place, and after the image is created, do you see that the Integrity check does not take place?

Quote:
user prompted checks return the " Invalid Partition Offset-40207 "

When doing the Integrity check--Ghost is *pretending* to restore the image to a HDD--I suspect it is checking internal partition *integrity* during this check which apparently it does not check during image creation--you have already demonstrated that the image *is* okay by doing the test restore--but, obviously Ghost is detecting something that it doesn't like--even though it does not prevent your system from functioning *OK*.

*Partition Offset* has to do with where data starts and ends on the HDD--and is probably something that's stored in the Partition Table--and probably there is a mis-match between the Partition Table data and the reported size of the HDD--not my area of expertise--Dan Goodell is more likely to be able to advise on this kind of stuff.  You might be able to *attract* his attention by changing your thread title to *Invalid Partition Offset-40207 error during Integrity Check*--edit that in your first post and re-save it.

You might want to try booting from a Ghost boot floppy disk or bootable optical disc to DOS, and running the Integrity check from DOS to see if that same error occurs.
 

____________________________________________________________________________________________

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-40207 error during In
Reply #5 - Jan 23rd, 2007 at 4:41pm
 
Hi Nightowl,

I'm sure glad to hear from you--I was beginning to wonder what I'd done to upset anyone since I wasn't getting

any responses

I am watching the making of the ghost and seeing that the integrity check does not take place after the image creation.

I did boot from floppy, and am happy to say that the integrity check worked just fine

I retitled my first post but " Invalid Partition Offset-40207 error during Integr " is all that would fit.

Since you know Dan Goodell, could you try to contact him and ask him to get involved?

I am going to get the failed integrity check log into my next post(s), and then wait to hear from you and hopefully Dan.

Thank you again for getting involved--I'm really curious to hear your thoughts about the log!

How come this forum, unlike so many others I've visited, doesn't have the option to attach a file like the log file for review? So far, this is the only forum where I haven't had the option to do that.

Looking forward to hearing from you. Thanks, 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
 

barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset-40207 error during In
Reply #6 - Jan 23rd, 2007 at 4:48pm
 
Log part 1:
ImageCheckOperation 0

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

*********************************
Date   : Tue Jan 23 14:16:42 2007
Error Number: (40207)
Message: Invalid partition offset
Version: 2003.793 (Dec 17 2003, Build=793)
Command line arguments: -wizard -chkimg,@GFfb9299eb-08f9-405b-a389-f3ff645c208a:16128\My Documents\1 23 07\1 23 07.GHO -ghwrap
Active Switches :
      AutoName
      Sure
ProgMode            : PROG_LOCAL
PathName            :
DumpFile            :
DumpPos             : 0
File64 buffersize   : 0
FlagImplode         : 0
FlagExplode         : 0

CloneSrc            : @GFFB9299EB-08F9-405B-A389-F3FF645C208A:16128\MY DOCUMENTS\1 23 07\1 23 07.GHO
BatchPartSrc        : 0
BatchPartMSrc       :

CloneDst            :
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.............128564960
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.............109117984
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-40207 error during In
Reply #7 - Jan 23rd, 2007 at 4:49pm
 
log part 2:

=======================================================
=======================================================
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.............23865992
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.....23865992
  pemax..............1
  Version............0

# Ord Boot Id Ext First    Num      Last     Used     NTFS
0   0   80 7  No  00000063 156280257 156280320 23865992 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   26941005

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 ----------------------------------------------------------

[ImageCheckOperation]
AlreadyProcessedFile = YES
BeginTimeParam = Tue Jan 23 14:16:36 2007
EndTimeParam = Tue Jan 23 14:16:43 2007
ExecutionStateParam = ExecutionFailed
FileIdParam = 1169588371
PathParam = \My Documents\1 23 07\1 23 07.GHO
SourceFingerprintParam = fb9299eb-08f9-405b-a389-f3ff645c208a
SourcePartitionOffsetParam = 16128
UseLFOParam = YES
WindowsPathParam = D:\My Documents\1 23 07\1 23 07.GHO

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

-wizard "-chkimg,@GFfb9299eb-08f9-405b-a389-f3ff645c208a:16128\My Documents\1 23 07\1 23 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
 
barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset-40207 error during In
Reply #8 - Jan 23rd, 2007 at 5:03pm
 
Hi Nightowl,

I just had a thought.....

When i run ghost from the Windows interface, I don't start with "Ghost Basic"--"backup", but rather "Ghost Advanced"--"Run Ghost Interactively".

Could that be why I'm having and have been having this integrity check problem all along?!!!

Am eagerly waiting to hear from you.

Thanks again, 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-40207 error during In
Reply #9 - Jan 24th, 2007 at 12:20am
 
barebear

I presume there is another log for the image creation part?

Quote:
When i run ghost from the Windows interface, I don't start with "Ghost Basic"--"backup", but rather "Ghost Advanced"--"Run Ghost Interactively".

Could that be why I'm having and have been having this integrity check problem all along?!!!

That would represent conflicting instructions for Ghost--you have it set to perform tasks in a step-by-step interaction--but the *Options* setting is to perform a function *automatically*--you should try the process using the *basic* backup routine and see if the integrity check works automatically using that setup.

Quote:
I did boot from floppy, and am happy to say that the integrity check worked just fine

This suggests that there is a procedural problem when using the Windows interface--it further suggests that you should test the *basic* backup, and see if the integrity check now completes without problems.
 

____________________________________________________________________________________________

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 #10 - Jan 24th, 2007 at 12:44am
 
Hi Nightowl,


I am going to try and make a ghost from "basic" per your suggestion to see if the image integrity check works  by either automatic, or manual mode if the automatic doesn't work . I  will send the log generated from the making of that ghost and also any failed integrity check log(s) generated. I will post again as soon as the preceding is done (about 30 min--its now 1045PM PST)
Here is the log of the last successful ghost creation:

StartGhostOperation 1

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

[StartGhostOperation]
AlreadyProcessedFile = YES
BeginTimeParam = Tue Jan 23 16:04:15 2007
EndTimeParam = Tue Jan 23 16:13:53 2007
ExecutionStateParam = ExecutionComplete

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

-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
 

barebear
Radmeister
**
Offline


Power User--someone running
Ghost in DOS !

Posts: 77


Back to top
Re: Invalid Partition Offset-error during Integrit
Reply #11 - Jan 24th, 2007 at 1:04am
 
Hi Nightowl,

The basic mode creation failed. Here is the log--if it doesn't all fit here, the rest will be in an immediately following post

log part 1

BackupOperation 0

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

*********************************
Date   : Tue Jan 23 22:50:58 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 23 07  basic mode\1 23 07 basic mode.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 23 07  BASIC MODE\1 23 07 BASIC MODE.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.............128564960
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.............109120296
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 #12 - Jan 24th, 2007 at 1:07am
 
Hi Hightowl,


creation failure log part 2  ---wait to hear from you about what to do now

=======================================================
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.............23934888
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.....23934888
  pemax..............1
  Version............0

# Ord Boot Id Ext First    Num      Last     Used     NTFS
0   0   80 7  No  00000063 156280257 156280320 23934888 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 = Tue Jan 23 22:50:52 2007
DestFingerprintParam = fb9299eb-08f9-405b-a389-f3ff645c208a
DestPartitionOffsetParam = 16128
EndTimeParam = Tue Jan 23 22:50:59 2007
ExecutionStateParam = ExecutionFailed
FileIdParam = 23744292
PathParam = \My Documents\1 23 07  basic mode\1 23 07 basic mode.gho
SourceFingerprintParam = fb9299eb-08f9-405b-a389-f3ff645c208a
UseImageDescriptionParam = YES
UseLFOParam = YES
WindowsPathParam = D:\My Documents\1 23 07  basic mode\1 23 07 basic mode.gho

[ImageCheckOperation]
AlreadyProcessedFile = YES
DestFingerprintParam = fb9299eb-08f9-405b-a389-f3ff645c208a
DestPartitionOffsetParam = 16128
ExecutionStateParam = ExecutionNotStarted
FileIdParam = 23744292
PathParam = \My Documents\1 23 07  basic mode\1 23 07 basic mode.gho
UseLFOParam = YES
WindowsPathParam = D:\My Documents\1 23 07  basic mode\1 23 07 basic mode.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 23 07  basic mode\1 23 07 basic mode.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
 
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 #13 - Jan 24th, 2007 at 9:40am
 
barebear

So, if you run Ghost in the *Interactive* mode, you can create the image without error, but running the Integrity check from the *Interactive* mode give you the error!

But, if booted directly to DOS, the Integrity check of the image created in the *Interactive* mode runs successfully!

And, if you attempt to use the Windows Ghost interface and set up the Ghost procedure to proceed *automatically*, you get the error during image creation--as opposed to the Integrity check stage!

And, you have restored the successful image and your system works fine from that restored image that passes the DOS integrity check, but not the *Interactive* mode Integrity check!

Question--when you create the image--are you doing a *whole disk* backup (Local > Disk > to Image), or are you doing a partition backup (Local > Partition > to Image)?

Do you have PartitionMagic available?  Can you try Dan Goodell's suggested *fix* for Stephen Diebel's problem in the thread you referenced in your first post:

Quote:
Although the anomaly isn't critical, it's not advisable to leave it that way.  If you have a good partitioning tool like PartitionMagic or Bootit-NG,
I would try shrinking the partition to slightly less than max size, then increasing it again to max size
.  The partitioning utility should be able to straighten out the inconsistencies in the partition table and the partition's boot sector.


PartitionMagic can make changes to your partitions without destroying the data on the partition--always good to have a current backup before using PartitionMagic--but, I have never had a loss of data using PartitionMagic (knock on wood)!
 

____________________________________________________________________________________________

No question is stupid ... but, possibly the answers are Wink !
 
IP Logged
 
John.
Übermensch
*****
Offline



Posts: 2072


Back to top
Re: Invalid Partition Offset Error during Integrit
Reply #14 - Jan 24th, 2007 at 1:11pm
 
barebear wrote on Jan 22nd, 2007 at 2:54am:
I found and registered with this forum today after doing a ... search for " Invalid Partition Offset message in Norton Ghost ".


Have you tried the Partition Table Doctor software?
http://www.ptdd.com/

I used it successfully once to repair a partition error.
 

Ghost4me  Ghost 9, 10, 12, 14, 15.  Windows XP, Vista, Windows 7
 
IP Logged
 
Pages: 1 2 
Send Topic Print