Ghost Imaging Problem

  • Thread starter Thread starter No.Thanks
  • Start date Start date
N

No.Thanks

I'm hoping some of you might be able to help. I've run into a problem
that I've never seen before and can't seem to solve. I have a BD7II
board with 512mb of RAM, 2.6GHz CPU, Matrox G-450, IBM 30GB drive for
my C: drive and a IBM 40GB drive for backups. I just did a fresh
install and want to image the drive so I don't have to do this again
if things go south... I created a boot disk and boot with it and
create an image. I get to about 98% of completion where it asks for
you to put in the 2nd media and soon thereafter I get an error message
saying there is not enough room on the D drive... Now I'm only
Ghosting about 5GB of data and putting it on a drive that has over
36GB of free space. No matter what I do I keep getting this error
message. I've used this program on my other 3 computers (all different
machines AMD and Intel but no P4 machines...) and have never
encountered this problem. I've tried imaging to other drives of
varying sizes and it's always the same.

Any ideas of what's going on and more importantly, what I can do to
fix this so I have a working image of my C drive? Thanks for any help
that you guys can give!

Dave
 
Forgot to mention, the version of Ghost that I'm using is 2002 for Win
2k + XP only.

Dave
 
said this...
Forgot to mention, the version of Ghost that I'm using is 2002 for Win
2k + XP only.

Dave
Click to expand...

If you open 'ghost' and point it at the D: drive, what size does it see?
 
}> Forgot to mention, the version of Ghost that I'm using is 2002 for
}> Win
}> 2k + XP only.
}>
}> Dave
}
}If you open 'ghost' and point it at the D: drive, what size does it
}see?

Good question, as I didn't say, it sees it just fine. The BIOS, Windows,
and Ghost Viewer and in DOS all see the target drive as the proper size
and having over 37gb free. It's driving me nuts why this is happening,
nothing I have tried seems to help. I've made sure that both drives are
run in LBA mode as some imaging software needs that but I just don't get
this one...

Thanks for the reply.

Dave
 
I'm hoping some of you might be able to help. I've run into a problem
that I've never seen before and can't seem to solve. I have a BD7II
board with 512mb of RAM, 2.6GHz CPU, Matrox G-450, IBM 30GB drive for
my C: drive and a IBM 40GB drive for backups. I just did a fresh
install and want to image the drive so I don't have to do this again
if things go south... I created a boot disk and boot with it and
create an image. I get to about 98% of completion where it asks for
you to put in the 2nd media and soon thereafter I get an error message
saying there is not enough room on the D drive... Now I'm only
Ghosting about 5GB of data and putting it on a drive that has over
36GB of free space. No matter what I do I keep getting this error
message. I've used this program on my other 3 computers (all different
machines AMD and Intel but no P4 machines...) and have never
encountered this problem. I've tried imaging to other drives of
varying sizes and it's always the same.

Any ideas of what's going on and more importantly, what I can do to
fix this so I have a working image of my C drive? Thanks for any help
that you guys can give!

Dave
Click to expand...

Hi,
I remember something similar happening when I used that version of Ghost on
the PC I had at the time.
I'm pretty sure all I did when it asked for the next media was to push
enter, which seemed to persuade it that the media had been changed.
I think it's to do with the maximum size set for each segment of the Ghost
image, which I'm sure you can alter (can't remember how at the moment
though)

HTH
SteveH
 
Howdy!

I'm hoping some of you might be able to help. I've run into a problem
that I've never seen before and can't seem to solve. I have a BD7II
board with 512mb of RAM, 2.6GHz CPU, Matrox G-450, IBM 30GB drive for
my C: drive and a IBM 40GB drive for backups. I just did a fresh
install and want to image the drive so I don't have to do this again
if things go south... I created a boot disk and boot with it and
create an image. I get to about 98% of completion where it asks for
you to put in the 2nd media and soon thereafter I get an error message
saying there is not enough room on the D drive... Now I'm only
Ghosting about 5GB of data and putting it on a drive that has over
36GB of free space. No matter what I do I keep getting this error
message. I've used this program on my other 3 computers (all different
machines AMD and Intel but no P4 machines...) and have never
encountered this problem. I've tried imaging to other drives of
varying sizes and it's always the same.

Any ideas of what's going on and more importantly, what I can do to
fix this so I have a working image of my C drive? Thanks for any help
that you guys can give!
Click to expand...

Try adding the SPLIT=650 AUTO directives to the GHOST command line.

Why?

Well, you're probably hitting the 2GB file size limit, and an AUTO
does an auto name of subsequent files, and a SPLIT=650 leaves them just
under CD-sized, so you can dump the files onto CDs for when the whole HD
dies.

BTW - this IS in the manual. Didn't you read it?

RwP
 
I remember something similar happening when I used that version of Ghost on
the PC I had at the time.
I'm pretty sure all I did when it asked for the next media was to push
enter, which seemed to persuade it that the media had been changed.
Click to expand...

Yes, this is what I always do and have never had a problem but for
some reason it won't work with this particular setup. :(
I think it's to do with the maximum size set for each segment of the Ghost
image, which I'm sure you can alter (can't remember how at the moment
though)
Click to expand...

Hmmm, that would be great if you can do this as it might help. You're
not referring to using the Ghost Viewer and spanning are you? Thanks
for your reply.

Dave
 
-
Ralph Wade Phillips stood up at show-n-tell, in
[email protected], and said:
Howdy!



Try adding the SPLIT=650 AUTO directives to the GHOST command
line.

Why?

Well, you're probably hitting the 2GB file size limit, and an
AUTO does an auto name of subsequent files, and a SPLIT=650 leaves
them just under CD-sized, so you can dump the files onto CDs for when
the whole HD dies.

BTW - this IS in the manual. Didn't you read it?
Click to expand...


What 2GB file size limit?
 
Howdy!

Strontium said:
-
Ralph Wade Phillips stood up at show-n-tell, in
[email protected], and said:


What 2GB file size limit?
Click to expand...

The maximum size of a Ghost data file (at least through 2002 / 7.5,
anyway - haven't looked at 2003 yet) is 2GB. Which is more of a combination
of the FAT32 4GB limit and a lazy programmer that didn't pay attention to
the sign (as in positive / negative).

RwP
 
Try adding the SPLIT=650 AUTO directives to the GHOST command line.

Why?

Well, you're probably hitting the 2GB file size limit, and an AUTO
does an auto name of subsequent files, and a SPLIT=650 leaves them just
under CD-sized, so you can dump the files onto CDs for when the whole HD
dies.
Click to expand...

I guess I'm wondering why I even need to do this when it has never
been a problem in the past. I don't want to go out and buy 8+ CDs to
store this on as I have a 2nd HD for this purpose and it has served me
well in all my other machines. Thanks for the suggestion but I'd
really like to understand why this is even a problem to begin with.
BTW - this IS in the manual. Didn't you read it?
Click to expand...

Yes, it is and I have. I've just never had a reason or desire to do
this. Thanks for the reply.

Dave
 
| I'm hoping some of you might be able to help. I've run into a problem
| that I've never seen before and can't seem to solve. I have a BD7II
| board with 512mb of RAM, 2.6GHz CPU, Matrox G-450, IBM 30GB drive for
| my C: drive and a IBM 40GB drive for backups. I just did a fresh
| install and want to image the drive so I don't have to do this again
| if things go south... I created a boot disk and boot with it and
| create an image. I get to about 98% of completion where it asks for
| you to put in the 2nd media and soon thereafter I get an error message
| saying there is not enough room on the D drive... Now I'm only
| Ghosting about 5GB of data and putting it on a drive that has over
| 36GB of free space. No matter what I do I keep getting this error
| message. I've used this program on my other 3 computers (all different
| machines AMD and Intel but no P4 machines...) and have never
| encountered this problem. I've tried imaging to other drives of
| varying sizes and it's always the same.
|
| Any ideas of what's going on and more importantly, what I can do to
| fix this so I have a working image of my C drive? Thanks for any help
| that you guys can give!

Have you tried "ordering" the image from within Windows? I find that usually
works better than when I boot with the Ghost disk and do everything from DOS.

If you've got 36GB free on the target drive, I can't imagine why there would be
any problem. Did you defrag the target drive first?

Larc



§§§ - Please raise temperature of mail to reply by e-mail - §§§
 
}Have you tried "ordering" the image from within Windows? I find that
}usually works better than when I boot with the Ghost disk and do
}everything from DOS.

No, I've never done this but have always run the boot disk and have
never had a problem in 5+ years (used earlier version also) of doing
this until now! I'll give that a shot and see but I'm doubtful.

}If you've got 36GB free on the target drive, I can't imagine why there
}would be any problem. Did you defrag the target drive first?

This is my feeling. No, I didn't defrag the target drive as there was
nothing on it initially when I first got this problem. There is
something going on with this system that is preventing the image process
from completing but I'll be darned if I know what it is! I was just
hoping that someone else has encountered this problem and knows what to
do to get around it or fix it permanently. Thanks.

Dave
 
Howdy!

I guess I'm wondering why I even need to do this when it has never
been a problem in the past. I don't want to go out and buy 8+ CDs to
store this on as I have a 2nd HD for this purpose and it has served me
well in all my other machines. Thanks for the suggestion but I'd
really like to understand why this is even a problem to begin with.
Click to expand...

Then you can use a SPLIT=2000 directive instead. I just like 650M
splits so that I CAN stuff them onto a CD-R if I so desire.

BTW - Where are you in the world? I buy blanks at about 10 cents
each (CD-R Verbatim on spindles).
Yes, it is and I have. I've just never had a reason or desire to do
this. Thanks for the reply.
Click to expand...

RwP
 
BTW - Where are you in the world? I buy blanks at about 10 cents
each (CD-R Verbatim on spindles).
Click to expand...

Where are you getting Verbatims at 10¢ each? I buy the DataLife disks in
spindles of 100 for about $24 at Sam's Club, at last purchase anyway
(several months ago). Are they down to 10¢ now in the U.S.? If so, where?
(I'm getting low and need more.)
 
I'm hoping some of you might be able to help. I've run into a problem
that I've never seen before and can't seem to solve. I have a BD7II
board with 512mb of RAM, 2.6GHz CPU, Matrox G-450, IBM 30GB drive for
my C: drive and a IBM 40GB drive for backups. I just did a fresh
install and want to image the drive so I don't have to do this again
if things go south... I created a boot disk and boot with it and
create an image. I get to about 98% of completion where it asks for
you to put in the 2nd media and soon thereafter I get an error message
saying there is not enough room on the D drive... Now I'm only
Ghosting about 5GB of data and putting it on a drive that has over
36GB of free space. No matter what I do I keep getting this error
message. I've used this program on my other 3 computers (all different
machines AMD and Intel but no P4 machines...) and have never
encountered this problem. I've tried imaging to other drives of
varying sizes and it's always the same.

Any ideas of what's going on and more importantly, what I can do to
fix this so I have a working image of my C drive? Thanks for any help
that you guys can give!

Dave
Click to expand...

Hi Dave, I've had the same problem, where if the Ghost boot disk,
whether a floppy or boot CD, has been created with a version of DOS
other than Ghosts own PC-DOS then the target drive or partition may not
be recognised as FAT32 or NTFS, so Ghost thinks the target drive
capacity is smaller than it actually is.

Hope this helps.
 
Hi Dave, I've had the same problem, where if the Ghost boot disk,
whether a floppy or boot CD, has been created with a version of DOS
other than Ghosts own PC-DOS then the target drive or partition may not
be recognised as FAT32 or NTFS, so Ghost thinks the target drive
capacity is smaller than it actually is.

Hope this helps.
Click to expand...

Hi George,

Thanks for your reply, it seems it was very close. I just stumbled
upon a possible solution on Symantec's own site. It's actually just
the opposite of what you state. I always have used PC-DOS when making
my boot disks and have never had a problem to date. Well on their site
they mention that a few "rare" types of computer BIOS' might be
incompatible with PC-DOS and you'll get this error that I'm
experiencing. Has nothing to do with the size of the image before
spanning to another one.

I'll give it a shot later today after work and see. Thanks again for
your idea!

Avatar
 
Then you can use a SPLIT=2000 directive instead. I just like 650M
splits so that I CAN stuff them onto a CD-R if I so desire.
Click to expand...

I understand your reasons for doing so. I just don't feel that this is
the problem. After reading Symantec's database again I found a
possible solution:

Some computer BIOS versions are incompatible with PC-DOS so you need
to use MS-DOS instead or you'll get the error I'm seeing.
BTW - Where are you in the world? I buy blanks at about 10 cents
each (CD-R Verbatim on spindles).
Click to expand...

I'm in the states but you didn't get my point, as I didn't explain it
clearly. It's not the cost, it's the actually going out and buying
them (I'm not near any place that sells them and would spend over an
hour doing so) but more importantly, the added time it takes to sit
and keep swapping the CDs. I only have to respond once during this
process so it's pretty much unattended, I'd have to hang around and
change disks and respond about 10x. Not that big of a deal but not
necessary either with the way I have things set up. Thanks again for
replying and giving your ideas.

Dave
 
Howdy!

Bob Davis said:
Where are you getting Verbatims at 10¢ each? I buy the DataLife disks in
spindles of 100 for about $24 at Sam's Club, at last purchase anyway
(several months ago). Are they down to 10¢ now in the U.S.? If so, where?
(I'm getting low and need more.)
Click to expand...

That will teach me to post without enough caffeine in my blood.

You're right, somehow I divided 24 by 100 and got .10 ...

Not that there's THAT much difference in the point, of course ...

RwP
 
Howdy!

I understand your reasons for doing so. I just don't feel that this is
the problem. After reading Symantec's database again I found a
possible solution:

Some computer BIOS versions are incompatible with PC-DOS so you need
to use MS-DOS instead or you'll get the error I'm seeing.
Click to expand...

Mmm ... Well, I've not run into that myself. But I AM aware of the
2GB file size limit.
I'm in the states but you didn't get my point, as I didn't explain it
clearly. It's not the cost, it's the actually going out and buying
them (I'm not near any place that sells them and would spend over an
hour doing so) but more importantly, the added time it takes to sit
and keep swapping the CDs. I only have to respond once during this
process so it's pretty much unattended, I'd have to hang around and
change disks and respond about 10x. Not that big of a deal but not
necessary either with the way I have things set up. Thanks again for
replying and giving your ideas.
Click to expand...

I don't think you quite understood me ... I archive to a HARD DISK
with the SPLIT=650 directive, so that I can LATER burn the CD-Rs off.

So I don't stand there waiting to feed the next CD-R into it, but I
can burn them later.

It's called "planning for the maximum of flexibility".

RwP
 
I don't think you quite understood me ... I archive to a HARD DISK
with the SPLIT=650 directive, so that I can LATER burn the CD-Rs off.

So I don't stand there waiting to feed the next CD-R into it, but I
can burn them later.
Click to expand...

Yes, I didn't understand you right. Thanks for setting me straight.
It's called "planning for the maximum of flexibility".
Click to expand...

I got it now. :)

Dave
 
Back
Top