Cloned my HD successfully but the 2nd. attempt was a failure

[Guest]

To supply the background to my post will mean a long post. So if you choose
to read it and respond, allow me to express my appreciation in advance.

I am running XPSP2.

Back in Dec. 05 I cloned my original Samsung HD to a brand new and unused
Seagate drive. (The Samsung was my only drive in the system until I stuck
the Seagate in.) I do not recall that I set the Seagate up as slave...if I
didn't I probably should have. Anyway I connected it to the same cable as
the Samsung, plugged in the power cable and cloned it successfully with
Acronis. I am pretty sure I did not have to activate at this time; however I
did have to activate the Seagate (at the time my only and master drive) after
a Repair Install a la michaelstevenstech.

But...going back, after my successful clone I took the Seagate out, stored
it and put the Samsung back in. All was as before for a while. But then
several things got screwed up and I took the Samsung out and put the Seagate
in its place--as master. Everything was hunky dory. I did add Irfanview and
Roxio Easy Media Creator 7.0--no problem with that.

Now I thought: "OK, I should now clone my Seagate to my old Samsung as I
don't have an emergency copy HD stored away." So I put the Samsung back in as
slave. This time I installed Norton Ghost 2003 (as the 15-day trial Acronis
period has ended back in December.) Both master Seagate and Samsung slave
worked just fine.

I now attempted to clone the Seagate to the Samsung. But it did not clone.
I got the message "Invalid Destination Drive...error 11030." I foundno
helpfrom Symantec re this error. it seemed reasonable to try formatting the
Samsung since the files and data I wanted were on the Seagate anyway. Thus I
right clicked on the Samsung (in this case the G drive) and did a quick
format. Then I tried again with Ghost 2003 to clone. I got the same error
message as before. From an online site I found this: "The problem occurs
because the hard drive has been changed. Did you install another HD? Is the
present HD installed correctly? (my note: answer to both questions: 'Yes').
Check if the present HD is bad using the manufacturer's utility check." i
Itried but was unable to run such a check, perhaps because Samsung no longer
makes that particular HD--it is 4 years old.

In all this I have changed none of my hardware...i.e. printers, scanners,
flashcard reader etc.

So my questions:

1.) Is my Samsung junk?

2.) Is it likely that the clone failure had something to do with XP
activation?

3.) XP requires I go into the Recovery Console to run chkdsk. Would you
recommend that?

4.) What avenues are open to me to try to get my Seagate cloned? Start
with a brand new HD ($50)? Buy Acronis (I mean it worked before. Also $50
But why when I have Ghost 2003?). What do you suggest...do I have some good
options? I should much prefer not to get into multiple command line
parameters that may or may not work, or into situations that get involved and
require endless back and forth posts with negative results or "Now What's"
for that can take a month of Sundays.

Thank you.

 

[Anna]

To supply the background to my post will mean a long post. So if you
choose
to read it and respond, allow me to express my appreciation in advance.

I am running XPSP2.

Back in Dec. 05 I cloned my original Samsung HD to a brand new and unused
Seagate drive. (The Samsung was my only drive in the system until I stuck
the Seagate in.) I do not recall that I set the Seagate up as slave...if
I
didn't I probably should have. Anyway I connected it to the same cable as
the Samsung, plugged in the power cable and cloned it successfully with
Acronis. I am pretty sure I did not have to activate at this time;
however I
did have to activate the Seagate (at the time my only and master drive)
after
a Repair Install a la michaelstevenstech.

But...going back, after my successful clone I took the Seagate out, stored
it and put the Samsung back in. All was as before for a while. But then
several things got screwed up and I took the Samsung out and put the
Seagate
in its place--as master. Everything was hunky dory. I did add Irfanview
and
Roxio Easy Media Creator 7.0--no problem with that.

Now I thought: "OK, I should now clone my Seagate to my old Samsung as I
don't have an emergency copy HD stored away." So I put the Samsung back in
as
slave. This time I installed Norton Ghost 2003 (as the 15-day trial
Acronis
period has ended back in December.) Both master Seagate and Samsung
slave
worked just fine.

I now attempted to clone the Seagate to the Samsung. But it did not
clone.
I got the message "Invalid Destination Drive...error 11030." I foundno
helpfrom Symantec re this error. it seemed reasonable to try formatting
the
Samsung since the files and data I wanted were on the Seagate anyway.
Thus I
right clicked on the Samsung (in this case the G drive) and did a quick
format. Then I tried again with Ghost 2003 to clone. I got the same
error
message as before. From an online site I found this: "The problem occurs
because the hard drive has been changed. Did you install another HD? Is
the
present HD installed correctly? (my note: answer to both questions:
'Yes').
Check if the present HD is bad using the manufacturer's utility check." i
Itried but was unable to run such a check, perhaps because Samsung no
longer
makes that particular HD--it is 4 years old.

In all this I have changed none of my hardware...i.e. printers, scanners,
flashcard reader etc.

So my questions:

1.) Is my Samsung junk?

2.) Is it likely that the clone failure had something to do with XP
activation?

3.) XP requires I go into the Recovery Console to run chkdsk. Would you
recommend that?

4.) What avenues are open to me to try to get my Seagate cloned? Start
with a brand new HD ($50)? Buy Acronis (I mean it worked before. Also
$50
But why when I have Ghost 2003?). What do you suggest...do I have some
good
options? I should much prefer not to get into multiple command line
parameters that may or may not work, or into situations that get involved
and
require endless back and forth posts with negative results or "Now What's"
for that can take a month of Sundays.

Thank you.

wumply:
1. The first thing you should do is download Samsung's HD diagnostic utility
(Shdiag.exe) available from their website at
http://www.samsung.com/Products/HardDiskDrive/utilities/shdiag.htm
It should be able to test your four-year-old Samsung HD.

If the drive checks out defective, then that's the end of that...
If it checks out OK...

2. Whatever clone failure you encountered has nothing to do with the XP
activation feature.

3. I don't understand your comment that "XP requires I go into the Recovery
Console to run chkdsk." Are you saying that when you boot to your Seagate
HD, you're getting some sort of message to that effect? Assuming your
secondary Samsung HD is disconnected, are you able to boot to your Seagate
without any problem? Is it functional in all respects?

Assuming there are no problems with your source & destination disks, i.e.,
they're both non-defective and the contents of your source disk (as it
involves the XP OS) contain no system files corruption, and both drives are
properly connected, i.e., the motherboard's BIOS detects both drives,
there's no reason why a valid clone cannot be created with the Ghost 2003
program (or with the Acronis True Image program for that matter). I assume
that when you attempted your cloning operation you disconnected any other
storage device from your computer other than the source & destination disks.
And that includes your "flashcard reader", right?
Anna

 

[Guest]

wumply:
1. The first thing you should do is download Samsung's HD diagnostic utility
(Shdiag.exe) available from their website at
http://www.samsung.com/Products/HardDiskDrive/utilities/shdiag.htm
It should be able to test your four-year-old Samsung HD.

If the drive checks out defective, then that's the end of that...
If it checks out OK...

2. Whatever clone failure you encountered has nothing to do with the XP
activation feature.

3. I don't understand your comment that "XP requires I go into the Recovery
Console to run chkdsk." Are you saying that when you boot to your Seagate
HD, you're getting some sort of message to that effect? Assuming your
secondary Samsung HD is disconnected, are you able to boot to your Seagate
without any problem? Is it functional in all respects?

Assuming there are no problems with your source & destination disks, i.e.,
they're both non-defective and the contents of your source disk (as it
involves the XP OS) contain no system files corruption, and both drives are
properly connected, i.e., the motherboard's BIOS detects both drives,
there's no reason why a valid clone cannot be created with the Ghost 2003
program (or with the Acronis True Image program for that matter). I assume
that when you attempted your cloning operation you disconnected any other
storage device from your computer other than the source & destination disks.
And that includes your "flashcard reader", right?
Anna

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

Ann:

Thanks for your reply and promptness.
-------------
My comment re having to go into Recovery Console to run chkdsk caem from
XP's Help and Support, which read: "The chkdsk comand with the parameters
listed below is only available when you are using the Recovery Console, viz:
chkdsk[drives] [/p] [/r]

Parameters

None
Used without parameters, chkdsk displays the status of the disk in the
current drive:

Specifies the drive that you want chkdsk to check.

/p

Performs an exhaustive check even if the drive is not marked for chkdsk to
run. This parameter does not make any changes to the drive.

/r

Locates bad sectors and recovers readable information. Implies /p.
-------------
I assumed that I would need to go into recovery Console before /p and /r
would work. But apparently this is not the case. But what then is meant by
"the parameters'? Aren't /p and /r THE parameters? Or is it that if not in
the Recovery Console you use [/p] and [/r] but in the Recovery Console, you
just use /p and /r?

With my secondary Samsung disconnected I can boot to my Seagate with no
problem and it works perfectly. (And if the Samsung is in there all alone,
it boots and works perfectly.)

No, I didn't realize I should have disconnected my Flash Card Reader--guess
I hadn't firmly grasped that it was a storage device. But then when I first
cloned to my new Seagate drive back last December...well, I didn't disconnect
it then either. And that clone worked beautifully. Well, I will disconnect
it in the future.

Now again I have a CDROM and a CD-RW drive...E and F. I hadn't disconnected
those either when I made my first successful clone and so not with the 2nd.
clone attempt. But I should disconnect these in future clones?

I will download and run Shdiag.exe

IF the flshcard readaer was the problem, why would i get a message saying
"Invalid Destination Drive...Error 11030"? The card reader wasn't my
destination drive.

wumply

 

[cdm]

I finally got fed up with either manual clones or Norton Ghost clones,
and I tried the Acronis True Image... It worked so well I bought it...
I don't work for them.. I'm just a guy who bought a few bad hard
drives...

Anyways... Acronis is cheap, easy to use and it works.

CDM

 

[Guest]

wumply:
1. The first thing you should do is download Samsung's HD diagnostic utility
(Shdiag.exe) available from their website at
http://www.samsung.com/Products/HardDiskDrive/utilities/shdiag.htm
It should be able to test your four-year-old Samsung HD.

If the drive checks out defective, then that's the end of that...
If it checks out OK...

2. Whatever clone failure you encountered has nothing to do with the XP
activation feature.

3. I don't understand your comment that "XP requires I go into the Recovery
Console to run chkdsk." Are you saying that when you boot to your Seagate
HD, you're getting some sort of message to that effect? Assuming your
secondary Samsung HD is disconnected, are you able to boot to your Seagate
without any problem? Is it functional in all respects?

Assuming there are no problems with your source & destination disks, i.e.,
they're both non-defective and the contents of your source disk (as it
involves the XP OS) contain no system files corruption, and both drives are
properly connected, i.e., the motherboard's BIOS detects both drives,
there's no reason why a valid clone cannot be created with the Ghost 2003
program (or with the Acronis True Image program for that matter). I assume
that when you attempted your cloning operation you disconnected any other
storage device from your computer other than the source & destination disks.
And that includes your "flashcard reader", right?
Anna

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

Ann:

Thanks for your reply and promptness.
-------------
My comment re having to go into Recovery Console to run chkdsk caem from
XP's Help and Support, which read: "The chkdsk comand with the parameters
listed below is only available when you are using the Recovery Console, viz:
chkdsk[drives] [/p] [/r]

Parameters

None
Used without parameters, chkdsk displays the status of the disk in the
current drive:

Specifies the drive that you want chkdsk to check.

/p

Performs an exhaustive check even if the drive is not marked for chkdsk to
run. This parameter does not make any changes to the drive.

/r

Locates bad sectors and recovers readable information. Implies /p.
-------------
I assumed that I would need to go into recovery Console before /p and /r
would work. But apparently this is not the case. But what then is meant by
"the parameters'? Aren't /p and /r THE parameters? Or is it that if not in
the Recovery Console you use [/p] and [/r] but in the Recovery Console, you
just use /p and /r?

With my secondary Samsung disconnected I can boot to my Seagate with no
problem and it works perfectly. (And if the Samsung is in there all alone,
it boots and works perfectly.)

No, I didn't realize I should have disconnected my Flash Card Reader--guess
I hadn't firmly grasped that it was a storage device. But then when I first
cloned to my new Seagate drive back last December...well, I didn't disconnect
it then either. And that clone worked beautifully. Well, I will disconnect
it in the future.

Now again I have a CDROM and a CD-RW drive...E and F. I hadn't disconnected
those either when I made my first successful clone and so not with the 2nd.
clone attempt. But I should disconnect these in future clones?

I will download and run Shdiag.exe

IF the flshcard readaer was the problem, why would i get a message saying
"Invalid Destination Drive...Error 11030"? The card reader wasn't my
destination drive.

wumply

================
Anna:

Problems right off with shdiag.exe (well...with me, I guess)

I downloaded shdiag.exe, double clicked on it, accepted the license
agreement. (It's DOS-like btw). The next screen read:


auto Detection of your drives:

It announced I could only select a Samsung drive. But it listed NO
drives...NONE!

Perhaps it didn't list the Samsung drive because as I metioned in my initial
post that I had formatted the Samsung drive...which I did because I thought
it might solve my cloning problem and because I only wanted the files as they
were on the Seagate? But then why didn't it find the Seagate drive and list
it. Seagate is master; Samsung jumpered as slave.

wumply

What now? Is it even possible to run the shdiag check on the Samsung drive?
I'd guess I will need to format the Samsung--does that mean loading XP onto
it or what? If I don't need to load XP on it, how do I 'just format 'it?

wumply

wumply
=============

 

[Anna]

"wumply" responds...

Ann:

Thanks for your reply and promptness.
-------------
My comment re having to go into Recovery Console to run chkdsk caem from
XP's Help and Support, which read: "The chkdsk comand with the parameters
listed below is only available when you are using the Recovery Console,
viz:
chkdsk[drives] [/p] [/r]

Parameters

None
Used without parameters, chkdsk displays the status of the disk in the
current drive:

Specifies the drive that you want chkdsk to check.

/p

Performs an exhaustive check even if the drive is not marked for chkdsk
to
run. This parameter does not make any changes to the drive.

/r

Locates bad sectors and recovers readable information. Implies /p.
-------------
I assumed that I would need to go into recovery Console before /p and /r
would work. But apparently this is not the case. But what then is meant
by
"the parameters'? Aren't /p and /r THE parameters? Or is it that if not
in
the Recovery Console you use [/p] and [/r] but in the Recovery Console,
you
just use /p and /r?

With my secondary Samsung disconnected I can boot to my Seagate with no
problem and it works perfectly. (And if the Samsung is in there all
alone,
it boots and works perfectly.)

No, I didn't realize I should have disconnected my Flash Card
Reader--guess
I hadn't firmly grasped that it was a storage device. But then when I
first
cloned to my new Seagate drive back last December...well, I didn't
disconnect
it then either. And that clone worked beautifully. Well, I will
disconnect
it in the future.

Now again I have a CDROM and a CD-RW drive...E and F. I hadn't
disconnected
those either when I made my first successful clone and so not with the
2nd.
clone attempt. But I should disconnect these in future clones?

I will download and run Shdiag.exe

IF the flshcard readaer was the problem, why would i get a message saying
"Invalid Destination Drive...Error 11030"? The card reader wasn't my
destination drive.

wumply ================

"wumply" later adds...
Anna
Problems right off with shdiag.exe (well...with me, I guess)
I downloaded shdiag.exe, double clicked on it, accepted the license
agreement. (It's DOS-like btw). The next screen read:


auto Detection of your drives:

It announced I could only select a Samsung drive. But it listed NO
drives...NONE!

Perhaps it didn't list the Samsung drive because as I metioned in my
initial
post that I had formatted the Samsung drive...which I did because I
thought
it might solve my cloning problem and because I only wanted the files as
they
were on the Seagate? But then why didn't it find the Seagate drive and
list
it. Seagate is master; Samsung jumpered as slave.

wumply

What now? Is it even possible to run the shdiag check on the Samsung
drive?
I'd guess I will need to format the Samsung--does that mean loading XP
onto
it or what? If I don't need to load XP on it, how do I 'just format 'it?

wumply

wumply:
First of all I wouldn't be concerned with using the Recovery Console at this
point. So just put that aside at least for the time being.

I'm not sure why the Samsung diagnostic utility didn't work although I have
to admit that we've run into non-recognition problems as well with that
software. When we queried Samsung tech support about it they insisted the
utility is perfectly functional. I think the Hitachi (formerly IBM)
diagnostic utility will work with the Samsung drives. I'll try it out and
let you know.

In the meantime would you explain your statement that "With my secondary
Samsung disconnected I can boot to my Seagate with no problem and it works
perfectly. And if the Samsung is in there all alone, it boots and works
perfectly." Well, if the Samsung boots and is functional, what's the
problem?
Anna

 

[Guest]

"wumply" responds...

Ann:

Thanks for your reply and promptness.
-------------
My comment re having to go into Recovery Console to run chkdsk caem from
XP's Help and Support, which read: "The chkdsk comand with the parameters
listed below is only available when you are using the Recovery Console,
viz:
chkdsk[drives] [/p] [/r]

Parameters

None
Used without parameters, chkdsk displays the status of the disk in the
current drive:

Specifies the drive that you want chkdsk to check.

/p

Performs an exhaustive check even if the drive is not marked for chkdsk
to
run. This parameter does not make any changes to the drive.

/r

Locates bad sectors and recovers readable information. Implies /p.
-------------
I assumed that I would need to go into recovery Console before /p and /r
would work. But apparently this is not the case. But what then is meant
by
"the parameters'? Aren't /p and /r THE parameters? Or is it that if not
in
the Recovery Console you use [/p] and [/r] but in the Recovery Console,
you
just use /p and /r?

With my secondary Samsung disconnected I can boot to my Seagate with no
problem and it works perfectly. (And if the Samsung is in there all
alone,
it boots and works perfectly.)

No, I didn't realize I should have disconnected my Flash Card
Reader--guess
I hadn't firmly grasped that it was a storage device. But then when I
first
cloned to my new Seagate drive back last December...well, I didn't
disconnect
it then either. And that clone worked beautifully. Well, I will
disconnect
it in the future.

Now again I have a CDROM and a CD-RW drive...E and F. I hadn't
disconnected
those either when I made my first successful clone and so not with the
2nd.
clone attempt. But I should disconnect these in future clones?

I will download and run Shdiag.exe

IF the flshcard readaer was the problem, why would i get a message saying
"Invalid Destination Drive...Error 11030"? The card reader wasn't my
destination drive.

wumply ================

"wumply" later adds...
Anna
Problems right off with shdiag.exe (well...with me, I guess)
I downloaded shdiag.exe, double clicked on it, accepted the license
agreement. (It's DOS-like btw). The next screen read:


auto Detection of your drives:

It announced I could only select a Samsung drive. But it listed NO
drives...NONE!

Perhaps it didn't list the Samsung drive because as I metioned in my
initial
post that I had formatted the Samsung drive...which I did because I
thought
it might solve my cloning problem and because I only wanted the files as
they
were on the Seagate? But then why didn't it find the Seagate drive and
list
it. Seagate is master; Samsung jumpered as slave.

wumply

What now? Is it even possible to run the shdiag check on the Samsung
drive?
I'd guess I will need to format the Samsung--does that mean loading XP
onto
it or what? If I don't need to load XP on it, how do I 'just format 'it?

wumply

wumply:
First of all I wouldn't be concerned with using the Recovery Console at this
point. So just put that aside at least for the time being.

I'm not sure why the Samsung diagnostic utility didn't work although I have
to admit that we've run into non-recognition problems as well with that
software. When we queried Samsung tech support about it they insisted the
utility is perfectly functional. I think the Hitachi (formerly IBM)
diagnostic utility will work with the Samsung drives. I'll try it out and
let you know.

In the meantime would you explain your statement that "With my secondary
Samsung disconnected I can boot to my Seagate with no problem and it works
perfectly. And if the Samsung is in there all alone, it boots and works
perfectly." Well, if the Samsung boots and is functional, what's the
problem?
Anna
============

Anna...Hi:

This interchange may be getting to a poit where a phone call would be
practical. So if you would like to continue this by phone, perhaps you could
email me ([email protected]) your phone #and tell me of a good time to
call you. That way I could pay for the call. I'm retired so anytime would
be good for me. If you should not be amenable to this suggestion and/or feel
things are getting too involved to make continuing via this forum practical,
then I would understand if you should wish to opt out. I hope you won't feel
that...but neither do I want to be an imposition.

OK re holding on the recovery console matter. Your Hitachi diagnostic
try-outnoted. Hope it's successful.

A question(new): Will my 'quick" format of my /Samsung (made AFTER the
initial attempt to clone the Seagate to the Samsung failed) prevent a cloning
in and of itself? I formatted it becuse I reasoned that would make it blank
like a new drive andI hoped then it would clone. (It didn't though.)

Re my statement that was unclear to you, I had written: "with my secondary
(slave) Samsung disconnected I can boot to my Seagate with no problem and it
works perfectly." That was in answer to your question. (My adding "that if
the Samsung is in there all alone, it too boots and works perfectly" was
imprecise. It WAS true before the format and afterwards, of course, false.
What I had meant to indicate was that before I had formatted the Sansung and
while it was instealled with the Seagate as master, the Seagate booted OK
and worked OK, AND that in this situation, I could also access and work with
the Samsung slave.) BUT I COULD NOT, EVEN BEFORE THE FORMAT, CLONE THE
SAMSUNG FROM THE SEAGATE.) THAT was/is the problem--that was what was NOT
working. (I wanted to cloned the Seagate as it had some apps added since I
started using it--apps that were not on the Samsung.

wumply
==============

 

[Anna]

(THE BASIC ISSUE IS THAT USING THE GHOST 2003 PROGRAM, THE OP HAS BEEN
UNABLE TO CLONE THE CONTENTS OF ONE HD TO ANOTHER HD (HIS SAMSUNG HD). IT'S
NOT CLEAR WHETHER THE SAMSUNG HD IS DEFECTIVE AND THAT'S WHAT CAUSING THE
PROBLEM)

SNIP

Anna...Hi:
This interchange may be getting to a poit where a phone call would be
practical. So if you would like to continue this by phone, perhaps you
could
email me ([email protected]) your phone #and tell me of a good time to
call you. That way I could pay for the call. I'm retired so anytime
would
be good for me. If you should not be amenable to this suggestion and/or
feel
things are getting too involved to make continuing via this forum
practical,
then I would understand if you should wish to opt out. I hope you won't
feel
that...but neither do I want to be an imposition.

OK re holding on the recovery console matter. Your Hitachi diagnostic
try-outnoted. Hope it's successful.

A question(new): Will my 'quick" format of my /Samsung (made AFTER the
initial attempt to clone the Seagate to the Samsung failed) prevent a
cloning
in and of itself? I formatted it becuse I reasoned that would make it
blank
like a new drive andI hoped then it would clone. (It didn't though.)

Re my statement that was unclear to you, I had written: "with my secondary
(slave) Samsung disconnected I can boot to my Seagate with no problem and
it
works perfectly." That was in answer to your question. (My adding "that
if
the Samsung is in there all alone, it too boots and works perfectly" was
imprecise. It WAS true before the format and afterwards, of course,
false.
What I had meant to indicate was that before I had formatted the Sansung
and
while it was instealled with the Seagate as master, the Seagate booted OK
and worked OK, AND that in this situation, I could also access and work
with
the Samsung slave.) BUT I COULD NOT, EVEN BEFORE THE FORMAT, CLONE THE
SAMSUNG FROM THE SEAGATE.) THAT was/is the problem--that was what was NOT
working. (I wanted to cloned the Seagate as it had some apps added since
I
started using it--apps that were not on the Samsung.

wumply

wumply:
First of all, formatting the Samsung HD (either "quick" or regular) will
have NO effect in resolving your problem. If the cloning process fails, as
it apparently has in your case, a re:format of the drive will not correct
the situation.

As I suspected, the Hitachi/IBM diagnostic utility I mentioned will detect
your Samsung HD, so download that Drive Fitness Test utility from:
http://www.hgst.com/hdd/support/download.htm and test out your drive.

Since you have the Ghost 2003 program available to you, here are
step-by-step instructions for using that program...

But before doing so, let me make the following points...

1. It is *vital* that you work with the latest version of the Ghost 2003
program. That's the Ghost 2003.793 build. Should you have an earlier
version, you can use Symantec's LiveUpdate feature available in the Ghost
program to download & automatically install that latest update.

2. In using the Ghost 2003 program, our preference is to work with the Ghost
2003 bootable floppy disk (or on occasion the Ghost 2003 bootable CD). We
find that media simpler to use in comparison with the Windows GUI and we
enjoy the portability aspects of using that media. It's just our personal
preference - you're free, of course to use the Ghost GUI in using the
program.

So, here are step-by-step instructions for using the Ghost 2003 program
(using a Ghost 2003 bootable floppy disk or bootable CD) to directly clone
the contents of one HD to another HD...

Creating the bootable Ghost floppy disk:
1. Install the Ghost 2003 program on your computer. Again, make sure you're
using the latest "build" - Ghost 2003.793. If not, use Ghost's LiveUpdate
feature to automatically download the latest version. It's important that
you be using this latest "build".
2. Insert a blank floppy disk (it need not be formatted) and access your
Ghost program.
3. Click on Ghost Utilities.
4. Click on Norton Ghost Boot Wizard.
5. Select Standard Ghost Boot Disk. A dialog box will appear.
a. Select the USB 2.0 Support option (assuming you have that
capability).
b. Select the Assign DOS drive letters option and click Next.
6. Select the Use PC-DOS option.
7. Complete the process following the screen prompts.
8. Remove floppy and label accordingly.

That's it. Now you have a Ghost bootable floppy disk which you can use to
undertake your cloning operations now and in the future. Now when you want
to clone the contents of one HD to another HD you simply insert the Ghost
bootable floppy disk in your floppy drive and boot up with both drives
connected.

After creating the Ghost bootable floppy disk, you can, if you desire,
create a Ghost bootable CD from it using the Roxio or Nero CD burning
programs, or most other CD burning programs that allow you to create a
bootable CD. Unfortunately I know of no way to *directly* create this
bootable CD from within the Ghost program (as you can do, for example, with
the Acronis True Image program).

Here's how to perform the cloning operation...
1. With both drives connected, boot up with the Ghost bootable floppy (or
Ghost bootable CD). You'll get an initial screen that displays "License
agreement warning". Right-arrow (or tab) over to the "Continue without
marking drives" button and press Enter.
2. The "About Norton Ghost" screen appears. Click OK.
3. Right-arrow twice over to the "To Disk" button and press Enter.
4. The next screen will list both your drives - the Drive 1 (source disk)
and Drive 2 (destination disk). MAKE ABSOLUTELY CERTAIN Drive 1 IS INDEED
YOUR SOURCE DISK, I.E., THE DISK YOU'RE CLONING *FROM*!
Drive 1 will be highlighted. Press Enter.
5. The next screen will have Drive 2 (destination disk) highlighted. AGAIN,
ENSURE THAT Drive 2 IS YOUR DESTINATION DISK, I.E., THE DISK YOU'RE CLONING
*TO*! Press Enter.
6. The next screen is the "Destination Drive Details" window, and reflects
your ultimate destination disk, i.e., your current Drive 2. Press your Tab
key to highlight the OK button and press Enter.
7. The "Proceed with disk clone?" dialog box will open. Left-arrow over to
the Yes button and press Enter.
8. The cloning process will begin. The data transfer speed will vary
depending upon the speed of your processor and the HDs involved. On a medium
to high-powered system you should get transfer speeds ranging from 800
MB/min to 1.5 GB/min should you be cloning internal drives. It will be
considerably slower if you're cloning to a USB external HD.
9. After you get the "Clone Completed Successfully" message, left-arrow over
to the Continue button and press Enter.
10. Down-arrow to Quit and press Enter.
11. Click Yes at the "Are you sure you want to quit?" message.
12. Remove the Ghost floppy and shut down the computer.
13. Disconnect your source disk and boot up with the cloned drive. In most
cases (but not always), a Windows "Found New Hardware" message will appear
in the Desktop's Notification Area followed by a "System Settings Change"
message window informing you that new hardware has been found and asks "Do
you want to restart your computer now?" Click Yes.
14. BTW, the reboot of the newly-cloned drive usually takes a longer time
than usual, so one must be patient. On rare occasions the system will fail
to reboot - the system will hang before reaching the Windows XP Welcome
screen. It's a rare occurrence, but you may experience it from time-to-time.
If that does occur, simply use the Ctrl-Alt-Delete keys to reboot.

Assuming you've cloned the contents of your working drive to your second
internal drive, that second drive will be bootable (after disconnecting your
primary one, of course) as indicated above. You also have the option of
cloning your working drive to a USB external hard drive. In that case the
USB EHD is *not* bootable, but you could clone the contents back to your
internal drive for restoration purposes should the need arise.

Just one other point I wish to emphasize with respect to the cloning
operation involving internal drives. Immediately following the cloning
operation and the shutdown of your machine, disconnect your source drive and
boot ONLY to the newly-cloned drive (as indicated in step 13. above). DO NOT
BOOT IMMEDIATELY FOLLOWING THE CLONING OPERATION WITH BOTH DRIVES CONNECTED.
Doing so is likely to cause future boot problems with the cloned drive.
Obviously there is no problem in this area should a USBEHD be involved in
the cloning process since that device is not bootable in an XP environment.

I should add that the Ghost 2003 program can just as easily clone individual
partitions on one HD to another HD as cloning the entire contents of one HD
to another HD. In our case we rarely have need to clone individual
partitions, usually preferring to clone the contents of the entire drive
instead, but that capability is there should you need it. And it's no more
difficult than cloning the entire contents of one drive to another. (I might
mention in passing that based on our experience with the Acronis True Image
8 program, that program does *not* have the capability of *directly* cloning
individual partitions from one drive to another. At least we couldn't find
that capability. Not having worked with the ATI 9 program, I don't know if
that capability now exists).


I trust the above will be of use to you and others who might be thinking
about using the Ghost 2003 program for a routine backup system.
Anna

 

[Guest]

(THE BASIC ISSUE IS THAT USING THE GHOST 2003 PROGRAM, THE OP HAS BEEN
UNABLE TO CLONE THE CONTENTS OF ONE HD TO ANOTHER HD (HIS SAMSUNG HD). IT'S
NOT CLEAR WHETHER THE SAMSUNG HD IS DEFECTIVE AND THAT'S WHAT CAUSING THE
PROBLEM)

SNIP






wumply:
First of all, formatting the Samsung HD (either "quick" or regular) will
have NO effect in resolving your problem. If the cloning process fails, as
it apparently has in your case, a re:format of the drive will not correct
the situation.

As I suspected, the Hitachi/IBM diagnostic utility I mentioned will detect
your Samsung HD, so download that Drive Fitness Test utility from:
http://www.hgst.com/hdd/support/download.htm and test out your drive.

Since you have the Ghost 2003 program available to you, here are
step-by-step instructions for using that program...

But before doing so, let me make the following points...

1. It is *vital* that you work with the latest version of the Ghost 2003
program. That's the Ghost 2003.793 build. Should you have an earlier
version, you can use Symantec's LiveUpdate feature available in the Ghost
program to download & automatically install that latest update.

2. In using the Ghost 2003 program, our preference is to work with the Ghost
2003 bootable floppy disk (or on occasion the Ghost 2003 bootable CD). We
find that media simpler to use in comparison with the Windows GUI and we
enjoy the portability aspects of using that media. It's just our personal
preference - you're free, of course to use the Ghost GUI in using the
program.

So, here are step-by-step instructions for using the Ghost 2003 program
(using a Ghost 2003 bootable floppy disk or bootable CD) to directly clone
the contents of one HD to another HD...

Creating the bootable Ghost floppy disk:
1. Install the Ghost 2003 program on your computer. Again, make sure you're
using the latest "build" - Ghost 2003.793. If not, use Ghost's LiveUpdate
feature to automatically download the latest version. It's important that
you be using this latest "build".
2. Insert a blank floppy disk (it need not be formatted) and access your
Ghost program.
3. Click on Ghost Utilities.
4. Click on Norton Ghost Boot Wizard.
5. Select Standard Ghost Boot Disk. A dialog box will appear.
a. Select the USB 2.0 Support option (assuming you have that
capability).
b. Select the Assign DOS drive letters option and click Next.
6. Select the Use PC-DOS option.
7. Complete the process following the screen prompts.
8. Remove floppy and label accordingly.

That's it. Now you have a Ghost bootable floppy disk which you can use to
undertake your cloning operations now and in the future. Now when you want
to clone the contents of one HD to another HD you simply insert the Ghost
bootable floppy disk in your floppy drive and boot up with both drives
connected.

After creating the Ghost bootable floppy disk, you can, if you desire,
create a Ghost bootable CD from it using the Roxio or Nero CD burning
programs, or most other CD burning programs that allow you to create a
bootable CD. Unfortunately I know of no way to *directly* create this
bootable CD from within the Ghost program (as you can do, for example, with
the Acronis True Image program).

Here's how to perform the cloning operation...
1. With both drives connected, boot up with the Ghost bootable floppy (or
Ghost bootable CD). You'll get an initial screen that displays "License
agreement warning". Right-arrow (or tab) over to the "Continue without
marking drives" button and press Enter.
2. The "About Norton Ghost" screen appears. Click OK.
3. Right-arrow twice over to the "To Disk" button and press Enter.
4. The next screen will list both your drives - the Drive 1 (source disk)
and Drive 2 (destination disk). MAKE ABSOLUTELY CERTAIN Drive 1 IS INDEED
YOUR SOURCE DISK, I.E., THE DISK YOU'RE CLONING *FROM*!
Drive 1 will be highlighted. Press Enter.
5. The next screen will have Drive 2 (destination disk) highlighted. AGAIN,
ENSURE THAT Drive 2 IS YOUR DESTINATION DISK, I.E., THE DISK YOU'RE CLONING
*TO*! Press Enter.
6. The next screen is the "Destination Drive Details" window, and reflects
your ultimate destination disk, i.e., your current Drive 2. Press your Tab
key to highlight the OK button and press Enter.
7. The "Proceed with disk clone?" dialog box will open. Left-arrow over to
the Yes button and press Enter.
8. The cloning process will begin. The data transfer speed will vary
depending upon the speed of your processor and the HDs involved. On a medium
to high-powered system you should get transfer speeds ranging from 800
MB/min to 1.5 GB/min should you be cloning internal drives. It will be
considerably slower if you're cloning to a USB external HD.
9. After you get the "Clone Completed Successfully" message, left-arrow over
to the Continue button and press Enter.
10. Down-arrow to Quit and press Enter.
11. Click Yes at the "Are you sure you want to quit?" message.
12. Remove the Ghost floppy and shut down the computer.
13. Disconnect your source disk and boot up with the cloned drive. In most
cases (but not always), a Windows "Found New Hardware" message will appear
in the Desktop's Notification Area followed by a "System Settings Change"
message window informing you that new hardware has been found and asks "Do
you want to restart your computer now?" Click Yes.
14. BTW, the reboot of the newly-cloned drive usually takes a longer time
than usual, so one must be patient. On rare occasions the system will fail
to reboot - the system will hang before reaching the Windows XP Welcome
screen. It's a rare occurrence, but you may experience it from time-to-time.
If that does occur, simply use the Ctrl-Alt-Delete keys to reboot.

Assuming you've cloned the contents of your working drive to your second
internal drive, that second drive will be bootable (after disconnecting your
primary one, of course) as indicated above. You also have the option of
cloning your working drive to a USB external hard drive. In that case the
USB EHD is *not* bootable, but you could clone the contents back to your
internal drive for restoration purposes should the need arise.

Just one other point I wish to emphasize with respect to the cloning
operation involving internal drives. Immediately following the cloning
operation and the shutdown of your machine, disconnect your source drive and
boot ONLY to the newly-cloned drive (as indicated in step 13. above). DO NOT
BOOT IMMEDIATELY FOLLOWING THE CLONING OPERATION WITH BOTH DRIVES CONNECTED.
Doing so is likely to cause future boot problems with the cloned drive.
Obviously there is no problem in this area should a USBEHD be involved in
the cloning process since that device is not bootable in an XP environment.

I should add that the Ghost 2003 program can just as easily clone individual
partitions on one HD to another HD as cloning the entire contents of one HD
to another HD. In our case we rarely have need to clone individual
partitions, usually preferring to clone the contents of the entire drive
instead, but that capability is there should you need it. And it's no more
difficult than cloning the entire contents of one drive to another. (I might
mention in passing that based on our experience with the Acronis True Image
8 program, that program does *not* have the capability of *directly* cloning
individual partitions from one drive to another. At least we couldn't find
that capability. Not having worked with the ATI 9 program, I don't know if
that capability now exists).


I trust the above will be of use to you and others who might be thinking
about using the Ghost 2003 program for a routine backup system.
Anna

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

OK, I ran the Drive Fitness Test download onthe Samsung. A successful
result was reported...Disposition Code0x00. It was the Quick Test as the
User's Guide said more advanced tests would not run with non-Hitachi drives.
The Drive Fitness Test found:

My primary master------the Seagate
My primary slave-------the Samsung
My secondary master---My CDROM
My secondary slave-----My CD-RW

My flash card reader was not listed.

Next I made the Ghost 2003 bootable floppy per your directions. No problem
there. I attempted to clone now with this floppy. I stuck it in my A drive
and booted. Here is a partial listing of some of the DOS-type lines
(sentences, whatever) when it finally waited for a response from me.

Adapter not present
Iomega Guest driver 8.5
Finding a drive letter for your Iomega drive. (Idon't have one)
No drive letters added.
Driver notinstalled...mousenot found.
Loading...
General Protection Fault eip=214...flags...
A:\GHOST>_ (blinking cursor here)

wumply
Should I have entered some command here...if so, can you tell me which
command?

OK, I figured I might as well try to clone one more time from Ghost 2003 in
my computer...just because someties something works on a 2nd. try. It gave
the same result as before.

I will include the following "screen" just in case it might have been (or
rmay be) implicated as a possible cause of the clone failure...I hadn't
thought it was with my first"Ghost-on-my-computer" attempt, which is why I
didn't mention it before.

=======================================================
Devices were detected on your system that need your attention. Please
review below and what you need to be aware of in order to use them

Logitech USB Receiver USB 1.1
Warning
San Disk Corp-Image Mate Copact Flash USB 1.1 Inaccessible
Unknown USB 1.1
Warning
Firewire Storage Controller IEEE 1394
Accessible

Notes (from me)

The Logitech USB receiver is my radio signal mouse.
Unknown could be my USB 1.1 webcam or my USB 1.1 printer.
The Firewire -all that is is a never-used connection on my soundcard.

All these devices are working perfectly.

Well, I continued on through a series of screens...nothing special. I
clicked "Run now" and per the warning, closed all programs in the systray.
(BTW HOW REALLY NECESSARY IS THAT? I see the warning constantly but a
hundred times I've ignored it without ever a problem.) I checked that all my
important data had been saved. I hit OK and got the message: "Abort
11030...Invalid destination drive."

I have checked that all connections re my 2 drives are firmly in place.