Hey, as the thread title suggests, I'm having troubles with a disk check.
Firstly, I'd like to mention that I've had this PC for a while... I've even taken the whole thing apart and swapped out all of the components (slowly upgraded over time). It's actually at the stage where I've been left with all the old parts as spares, and put everything back together, almost exactly as it was when I bought it. All in all, the initial build is probably 2 or 3 years old now (for the most part, the specs can be found here).
After formatting the hard drive, putting things together back with the old build, and booting up Windows 8 onto it as a gift for my dad, most things were working fine, but one exe file which I copied across wasn't running (at least one which I noticed). I checked up the error code, found people with similar problems, and heard it could just be that the file was corrupted.
So, to get to the main point... I figured it wouldn't hurt to run a disk check, in case there were any other errors or problems. I knew it would take a while, so I opened command prompt, and typed in "chkdsk C: /r", before hitting enter, letting it schedule the disk check for next startup, rebooting the PC, and then leaving it to do its thing. It's been running probably for about 4 or so hours now, and for most of that time it's been at 27% on "Scanning and repairing drive (C". Normally I'd just give in and force shut down at this point, but I'm wondering... what's the best course of action if it doesn't get anywhere with this?
I'd really prefer not to force shut down, in case it causes any errors... I mean to say the least it's taken some effort and persistence to get the old build up and running again. =/
Any advice would be appreciated, including why it might be sticking at this point in the first place (my guess is because of finding an error it can't manage to fix and getting stuck in an infinite loop or something).
Thanks.
Edit - Ahh of course... sod's law comes to slap me in the face once again... I finish writing this post and submit it, after waiting a couple more hours in case the scan moved along a bit (something like 7 hours into the scan before I submitted this), and it suddenly decides it's finished the exact moment I press submit thread...
Moral of the story - even if it takes forever, just be patient while your PC runs a scan...
Sorry guys, as you were...
Firstly, I'd like to mention that I've had this PC for a while... I've even taken the whole thing apart and swapped out all of the components (slowly upgraded over time). It's actually at the stage where I've been left with all the old parts as spares, and put everything back together, almost exactly as it was when I bought it. All in all, the initial build is probably 2 or 3 years old now (for the most part, the specs can be found here).
After formatting the hard drive, putting things together back with the old build, and booting up Windows 8 onto it as a gift for my dad, most things were working fine, but one exe file which I copied across wasn't running (at least one which I noticed). I checked up the error code, found people with similar problems, and heard it could just be that the file was corrupted.
So, to get to the main point... I figured it wouldn't hurt to run a disk check, in case there were any other errors or problems. I knew it would take a while, so I opened command prompt, and typed in "chkdsk C: /r", before hitting enter, letting it schedule the disk check for next startup, rebooting the PC, and then leaving it to do its thing. It's been running probably for about 4 or so hours now, and for most of that time it's been at 27% on "Scanning and repairing drive (C". Normally I'd just give in and force shut down at this point, but I'm wondering... what's the best course of action if it doesn't get anywhere with this?
I'd really prefer not to force shut down, in case it causes any errors... I mean to say the least it's taken some effort and persistence to get the old build up and running again. =/
Any advice would be appreciated, including why it might be sticking at this point in the first place (my guess is because of finding an error it can't manage to fix and getting stuck in an infinite loop or something).
Thanks.
Edit - Ahh of course... sod's law comes to slap me in the face once again... I finish writing this post and submit it, after waiting a couple more hours in case the scan moved along a bit (something like 7 hours into the scan before I submitted this), and it suddenly decides it's finished the exact moment I press submit thread...
Moral of the story - even if it takes forever, just be patient while your PC runs a scan...
Sorry guys, as you were...
My Computer
System One
-
- OS
- Windows8/ Windows7
- System Manufacturer/Model
- HP Pavillion 6310uk