phantom disk - longish

  • Thread starter Thread starter neon
  • Start date Start date
N

neon

Had a situation a month ago & forgot exact sequence but bear with me

went round the houses with acronis & finally gave up on them. would
not escalate & kept asking same questions. usless.

have 7 hard drives on my computer (c,d,e,f,j,k,l) (g=dvd)
c&d on primary ide
g(dvd) on secondary ide
j on usb2
e f k l on promise controller

c had bearing noises so decided to replace. bought acronis & new drive
(c still ok at this point)
installed new drive, as h, & used acronis to image from c to f
restored from f to h
removed c & put in new c (was h)
(think that's how it went) and then the trouble started

i have dual boot - 98se on c & xp pro on f
when i booted 98se on c all drive allocations ok
but when i booted xp on f, xp sees c as h

acronis asked me to:
Please do the following:
-run /Start/Setting/Control Panel/Administrative Tools/Computer
Management/Disk Management
-click right button of mouse on H: partition
-choose "Change Drive Letter and Path"
-click "Change"
-choose C: letter and click OK button.

forget what happened!!

so then they asked me to go to:
http://support.microsoft.com/?kbid=223188

went to regedit and renamed c to z and h to c
but when i rebooted explorer now can see c but has another drive entry
for h which is a dup of c
so if you click on h you see same data
went to regedit & deleted h, rebooted & h back again (in explorer &
mounted devices in regedit) so boot process is adding it
i gave h another name, under explorer - mm
when you go into control panel/admin tools/computer mgmt/disk mgmt -
there is no h but c has the name i gave h "mm"
weird

summary - current situation
now when i boot xp (on f), xp sees c & a duplicate c it calls h (acts
just like c)
explorer = c d e f g(dvd) h(dupc) j k l
sisoftware sandra = as above
acronis = as above

computer management = disk0 d, disk1 c, disk2 e, disk3 f, disk4 k,
disk5 l, disk6 j (doesn't see phantom h!)
device manager = as above

any way to get rid of the phony/phantom h?

appreciate any help
thanks in advance
 
Had a situation a month ago & forgot
exact sequence but bear with me
went round the houses with acronis & finally gave up on them.
would not escalate & kept asking same questions. usless.
have 7 hard drives on my computer (c,d,e,f,j,k,l) (g=dvd)
c&d on primary ide
g(dvd) on secondary ide
j on usb2
e f k l on promise controller
c had bearing noises so decided to replace.
bought acronis & new drive (c still ok at this point)
installed new drive, as h, & used acronis
to image from c to f restored from f to h

Why did you do it that way ? The usual thing is to use the clone
entry after booting the rescue CD. That works fine, I just did it
the other day, replacing the boot drive with a larger drive.
removed c & put in new c (was h)
(think that's how it went) and then the trouble started
i have dual boot - 98se on c & xp pro on f
when i booted 98se on c all drive allocations ok
but when i booted xp on f, xp sees c as h

Yeah, that's the downside of the way you did it.
acronis asked me to:
Please do the following:
-run /Start/Setting/Control Panel/Administrative Tools/Computer
Management/Disk Management
-click right button of mouse on H: partition
-choose "Change Drive Letter and Path"
-click "Change"
-choose C: letter and click OK button.
forget what happened!!
went to regedit and renamed c to z and h to c
but when i rebooted explorer now can see c but has another drive entry
for h which is a dup of c
so if you click on h you see same data
went to regedit & deleted h, rebooted & h back again (in explorer &
mounted devices in regedit) so boot process is adding it
i gave h another name, under explorer - mm
when you go into control panel/admin tools/computer mgmt/disk mgmt -
there is no h but c has the name i gave h "mm"
weird
summary - current situation
now when i boot xp (on f), xp sees c & a duplicate c it calls h (acts
just like c)
explorer = c d e f g(dvd) h(dupc) j k l
sisoftware sandra = as above
acronis = as above

computer management = disk0 d, disk1 c, disk2 e, disk3 f, disk4 k,
disk5 l, disk6 j (doesn't see phantom h!)
device manager = as above

any way to get rid of the phony/phantom h?

I'd do it again, this time using the clone entry when you boot the rescue CD.

Thats not the same thing as Add New Hard Drive, thats just an additional drive.

If you cant do that for some reason, say because you have been using the
new drive too much since you cloned it, it gets quite messy but is possible.
 
Rod Speed said:
Why did you do it that way ? The usual thing is to use the clone
entry after booting the rescue CD. That works fine, I just did it
the other day, replacing the boot drive with a larger drive.

think i did it this so i'd have two copies (infant mortality)
& location of drives
doesn't make too much sense now
Yeah, that's the downside of the way you did it.






I'd do it again, this time using the clone entry when you boot the rescue CD.

Thats not the same thing as Add New Hard Drive, thats just an additional drive.

If you cant do that for some reason, say because you have been using the
new drive too much since you cloned it, it gets quite messy but is possible.
too much data under the bridge (scrapped old c)
can we try the "messy but possible"? please
 
think i did it this so i'd have two copies (infant mortality)

OK, what you should have done is clone the drive from the
booted rescue CD and created an image file as a separate
process, best of the new drive too, after the clone worked.

With 20/20 hindsight, even the acronis manual isnt that clear
about that being the best way to replace the boot drive.
& location of drives doesn't make too much sense now

Likely it refused to change the letter since its the boot drive.
too much data under the bridge (scrapped old c)

Yeah, thought that might be the case.
can we try the "messy but possible"? please

If that 'data under the bridge' includes application installs,
it would be safer to not try making the boot drive C now.
Gets very messy indeed fixing the registry entrys for
stuff thats been installed with the H drive the boot drive.

The safest approach would be to do a clean install of XP
now, using the Files and Settings Transfer Wizard to carry
everything that matters over from the current install. That
might bite tho given that you have been running with rather
a mess drive wise for some time.
 
Rod Speed said:
OK, what you should have done is clone the drive from the
booted rescue CD and created an image file as a separate
process, best of the new drive too, after the clone worked.

With 20/20 hindsight, even the acronis manual isnt that clear
about that being the best way to replace the boot drive.


Likely it refused to change the letter since its the boot drive.



Yeah, thought that might be the case.


If that 'data under the bridge' includes application installs,
it would be safer to not try making the boot drive C now.
Gets very messy indeed fixing the registry entrys for
stuff thats been installed with the H drive the boot drive.

haven't installed any new c - w98se - apps
& don't physically have the drive
spend most of the time (99.5) under xp (dual boot)
i think c is the boot under bios
belts & suspenders - WHAT - NOT WORKING !!!
maybe not quite that serious - but heh! when a backup prog allows you
to "get it wrong" and write to an OS specific location - on a target
drive - IN ERROR - Such that mapping is a mess!! and not tell you how
to patch yourself out of misery - or else just ignore the problem
(acronis) - well then what's the chance of a GREAT cup of coffee
The safest approach would be to do a clean install of XP
now, using the Files and Settings Transfer Wizard to carry
everything that matters over from the current install
that sounds sexy.
That >might bite tho given that you have been running with rather
a mess drive wise for some time.

sounds like a plan. i'll rtfm on that - seeing as it's c - and i
dual boot - now almost always into xp. locked out of c. but thats
another story (fu)
so i realy want c to be c, and only c, and nothing but the truth, so
help me..., then work my way out of the second problem.
 
Rod Speed said:
OK, what you should have done is clone the drive from the
booted rescue CD and created an image file as a separate
process, best of the new drive too, after the clone worked.

With 20/20 hindsight, even the acronis manual isnt that clear
about that being the best way to replace the boot drive.


Likely it refused to change the letter since its the boot drive.



Yeah, thought that might be the case.


If that 'data under the bridge' includes application installs,
it would be safer to not try making the boot drive C now.
Gets very messy indeed fixing the registry entrys for
stuff thats been installed with the H drive the boot drive.

The safest approach would be to do a clean install of XP
now, using the Files and Settings Transfer Wizard to carry
everything that matters over from the current install.

how do you do that when target and source are the same c?
 
neon said:
how do you do that when target and source are the same c?

That doesnt care about drive letters. It basically saves what
you choose to transfer into file and you extract the contents
of that file back onto the clean install after the clean install.
 
How It Happened
clip - (ugly & acronis)

Summary
now have time to get back to this
but c is my w98se drive
does w98 do the Transfer Wizard trick?
appreciate the help Rod
tia
That doesnt care about drive letters. It basically saves what
you choose to transfer into file and you extract the contents
of that file back onto the clean install after the clean install.
clip
 
neon said:
How It Happened
clip - (ugly & acronis)

Summary

now have time to get back to this
but c is my w98se drive
does w98 do the Transfer Wizard trick?

Fraid not, its only in XP.

You only need to do a clean reinstall of XP tho
because its the only one with the drive letter
problem for the boot drive, so that shouldnt matter.
appreciate the help Rod

No problem, thats what the newsgroup is here for.
 
Rod Speed said:
Fraid not, its only in XP.

You only need to do a clean reinstall of XP tho
because its the only one with the drive letter
problem for the boot drive, so that shouldnt matter.
180 - I've been thinking it's C that has the problem!!
I've backed up F & will try the Wizard
let you know
 
Back
Top