Re: Recovering an NTFS drive




"Poldie" <Poldie@xxxxxxxxx> wrote in message
news:1191164069.316398.205220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm asking here 'cos I've seen other techies post here.

I booted from my XP SP2 CD to try and perform scandisk on a drive. (I
couldn't defrag it because there was some problem or other which
Windows suggested I run scandisk to fix). The PC loaded up the
drivers etc, but then the PC rebooted. Great. Even better, now, my
other 300gb drive is showing as "not initialized" and "unallocated" in
the Computer Management tool. This has happened before, and I fixed
it by initializing it, then running some freeware app to recover
files, which it sort of did, although it couldn't get everything back,
but it was mostly ok. I have no idea why this happens. It doesn't
seem to be something which I can find references to on the net. My
PC is ok apart from this, and I have no idea why it happens. I have
two physical drives. One is partitioned as C: and D:, which are fine,
and the other is F:.

So my questions are:

1) Why does this happen?
2) Which app do you recommend I use to recover the data?
3) Is there a way of simply `initializing` the drive and have it
rebuild the various structures it needs to see the data which is
manifestly still perfectly intact on the drive?

Cheers!



I went through a stage a while back of every SATA drive suffering from
hal.dll errors regularly and this on several set ups. Touch would hasn't
happened for ages. Never got to the bottom of it. I think certain
combinations of motherboard and chipset, processor, drivers, bios etc. cause
problems with certain drives.

I have found after many tries with different software that Active Undelete
does the job most times. It takes a while to scan a disc, but the results
are reliable and it seems able to get pretty much anything that's there.

www.active-undelete.com

I'm not aware of an answer to 3), although maybe somebody else can provide
one.

The easiest answer of all? Get hold of Acronis True Image and a spare hard
drive large enough to take all of your data. Once a week, plug the spare
drive in to a spare SATA or PATA cable and back the whole thing up as a
drive image over night.

If anything goes wrong, simply plug the other drive in and start backing up
onto the first drive(s).

It's so much easier than faffing about trying to figure stuff out.


.



Relevant Pages

  • Re: DVD problems solved?
    ... drive properties under the tools tab, ... Although I haven't confirmed it yet, I do seem to get better results with blank DVDs rated at 4X rather than multi-speed ones rated up to 8X or 10X. ... SCANDISK- One suggested testing the DVDs using scandisk. ... COMMON SENSE- You need to have a good DVD, and your drives should be clean. ...
    (alt.sys.pc-clone.dell)
  • scandisk executing on boot, DSL problems
    ... an Actiontec external modem (connects through the ... The computer is setup for dual boot ... time it decides it needs to run scandisk (maybe it's ... The computer has 2 hard drives and is ...
    (microsoft.public.windowsxp.network_web)
  • Re: Back ups takes ages! Why?
    ... I ran a defrag last night after my first Scandisk but will try the Scandisk and defrag again if you think it's a good idea. ... If you have corruption on either of your drives Acronis will balk during the backup or recovery. ... Those same bad sectors may be causing the backup program that is part of Windows XP to take so long. ...
    (microsoft.public.windowsxp.basics)
  • Re: disk repair w/ XP?
    ... I have a HP desktop PC w/ W98 that will not boot up. ... I noticed that there is no ScanDisk w/ XP. ... Then the other question is that the laptop uses NTFS. ... combinations of NTFS, FAT32, FAT16, and FAT12, on different drives, or ...
    (microsoft.public.windowsxp.basics)
  • Re: LOST EVERYTHING on F: from Virus Is C: at Risk now?
    ... Please tell us the name, version, and whether your virus definitions ... Since you mention "Scandisk", you are running Win9x/ME since there is no ... finished, get and install a full-featured av, update it, and do a ... most definitely all Windows drives are at risk. ...
    (microsoft.public.security)