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 dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
chkdsk: "windows found problem with file system" but doesn't repair
- Thread starter hiker056
- Start date
firewolfrl
Technical User
run it with /R
Locates bad sectors and recovers readable information. Implies /p.
that should help but beware it could take quite a while to run as it does 5 stages
Locates bad sectors and recovers readable information. Implies /p.
that should help but beware it could take quite a while to run as it does 5 stages
ChkDsk Logs are kept in the Event Viewer. Search for Winlogon events in the Event Viewer (Application Folder) shortly after you run ChkDsk. See what errors were found (if any) in there.
- Thread starter
- #4
- Thread starter
- #5
I found a winLogon entry from when i ran chkdsk with /r and /f yesterday. A couple of lines about fixing 3 unused index entries and 3 unused security descriptors.
I ran "chkdsk c:" again right after the reboot and it still says windows found an error with the file system.
I ran "chkdsk c:" again right after the reboot and it still says windows found an error with the file system.
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.
The drive manufacturer will have free diagnostic software to thoroughly check the condition of your hard drive in case that is failing.
If you are regularly inside the computer box, a loose connection may be the cause?
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.
The drive manufacturer will have free diagnostic software to thoroughly check the condition of your hard drive in case that is failing.
If you are regularly inside the computer box, a loose connection may be the cause?
- Thread starter
- #7
Thanks for trying. That fsutil dirty query came back NOT DIRTY.
This is happening on the c: drive.
I have only opened the tower box once and that was at least a year ago to replace a sound card. The machine i think is 5-6 years old, so something going wrong with the hardware is entirely possible.
This is happening on the c: drive.
I have only opened the tower box once and that was at least a year ago to replace a sound card. The machine i think is 5-6 years old, so something going wrong with the hardware is entirely possible.
firewolfrl
Technical User
I have seen that before and everytime that a bad chkdsk error happens that does not go away it was a bad drive
Start saving your data as you may not have much time with the drive
Start saving your data as you may not have much time with the drive
preferably manufacturer's diag, as it can attempt to recover bad sectors.
or seatools to detect errors
or seatools to detect errors
- Thread starter
- #12
Seagate tool didn't find the c: drive. This is an IBM PC, but not sure if that's who manufactured the HD or not.
Also notice a big performance drag recently, more than normal. Thought may be just not enough RAM for new applications, but maybe it's also pointing to a HD going bad.
Also notice a big performance drag recently, more than normal. Thought may be just not enough RAM for new applications, but maybe it's also pointing to a HD going bad.
mscallisto
Technical User
If you don't have a Seagate drive then I wouldn't expect the Seagare diagnostic software to work.
You need to determine what brand and model drive you have then visit their web site and look for their diagnostic tool. If you're lucky they may have one to download.
Some ways to determine Drive types are
Sure way
Open the box and look
(you may have to remove the drive to find the Brand/Model label)
It may be found in your device manager
Start > Control Panel > System Icon > Hardware tab > Device Manager > Disk Drives > double click on the HDrive and pick the "Details" tab. You may need to pick Hardware Ids from the dropDown List.
Finally it may be found in your Bios but usually the manufacturer doesn't spend the extra dollars for somewhat useless bios info
sam
You need to determine what brand and model drive you have then visit their web site and look for their diagnostic tool. If you're lucky they may have one to download.
Some ways to determine Drive types are
Sure way
Open the box and look
(you may have to remove the drive to find the Brand/Model label)
It may be found in your device manager
Start > Control Panel > System Icon > Hardware tab > Device Manager > Disk Drives > double click on the HDrive and pick the "Details" tab. You may need to pick Hardware Ids from the dropDown List.
Finally it may be found in your Bios but usually the manufacturer doesn't spend the extra dollars for somewhat useless bios info
sam
Give this utility a try. But I'm inclined to think like everyone else - better make a backup of anything important because the drive is probably on its way out.
- Thread starter
- #15
Thanks. I think i'm square now. I'd checked the hardware information prior to originally posting as the last post referenced; however i was thinking i didn't see the real c: drive (it's MAXTOR) because i'd recently connected a MAXTOR external harddrive by USB.
The seagate diagnostic tool someone had previously mentioned DOES pick up my c: drive now that i know what i'm looking for.
The seagate diagnostic tool someone had previously mentioned DOES pick up my c: drive now that i know what i'm looking for.
- Thread starter
- #16
When you checked the Event Viewer, were there any other errors mentioned in there?
I wonder whether checking your RAM might show any problems?
I wonder whether checking your RAM might show any problems?
firewolfrl
Technical User
Was this a fresh install of Windows or a was it a cloned install?
- Thread starter
- #19
The event monitor (application) showed no errors relevant to chkdsk.
This is an original install. (purchased in spring 2002).
Having trouble using those RAM check tools. I had considered a RAM update regardless since this system only has about 256MB.
We've noticed some serious system performance issues in the last few weeks. That would also correlate to some hardware/memory issues.
Given all the considerations (could use a RAM upgrade, poor performance, possible hardware issues) i decided to purchase a new system this week. should be on the way.
This is an original install. (purchased in spring 2002).
Having trouble using those RAM check tools. I had considered a RAM update regardless since this system only has about 256MB.
We've noticed some serious system performance issues in the last few weeks. That would also correlate to some hardware/memory issues.
Given all the considerations (could use a RAM upgrade, poor performance, possible hardware issues) i decided to purchase a new system this week. should be on the way.
- Status
Similar threads