Unsolved
This post is more than 5 years old
15 Posts
0
26953
January 16th, 2004 17:00
NTFS File System Error.....
Moderator/ Forum Users....Please help me on this following issue.
When I run CHKDSK at the command prompt I get the following message.
Stage 1….completed
Stage 2….completed
CHKDSK is recovering lost files.
Recovering Orphaned file SHOWLE~1 <61375> into directory file 18331.
Recovering Orphaned file SHOWLETTER[1] <61375> into directory file 18331.
Stage 3 ….completed
Correcting errors in the master file table’s Bitmap attribute
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these"
History & Corrective Actions Tried:
I got my SmartStep 250N back from Dell Repair 4 days back. I had sent it because of my shutdown problems and they have done some work on heat sink flow though not sure what was done. I had the latest A05 BIOS updated in the system even before I sent the system for repair but the work card showed that the system BIOS was updated. Not sure why they did it again or there is a latest one than this one. But when I was working in the evening I got a BLUE SCREEN with this error message "KERNEL STACK INPAGE ERROR" and "beginning physical dump of memory". Not sure what this means.
I found two Microsoft Knowledge Base articles that have information on diagnosing what may cause this error message :
Troubleshooting "Stop 0x00000077" or "KERNEL_STACK_INPAGE_ERROR"
http://support.microsoft.com/default.aspx?scid=kb;en-us;315266
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
I ran the chkdsk in the command prompt and it said there was some errors in the harddisk and asked me to run a chkdsk /f command. But my system wouldn't allow that saying that there are some open programs. So I got it touch with Dell technical support and learnt that it has to be done through Recovery Console.
I tried to do it with recovery console but it allows only chkdsk /p and chkdsk /r options it doesn't list any chkdsk /f option. So I ran the chkdsk /p option first and it said the disk some errors. chkdsk /r didn't give any error messages. So i exited from recovery console and ran again chkdsk in the command window. But still it shows there is some error and I need to run chkdsk /f.
When I run chkdsk/f at the command prompt I got this following error....Cannot lock device...do u need to run it during restart(Y/N)...I said yes.
So I scheduled the chkdsk/f when the system restarts. The system restarted and the 5 stages of chkdsk were completed and windows was loaded.
When I ran the chkdsk command again at the command prompt to see if the errors have been removed it still gives me the error showing
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
I also ran the DFT ( Drive Fitness Test of Hitachi. My hard disk is TravelStar 40GN Model IC25N040ATCS04-0 of Hitachi's ) both quick and advanced tests which passed the IDE successfully. I also ran the DELL diagnostics for HDD and it also passed successfully.
Does it mean I don't have any physical damage and just file corruption on the NTFS.
For a complete list of messages that I sent/got from Dell
http://forums.us.dell.com/supportforums/board/message?board.id=SS-portGH&message.id=1726
What should I do now. Please help.
KI Technology G
4 Posts
0
January 16th, 2004 17:00
It sounds like you are having some form of Boot record problems. You may want to try a "Fixmbr" to recreate the master boot record.
You may want to backup your data by plugigng your drive into another machine and setting is as the slave drive. Then copying files over to another drive. Fixmbr sometimes solves the problem... othertimes it does not.
You may also want to try a reinstallation of Windows XP over the top (replaces system files)
geearrkay
15 Posts
0
January 16th, 2004 20:00
Thanks Rob. I appreciate your efforts for helping me out. Please post the links once you find them.
I will check the log and see if there is anything I can make out of it.
geearrkay.
robnalex
2 Intern
•
720 Posts
0
January 16th, 2004 20:00
The behavior of CHKDSK you are describing is perfectly normal. The explanation is complicated, so I'll just post some links for you to ckeck out. After you've run chkdsk /f and restarted, go to start-control panel-admin tools- event viewer. In the left pane click application. In the right pane right click the most recent winlogon and select properties. You will be able to see the corrective action windows took when you restarted.
This should help clarify:
http://webspiffy.com/archives/2002/08/ntfs_file_system_glitch/
Also, see this thread:
http://forums.us.dell.com/supportforums/board/message?board.id=sw_winxp&message.id=100013&highlight=chkdsk#M100013
Rob
Message Edited by robnalex on 01-16-2004 04:43 PM
geearrkay
15 Posts
0
January 16th, 2004 20:00
Rob:
This was the message in the Winlogon. Does this mean my system is ok ?
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
39062015 KB total disk space.
16548952 KB in 85222 files.
28048 KB in 8123 indexes.
0 KB in bad sectors.
184003 KB in use by the system.
32784 KB occupied by the log file.
22301012 KB available on disk.
4096 bytes in each allocation unit.
9765503 total allocation units on disk.
5575253 allocation units available on disk.
Internal Info:
6a 47 02 00 ab 6c 01 00 19 e9 01 00 00 00 00 00 jG...l..........
13 09 00 00 00 00 00 00 ba 01 00 00 00 00 00 00 ................
90 fc d7 05 00 00 00 00 40 71 fc 8b 00 00 00 00 ........@q......
20 c2 63 07 00 00 00 00 20 16 16 ef 04 00 00 00 .c..... .......
f0 1f 3c af 03 00 00 00 00 22 90 3f 09 00 00 00 ..<......".?....
99 9e 36 00 00 00 00 00 e6 4c 01 00 00 00 00 00 ..6......L......
00 60 11 f2 03 00 00 00 bb 1f 00 00 00 00 00 00 .`..............
Windows has finished checking your disk.
Please wait while your computer restarts.
Interestingly once I got back the computer from Dell repair and once I got the "KERNEL_STACK_INPAGE_ERROR" my system requested a CHKDSK at restart and I allowed it. The following is the log for that CHKDSK. It shows 215 index entries were cleaned up,etc. I think something went wrong in Dell repair or in shipping that caused this error. So can I request Dell to replace my hard disk. It is still under warranty.
Checking file system on C:
The type of the file system is NTFS.
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.
Cleaning up minor inconsistencies on the drive.
Cleaning up 215 unused index entries from index $SII of file 0x9.
Cleaning up 215 unused index entries from index $SDH of file 0x9.
Cleaning up 215 unused security descriptors.
39062015 KB total disk space.
16414680 KB in 82645 files.
26856 KB in 8116 indexes.
0 KB in bad sectors.
184003 KB in use by the system.
32784 KB occupied by the log file.
22436476 KB available on disk.
4096 bytes in each allocation unit.
9765503 total allocation units on disk.
5609119 allocation units available on disk.
Internal Info:
6a 47 02 00 93 62 01 00 fd d6 01 00 00 00 00 00 jG...b..........
b5 08 00 00 00 00 00 00 87 02 00 00 00 00 00 00 ................
80 6c 41 06 00 00 00 00 90 0b 0a 7f 00 00 00 00 .lA.............
00 ad 12 09 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 c0 14 8a 96 00 00 00 00 ................
99 9e 36 00 00 00 00 00 d5 42 01 00 00 00 00 00 ..6......B......
00 60 df e9 03 00 00 00 b4 1f 00 00 00 00 00 00 .`..............
Windows has finished checking your disk.
Please wait while your computer restarts.
robnalex
2 Intern
•
720 Posts
0
January 16th, 2004 20:00
Previous message above has been edited to include one excellent link and the link to the forum thread where I found it.
Rob
Message Edited by robnalex on 01-16-2004 04:46 PM
geearrkay
15 Posts
0
January 16th, 2004 21:00
Thanks JRosenfield for your information. Inputs from both you and Rob make me feel better and stop worrying about this and carry on with my work.
Do you know if there is any tool to continuously monitor the state of Harddisk and report if there is something wrong going on or the disk to going to fail and info like that.
JRosenfeld
2 Intern
•
4.4K Posts
0
January 16th, 2004 21:00
Although about new switch commands for chkdsk, this article includes a good description of what it does:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314835&Product=winxp
it also says that chkdsk /r implies (i.e. includes) chkdsk /f
It is quite usual to find that chkdsk finds and fixes minor inconsistencies in the indexes; I think that they often relate to files that have been deleted, but are stuill recorded in the NTFS indexes. Anyway it is not a problem.
geearrkay
15 Posts
0
January 16th, 2004 21:00
robnalex
2 Intern
•
720 Posts
0
January 16th, 2004 21:00
geearrkay-
The log you posted indicates that windows did its job when you restarted. There is nothing in your log any different than what I see when I run chkdsk, nor is there anything to indicate a problem with your hard drive. If you want to be sure, boot from the Dell Diagnostic Tools CD and run a test on the disk.
Check the link I added to my previous post above. I think that will help you understand better what's happening with chkdsk.
I got very obsessed with this whole chkdsk deal a while back and found it next to impossible to get any good explanation, even from Microsoft, as to why chkdsk keeps indicating 'problems'. Actually, there is NO problem.
I hope this helps.
Rob
robnalex
2 Intern
•
720 Posts
0
January 16th, 2004 21:00
The following is from a post by Mike Steinbaugh at Webspiffy.com:
http://webspiffy.com/archives/2002/08/ntfs_file_system_glitch/
This problem occurs because when Chkdsk is run against an NTFS volume, Chkdsk.exe may report that security descriptors are in the database that are no longer referenced by any file or folder, and that it is removing them. However, Chkdsk.exe just reclaims the unused security descriptors as a housekeeping activity, and is not actually fixing any kind of problem.
Microsoft has confirmed that this is a problem in Windows. Fortunately, this error message is an informational message, and can be safely ignored.
All NTFS volumes contain a security descriptor database. This database is populated with security identifiers that represent unique permission settings applied to files and folders. When files or folders have unique NTFS permissions applied, NTFS stores a unique security descriptor once on the volume, and also stores a pointer to the security descriptor on any file or folder that references it.
If files or folders no longer use that unique security descriptor, NTFS does not remove the unique security descriptor from the database, but instead, keeps it cached. Like any caching strategy, you want to keep the cached information as long as possible because it may be used again.
To determine if more serious problems exist before scheduling or running Chkdsk.exe with the /f switch, run the "chkntfs :" (without
the quotation marks) command, where is the drive letter of the drive you want to run the "chkdsk /f" (without the quotation marks) command against. If this command reports that the "dirty bit" is set, there may be real damage that needs to be fixed.
robnalex
2 Intern
•
720 Posts
0
January 16th, 2004 21:00
geearrkay writes: 'That's what I expect it to be. But do you have any idea why these inconsistencies occur in the NTFS filesystem ? I don't have any clue what's happening.'
HERE:
http://webspiffy.com/archives/2002/08/ntfs_file_system_glitch/
robnalex
2 Intern
•
720 Posts
0
January 16th, 2004 21:00
geearrkay-
FYI, here is a recent log from my computer:
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up 6 unused index entries from index $SII of file 0x9.
Cleaning up 6 unused index entries from index $SDH of file 0x9.
Cleaning up 6 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
30724280 KB total disk space.
9033940 KB in 95793 files.
25456 KB in 2530 indexes.
0 KB in bad sectors.
189132 KB in use by the system.
65536 KB occupied by the log file.
21475752 KB available on disk.
4096 bytes in each allocation unit.
7681070 total allocation units on disk.
5368938 allocation units available on disk.
Internal Info:
d6 bc 01 00 1e 80 01 00 76 bf 01 00 00 00 00 00 ........v.......
be 00 00 00 00 00 00 00 ed 00 00 00 00 00 00 00 ................
ae 5a 54 07 00 00 00 00 c2 ad f7 0b 00 00 00 00 .ZT.............
64 83 e2 08 00 00 00 00 00 00 00 00 00 00 00 00 d...............
00 00 00 00 00 00 00 00 b4 0a c8 23 00 00 00 00 ...........#....
70 1f 43 be 00 00 00 00 31 76 01 00 00 00 00 00 p.C.....1v......
00 50 63 27 02 00 00 00 e2 09 00 00 00 00 00 00 .Pc'............
Windows has finished checking your disk.
Please wait while your computer restarts.
See? Not much different from what yours is showing.
Rob
JRosenfeld
2 Intern
•
4.4K Posts
0
January 16th, 2004 21:00
robnalex
2 Intern
•
720 Posts
0
January 16th, 2004 22:00
Some hard drives I think may be designed to initiate a warning if things get funky, and Windows may do the same, but sometimes when they die, they just die, and that's the end of the story.
I keep recent images of my C: Drive and keep everything else backed up on other drives.
Rob
Message Edited by robnalex on 01-16-2004 06:12 PM