Before I run chkdsk on a drive, I want to make sure there's not some
other better way, so I thought I should ask some advice. My primary
hard drive died. Using a thing called the SimpleTouch HDKit that
allows you to turn any hard drive into a USB drive, I hooked drive up
to my backup PC and find I cannot access it as it is corrupted, I ran
chkdsk on it in read-only mode (i.e. without the /f flag) and it found
a few errors, which I assume it could fix. But I'm wondering how much
that will screw up the disk. My hope is I can recover most of the data
off it, so I just don't want to do anything that might permanently make
a lot of that data inaccessible. So, is the best thing in this
situaiton chkdsk, or is there something that would do a better job of
restoring my data?

This is what chkdsk says:
CHKDSK is verifying files (stage 1 of 3)...
Deleted corrupt attribute list entry
with type code 128 in file 35125.
Deleting corrupt attribute record (128, $J)
from file record segment 11430.
Deleting corrupt attribute record (128, $J)
from file record segment 27092.
File verification completed.
Deleting orphan file record segment 11430.
Deleting orphan file record segment 27092.

Errors found. CHKDSK cannot continue in read-only mode.

Try typing in cmd:CHKDSK C: /R Agree to restart,then type:EXIT Restart
computer.C: being the drive you want to chk

"cherold@gmail.com" wrote:

> Before I run chkdsk on a drive, I want to make sure there's not some
> other better way, so I thought I should ask some advice. My primary
> hard drive died. Using a thing called the SimpleTouch HDKit that
> allows you to turn any hard drive into a USB drive, I hooked drive up
> to my backup PC and find I cannot access it as it is corrupted, I ran
> chkdsk on it in read-only mode (i.e. without the /f flag) and it found
> a few errors, which I assume it could fix. But I'm wondering how much
> that will screw up the disk. My hope is I can recover most of the data
> off it, so I just don't want to do anything that might permanently make
> a lot of that data inaccessible. So, is the best thing in this
> situaiton chkdsk, or is there something that would do a better job of
> restoring my data?
>
> This is what chkdsk says:
> CHKDSK is verifying files (stage 1 of 3)...
> Deleted corrupt attribute list entry
> with type code 128 in file 35125.
> Deleting corrupt attribute record (128, $J)
> from file record segment 11430.
> Deleting corrupt attribute record (128, $J)
> from file record segment 27092.
> File verification completed.
> Deleting orphan file record segment 11430.
> Deleting orphan file record segment 27092.
>
> Errors found. CHKDSK cannot continue in read-only mode.
>
>

cherold@gmail.com wrote:

> Before I run chkdsk on a drive, I want to make sure there's not some
> other better way, so I thought I should ask some advice. My primary
> hard drive died. Using a thing called the SimpleTouch HDKit that
> allows you to turn any hard drive into a USB drive, I hooked drive up
> to my backup PC and find I cannot access it as it is corrupted, I ran
> chkdsk on it in read-only mode (i.e. without the /f flag) and it found
> a few errors, which I assume it could fix. But I'm wondering how much
> that will screw up the disk. My hope is I can recover most of the
> data off it, so I just don't want to do anything that might
> permanently make
> a lot of that data inaccessible. So, is the best thing in this
> situaiton chkdsk, or is there something that would do a better job of
> restoring my data?
>
> This is what chkdsk says:
> CHKDSK is verifying files (stage 1 of 3)...
> Deleted corrupt attribute list entry
> with type code 128 in file 35125.
> Deleting corrupt attribute record (128, $J)
> from file record segment 11430.
> Deleting corrupt attribute record (128, $J)
> from file record segment 27092.
> File verification completed.
> Deleting orphan file record segment 11430.
> Deleting orphan file record segment 27092.
>
> Errors found. CHKDSK cannot continue in read-only mode.

If the data is crucial, see if you can retrieve it first. I would boot
with Knoppix or a Bart's PE and see if you can get the files off that
way. If Knoppix or Bart's can't do it, then you may be able to get the
data off with specialized data recovery software. I use Ontrack's Easy
Recovery Pro but that is quite expensive. If you need to go that route,
you may want to call around and see if any local professional computer
repair shops do data recovery. If data recovery software can't get it,
then a professional data recovery company such as DriveSavers probably
can but now you're talking $500usd and up.

Here's information about using Knoppix, a Linux distro on a live cd. You
will need a computer with two cd drives, one of which is a cd/dvd-rw OR
a usb thumb drive with enough capacity to hold your data. To get
Knoppix, you need a computer with a fast Internet connection and
third-party burning software. Download the Knoppix .iso from
www.knoppix.net and create your bootable cd. Then boot with it and it
will be able to see the Windows files. If you are using the usb thumb
drive, right-click on its icon (on the Desktop) to get its properties
and uncheck the box that says "Read Only". Then click on it to open it.
Note that the default mouse action in the window manager used by
Knoppix (KDE) is a single click to open instead of the traditional MS
Windows' double-click. Otherwise, use the K3b burning program to burn
the files to cd/dvd-r's.

Once you've retrieved your data, you can run Chkdsk /r and if it messes
up you haven't lost anything. If Chkdsk still gives errors, download a
hard drive diagnostic utility from the drive mftr. and do a thorough
test with it. If the drive fails any physical tests, replace it. If the
drive passes, format it and clean install Windows.

Good luck,

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

"How to", for if you use Knoppix for the Rescue:

http://www.shockfamily.net/cedric/knoppix/

"cherold@gmail.com" wrote:

> Before I run chkdsk on a drive, I want to make sure there's not some
> other better way, so I thought I should ask some advice. My primary
> hard drive died. Using a thing called the SimpleTouch HDKit that
> allows you to turn any hard drive into a USB drive, I hooked drive up
> to my backup PC and find I cannot access it as it is corrupted, I ran
> chkdsk on it in read-only mode (i.e. without the /f flag) and it found
> a few errors, which I assume it could fix. But I'm wondering how much
> that will screw up the disk. My hope is I can recover most of the data
> off it, so I just don't want to do anything that might permanently make
> a lot of that data inaccessible. So, is the best thing in this
> situaiton chkdsk, or is there something that would do a better job of
> restoring my data?
>
> This is what chkdsk says:
> CHKDSK is verifying files (stage 1 of 3)...
> Deleted corrupt attribute list entry
> with type code 128 in file 35125.
> Deleting corrupt attribute record (128, $J)
> from file record segment 11430.
> Deleting corrupt attribute record (128, $J)
> from file record segment 27092.
> File verification completed.
> Deleting orphan file record segment 11430.
> Deleting orphan file record segment 27092.
>
> Errors found. CHKDSK cannot continue in read-only mode.
>
>

visit the below link they are expert in Data Recovery

http://www.datadoctor.biz

contact to these people

http://www.datadoctor.biz

Hello,

EASEUS DataRecoveryWizard utility can help. Speaking about me, it was
easily able to restore deleted, lost file and unformat drive,
so I think you will also find it quite useful. Really recommended
tool, give it a try.

http://www.easeus.com/
--
Good work, Good day.


"cherold@gmail.com" wrote:

> Before I run chkdsk on a drive, I want to make sure there's not some
> other better way, so I thought I should ask some advice. My primary
> hard drive died. Using a thing called the SimpleTouch HDKit that
> allows you to turn any hard drive into a USB drive, I hooked drive up
> to my backup PC and find I cannot access it as it is corrupted, I ran
> chkdsk on it in read-only mode (i.e. without the /f flag) and it found
> a few errors, which I assume it could fix. But I'm wondering how much
> that will screw up the disk. My hope is I can recover most of the data
> off it, so I just don't want to do anything that might permanently make
> a lot of that data inaccessible. So, is the best thing in this
> situaiton chkdsk, or is there something that would do a better job of
> restoring my data?
>
> This is what chkdsk says:
> CHKDSK is verifying files (stage 1 of 3)...
> Deleted corrupt attribute list entry
> with type code 128 in file 35125.
> Deleting corrupt attribute record (128, $J)
> from file record segment 11430.
> Deleting corrupt attribute record (128, $J)
> from file record segment 27092.
> File verification completed.
> Deleting orphan file record segment 11430.
> Deleting orphan file record segment 27092.
>
> Errors found. CHKDSK cannot continue in read-only mode.
>
>