This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
My first problem is that i run powershell with admin rights and ran chkdsk f: /f /r . I thought it would restart pc after that but no, just started running chkdsk until now, so i could access the disk. Now, after about 3 hours total progress is 0%, but in phase 2, is this normal? should i wait? HD is not SSD and with 3.63TB capacity. I made chkdsk previously with CMD and didnt take so long, maybe is slower cause didnt boot windows?
Another problem is that the hard drive which made the windows boot was hit and cant be recovered. I had a SSD with the old windows partition, but dont know why needed this other hard drive to boot, i couldnt start Windows so i saw in the internet that could use bootrec /fixmbr, then bootrec /fixboot and then bootrec /rebuildcbd but that just made it worse. After making a clean install in other SSD i see the old windows partition in the other SSD shows my partition with all the data as EFI dont know why and cant access it, i tried to assign it a letter but gives me access denied
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
No, i am completely sure it was with the same partition which was the only one failing, the difference is that this one is with powershell and with no reboot, i can use windows freely and my hard drive is not unmounted, i could access it while it is running chkdsk
You could risk rebooting then. But, I'd leave it go a couple more hours at least with that kind of thing and see if you see the state increasing.
Don't know why. Maybe it has an issue since then. Maybe you did it with a different drive and remembering incorrectly? Not sure.
Adding this in since its relevant to that: https://superuser.com/questions/710516/possible-chkdsk-hang-safe-to-shutdown
Generally, if the drive light isn't blinking, I'm prone to hitting the reboot button on stuck things at the very least. Its as good as it will get there lol. If it is blinking, its more risky.
But i did a chkdsk /f /r some days ago with cmd and automatic booting in the same partition and didnt take so long
/r use can supposedly take a long time as it tries to recover readable information. chkdsk can run right away if the drive meets the requirements to do so.
/r is slower than a full format because of the recovery. A full format will likely take hours. So chkdsk /r will run even longer.
If you see the stage increasing then it should still be running. There's about 12 stages or so when I run chkdsk.
The difference between chkdsk /f /r and full format is that a full format doesn't need to do recovery since everything is destroyed and a full format goes well with a clean install of everything whereas a chkdsk /r may leave issues. The /r can only recover readable information. It fails on anything else. So a chkdsk is longer since you're trying to keep everything but stability isn't as guaranteed as a full format plus clean OS install.
