Chkdsk ran on external hdd on boot. Would it hault if it found an error?

Hi All,

I had someone in the office today tell me that upon rebooting (Windows XP) her computer started running chkdsk and ran all three verifying steps for about 30 minutes before the machine would boot.  It was being run on her external hard drive that was plugged in that is used on occasion for off-site file storage.  She was smart enough to write down the volume name so we condluded that.  She believes that the last time it was removed, she did not use the "safely remove" feature.  I'm guessing this might have prompted chkdsk.  

However, since the test was taking awhile she walked away and didn't watch the rest of the messages on the screen.  It seemed to finish it's checks and it booted into Windows and the drive was accessible.  The question is, and I don't remember off-hand, if chkdsk found an a bad error on the drive, would it have haulted when it was done instead of booting into Windows?  Like I said, the drive was useable after this.  I'm just trying to determine if we should recommend further follow-up testing of the drive.  

Thanks
JsmplyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Thermo-MonkeyCommented:
To answer your primary question, does chkdsk pause on completion? No, it will fix any errors it finds and continue on with the boot.

You are exactly right though when you said "She believes that the last time it was removed, she did not use the "safely remove" feature.  I'm guessing this might have prompted chkdsk."

So, in knowing that I believe it is safe to say there was never a real issue with the disk that prompted chkdsk to run.
0
ClintB12Commented:
In my experience, it wouldn't halt the boot process. The question is, was it set to automatically fix the errors? I would run chkdsk again with a /R switch which will search for and automatically attempt to recover readable information from bad sectors. This is an extensive test which could take hours, but just do it when you know you won't need to use the drive in question. It couldn't hurt if there is any doubt before you put more data on the drive, and if a lot of errors pop up, it would be good to recover all the data stored on that drive before it fails completely.
0
enriquecadalsoCommented:
Hello. You can always check the results of the chkdsk in the event viewer, in the Application log, with "winlogon" source. Look for the events in the time the check was performed,  or filter by source = winlogon.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

nobusCommented:
>>   I'm just trying to determine if we should recommend further follow-up testing of the drive.  <<  if you have a spare pc, or the time, it never hurts to test it.
you find all diags on the ubcd : http://www.ultimatebootcd.com/      
 
0
noxchoGlobal Support CoordinatorCommented:
Actually Windows tested the drive that was not tested before. When you connect the new drive and use it on the system it could prompt "check the drive" but normally we do ignore that. Windows 7 and Vista for example are more insisting on this. Once you ignore the check message the file system of the drive is marked as "dirty" and check is done during next reboot. This is most possibly what happened in your case.
Standard check.
If you want to check the drive - run command line CHKDSK without /f parameter. It will run read only mode and show if any problem exists.
0
JsmplyAuthor Commented:
Thanks everyone. Enrique, the results of the chkdsk prior to booting of Windows will still show in the event viewer?
0
enriquecadalsoCommented:
Yes, it will. Thats precisely the point, the blue screen goes away too fast to see it when it finish the check.
0
nobusCommented:
if the BSOD disappears, set your system to not reboot on erros from device manager...
0
JsmplyAuthor Commented:
Okay I found it in the event viewer.  Here is what it showed.  Does it look consistent with what an "inproper removal" would have done?  

Does anyone see anything relevant to show the drive might be failing, etc?  Thanks!
Event Type:	Information
Event Source:	Winlogon
Event Category:	None
Event ID:	1001
Computer:	COMP
Description:
Checking file system on G:
The type of the file system is NTFS.
Volume label is DataDrive

The volume is dirty.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file SYMEFA~1.DB- (80173) into directory file 778479.
Recovering orphaned file SYMEFA.DB-journal (80173) into directory file 778479.
Recovering orphaned file ETILQS~1 (80174) into directory file 778479.
Recovering orphaned file etilqs_CAFF99372A18ED2D741DD419 (80174) into directory file 778479.
Cleaning up 9 unused index entries from index $SII of file 0x9.
Cleaning up 9 unused index entries from index $SDH of file 0x9.
Cleaning up 9 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has made corrections to the file system.

 488384000 KB total disk space.
 446252208 KB in 789102 files.
    324988 KB in 52268 indexes.
         0 KB in bad sectors.
    995504 KB in use by the system.
     65536 KB occupied by the log file.
  40811300 KB available on disk.

      4096 bytes in each allocation unit.
 122096000 total allocation units on disk.
  10202825 allocation units available on disk.

Internal Info:
70 ef 0d 00 a6 d6 0c 00 f1 87 15 00 00 00 00 00  p...............
07 00 00 00 00 00 00 00 1f 00 00 00 00 00 00 00  ................
10 82 5c 3e 00 00 00 00 d4 da ac 96 03 00 00 00  ..\>............
10 36 21 43 00 00 00 00 00 00 00 00 00 00 00 00  .6!C............
00 00 00 00 00 00 00 00 ba 73 7a 1c 04 00 00 00  .........sz.....
00 76 05 6b 00 00 00 00 98 3c 07 00 6e 0a 0c 00  .v.k.....<..n...
00 00 00 00 00 c0 12 65 6a 00 00 00 2c cc 00 00  .......ej...,...


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
noxchoGlobal Support CoordinatorCommented:
The drive was given dirty flag due to minor file system issues: "The volume is dirty."
And maintenance was done on four items only:

Recovering orphaned file SYMEFA~1.DB- (80173) into directory file 778479.
Recovering orphaned file SYMEFA.DB-journal (80173) into directory file 778479.
Recovering orphaned file ETILQS~1 (80174) into directory file 778479.
Recovering orphaned file etilqs_CAFF99372A18ED2D741DD419 (80174) into directory file 778479.

This is normal percentage of possible problems on actively used HDD. So really nothing to worry about. Take frequent backups of the important data. That is helpful.
0
JsmplyAuthor Commented:
Thanks noxcho.  This is the backup drive so that is why we were concerned.  Thanks everyone else also!
0
JsmplyAuthor Commented:
Well actually just to be thorough, should this be seen on a backup drive that is only used on occasion, and not a regular system drive?  Just curious since you said actively used HDD.  
0
noxchoGlobal Support CoordinatorCommented:
It can be seen on any drive. If you create\delete files, install deinstall applications, move folders - be sure that CHKDSK will find some inconsistency.
Another problem is that Microsoft never did publish documentation on NTFS file system and the information available on www.ntfs.com is collected by volunteers. So only MS dev guys should know the answer to the question - why does all those errors occur.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JsmplyAuthor Commented:
Thx!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.