irregularjoe Posted March 20, 2013 Report Share Posted March 20, 2013 Anyone know why I can't CHKDSK /f from a command prompt using a Windows Recovery disk? CHKDSK /r works, but doesn't seem to help. When I attempt CHKDSK /f , message says "Unknown Parameter". I formatted C drive but have a seperate partition for data. Trying to re-install XP without data loss. Appreciate all replies. Quote Link to post Share on other sites
Besttechie Posted March 20, 2013 Report Share Posted March 20, 2013 Anyone know why I can't CHKDSK /f from a command prompt using a Windows Recovery disk? CHKDSK /r works, but doesn't seem to help. When I attempt CHKDSK /f , message says "Unknown Parameter". I formatted C drive but have a seperate partition for data. Trying to re-install XP without data loss. Appreciate all replies.This is just a shot in the dark, but since you have separate partitions have you tried running chkdsk driveletter: /f (e.g. chkdsk c: /f)?B Quote Link to post Share on other sites
Pete_C Posted March 20, 2013 Report Share Posted March 20, 2013 Read thishttp://www.thecomputerparamedic.com/?p=61Chkdsk worked just fine in beta versions of Windows 7, but somewhere between the last test version and the general release something changed and for some computers running Windows 7 the CHKDSK /f command simply will not run–though oddly, the CHKDSK /r command does run. The problem with that is on todays modern computers with large harddrives, CHKDSK /r can take a couple hours to run.Microsoft implies this is a problem with computers that have certain infrared controllers on them, though I have seen this happen on computers without any such controller.Fortunately, Microsoft supplies a little know patch for computers suffering this problem.Just go to this pagehttp://support.microsoft.com/kb/975778Click the REQUEST HOTFIX link on the top and follow the prompts.After downloading and running the hotfix, your computer will run CHKDSK c: /f normally. Quote Link to post Share on other sites
irregularjoe Posted March 20, 2013 Author Report Share Posted March 20, 2013 Anyone know why I can't CHKDSK /f from a command prompt using a Windows Recovery disk? CHKDSK /r works, but doesn't seem to help. When I attempt CHKDSK /f , message says "Unknown Parameter". I formatted C drive but have a seperate partition for data. Trying to re-install XP without data loss. Appreciate all replies.This is just a shot in the dark, but since you have separate partitions have you tried running chkdsk driveletter: /f (e.g. chkdsk c: /f)?B Quote Link to post Share on other sites
irregularjoe Posted March 20, 2013 Author Report Share Posted March 20, 2013 Yes. Didn't help. Quote Link to post Share on other sites
flashh4 Posted March 20, 2013 Report Share Posted March 20, 2013 Joe you do have Administrator privileges ? It is required to run the chkdsk / f command.Also, have you tried this: right-clicking on the Start menu on the computer taskbar. Next, select "Explore." Right-click on the "f" disk drive or designated hard drive volume letter and then select "Properties." Go to the Tools tab and click "Check Now" under the Error-Checking section.Will this help !! http://technet.microsoft.com/en-us/magazine/dd637756.aspxChuck Quote Link to post Share on other sites
irregularjoe Posted March 20, 2013 Author Report Share Posted March 20, 2013 This is XP, Pete. Also, only an 80 gig HDD with two partitions .Read thishttp://www.thecomput...medic.com/?p=61Chkdsk worked just fine in beta versions of Windows 7, but somewhere between the last test version and the general release something changed and for some computers running Windows 7 the CHKDSK /f command simply will not run–though oddly, the CHKDSK /r command does run. The problem with that is on todays modern computers with large harddrives, CHKDSK /r can take a couple hours to run.Microsoft implies this is a problem with computers that have certain infrared controllers on them, though I have seen this happen on computers without any such controller.Fortunately, Microsoft supplies a little know patch for computers suffering this problem.Just go to this pagehttp://support.microsoft.com/kb/975778Click the REQUEST HOTFIX link on the top and follow the prompts.After downloading and running the hotfix, your computer will run CHKDSK c: /f normally. Quote Link to post Share on other sites
irregularjoe Posted March 20, 2013 Author Report Share Posted March 20, 2013 Joe you do have Administrator privileges ? It is required to run the chkdsk / f command.Also, have you tried this: right-clicking on the Start menu on the computer taskbar. Next, select "Explore." Right-click on the "f" disk drive or designated hard drive volume letter and then select "Properties." Go to the Tools tab and click "Check Now" under the Error-Checking section.Will this help !! http://technet.micro...e/dd637756.aspxChuckYes, I am admin. I could not get into windows at all. This was all being attempted from the recover console with command promts. The "f" refers to switch in the command, not the drive letter. Quote Link to post Share on other sites
Pete_C Posted March 21, 2013 Report Share Posted March 21, 2013 My bet is that just as in Win7 case something is preventing the drive from being "locked" to allow a chkdsk /f to workDid Chkdsk /r workWhat about chkdsk /f /rhttp://answers.microsoft.com/en-us/windows/forum/windows_xp-performance/win-xp-chkdsk-f-does-not-run-at-startup/ab902846-5058-42bc-9f0e-7d29fc2c1c6f?msgId=ccb250ec-6db8-4d62-884d-a9ad3ced78c2Use chkntfs to reset chkdsk to default behaviorin command promptchkntfs /DMight want to try speedefrag it is used to schedule defrag to run on next boot, but will run chkdsk as part of the process.Freeware, just watch that it does not try to install toolbars etchttp://www.vcsoftwares.com/SpeeDefrag.htmlOne other thing that I can think of would be a boot sector virus with a hidden 1mb partition.Flash can help you here, Need to run Tdsskiller and aswmbr Quote Link to post Share on other sites
irregularjoe Posted March 21, 2013 Author Report Share Posted March 21, 2013 Thanks for that info, Pete. I appreciate it. I just posted an update to the saga. Quote Link to post Share on other sites
Pete_C Posted March 21, 2013 Report Share Posted March 21, 2013 I missed that it was a clean install on a defective drive that was the issue.Bad drive, toss it, drives are cheap these days. Quote Link to post Share on other sites
irregularjoe Posted March 21, 2013 Author Report Share Posted March 21, 2013 That's the plan. But want to get data off first. Quote Link to post Share on other sites
Pete_C Posted March 23, 2013 Report Share Posted March 23, 2013 I would try the icebox methodRemove old driveDo a clean install on new driveTake old drive and place it in an external enclosuer.Place this in a zip lock bag with a cooler gel pack, small slits to let the power and data cable through seal with duct tape.Place in freezer overnight.Then connect it to your computer, and copy what you can to a "recovery" folder on your new drive.You can worry about taking possession of etc later. Quote Link to post Share on other sites
irregularjoe Posted March 24, 2013 Author Report Share Posted March 24, 2013 I would try the icebox methodRemove old driveDo a clean install on new driveTake old drive and place it in an external enclosuer.Place this in a zip lock bag with a cooler gel pack, small slits to let the power and data cable through seal with duct tape.Place in freezer overnight.Then connect it to your computer, and copy what you can to a "recovery" folder on your new drive.You can worry about taking possession of etc later.Thanks, Pete. I have heard of that. Might be worth a try. Btw, "new drive" turned out to be another problem. I'm posting the updated story. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.