Several problems with hard drives, with CHKDSK and EFI partition

Anonymous
2022-04-15T17:53:59+00:00

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

Windows for home | Windows 10 | Files, folders, and storage

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.

0 comments

64 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-04-15T18:10:38+00:00

    /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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-04-15T18:14:30+00:00

    But i did a chkdsk /f /r some days ago with cmd and automatic booting in the same partition and didnt take so long

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-04-15T18:19:05+00:00

    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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-04-15T18:23:04+00:00

    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

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-04-15T18:24:51+00:00

    Added in a further edit in my last reply for if chkdsk gets stuck.

    Was this answer helpful?

    0 comments