 |
|
 |
|
Next: Last Access Time
|
| Author |
Message |
External

Since: Jun 15, 2005 Posts: 45
|
(Msg. 1) Posted: Tue Aug 15, 2006 2:55 pm
Post subject: NTFS Volume Corrupt Archived from groups: microsoft>public>win2000>file_system, others (more info?)
|
|
|
I am running Win2K/SP4. I have the boot disk in a removable bay so I
can clone and swap for backup and archive. What I will describe
applies to all three WD 80GB Caviar disks.
Sometimes when I reboot the machine, I get a blue screen which forces
me to mount the corrupt disk in D: and run CHKDSK D: /f. That has
always cleaned up the disk so I can continue to boot from it.
Here is the output of CHKDSK. Please suggest some things I can do to
fix this nuisance problem.
+++
The type of the file system is NTFS.
Volume label is System.
CHKDSK is verifying files (stage 1 of 3)...
0 percent completed.
Deleted corrupt attribute list entry
with type code 128 in file 9.
Deleting corrupt attribute record (128, $SDS)
from file record segment 10251.
1 percent completed.
2 percent completed.
3 percent completed.
[...]
97 percent completed.
98 percent completed.
99 percent completed.
100 percent completed.
File verification completed.
Correcting cross-link for file 6729.
CHKDSK is verifying indexes (stage 2 of 3)...
0 percent completed.
1 percent completed.
2 percent completed.
3 percent completed.
[...]
97 percent completed.
98 percent completed.
99 percent completed.
100 percent completed.
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Repairing the security file record segment.
Deleting an index entry with Id 256 from index $SII of file 9.
Deleting an index entry with Id 257 from index $SII of file 9.
Deleting an index entry with Id 259 from index $SII of file 9.
[...]
Deleting an index entry with Id 436 from index $SDH of file 9.
Deleting an index entry with Id 406 from index $SDH of file 9.
Deleting an index entry with Id 435 from index $SDH of file 9.
0 percent completed.
Replacing invalid security id with default security id for file 11.
Replacing invalid security id with default security id for file 29.
Replacing invalid security id with default security id for file 43.
0 percent completed.
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Repairing Usn Journal file record segment.
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
78148160 KB total disk space.
42498444 KB in 31285 files.
11004 KB in 2743 indexes.
0 KB in bad sectors.
172730 KB in use by the system.
65536 KB occupied by the log file.
35465981 KB available on disk.
512 bytes in each allocation unit.
156296321 total allocation units on disk.
70931963 allocation units available on disk.
+++
--
"One must realize that the world is a network of real and virtual
combat zones where the stakes are high, struggle is the primary
mode of being and only total victory is acceptable.
-- Sun Tzu, "The Art Of War" >> Stay informed about: NTFS Volume Corrupt |
|
| Back to top |
|
 |  |
External

Since: Mar 14, 2004 Posts: 1030
|
(Msg. 2) Posted: Tue Aug 15, 2006 4:38 pm
Post subject: Re: NTFS Volume Corrupt [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
From: "Bob" <spam RemoveThis @uce.gov>
| I am running Win2K/SP4. I have the boot disk in a removable bay so I
| can clone and swap for backup and archive. What I will describe
| applies to all three WD 80GB Caviar disks.
|
| Sometimes when I reboot the machine, I get a blue screen which forces
| me to mount the corrupt disk in D: and run CHKDSK D: /f. That has
| always cleaned up the disk so I can continue to boot from it.
|
| Here is the output of CHKDSK. Please suggest some things I can do to
| fix this nuisance problem.
|
| +++
| The type of the file system is NTFS.
| Volume label is System.
|
| CHKDSK is verifying files (stage 1 of 3)...
| 0 percent completed.
| Deleted corrupt attribute list entry
| with type code 128 in file 9.
| Deleting corrupt attribute record (128, $SDS)
| from file record segment 10251.
| 1 percent completed.
| 2 percent completed.
| 3 percent completed.
| [...]
| 97 percent completed.
| 98 percent completed.
| 99 percent completed.
| 100 percent completed.
| File verification completed.
| Correcting cross-link for file 6729.
| CHKDSK is verifying indexes (stage 2 of 3)...
| 0 percent completed.
| 1 percent completed.
| 2 percent completed.
| 3 percent completed.
| [...]
| 97 percent completed.
| 98 percent completed.
| 99 percent completed.
| 100 percent completed.
| Index verification completed.
| CHKDSK is verifying security descriptors (stage 3 of 3)...
| Repairing the security file record segment.
| Deleting an index entry with Id 256 from index $SII of file 9.
| Deleting an index entry with Id 257 from index $SII of file 9.
| Deleting an index entry with Id 259 from index $SII of file 9.
| [...]
| Deleting an index entry with Id 436 from index $SDH of file 9.
| Deleting an index entry with Id 406 from index $SDH of file 9.
| Deleting an index entry with Id 435 from index $SDH of file 9.
| 0 percent completed.
| Replacing invalid security id with default security id for file 11.
| Replacing invalid security id with default security id for file 29.
| Replacing invalid security id with default security id for file 43.
| 0 percent completed.
| Security descriptor verification completed.
| CHKDSK is verifying Usn Journal...
| Repairing Usn Journal file record segment.
| Usn Journal verification completed.
| CHKDSK discovered free space marked as allocated in the
| master file table (MFT) bitmap.
| Correcting errors in the Volume Bitmap.
| Windows has made corrections to the file system.
|
| 78148160 KB total disk space.
| 42498444 KB in 31285 files.
| 11004 KB in 2743 indexes.
| 0 KB in bad sectors.
| 172730 KB in use by the system.
| 65536 KB occupied by the log file.
| 35465981 KB available on disk.
|
| 512 bytes in each allocation unit.
| 156296321 total allocation units on disk.
| 70931963 allocation units available on disk.
| +++
|
This is NOT a Registry problem. If you are going to Cross-Post make sure the post is
relevant and On Topic to ALL News Groups it is Cross-Posted to.
Go to the hard disk manufacturer's web site and download their diagnostic software
respective to your hard disk. After the test, you will know if the hard disk is bad or
not..
Quantum/Maxtor - PowerMax
http://www.maxtor.com/en/support/downloads/powermax.htm
Western Digital - Data LifeGuard Tools (DLGDiag)
http://support.wdc.com/download/
Hitachi/IBM - Drive Fitness Test (DFT)
http://www.hgst.com/hdd/support/download.htm
Seagate - SeaTools
http://www.seagate.com/support/seatools/
Fujitsu - Diagnostic Tool
http://www.fcpa.com/download/hard-drives/
Samsung - Disk manager
http://www.samsung.com/Products/HardDiskDrive/utilities/shdiag.htm
--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm >> Stay informed about: NTFS Volume Corrupt |
|
| Back to top |
|
 |  |
External

Since: Jun 15, 2005 Posts: 45
|
(Msg. 3) Posted: Thu Aug 17, 2006 8:55 am
Post subject: Re: NTFS Volume Corrupt [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Wed, 16 Aug 2006 17:32:21 -0400, "David H. Lipman"
<DLipman~nospam~@Verizon.Net> wrote:
>< PLONK > !
How juvenile.
--
"One must realize that the world is a network of real and virtual
combat zones where the stakes are high, struggle is the primary
mode of being and only total victory is acceptable.
-- Sun Tzu, "The Art Of War" >> Stay informed about: NTFS Volume Corrupt |
|
| Back to top |
|
 |  |
External

Since: Aug 18, 2006 Posts: 1
|
(Msg. 4) Posted: Fri Aug 18, 2006 10:55 am
Post subject: Re: NTFS Volume Corrupt [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Bob wrote:
>
> Here is the output of CHKDSK. Please suggest some things I can do to
> fix this nuisance problem.
>
> +++
> The type of the file system is NTFS.
> Volume label is System.
>
> CHKDSK is verifying files (stage 1 of 3)...
> 0 percent completed.
> Deleted corrupt attribute list entry
> with type code 128 in file 9.
> Deleting corrupt attribute record (128, $SDS)
These messages mean that file $Secure (number 9) becames too fragmented.
I don't know why NTFS driver (?) creates invalid attribute list for this
file.
When chkdsk deletes attribute 0x80 $SDS then all securities are deleted
and each reference to these security became invalid too.
Each file has reference to security placed in attribute 0x80 : $SDS.
chkdsk creates a default security and fixes all invalid references.
I think that you should defragment volume to make easy to extend file
$Secure >> Stay informed about: NTFS Volume Corrupt |
|
| Back to top |
|
 |  |
External

Since: Jun 15, 2005 Posts: 45
|
(Msg. 5) Posted: Sat Aug 19, 2006 11:55 am
Post subject: Re: NTFS Volume Corrupt [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Fri, 18 Aug 2006 17:45:57 +0300, shura <a@a> wrote:
>These messages mean that file $Secure (number 9) becames too fragmented.
>I don't know why NTFS driver (?) creates invalid attribute list for this
>file.
>When chkdsk deletes attribute 0x80 $SDS then all securities are deleted
>and each reference to these security became invalid too.
>Each file has reference to security placed in attribute 0x80 : $SDS.
>chkdsk creates a default security and fixes all invalid references.
>I think that you should defragment volume to make easy to extend file
>$Secure
I have used the Win2K defrag but it doesn't help. Sometimes it
actually corrupts a disk that was not corrupt on startup.
--
"One must realize that the world is a network of real and virtual
combat zones where the stakes are high, struggle is the primary
mode of being and only total victory is acceptable.
-- Sun Tzu, "The Art Of War" >> Stay informed about: NTFS Volume Corrupt |
|
| Back to top |
|
 |  |
External

Since: Jun 15, 2005 Posts: 45
|
(Msg. 6) Posted: Mon Aug 21, 2006 6:55 am
Post subject: Re: NTFS Volume Corrupt [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Fri, 18 Aug 2006 17:45:57 +0300, shura <a@a> wrote:
>> CHKDSK is verifying files (stage 1 of 3)...
>> 0 percent completed.
>> Deleted corrupt attribute list entry
>> with type code 128 in file 9.
>> Deleting corrupt attribute record (128, $SDS)
>These messages mean that file $Secure (number 9) becames too fragmented.
>I don't know why NTFS driver (?) creates invalid attribute list for this
>file.
>When chkdsk deletes attribute 0x80 $SDS then all securities are deleted
>and each reference to these security became invalid too.
>Each file has reference to security placed in attribute 0x80 : $SDS.
>chkdsk creates a default security and fixes all invalid references.
>I think that you should defragment volume to make easy to extend file
>$Secure
Another thing I should mention is that everytime I reboot, I get the
following error message in Event Viewer under Applications:
+++
Event Type: Warning
Event Source: SysmonLog
Event Category: None
Event ID: 2006
Date: 8/21/2006
Time: 4:54:17 AM
Description:
Unable to read the Log File Folder value of the System Overview log or
alert configuration. The default value will be used. The error code
returned is in the data.
Data:
0000: 02 00 00 00 ....
+++
What is causing this and how do I fix it?
--
Rope, Tree, Journalist - some assembly required. >> Stay informed about: NTFS Volume Corrupt |
|
| Back to top |
|
 |  |
External

Since: Sep 19, 2006 Posts: 3
|
(Msg. 7) Posted: Tue Sep 19, 2006 11:58 am
Post subject: Re: NTFS Volume Corrupt [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:OKtH1qKwGHA.1224@TK2MSFTNGP03.phx.gbl...
> From: "Bob" <spam.TakeThisOut@uce.gov>
>
> | I am running Win2K/SP4. I have the boot disk in a removable bay so I
> | can clone and swap for backup and archive. What I will describe
> | applies to all three WD 80GB Caviar disks.
> |
> | Sometimes when I reboot the machine, I get a blue screen which forces
> | me to mount the corrupt disk in D: and run CHKDSK D: /f. That has
> | always cleaned up the disk so I can continue to boot from it.
> |
> | Here is the output of CHKDSK. Please suggest some things I can do to
> | fix this nuisance problem.
> |
> | +++
> | The type of the file system is NTFS.
> | Volume label is System.
> |
> | CHKDSK is verifying files (stage 1 of 3)...
> | 0 percent completed.
> | Deleted corrupt attribute list entry
> | with type code 128 in file 9.
> | Deleting corrupt attribute record (128, $SDS)
> | from file record segment 10251.
> | 1 percent completed.
> | 2 percent completed.
> | 3 percent completed.
> | [...]
> | 97 percent completed.
> | 98 percent completed.
> | 99 percent completed.
> | 100 percent completed.
> | File verification completed.
> | Correcting cross-link for file 6729.
> | CHKDSK is verifying indexes (stage 2 of 3)...
> | 0 percent completed.
> | 1 percent completed.
> | 2 percent completed.
> | 3 percent completed.
> | [...]
> | 97 percent completed.
> | 98 percent completed.
> | 99 percent completed.
> | 100 percent completed.
> | Index verification completed.
> | CHKDSK is verifying security descriptors (stage 3 of 3)...
> | Repairing the security file record segment.
> | Deleting an index entry with Id 256 from index $SII of file 9.
> | Deleting an index entry with Id 257 from index $SII of file 9.
> | Deleting an index entry with Id 259 from index $SII of file 9.
> | [...]
> | Deleting an index entry with Id 436 from index $SDH of file 9.
> | Deleting an index entry with Id 406 from index $SDH of file 9.
> | Deleting an index entry with Id 435 from index $SDH of file 9.
> | 0 percent completed.
> | Replacing invalid security id with default security id for file 11.
> | Replacing invalid security id with default security id for file 29.
> | Replacing invalid security id with default security id for file 43.
> | 0 percent completed.
> | Security descriptor verification completed.
> | CHKDSK is verifying Usn Journal...
> | Repairing Usn Journal file record segment.
> | Usn Journal verification completed.
> | CHKDSK discovered free space marked as allocated in the
> | master file table (MFT) bitmap.
> | Correcting errors in the Volume Bitmap.
> | Windows has made corrections to the file system.
> |
> | 78148160 KB total disk space.
> | 42498444 KB in 31285 files.
> | 11004 KB in 2743 indexes.
> | 0 KB in bad sectors.
> | 172730 KB in use by the system.
> | 65536 KB occupied by the log file.
> | 35465981 KB available on disk.
> |
> | 512 bytes in each allocation unit.
> | 156296321 total allocation units on disk.
> | 70931963 allocation units available on disk.
> | +++
> |
>
> This is NOT a Registry problem. If you are going to Cross-Post make sure
the post is
> relevant and On Topic to ALL News Groups it is Cross-Posted to.
>
> Go to the hard disk manufacturer's web site and download their diagnostic
software
> respective to your hard disk. After the test, you will know if the hard
disk is bad or
> not..
>
> Quantum/Maxtor - PowerMax
> http://www.maxtor.com/en/support/downloads/powermax.htm
>
> Western Digital - Data LifeGuard Tools (DLGDiag)
> http://support.wdc.com/download/
>
> Hitachi/IBM - Drive Fitness Test (DFT)
> http://www.hgst.com/hdd/support/download.htm
>
> Seagate - SeaTools
> http://www.seagate.com/support/seatools/
>
> Fujitsu - Diagnostic Tool
> http://www.fcpa.com/download/hard-drives/
>
> Samsung - Disk manager
> http://www.samsung.com/Products/HardDiskDrive/utilities/shdiag.htm
>
>
> --
> Dave
> http://www.claymania.com/removal-trojan-adware.html
> http://www.ik-cs.com/got-a-virus.htm
>
>
I'd rather see crossposts than multi posts; relax, have a sip. >> Stay informed about: NTFS Volume Corrupt |
|
| Back to top |
|
 |  |
| Related Topics: | ntfs.sys is corrupt - while installing window2000,after copying files,it says,file ntfs,sys is corrupt,press any key to restaret your computer.then installation process is terminated
Windows 2K Failure wiht a Spanned Volume - Hello, I have a server that has a local c: partition, a E Drive and F drive on a SAN. The Edrive is approx 1tb and is a spanned volume across a set of two logical drives on the SAN. I am wondering if we have an OS failure, when I rebuild the server,....
Corrupt File System on Disk - I have a WD 250GB SATA Disk set up with 2 partitions and installed with W2K Pro. The first partition 109GB is primary active; the second 125GB is primary for data only. Both are setup with the ntfs format. This Disk was transferred to a server running..
ERROR MESSAGE: The filename, directory name, or volume lab.. - ERROR MESSAGE: The filename, directory name, or volume label syntax is incorrect. Cannot create or replace 105????R3?????(????): The filename, directory name, or volume label syntax is incorrect. i am facing difficulty copy/move file using windows..
Cannot delete corrupt directory--W2000 Server - I am hoping that someone can offer some additional suggestions to cure a problem that I am having on my W2k server. On my W2000 Server, I have a directory that I cannot delete no matter what I try. I am logging in as administrator and this is what.. |
|
You can post new topics in this forum You can reply to topics in this forum You can edit your posts in this forum You can delete your posts in this forum You can vote in polls in this forum
|
|
|
|
 |
|
|