SATA HDD If drive imaged and both in there, not seen ?

  • Thread starter Thread starter - Bobb -
  • Start date Start date
B

- Bobb -

history:
PC has 2 SATA drives and 1 IDE HDD
SATA #1 and IDE hdd in daily use.
SATA #1 is bootable and has XP on it
IDE is bootable and has XP and X64 on it ( partitions for beta testing )
Normally boots to boot menu on IDE - if not testing, I choose SATA boot -
it boots XP there and all is well. In the PC there is also SATA #2 hdd -
was disconnected long ago ( I forget now why) and I forgot that I had it. I
got the Win7 upgrade and checking things out / backing up and thinking -
great I can use THAT drive ....

Today:
So, I hook up sata #2, BIOS sees it , and I boot SATA #1. Windows config
looks normal - that is - doesn't see the "new sata drive". I reboot and if
I boot off IDE it sees 2 SATA drives - I can open folders anywhere - all is
well. SATA #2 looks like is was imaged (using Ghost ?) from my old drive #1.
Same structure /info, except files are 3 years old.
SO - why second SATA not seen when SATA #1 is booted ?
( I have not tried to boot directly from SATA #2 yet. I'd like to figure
this out FIRST)

MIGHT it be that I copied /imaged SATA #1 to #2 long ago and both have same
ID etc ?
I don't know how that works but just guessing and asking in case someone out
there DOES know.
I'm still googling but if anyone can offer some input, I'd appreciate it.
Worst case I'll hook up ONLY SATA #2 and boot it directly.

Also I found a note about SATA and Ghost 2003 not working.
I had Ghost 2003 and THOUGHT that I used that to do the copy.
I'm checking that out too.
Thanks folks and Merry Christmas
 
- Bobb - said:
history:
PC has 2 SATA drives and 1 IDE HDD
SATA #1 and IDE hdd in daily use.
SATA #1 is bootable and has XP on it
IDE is bootable and has XP and X64 on it ( partitions for beta testing )
Normally boots to boot menu on IDE - if not testing, I choose SATA boot -
it boots XP there and all is well. In the PC there is also SATA #2 hdd -
was disconnected long ago ( I forget now why) and I forgot that I had it.
I got the Win7 upgrade and checking things out / backing up and thinking -
great I can use THAT drive ....

Today:
So, I hook up sata #2, BIOS sees it , and I boot SATA #1. Windows config
looks normal - that is - doesn't see the "new sata drive". I reboot and
if I boot off IDE it sees 2 SATA drives - I can open folders anywhere -
all is well. SATA #2 looks like is was imaged (using Ghost ?) from my old
drive #1. Same structure /info, except files are 3 years old.
SO - why second SATA not seen when SATA #1 is booted ?
( I have not tried to boot directly from SATA #2 yet. I'd like to figure
this out FIRST)

MIGHT it be that I copied /imaged SATA #1 to #2 long ago and both have
same ID etc ?
I don't know how that works but just guessing and asking in case someone
out there DOES know.
I'm still googling but if anyone can offer some input, I'd appreciate it.
Worst case I'll hook up ONLY SATA #2 and boot it directly.

Also I found a note about SATA and Ghost 2003 not working.
I had Ghost 2003 and THOUGHT that I used that to do the copy.
I'm checking that out too.
Thanks folks and Merry Christmas
Click to expand...


Bobb:
When you boot to your SATA HDD (#1) with the secondary SATA HDD installed I
assume you boot to a Desktop without any problem. That's so isn't it? So
what happens when you access Disk Management re that secondary HDD? Not
listed at all? Or no drive letter assigned to it?

BTW, re Ghost 2003 - we've used that program for a fair number of years but
haven't used it to any appreciable extent during the past two or three years
or so. But in the past we nearly *always* used its disk-cloning capability -
rarely used the program for disk-imaging purposes. Our experience with its
disk-imaging process was problematic to say the least. In any event we
cloned hundreds of SATA HDDs with Ghost 2003 and it worked just fine (for
the most part) with that type of disk.
Anna
 
Anna said:
Bobb:
When you boot to your SATA HDD (#1) with the secondary SATA HDD installed
I assume you boot to a Desktop without any problem. That's so isn't it?
Click to expand...

Yes - just that it looks as if NO SATA #2 was installed

So what happens when you access Disk Management re that secondary HDD? Not
listed at all? Or no drive letter assigned to it?
Click to expand...

Not there at all - just 2 drives stat #1 and IDE

BTW, re Ghost 2003 - we've used that program for a fair number of years
but haven't used it to any appreciable extent during the past two or three
years or so. But in the past we nearly *always* used its disk-cloning
capability - rarely used the program for disk-imaging purposes. Our
experience with its disk-imaging process was problematic to say the least.
In any event we cloned hundreds of SATA HDDs with Ghost 2003 and it worked
just fine (for the most part) with that type of disk.
Anna
Click to expand...

I've use Ghost since DOS days and never a problem - BUT - this is the first
time I've ever had both drives in a box after cloning. Usually I clone a
drive then disconnect original - or ( more often) just ghost/restore a
partition to/from a file.
So AFTER you cloned - you can reboot XP with both drives in the same ?
XP SP3 , SATA and IDE controllers both are onboard ( Asus A8N-E)
Your disk mgmt sees both and XP assigns drive letters OK ?
If so, then why not here ?
Againa - boot IDE - disk mgmt shows 3 drives.
Boot SATA #1 and shows only 2 - itself and the IDE
This isn't an emergency I could move/ wipe old disk and start again - just
trying to learn - so I don;t do it again.
Thanks for the feedback.
 
My Win7 DVD still in shipping envelope - I'm just getting ready
But I will go thru that article - thanks
==============
 
RESPONSE...
Yes - just that it looks as if NO SATA #2 was installed


RESPONSE...
Not there at all - just 2 drives stat #1 and IDE
Click to expand...


- Bobb - said:
I've use Ghost since DOS days and never a problem - BUT - this is the
first time I've ever had both drives in a box after cloning. Usually I
clone a drive then disconnect original - or ( more often) just
ghost/restore a partition to/from a file.
So AFTER you cloned - you can reboot XP with both drives in the same ?
XP SP3 , SATA and IDE controllers both are onboard ( Asus A8N-E)
Your disk mgmt sees both and XP assigns drive letters OK ?
If so, then why not here ?
Againa - boot IDE - disk mgmt shows 3 drives.
Boot SATA #1 and shows only 2 - itself and the IDE
This isn't an emergency I could move/ wipe old disk and start again - just
trying to learn - so I don;t do it again.
Thanks for the feedback.
Click to expand...


Bobb...
As to your question re booting to the XP OS source & destination HDDs
following a disk-cloning operation...

There should be no problem doing so even if the three HDDs are connected.
All that's generally required is that the BIOS boot priority order is set so
that the bootable HDD you desire to boot to is first in that order. There's
no absolute need (unless for some reason you want to) to disconnect any of
the secondary drives regardless of whether they contain a bootable OS.

So in your situation there really should be no reason why, for example, you
couldn't boot to SATA #2 with your SATA #1 and PATA (IDE) HDDs connected as
secondary HDDs. The boot should proceed normally and all three drives should
be detected by the system without any problems. This naturally assumes all
disks are non-defective and that the boot drive (in this example SATA #2)
contains a bootable OS.

I honestly don't know why you're experiencing the problem you relate. What I
would recommend is that you re:clone the contents of your SATA #2 HDD to the
SATA #1 HDD. Or, alternatively, I suppose you could use your PATA HDD as the
source HDD and clone its contents to the SATA #2 HDD. Naturally I'm assuming
in all this that there's no data on the SATA #2 HDD that you need or want.
Obviously if there is you would copy such to one of the other two drives
before undertaking the disk-cloning operation.
Anna
 
Anna said:
Bobb...
As to your question re booting to the XP OS source & destination HDDs
following a disk-cloning operation...

There should be no problem doing so even if the three HDDs are connected.
All that's generally required is that the BIOS boot priority order is set
so that the bootable HDD you desire to boot to is first in that order.
There's no absolute need (unless for some reason you want to) to
disconnect any of the secondary drives regardless of whether they contain
a bootable OS.

So in your situation there really should be no reason why, for example,
you couldn't boot to SATA #2 with your SATA #1 and PATA (IDE) HDDs
connected as secondary HDDs. The boot should proceed normally and all
three drives should be detected by the system without any problems. This
naturally assumes all disks are non-defective and that the boot drive (in
this example SATA #2) contains a bootable OS.

I honestly don't know why you're experiencing the problem you relate. What
I would recommend is that you re:clone the contents of your SATA #2 HDD to
the SATA #1 HDD. Or, alternatively, I suppose you could use your PATA HDD
as the source HDD and clone its contents to the SATA #2 HDD. Naturally I'm
assuming in all this that there's no data on the SATA #2 HDD that you need
or want. Obviously if there is you would copy such to one of the other two
drives before undertaking the disk-cloning operation.
Anna
Click to expand...


Bobb...
I think I might have mixed-up the "numbering profile" re your two SATA HDDs
in the last paragraph of my post above...

If I correctly understand the problem you've related, when you boot to your
PATA HDD the system detects *both* the secondary HDDs installed, i.e., SATA
#1 & SATA #2. No problem there. And presumably the OS would similarly detect
SATA #2 without a problem should that have been the only secondary HDD
connected.

But when you boot to SATA #1 with SATA #2 connected as a secondary HDD,
while the boot to SATA#1 proceeds normally, the XP OS does not detect SATA
#2. And you believe that latter drive is a clone of SATA #1.

So assuming I have correctly identified the drives this time, my last
suggestion should be amended so that you might want to re:clone the contents
of SATA #1 to SATA #2 (not vice-versa as I previously suggested) and see
what happens under those circumstances.
Anna
 
Back
Top