Since this is RAID, I would disconnect all but one drive at a time for testing and use the bootable ultimate boot CD to run the diagnostics from.
That way, you don't boot into Windows after having disconnected one of the RAID drives and get all the warnings. Another question - why would the data drive be non-raid. You'd better find out what's going on in terms of what disks are RAID and what function they play or you won't understand the whole picture.
Let it go. Although it normally shouldn't, I've see chkdsk take 1 day or more and successfully complete. I would NOT let it go - it's a waste of time. You have two different opinions - you'll have to choose one course of action. Might be a big deal if it was the data disk and it wasn't RAIDed. When ChkDsk goes wrong it can lead to disaster and reformatting which is why I prefer to run any initial ChkDsk in "read only" mode before checking with any set parameter or box checked in the GUI.
There are some relevant XP links in this post, relevant more to my slight digression from the current subject, but relevant if you use ChkkDsk often. Is ChkDsk still a worry when run in Vista? Yes, yes. Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Correcting errors in the volume Bitmap. Thread starter jaymax Start date May 7, Status This thread has been Locked and is not open to further replies. The original thread starter may use the Report button to request it be reopened but anyone else with a similar issue should start a New Thread. Watch our Welcome Guide to learn how to use this site.
Joined May 28, Messages Macboatmaster Trusted Advisor. Spam Fighter. Joined Jan 14, Messages 25, It all depends on how chkdsk was commissioned to start. Chkdsk might fail in read-only mode or might report false errors.
But I'm wondering if it really isn't the hard drive but other file errors that chkdsk can't seem to fix. I'll run chkdsk in read only and it says: "Correcting errors in the Volume Bitmap.
Windows found problems with the file system. I'm running chkdsk about twice a day now. I was planning on Ghosting the current drive and cloning it to the new drive. But if the errors are OS related, won't I just be here with a new but still unstable drive? Is there some way to fix these errors?
Or, could it just be that the drive is failing and that's the real cause? Mar 29, 3, 0 20, 0. Hi, Your restore files are corrupted. This will clear all old corrupted restore files. After reboot, uncheck the box to restart system restore and then reboot. Try to create a new restore point. If it works, the system restore is now working normally. Hope it helps. Peter, thanks for the input. I turned off System Restore and I'll check that out in a bit.
It ran through everything, although it started rebooting before I could read the results. That computer has never shown any evidence of disk problems. One possible explanation? I have Executive Software Diskeeper running for a couple of years on both computers. Maybe it is causing chkdsk to report errors that really don't threaten the file system. Any ideas? Moreover, the time taken by check disk depends upon the size of the disk and the amount of data that it contains. Hope this information is helpful.
Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. So I would like to ask: 1 Should I let it continue? I can't tell if the process has stalled. There is no error message.
0コメント