I realize that this forum is to be for XP-Pro;however I am wondering if there is any resolution prior to putting the recovery CD and beginning again. A friend's machine, Dell Inspirion 2600 with XP-Home(NTFS) ask for some help. When the machine boots up, it immediately goes to chkdsk and begins to scan. The on-screen comment is that "Chkdsk is verifying files. Truncating badly linked attribute records from file record segment 31023". It begins the 2nd scan and ultimately goes to Windows XP. Everything appears to work even though Chkdsk aborts after a couple of checks and goes to Windows. She hasn't applied very many fixes on the OS but I wanted to try and fix the problem prior to adding all the fixes. I have run Adaware, Spybot & RegSeeker registry scan and they do not report major problems and Norton Disk Doctor is not able to fix the Files directory. Any thoughts would be appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Chkdsk on XP Home edition 2
- Thread starter coflyer
- Start date
-
1
- #2
-
1
- #3
Ditto on "micker377's" comments.
It might pay you to run ChkDsk anyway, manually, if it is finding some type of errors, right-click your Drive icon/ Properties/ Tools/ Error Checking.
Here is a collection of various information about ChkDsk.
218461 - Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000
831426 - Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your computer
283340 - Chkdsk in Read-Only Mode Does Not Detect Corruption on NTFS Volume
316506 - Chkdsk Runs Each Time That You Start Your Computer
Windows has finished checking your disk and???
thread779-580479
You Receive a "System Has Recovered from a Serious Error" Message After Every Restart (Q317277)
The fix in this might work for Chkdsk.
You can determine whether your file system errors are legitimate.
To know if you've got a file system error, you can type the following
command at the command prompt:
fsutil dirty query c: (replace c: with your drive letter)
If the response is that the volume is dirty, then a file system error has
occurred, and Chkdsk should run automatically at startup to fix the errors,
or you can schedule Chkdsk to run if you want.
An error message may occur when a disk check (Chkdsk.exe) that is scheduled to run during startup is unable to run.
Some other process is try to access the drive. The process of writing this file places a lock that prevents Chkdsk.exe from gaining exclusive access to the disk. Because Chkdsk.exe does not have exclusive access to the disk, Chkdsk.exe cannot run. To Isolate what is running at Start up use the Msconfig option. This might help you too.
Windows XP Professional starts logon scripts, startup programs, and services referenced in these registry subkeys and folder locations:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Runonce
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\Run
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup
%systemdrive%\Documents and Settings\username\Start Menu\Programs\Startup
It might pay you to run ChkDsk anyway, manually, if it is finding some type of errors, right-click your Drive icon/ Properties/ Tools/ Error Checking.
Here is a collection of various information about ChkDsk.
218461 - Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000
831426 - Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your computer
283340 - Chkdsk in Read-Only Mode Does Not Detect Corruption on NTFS Volume
316506 - Chkdsk Runs Each Time That You Start Your Computer
Windows has finished checking your disk and???
thread779-580479
You Receive a "System Has Recovered from a Serious Error" Message After Every Restart (Q317277)
The fix in this might work for Chkdsk.
You can determine whether your file system errors are legitimate.
To know if you've got a file system error, you can type the following
command at the command prompt:
fsutil dirty query c: (replace c: with your drive letter)
If the response is that the volume is dirty, then a file system error has
occurred, and Chkdsk should run automatically at startup to fix the errors,
or you can schedule Chkdsk to run if you want.
An error message may occur when a disk check (Chkdsk.exe) that is scheduled to run during startup is unable to run.
Some other process is try to access the drive. The process of writing this file places a lock that prevents Chkdsk.exe from gaining exclusive access to the disk. Because Chkdsk.exe does not have exclusive access to the disk, Chkdsk.exe cannot run. To Isolate what is running at Start up use the Msconfig option. This might help you too.
Windows XP Professional starts logon scripts, startup programs, and services referenced in these registry subkeys and folder locations:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Runonce
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\Run
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Startup
%systemdrive%\Documents and Settings\username\Start Menu\Programs\Startup
- Thread starter
- #4
After 42 critical updates, 20+ reboots and 3 hours the updates have all been added; however the same problem still exists. Have you seen any information on correcting attribute records in the start up? I don't know whether the problem being indetified by chkdsk is coming from the registry or somewhere else? Any thoughts about where to go to check tools or thoughts on what can be done would be of help. Thank you for responding.
Not sure whether these are much help or not, might be worth a read though.
Type "Fsutil: usn" in the Help and Support search box and see what it is talking about there.
This is an old article but it mentions what you are referring to.
169404 - NTFS Directory Corruption with Frequent File Creation
Type "Fsutil: usn" in the Help and Support search box and see what it is talking about there.
This is an old article but it mentions what you are referring to.
169404 - NTFS Directory Corruption with Frequent File Creation
- Status
Similar threads
- Locked
- Question