After imaging failure, why can't doesnt the computer detect my HD? - TechRepublic
Question
July 21, 2007 at 02:12 AM
make my day

After imaging failure, why can’t doesnt the computer detect my HD?

by make my day . Updated 18 years, 12 months ago

It started with my floppy – for some unknown reason, despite new cables and many new drives later, it doesnt read the floppies. (I do wonder though if it is to with the fact that I have a harddisk intall underneath it – can that demagnitise the floppy drive?).

Anyway, thinking I’ll bypass that problem, I started with installing XP on an on drive so that I can later klone it one the final drive that I really want XP to be on. Since my computer had problems accessing the floppy (lights come on and seems to spin the floppy disk but doesnt read anything) which prevents me from installing specific raid drivers need to operate the disks on which I ultimately want to install xp.

So instead I start by installing Xp, acronis image 10 (by unfortunately in German) on an old ide disk which I can access through the motherboard’s ide controller. All worked fine – even though this old disk moved like a snail (ide 100 rather than 133). Then I thought I’ll klone it. The process stopped midway with the blue screen. It was in German, I couldnt fully made out what it was – though before that I did select ‘user define’ for kloning the drives. I switched it off.

From then on, couldnt detect either drives – the source and and end drives with which I tried to klone one another.

Ran all kinds of tests. Harddisks dont seem to have any physical faults. And through Windows XP disk restore, I could see there’s still Windows on the source disk. What can I do now to get the motherboard/ cpu to detect the harddisk again?

This discussion is locked

All Comments