Data Recovery

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I 'm having a problem in my win 2000 system. The data on the 250 MB hard disk
is all corrupted. I had sp4 installed and there was the lba 48 entry in the
registry. I accidentally removed that entry. That caused at the begining some
inconcistency problems on the HD. I 've run the chkdsk /f /r command to fix
the problems. The file system seems ok but the files are all corrupted. Now
i' ve re-enter the lba 48 support on the registry and i would like to know if
there is a way to recover my lost data. I 've used "Recover my files" and
"EASEUS Data Recovery Wizard 3.3.4" with no success. Is there any way to undo
the chkdsk 'corrections' ??
 
Alex13 wrothe:
I 'm having a problem in my win 2000 system. The data on the 250 MB hard disk
is all corrupted. I had sp4 installed and there was the lba 48 entry in the
registry. I accidentally removed that entry. That caused at the begining some
inconcistency problems on the HD. I 've run the chkdsk /f /r command to fix
the problems. The file system seems ok but the files are all corrupted. Now
i' ve re-enter the lba 48 support on the registry and i would like to know if
there is a way to recover my lost data. I 've used "Recover my files" and
"EASEUS Data Recovery Wizard 3.3.4" with no success. Is there any way to undo
the chkdsk 'corrections' ??

You should not have to reverse any chkdsk error fixes. Have you tried
booting into repair console? Can you see your data files from there?
 
Frank Booth Snr said:
You should not have to reverse any chkdsk error fixes. Have you tried
booting into repair console? Can you see your data files from there?

I haven't tried the repair console because i use the disk just for data.
It's not my system disk. As it is now, i can see all files but when i check
them for integrity they are 100% corrupted. In my opinion the corruption was
done by the chkdsk command. Here is a part of the action from the event
viewer. These actions were repeated for a lot of headers. chkdsk took
considerable time to finish.
-------------------------------
-------------------------------
One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x5 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 5.
The index bitmap $I30 in file 0x5 is incorrect.
Correcting error in index $I30 for file 5.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Sorting index $I30 in file 5.
- - - - -
- - - - -
The object id in file 0x3c does not appear in the object
id index in file 0x19.
Inserting an index entry into index $O of file 25.
- - - - -
- - - - -

Thanks for your interest.
 
Alex13 said:
:




I haven't tried the repair console because i use the disk just for data.
It's not my system disk. As it is now, i can see all files but when i check
them for integrity they are 100% corrupted. In my opinion the corruption was
done by the chkdsk command. Here is a part of the action from the event
viewer. These actions were repeated for a lot of headers. chkdsk took
considerable time to finish.
-------------------------------
-------------------------------
One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x5 is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 5.
The index bitmap $I30 in file 0x5 is incorrect.
Correcting error in index $I30 for file 5.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Sorting index $I30 in file 5.
- - - - -
- - - - -
The object id in file 0x3c does not appear in the object
id index in file 0x19.
Inserting an index entry into index $O of file 25.
- - - - -
- - - - -

Thanks for your interest.

Chkdsk always takes a bit of a time. You didn't mentioned whether win2k
can still see the whole 160GB since you restored the lba48 registry
entry. You could try a defrag first to see what effect that has. It may
correctly link up what fragments of files remain. Then transfer any
files you can see to other media (flash memory etc). If you are unable
to see or open any files any after defrag, I'd say you've lost your
data, unless you take the disk to one of those expensive disk recovery
services. In any case you should always back up your data before
tampering with the system as most people have learnt the hard way by not
doing so.
 
Yes win2k can see the whole 250 GB. As i 've said the file system seems
intact. i 'll defrag the disk and report the results
 
Back
Top