Hard Drive - Checking File System on F: at Startup

G

ggalv

New Member
#1
I have a Computer with Windows XP, that is "Checking file system on F:" at startup. I booted the computer several times, and it did it about 5 times. Do you go guys know why it might be doing this?

I ran the Windows "Error-checking" tool and and selected to Automatically fix file system errors and scan for and attempt recovery of bad sectors. After one boot up, it did not check the file systems.

Is there a program that can tell me what might be going on? Believe this is an older western digital.
 
Midknyte

Midknyte

Caffeine Fiend
#2
Is F: a separate drive from your boot drive? Is it an external USB HD?

First thing I would do is run the manufacturer's hd diags.

If everything passes, check the status of a drive:

fsutil dirty query driveletter:

If the drives are marked as "dirty",
run this command for each dirty drive:

Chkdsk driveletter: /f /r
 
G

ggalv

New Member
#3
Yes, the F:Drive is a separte drive from my boot drive. It is an IDE 120GB Western Digital that is attached to my motherboard.

Do you know which manufacturer's hd (WD) diags utility do I need for this IDE drive?

Thanks
 
Shinma

Shinma

____________
#4
... It is an IDE 120GB Western Digital that is attached to my motherboard.

Do you know which manufacturer's hd (WD) diags utility do I need for this IDE drive? ...
If WD Caviar Blue,
Data Lifeguard Diagnostic for DOS and/or Data Lifeguard Diagnostic for Windows
 
G

ggalv

New Member
#5
Yes, it was the WD Caviar Blue. I ran the "Quick Test" and "Extended Test" and they both passed succesfully. Do you guys think the Windows "Error-checking" tool fixed this drive?

Should I check the if the drives are "dirty"? I typed "fsutil dirty query driveletter:" in the run window and nothing happened.
 
Midknyte

Midknyte

Caffeine Fiend
#6
Drive letter is the letter of the drive you want to scan. In your case, it would be F:

fsutil dirty query F:

Make sure to run it from a command prompt window.
 
G

ggalv

New Member
#7
I ran the command and it did not show any of my drives as being "dirty".

I had a lot of files in that drive, and they are all there right now. Is there any way those files might have been corrupted since my computer was "Checking file system on F:" several times at startup? Or is this something I should not be concerned with.
 
Midknyte

Midknyte

Caffeine Fiend
#8
chkdsk should have said "F: is NOT dirty". It's just a one line answer.

What file system are you using for F:? FAT32 or NTFS?

Anything is possible. If it stopped scanning and passed diags, i think you're ok. In any case, MAKE A BACKUP OF YOUR FILES.
 
G

ggalv

New Member
#9
Yes, that is what it said "Volume - F: is NOT Dirty"

The F: drive is NTFS

Yes, from past experience I make backups of all my files.

In the pass there has been one or two instances that say for example some picture files are there, but when I try to open them they don't open. Is there a way to check if pictures files are corrupted without having to open each one individually?
 
Midknyte

Midknyte

Caffeine Fiend
#10
Hmm. Not sure if there's a tool to check data files. SFC checks windows files.

You could try opening the directory in Faststone or another image viewer. If the thumbnail doesn't show, then you can try opening the file. If it still doesn't open, then that's probably corrupt.
 

Associates