leblanc
asked on
C Drive checkdisk does not work
I am trying to create a system image to backup my laptop which has Win 10 Home Edition. It said that C drive has an error and I need to check the disk. I click on the link for "check the disk for error". It rebooted the laptop and check for error. The I tried to create system image again and it kept asking me the to check the disk again. I did it again for 4 times now and I still have that C drive. Any thoughts how to fix this? Thx
Hi,
I recently wrote and published an article that I think might help you out here.
I've pasted the relevant parts I think could assist you from it below.
Lots of other good info and tips in the article as well though, so I'd recommend you read it.
That said:
Hope that's helpful.
Regards, Andrew
I recently wrote and published an article that I think might help you out here.
I've pasted the relevant parts I think could assist you from it below.
Lots of other good info and tips in the article as well though, so I'd recommend you read it.
That said:
First, open up an Administrative DOS command prompt. Many ways to do this, but one easy way is:
Press your Windows Key, type CMD and select Run as administrator.
Click Yes on the User Account Control (UAC) prompt to continue.
An Administrator: Command Prompt will appear. We will do our work here.
Maintenance Step 3. Check the integrity of Windows Protected System Files
Still in the Administrative Command Prompt window, issue the following command.
SFC /scannow
Windows will now run a series of tests and make any necessary repairs if it finds a problem.
In the example below, SFC reported that it did not find any integrity violations. That's a good thing. If it does find any, it will repair them and advise you of that once it completes its verification scan. No more to do with SFC for maintenance purposes now.
Maintenance Step 4. Use DISM to check for and correct system problems
The DISM command is often used when a computer has problems like not starting up or starting up with errors, performing poorly, or giving unexpected and unexplained errors. It basically repairs Windows installations that tools like SFC and CHKDSK can’t fix.
In such scenarios, the best option is to use DISM to attempt to repair any underlying issues. Its use is harmless so it is safe to use for routine maintenance. It can often do a lot of good by repairing errors that other repair tools can't fix.
Note: There are many switches associated with running DISM, but we're only going to concentrate on two of them for maintenance purposes, namely CheckHealth and RestoreHealth.
Here's how to use it...
Still in the Administrative Command Prompt window, optionally issue the following command.
DISM /Online /Cleanup-Image /CheckHealth and press the Enter key.
Many people recommend using the CheckHealth switch, so I've included it here for the sake of completeness only. However, I don't trust the command because it typically runs for less than a second and has consistently reported "No component store corruption detected." even when there were problems. For this reason, I recommend always running DISM with the RestoreHealth switch instead of CheckHealth.
Even if there are no problems, DISM will NOT do any harm, and the bonus is that if there are problems, then DISM will repair them for you. Since running DISM with RestoreHealth also does a health check, you only need to run this command:
DISM /Online /Cleanup-Image /RestoreHealth and press the Enter key
You should get a result like the following which means all is now A-OK, and any errors have been corrected automatically:
Oh, and it doesn't take all that long to run, either. With a decent Internet connection expect it to take about 10 minutes or so.
Hope that's helpful.
Regards, Andrew
note that the disk can have problems, so it would be good to run a disk diagnostic
find the disk model in device manager under disks, and post it here, since diagnostics differ by brand and model, and for HDD and SSD
it would be good practice to post the laptop model also
find the disk model in device manager under disks, and post it here, since diagnostics differ by brand and model, and for HDD and SSD
it would be good practice to post the laptop model also
Enter the Start screen
Press Windows key + C on your keyboard to show the Charms bar. (If you are using a touch screen: touch the right edge of the screen and swipe your finger toward the center of the screen to show the Charms bar)
Click Search
Type Command Prompt into the Search field
Right click Command Prompt (If you are using a touch screen: Touch and hold your finger to the Command Prompt, slide your finger down until you see an outline around the tile, and finally release your finger from the screen.)
Click Run as administrator
Enter the command: sfc /scannow
ASKER
The SSD hardrive came with the MSI laptop GE75 Raider.
chkdsk c: showed no errors
C:\WINDOWS\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is Windows.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
707840 file records processed.
File verification completed.
Phase duration (File record verification): 3.46 seconds.
7828 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.19 milliseconds.
Stage 2: Examining file name linkage ...
971 reparse records processed.
867858 index entries processed.
Index verification completed.
Phase duration (Index verification): 7.74 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 660.89 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.19 milliseconds.
971 reparse records processed.
Phase duration (Reparse point and Object ID verification): 5.39 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 29.73 milliseconds.
80010 data files processed.
Phase duration (Data attribute verification): 0.50 milliseconds.
CHKDSK is verifying Usn Journal...
40466512 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 113.05 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
498746367 KB total disk space.
382732680 KB in 359493 files.
212340 KB in 80011 indexes.
0 KB in bad sectors.
835059 KB in use by the system.
65536 KB occupied by the log file.
114966288 KB available on disk.
4096 bytes in each allocation unit.
124686591 total allocation units on disk.
28741572 allocation units available on disk.
chkdsk c: showed no errors
C:\WINDOWS\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is Windows.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
707840 file records processed.
File verification completed.
Phase duration (File record verification): 3.46 seconds.
7828 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.19 milliseconds.
Stage 2: Examining file name linkage ...
971 reparse records processed.
867858 index entries processed.
Index verification completed.
Phase duration (Index verification): 7.74 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 660.89 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.19 milliseconds.
971 reparse records processed.
Phase duration (Reparse point and Object ID verification): 5.39 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 29.73 milliseconds.
80010 data files processed.
Phase duration (Data attribute verification): 0.50 milliseconds.
CHKDSK is verifying Usn Journal...
40466512 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 113.05 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
498746367 KB total disk space.
382732680 KB in 359493 files.
212340 KB in 80011 indexes.
0 KB in bad sectors.
835059 KB in use by the system.
65536 KB occupied by the log file.
114966288 KB available on disk.
4096 bytes in each allocation unit.
124686591 total allocation units on disk.
28741572 allocation units available on disk.
>> The SSD hardrive << thank you for posting the laptop model, but you forgot the disk model it seems. can you post that also? eg Samsung SSD need samsung magician software, but each brand / model differs
ASKER
wdc pc sn730 sdbpnty-512g-1032
Check disk does not work for SSD related dirty bit, or error.
Go to wds.com and download the WDS diagnostic tools for ssds and test it.
Look at getting acronis tool for wd and you could use it to clone out or create an image of the OS.
Look at macrium as well for imaging.
You did not mention how you are trying to create an image and the destination.
Are you using the Windows backup tool to create an image? If so what is the destination to which you are writing it's!
Go to wds.com and download the WDS diagnostic tools for ssds and test it.
Look at getting acronis tool for wd and you could use it to clone out or create an image of the OS.
Look at macrium as well for imaging.
You did not mention how you are trying to create an image and the destination.
Are you using the Windows backup tool to create an image? If so what is the destination to which you are writing it's!
ASKER
Yes. Windows backup tool to create an image . Destination is an external harddrive.
Try the free acronis version for WD and use it to create an image to write out to the external drive.
Without knowing the error, it is hard to get what your issue is. Can you confirm that the external HD is not the issue.
try using fsutil drty query c: or the external harddrive to see whether it is seen as having a dirty bit.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-dirty
you can use the fsutil to clear this state and see if the backup works.
IF the issue is the source SSD as an issue, possibly a error that is corrected, but causes the hiccup. one option is to clone the existing drive. How old is the computer/ssd? 3-5 years?
Without knowing the error, it is hard to get what your issue is. Can you confirm that the external HD is not the issue.
try using fsutil drty query c: or the external harddrive to see whether it is seen as having a dirty bit.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-dirty
you can use the fsutil to clear this state and see if the backup works.
IF the issue is the source SSD as an issue, possibly a error that is corrected, but causes the hiccup. one option is to clone the existing drive. How old is the computer/ssd? 3-5 years?
you can use their dashboard; find it here with other softwares : Software and Firmware Downloads | WD Support (wdc.com)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
use the WDc diagnostic tools to see what it is reproting about the SSD.
chkdisk should not be run on SSDs
Best backup your data using windows backup specific paths versus the entire thing and reach out through whom you purchased it to see what options you have ...
If it is a faulty ssd, you might get it replaced....
chkdisk should not be run on SSDs
Best backup your data using windows backup specific paths versus the entire thing and reach out through whom you purchased it to see what options you have ...
If it is a faulty ssd, you might get it replaced....
does the recovery delete your Data ?? be sure you know what you do
i would ask for a warranty repair
i would ask for a warranty repair
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: 'leblanc' (https:#a43292943)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: 'leblanc' (https:#a43292943)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
cmd - Right-click "Run as administrator"
chkdsk c:
It won't be able to fix errors, but at least it will report them so you can see if there are problems. Let us know if it reports errors or not.