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





"Anna" wrote:


"wumply" <wumply@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:651F1472-56C1-4E81-BF61-71012FA98E89@xxxxxxxxxxxxxxxx
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

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



Relevant Pages

  • Re: Cloned my HD successfully but the 2nd. attempt was a failure
    ... UNABLE TO CLONE THE CONTENTS OF ONE HD TO ANOTHER HD. ... NOT CLEAR WHETHER THE SAMSUNG HD IS DEFECTIVE AND THAT'S WHAT CAUSING THE ... Since you have the Ghost 2003 program available to you, ...
    (microsoft.public.windowsxp.general)
  • Re: Cloned my HD successfully but the 2nd. attempt was a failure
    ... Back in Dec. 05 I cloned my original Samsung HD to a brand new and unused ... Seagate drive. ... I should now clone my Seagate to my old Samsung as I ... involves the XP OS) contain no system files corruption, and both drives are ...
    (microsoft.public.windowsxp.general)
  • Re: Cloned my HD successfully but the 2nd. attempt was a failure
    ... Seagate drive. ... (The Samsung was my only drive in the system until I ... I should now clone my Seagate to my old Samsung ... involves the XP OS) contain no system files corruption, and both drives ...
    (microsoft.public.windowsxp.general)
  • Re: Cloned my HD successfully but the 2nd. attempt was a failure
    ... (THE BASIC ISSUE IS THAT USING THE GHOST 2003 PROGRAM, ... UNABLE TO CLONE THE CONTENTS OF ONE HD TO ANOTHER HD. ... NOT CLEAR WHETHER THE SAMSUNG HD IS DEFECTIVE AND THAT'S WHAT CAUSING THE ...
    (microsoft.public.windowsxp.general)
  • Re: ATA 80GB disk recommendation
    ... >some 80 gig drives. ... >used a Samsung 80 gig drive with Windows without any ... >But I must say I also have a Seagate 120 gig, ... >because it has a 5 year warranty. ...
    (Debian-User)