chkdsk is unable to recover (guess) MFT entries

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

Guest

Hello!
Everytime Windows boots it runs chkdsk fist, before finishing the booting
process.
It always says it did not found any errors, so i tried a chkdsk d: /X / F /
R (the disk in this case is D:.. always.. C: is the system's disk and its
fine)

sooo.. I run full chkdsk check and get the following logfile:
(its German.. i'm trying to translate it as good as possible ;) )

Dateisystem auf D: wird überprüft. - D: gets checked.
Der Typ des Dateisystems ist NTFS. - type of D: is NTFS.
Die Volumebezeichnung lautet Daten. - Volume is named "Daten".

Die Datenträgerüberprüfung wird jetzt ausgeführt. - Check starts..

1 nicht verwendete Indexeinträge aus Index $SII der Datei 0x9 werden
aufgeräumt. - 1 unused Indexentry out of Index $SII of File 0x9 gets cleaned
up.
1 nicht verwendete Indexeinträge aus Index $SDH der Datei 0x9 werden
aufgeräumt. - 1 unused Indexentry out of Index $SDH of File 0x9 gets cleaned
up.
1 nicht verwendete Sicherheitsbeschreibungen werden aufgeräumt. - 1 unused
Safety Specification gets cleaned up.
CHKDSK überprüft Dateidaten (Phase 4 von 5)... - CHKDSK checks Filedata
Dateidatenüberprüfung beendet. - Finished without errors.
CHKDSK überprüft freien Speicherplatz (Phase 5 von 5)... - CHKDSK checks
free disk space.
Verifizierung freien Speicherplatzes ist beendet. - Finished without errors.

125580073 KB Complete Space on disk
116675896 KB in 187367 Files
73524 KB in 6251 Indixes
4 KB in damaged Sectors <----- !
268245 KB used by system
65536 KB used by logfile
8562404 KB available on disk

4096 Bytes in jeder Zuordnungseinheit - in every Cluster.
31395018 Zuordnungseinheiten auf dem Datenträger insgesamt - Clusters on
the disk.
2140601 Zuordnungseinheiten auf dem Datenträger verfügbar - Clusters
available.

Intern Informations:
a0 06 03 00 5d f4 02 00 c2 f5 04 00 00 00 00 00 ....]...........
9a 05 00 00 00 00 00 00 23 00 00 00 00 00 00 00 ........#.......
14 53 a3 04 00 00 00 00 ca c3 2b 82 00 00 00 00 .S........+.....
c0 3b 47 03 00 00 00 00 c8 c6 e1 4e 09 00 00 00 .;G........N....
e6 87 ea 92 00 00 00 00 10 d2 6d 73 0a 00 00 00 ..........ms....
99 9e 36 00 00 00 00 00 80 39 07 00 e7 db 02 00 ..6......9......
00 00 00 00 00 e0 54 d1 1b 00 00 00 6b 18 00 00 ......T.....k...


I hope this is enough of information and i didn't missed a thread (yes i
have used the search engine ;P).
Well it looks good - as its repairing the errors.. but I still get the
chkdsk check everytime I boot and it also does not get rid of the 4 KB of
damaged disk space.

Thanks in Advance
Gregg
 
Gregg said:
Hello!
Everytime Windows boots it runs chkdsk fist, before finishing the booting
process.
It always says it did not found any errors, so i tried a chkdsk d: /X / F
/
R (the disk in this case is D:.. always.. C: is the system's disk and its
fine)

sooo.. I run full chkdsk check and get the following logfile:
(its German.. i'm trying to translate it as good as possible ;) )

Dateisystem auf D: wird überprüft. - D: gets checked.
Der Typ des Dateisystems ist NTFS. - type of D: is NTFS.
Die Volumebezeichnung lautet Daten. - Volume is named "Daten".

Die Datenträgerüberprüfung wird jetzt ausgeführt. - Check starts..

1 nicht verwendete Indexeinträge aus Index $SII der Datei 0x9 werden
aufgeräumt. - 1 unused Indexentry out of Index $SII of File 0x9 gets
cleaned
up.
1 nicht verwendete Indexeinträge aus Index $SDH der Datei 0x9 werden
aufgeräumt. - 1 unused Indexentry out of Index $SDH of File 0x9 gets
cleaned
up.
1 nicht verwendete Sicherheitsbeschreibungen werden aufgeräumt. - 1 unused
Safety Specification gets cleaned up.
CHKDSK überprüft Dateidaten (Phase 4 von 5)... - CHKDSK checks Filedata
Dateidatenüberprüfung beendet. - Finished without errors.
CHKDSK überprüft freien Speicherplatz (Phase 5 von 5)... - CHKDSK checks
free disk space.
Verifizierung freien Speicherplatzes ist beendet. - Finished without
errors.

125580073 KB Complete Space on disk
116675896 KB in 187367 Files
73524 KB in 6251 Indixes
4 KB in damaged Sectors <----- !
268245 KB used by system
65536 KB used by logfile
8562404 KB available on disk

4096 Bytes in jeder Zuordnungseinheit - in every Cluster.
31395018 Zuordnungseinheiten auf dem Datenträger insgesamt - Clusters on
the disk.
2140601 Zuordnungseinheiten auf dem Datenträger verfügbar - Clusters
available.

Intern Informations:
a0 06 03 00 5d f4 02 00 c2 f5 04 00 00 00 00 00 ....]...........
9a 05 00 00 00 00 00 00 23 00 00 00 00 00 00 00 ........#.......
14 53 a3 04 00 00 00 00 ca c3 2b 82 00 00 00 00 .S........+.....
c0 3b 47 03 00 00 00 00 c8 c6 e1 4e 09 00 00 00 .;G........N....
e6 87 ea 92 00 00 00 00 10 d2 6d 73 0a 00 00 00 ..........ms....
99 9e 36 00 00 00 00 00 80 39 07 00 e7 db 02 00 ..6......9......
00 00 00 00 00 e0 54 d1 1b 00 00 00 6b 18 00 00 ......T.....k...


I hope this is enough of information and i didn't missed a thread (yes i
have used the search engine ;P).
Well it looks good - as its repairing the errors.. but I still get the
chkdsk check everytime I boot and it also does not get rid of the 4 KB of
damaged disk space.

Thanks in Advance
Gregg
Click to expand...
The only way to get rid of the damaged disk space is by replacing the disk.

What has happened is that the drive electronics have run out of spare
sectors. Hence, your
disk is on the way to disk heaven.

It is correct, though, that the drive electronics declares a sector bad when
the read signal is below some threshold.
Much more expensive equipment can read such sectors.

But, the disk should be watched and replaced when the damage space
increases.

Jim
 
Thank you for your very fast reply.
So you're sure about that the errors are caused by a hardware problem?
If it's like that it really is a pity, cause i am using a VIA Raid-Compound
with 2 disks :/

Well.. if the error is not in the MFT is there a possibility to flag this
section as "damaged" so that it gets ignored by every action to the disk?
(Think that would stop the permanent execution of chkdsk on every system
start and would also increase the lifetime of the disk.)
 
Gregg said:
Thank you for your very fast reply.
So you're sure about that the errors are caused by a hardware problem?
If it's like that it really is a pity, cause i am using a VIA
Raid-Compound
with 2 disks :/ Yes.

Well.. if the error is not in the MFT is there a possibility to flag this
section as "damaged" so that it gets ignored by every action to the disk?
(Think that would stop the permanent execution of chkdsk on every system
start and would also increase the lifetime of the disk.)
Click to expand...
What the drive electronics does is to remap the disk such that the bad area
no longer gets accessed.
Eventually, the drive electronics runs of spare sectors and cannot remap bad
areas. Your disk is
at this point in its life.

You should realise that there are several ways to view sectors.
First of all, there are the physical sectors themselves. Since it is not
possible to manufacture error free disks,
there are quite a few spare sectors.
Secondly, there are the sectors as reported by the drive electronics to the
computer. The drive electronics present
an error free view of the disk structure by replacing defective sectors with
valid ones. This is the view that you
see in a new drive.
Thirdly, as time wears on, additional sectors become defective. These are
replaced by the drive electronics with spare sectors from the
list of such items. This is the view that you see in an older drive.
Finally, more sectors become defective. However, the drive electronics has
run out of spare sectors and reports the
same to the operating system. This is where your disk now sits. All
remapping of defective sectors has been done.
You can expect that the amount of defective sectors will continue to grow.
It may be that XP can create a file which will allow the system to
pretend that the defective sectors should not be accessed; I don't know that
such a method exists.
Jim
 
Jim said:
What the drive electronics does is to remap the disk such that the bad area
no longer gets accessed.
Eventually, the drive electronics runs of spare sectors and cannot remap bad
areas. Your disk is
at this point in its life.

You should realise that there are several ways to view sectors.
First of all, there are the physical sectors themselves. Since it is not
possible to manufacture error free disks,
there are quite a few spare sectors.
Secondly, there are the sectors as reported by the drive electronics to the
computer. The drive electronics present
an error free view of the disk structure by replacing defective sectors with
valid ones. This is the view that you
see in a new drive.
Thirdly, as time wears on, additional sectors become defective. These are
replaced by the drive electronics with spare sectors from the
list of such items. This is the view that you see in an older drive.
Finally, more sectors become defective. However, the drive electronics has
run out of spare sectors and reports the
same to the operating system. This is where your disk now sits. All
remapping of defective sectors has been done.
You can expect that the amount of defective sectors will continue to grow.
It may be that XP can create a file which will allow the system to
pretend that the defective sectors should not be accessed; I don't know that
such a method exists.
Jim
Click to expand...

Alright.. then i will be forced to mirror my disk the next month.. kinda
annoying though the disk is just about 1 year old..
Well then.. thank you again esp. for the really detailed explanation of yours.

regards
Gregg
 
Gregg said:
Alright.. then i will be forced to mirror my disk the next month.. kinda
annoying though the disk is just about 1 year old..
Well then.. thank you again esp. for the really detailed explanation of
yours.

regards
Gregg
Click to expand...
Disks have been organized like for years and years. Now, since I started
with a PDP-11/45, I have gained
a log of (now mostly) useless information. I was reading a hardware manual
for those old disk drives one time and learned that the drive electronics
read and wright at a constant rate. Thus, it pays to keep the drive busy to
increase the effective throughput rate.

By the way, one of the more spectacular events is a head crash on one of the
SMD drives. It takes two days to get all of the debris out of the drive.

Jim
 
Back
Top