jeffy
11th September 2007, 14:49
This is the question, followed by a long story:
Could you please suggest to me a non-destructive method how to check and/or repair the hard drive NTFS filesystem WITHOUT chkdsk/autochk? The version in Windows 98 at least asked if I wanted to recover the file, but not the XP version, what it decides to save into DIRxxxx.CHK folders is usually useless.
This has not happened for the first time and its cause remains a mystery to me. I have encountered several PC machines (10?), that at some point in time suffered a serious NTFS directory file corruption.
What do the machines have in common?
- Windows XP Professional or Windows XP Home with all the available patches (where appropriate), OEM licensed versions
- NTFS file system
What is different amongst them:
almost everything: motherboards, different CPUs: AMD & Intel ones, different architectures (DDR1 & DDR2), different chipsets, different harddrives and their interfaces (brands: Western Digital and Seagate, interfaces: Ultra ATA, SATA1, SATA2).
Overclocked or not?
Some yes, some never were.
What could cause some corruptions, but not on all systems:
- ADSL modem drivers (BSOD confirmed)
- some versions of nVidia graphic drivers (BSOD confirmed)
- overclocking? (if yes, then this would not explain why it happened on non-overclocked PCs as well)
- bad sectors on the hard drive (1 case confirmed)
Some corruption happened all of the sudden, without any BSOD or power outage or whatever before.
Impacts:
- really serious: on some systems the chkdsk when allowed to run deleted much files without any hope for recovery
(eg. home video files 70 GB out of a 200 GB partition wiped out, their file sizes were truncated to 0 bytes). No recovery utility I was able to try, did get them back.
If they were really corrupt, it can't be explained why I was able to copy them right before the chkdsk run without any problem.
- a mystery:
on one Seagate drive, where all the S.M.A.R.T. attributes were absolutely ok, chkdsk run repeatedly with the message
Inserting an index entry into index $0 of file 25, similar to this thread:
http://www.msfn.org/board/index.php?showtopic=98121
The message disappeared after some time.... ???
If you have any questions/comments, feel free to ask. Thank you to all in advance.
Could you please suggest to me a non-destructive method how to check and/or repair the hard drive NTFS filesystem WITHOUT chkdsk/autochk? The version in Windows 98 at least asked if I wanted to recover the file, but not the XP version, what it decides to save into DIRxxxx.CHK folders is usually useless.
This has not happened for the first time and its cause remains a mystery to me. I have encountered several PC machines (10?), that at some point in time suffered a serious NTFS directory file corruption.
What do the machines have in common?
- Windows XP Professional or Windows XP Home with all the available patches (where appropriate), OEM licensed versions
- NTFS file system
What is different amongst them:
almost everything: motherboards, different CPUs: AMD & Intel ones, different architectures (DDR1 & DDR2), different chipsets, different harddrives and their interfaces (brands: Western Digital and Seagate, interfaces: Ultra ATA, SATA1, SATA2).
Overclocked or not?
Some yes, some never were.
What could cause some corruptions, but not on all systems:
- ADSL modem drivers (BSOD confirmed)
- some versions of nVidia graphic drivers (BSOD confirmed)
- overclocking? (if yes, then this would not explain why it happened on non-overclocked PCs as well)
- bad sectors on the hard drive (1 case confirmed)
Some corruption happened all of the sudden, without any BSOD or power outage or whatever before.
Impacts:
- really serious: on some systems the chkdsk when allowed to run deleted much files without any hope for recovery
(eg. home video files 70 GB out of a 200 GB partition wiped out, their file sizes were truncated to 0 bytes). No recovery utility I was able to try, did get them back.
If they were really corrupt, it can't be explained why I was able to copy them right before the chkdsk run without any problem.
- a mystery:
on one Seagate drive, where all the S.M.A.R.T. attributes were absolutely ok, chkdsk run repeatedly with the message
Inserting an index entry into index $0 of file 25, similar to this thread:
http://www.msfn.org/board/index.php?showtopic=98121
The message disappeared after some time.... ???
If you have any questions/comments, feel free to ask. Thank you to all in advance.