EzDevInfo.com

Windows chkdsk replaced bad cluster - are files now corrupted?

I ran chkdsk on a drive and when it got to stage 4 (verifying file data), this message appeared for some files:

Windows replaced bad clusters in file ######
of name \path\filename.ext

Does this mean that these files are now corrupt? I'm mainly concerned about ISOs and executables. Unfortunately, I don't have hashes of them so I have nothing to check their integrity against after chkdsk finishes running.

If it's relevant, this is a mechanical hard drive, a 2TB Western Digital Green.

Why does Windows run CHKDSK on every boot?

Every time I turn on my PC, I get the following message:

Checking file system on E:
The type of the file systen is NTFS.
One of your disks need 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.

CHKDSK is verifying files (stage 1 of 3)... 0 percent completed

I allow CHKDSK to to complete, but Windows does not load. This message appears every time I boot my computer.

Could someone explain me why this message appears and what I should do to make it disappear?

Running chkdsk on a disk partition without a drive letter

I have a hard drive that shows up in Disk Management as having two partitions.

One of the partitions says 69.71GB and that's it. The other says 4.82GB and, underneath that, Healthy (OEM Partition).

I'm trying to do chkdsk on the 69.71GB partition and am unsure of how to do it without a drive letter.

It's an NTFS partition that's gotten corrupted. Linux's ntfsfix spits out a bunch of errors so I'm thinking chkdsk might be better.

What are "reparse records"?

My computer just did a chkdisk, and when it finished processing file records, it said it had processed "44 reparse records". What exactly are they?

How to save chkdsk results to a .txt file?

Is there a way to get the results of chkdsk with the /f switch to a .txt file instead of having to go to the event viewer?

EDIT: I want to get the output of what chkdsk fixed, not just what errors have been shown.

PS: Im using Windows XP.

Does scandisk/CHKDSK produce a log file when running before login?

I scheduled and ran CHKDSK after restart, but it took a long time, so I left it to run all night. In the morning, it had finished and the computer had logged in, but I had no way of knowing if it found bad sectors or anything.

Is there a log file I can look at?

This is what CHKDSK looks like when running before login:

Change RAW partition to NTFS or recover files from RAW

I've resized my C:\ partition and now I can't boot. I tried to use CHKDSK but I get the error: CHKDSK does not support RAW disk. How can I restore it to NTFS or at least recover my files?

Thanks for any help.

What can I do with .chk files in FOUND.000 folders?

Just discovered I have gotten a FOUND.000 folder on my usb drive. I guess from running chkdsk once. It has three files in it:

• FILE0000.CHK
• FILE0001.CHK
• FILE0002.CHK

What exactly can I do with these files? What are my options? Are they lost files? Are they garbage? Can I use them for anything at all? Or will I just have to delete them?

Where are the results of chkdsk located in Windows 7?

I recently ran the chkdsk in Windows 7 on my local C: drive. After chkdsk completed, the results flashed on the screen for a few seconds and then the computer booted up. I wasn't able to read the results in time. Are the results saved to a text file somewhere?

How safe is it to run CHKDSK on an SSD?

I recently saw Windows 7 pop up a warning or two that I should run chkdsk on my laptop. My laptop came with an SSD and I'm not sure if there are any negative implications to running chkdsk on such a drive. Are there any potential issues with reporting "bad sectors" on the drive? I would imagine that the physical concept of sectors is completely different between a platter and a microchip.

I don't think my SSD supports TRIM. It's about 14 months old and a quick web search seems to hint that it doesn't (though it's nearly impossible to find out this info for sure!). I'm also not sure if TRIM is even relevant here since there shouldn't be much in the way of deletes.

So, how safe is it to run chkdsk on my SSD drive?

The model of SSD that I have is reported as "Samsung SSD PB22-JS3 2.5".

How can I run chkdsk on boot up for multiple drives in Windows (Vista)?

I know how to run a chkdsk on boot for C:.

How can I schedule chkdsk to run on boot for multiple drives (which normally will just be checked inside Windows)?

CHKDSK is not available for RAW drives

When I run the chkdsk command on my boot drive, I get an error message "CHKDSK is not available for RAW drives." What does this mean, and how can I fix it?

C:\>chkdsk c:
The type of the file system is RAW.
CHKDSK is not available for RAW drives.

I am running Windows 7, 64 bit. I am not experiencing any serious problems with my machine- this was just a matter of routine maintenance. I know I have run CHKDSK successfully on this machine before, but it has been a long time (probably several months).

Why is chkdsk using 90% of my RAM?

When I built my new computer, I gave my old one to my parents who were in dire need of an upgrade, after cleaning everything out of it, of course, leaving just the OS and a few programs. It worked fine for a while, before it started to fail to load Windows (it would just get stuck). After investigating this behavior and asking around, I decided that it might be a failing hard drive, so I pulled it out and plugged it into my own computer to run chkdsk on it (I initially did this to try and boot to the drive, but since my computer is set up with RAID and that Windows installation didn't have RAID drivers, I just booted into my own Windows 7 installation and ran chkdsk on it).

I did this last Friday evening, and it's been running since then (which makes it about 6 days so far). I am not surprised since it can be slow, it's a 1 TB hard drive, and a Western Digital "green" one at that, so it's likely running at a slower RPM anyway. I do see it make progress, so I know it's not stuck, and the hard drive light has been perpetually on, on my computer, which I haven't used for much of anything else, other than sharing files over the network and light web browsing, while this has been running.

My computer has 16 GB of RAM, and is running Windows 7 Pro x64. Why does chkdsk take up 90% of that? It's holding that level steady, and has been for days, going between 90% and 91%, as it frees and fills memory constantly. CPU usage is very low (which I expect since this is a very I/O heavy operation).

It doesn't look like anything bad is going on, but I am curious. Why is chkdsk taking up so much memory? I am at least glad that it seems to be doing this intelligently, as it's maintaining a high level without starting to thrash the main HDD by paging.

Does anyone know? Is this normal?

Why is NTFS case sensitive?

I personally thought that NTFS was case insensitive, since you can type cmd, CMD, cMd or even CmD and still get the command prompt. However, why is it that during a CHKDSK x: /f /r, sometimes it fixes capitalization in some files? If it didn't care about the case, it shouldn't matter about that, and CHKDSK shouldn't be checking if it's actually CMD or cmd. Am I right? Where does it actually matter in the file system?

Chkdsk Questions

Recently in running chkdsk /r on my system drive (platter drive, Windows 7 Ultimate 64bit) I've gotten back "4 EA records processed" and "76 reparse records processed". Am I right in assuming these aren't problematic reports? Do most NTFS system drives report back EA and reparse records processed when chkdsk is run?