How to fix NTFS table?

[CrazyDoctor]

Hi all,

I have an hard drive which every time I connect to my computer, it's restart the machine again and again untill I plug it out.

After imaging it to a new hard drive, the new hard drive cause to the same symptom.
I scanned the new hard drive with the mhdd but it seems all right.
Nothing left but NTFS table problem. Am I right?

How do I fix that?
A friend tipped me to use systemrescuecd
http://www.sysresccd.org/

I don't know the software. How do I fix the hard drive with that?
Or there are other options?


Many Thanks!

[microsoftengineer]

hi
Do u want to Fix the Drive or u want to recover Data from it ?

for data recovery connect it to any External casing use R-studio or any DR software.

[CrazyDoctor]

hi
Do u want to Fix the Drive or u want to recover Data from it ?

for data recovery connect it to any External casing use R-studio or any DR software.

I can't do it.
Any time the drive is plug on to the system it's crash the windows.

I need to fix the table with some bootable software.

[hddguy]

I can't do it.
Any time the drive is plug on to the system it's crash the windows.

.

so recover from a non-windows environment....

[BlackST]

Fix the drive AND erase data = connect directly to motherboard, start PC and in system management delete all partition, re-create and reformat.

Fix the drive (probably) : connect directly to motherboard , start minimal NT , mount the drive and run CHKDSK /R on it. It will kill any orphan reference file and fix the majority of problems, BUT THERE'S HIGH RISK OF DATA LOSS. Also a bad boot sector can be the problem.

Best : clone the drive, work on clone and try to get data out safely. If you want a click only solution there are tools that claim to be able to fix NTFS partitions with problems. Don't want to suggest anything as I don't trust these tools, I have other ways. In any case work via SW is possible as long as the drive is working correctly.

Happy tinkering with the FS.

[CrazyDoctor]

I can't do it.
Any time the drive is plug on to the system it's crash the windows.

.

so recover from a non-windows environment....

Easy to say,

It's crash ERD, mini xp, and more non-windows environment.

What software do you recommand?

[CrazyDoctor]

Best : clone the drive, work on clone and try to get data out safely. If you want a click only solution there are tools that claim to be able to fix NTFS partitions with problems. Don't want to suggest anything as I don't trust these tools, I have other ways. In any case work via SW is possible as long as the drive is working correctly.

Happy tinkering with the FS.

That is the technique which I work.
What is via SW?

[hddguy]

Easy to say,

It's crash ERD, mini xp, and more non-windows environment.

What software do you recommand?

Both are windows platforms.....

[BlackST]

Via SW = is a street between Disc Drive and Off Road.

OMG.

[CrazyDoctor]

Via SW = is a street between Disc Drive and Off Road.

OMG.

BlackST thanks for the joke.
Now seriously, tell me what did you mean by Via SW?
Or I didn't get you right?

[BlackST]

VIA = by the means/use of SW = using some software

Didn't study Latin, eh ?

[CrazyDoctor]

VIA = by the means/use of SW = using some software

Didn't study Latin, eh ?

I sleep in those lessons..

I am looking for a bootable software that I can run through it chkdsk.
I tried the repair console of windows but it crashed also.

Do you know any?

[BlackST]

CRASH of recovery console ?

Post screenshots...

[swersig]

NTFS problem, not correctable by chkdsk. probably stop 0x00000024, turn off automatic restart by pressing f8 at boot time and youll see. use ntfs4dos it works all the time, but not on vista or 7 partitions...

[BlackST]

But how can it crash the recovery console if he starts from XP CD ?
Never seen THIS way. Usually you get an error enumerating directories LATER, unless there's something really weird.

[swersig]

i had several cases where any windows based system crashed when trying to mount the bad partition, always stop 24, sometimes mentioning ntfs.sys. since recovery console has to start this driver it crashes also. so you dont have any option repairing this fault from any windows based os. only option i found was ntfs4dos since it can use native os'es chkdsk to repair file system. but it works only up to xp, on vista and 7 partitions you would have to use xp chkdsk, not sure if there would be any compatibility issues here.

[BlackST]

Interesting. I have some drives that crashed XP still with data inside (recovered other ways), I do some experiments tonight.

[swersig]

yeah, to recover data you could use linux live (even any winpe crashes). in the cases i had customer wanted also his installation back so only option was to repair (of course on copy first).

[drc]

I have run into that before back when I was a pc tech. Agreed, it will crash any winpe or other windows related system when it tries to mount. It is fixable (easy fix).

If you know that you can't use a windows environment to get to it, that only leaves a few other options...

[Russwinters]

The best thing to do is overwrite (whatever pattern) the first 63 sectors 0-63.

This will wipe only the MBR, which is what Windows is freaking out about.



Then run R-studio scan, recover data.


note: This should be done on a imaged copy of the drive.