Windows 10: been running scanning and repair for a week!
been running scanning and repair for a week!
I had a problem with my HDD and had been running scanning and repair for a week now where it stuck at 27% since the first day.
I'm using chkdsk r/ f/ c: to check my 1Tb of HDD.
It had been too long for me. What should I do next? Should I wait the process or what?
It might be better to let the process run; there has been scuttlebutt that interrupting the once-started/once-ongoing process could result in even worse problems -- no boot/no load/no startup is one of a few worse things that can happen.
He's been letting the process run for a week now. What would you suggest be the cutoff point for waiting? 1 month? 1 year?
A week seems excessive to me.
IMO, the process has glitched and/or the HDD has suffered a catastrophic number of block failures.
A few years ago, I tried doing this on a new 2 TB USB HDD (file transfer issues).
After 18 hours, I cancelled the operation and returned the HDD to the store.
This is what I would do:
Do a hard power off - hold the power key down until the computer turns off.
Remove the old HDD. Install a new HDD.
Boot the computer from a Windows 10 installation USB flash drive or DVD. Clean install Windows 10 to the new HDD.
Connect the old HDD as a secondary drive and see what you can salvage off it.
I didn't see the part about it running a whole week, sorry!
I too would have cut it off once 24 hours+ hit.
However, here too, having an earlier backup of OS and data partitions would be useful -- for the old or for the new hard-drive.
Bad blocks can make for a very long 'chkdsk', as I know from personal experience. I had a 1TB USB drive that slipped off my lap and fell while running. There was an ominously loud 'ting' as the heads hit the platter
I ran Chkdsk /f /r on it, It did stick at one particular percentage for a very long time, how long I don't know, I had to go to sleep and let it get on with it. In the end it took two days to find just 4k of bad blocks. At that rate, a week would have had time to find about 16k. It's not
unreasonable unexpected that it can take this long. If you have the patience, I would just let it run. It does speed up dramatically once it gets past the bad blocks.
What is the history of this disk? What prompted the use of chkdsk? It seems to me that it's likely chkdsk is still running correctly, but has a fair few bad blocks to cope with.
Last edited by Bree; 3 Weeks Ago at 23:23.
I'd only wait an hour -- but then I always have backups so I'd just forget that HDD, install a new one and restore.
YOU CAN NEVER HAVE TOO MUCH BACKUP --especially with excellent FREE programs like Macrium around --simply NO excuse.
Anyway after that little lecture - what I'd do is boot a Linux Live distro up (they all can Read / Write Windows files) and see if any data on the HDD can be read - then grab what you want.
Linux Mint is probably the most "Windows Like" distro for this type of purpose - download to a USB stick and simply boot it - the file explorer will look very similar to Windows and the HDD's will be seen in the "browser List".
Download - Linux Mint
Another solution if you aren't comfortable with Linux is to see if you can access that HDD from another computer (set as shared) - It sometimes can work - especially if the Host computer has got itself a bit screwed.
The Wonders of Windows never cease to amaze me --I've had that scenario where HDD on computer A was barely readable but on Computer B accessing the HDD as a network drive allowed me to grab a load more files off the defective HDD. I learned though after that to ALWAYS HAVE BACKUP. Can't emphasize that too often.
If the HDD is totally defective then you've had it I'm afraid.
Don't try and keep using it - not worth it - HDD's are cheap enough these days.
An another solution would be to buy an external hard disk enclosure and see if you can access it when plugged in as an external USB drive on another computer.
If the drive has been developing faults over a period of time then it's probably time to scrap it. My damaged drive had a known cause for its bad blocks and was otherwise in good order. That one was worth saving - yours may not be.
Why not just use Kyhi's Recovery Tools that has Windows Explorer built right in it?
Windows 10 Recovery Tools - Bootable Rescue Disk
I am getting a BSOD (Blue Screen Of Death) Startup repair couldn't repair my pc and when I tried to reset the pc wont repair the problems used all the troubleshooting tools which didn't work. Won't let me boot into safe mode. After I go though all...
So, two days ago I got stuck in an automatic repair loop after trying to enable an old soundcard connected trhough usb in my DAW software.
I tried everything there is about fixing it (because reinstalling all the programs I got in...
My pc is :C440 Touch All-in-One (Lenovo)
Operating system : Windows 10
I can't run my PC, every time i try to run it shows me blue screen wrote on it
" Automatic repair couldn't repair your PC
I have two Windows 10 installations on my PC. Primary and temp.
The primary installation cannot boot with error "The boot configuration data file is missing some required information ".
This happened aftter I wiped out another third disk...
I've been trying to repair an error which system file checker gives me, however no matter what I try as it seems, I can't get windows to fix it.
So it begins with sfc /scannow, and when I create the log file, I find this: