New
#31
The parameter/rcould take dozens of hours.
Lost partition on an external drive
-
-
New #32
When I use chkdsk /r on my working 7200 RPM HDD it takes about 2 HRS / TB if I recall correctly.The parameter/rcould take dozens of hours.
No idea how much that rate will go up with an ill HDD, but data recovery is a slow tedious process that requires a lot of patience from what I've seen here.
Thanks for your update @ joe
I know you'll see this.
Last edited by steve108; 27 Jan 2022 at 22:01.
-
-
-
New #35
Yes, it is progressing
86%, I think stage 1?
This is what it says now
Microsoft Windows [Version 10.0.19043.1466]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>CHKDSK f: /f /v /r /x
The type of the file system is NTFS.
Volume label is easystore.
Stage 1: Examining basic file system structure ...
File record segment 8500 is unreadable.
File record segment 8501 is unreadable.
File record segment 8502 is unreadable.
File record segment 8503 is unreadable.
File record segment 196BC is unreadable.
File record segment 196BD is unreadable.
File record segment 196BE is unreadable.
File record segment 196BF is unreadable.
File record segment 255C4 is unreadable.
File record segment 255C5 is unreadable.
File record segment 255C6 is unreadable.
File record segment 255C7 is unreadable.
File record segment 26BD4 is unreadable.
File record segment 26BD5 is unreadable.
File record segment 26BD6 is unreadable.
File record segment 26BD7 is unreadable.
File record segment 276F8 is unreadable.
File record segment 276F9 is unreadable.
File record segment 276FA is unreadable.
File record segment 276FB is unreadable.
File record segment 27C3C is unreadable.
File record segment 27C3D is unreadable.
File record segment 27C3E is unreadable.
File record segment 27C3F is unreadable.
File record segment 28E28 is unreadable.
File record segment 28E29 is unreadable.
File record segment 28E2A is unreadable.
File record segment 28E2B is unreadable.
Progress: 167500 of 194048 done; Stage: 86%; Total: 0%; ETA: 999:00:00
-
New #36
Those are probably the weak sectors in the MFT area ( I may be wrong. its just a guess). Let us wait and see if Checkdisk repairs the problem. When stage 1 is completed, checkdisk will perhaps go faster with other stages.
-
New #37
This is going to be very long ... And chkdsk will use large amount of ram if it doesn't completely max it out.
Loll.
-
New #38
Really surprising why Checkdisk should take such a long time when Hard Disk Sentinel reported no bad sector/s, only 5 weak sectors.It should have definitely passed Stage 1 by now.Let us wait for joejoe3's report. Most probably he will report the current status after he returns from office.
-
-
New #39
I think it's just because of the size of the disk. If it takes 3 days to go trough Stage 1, I can imagine 4 and 5.
There's Five Trillion Bytes to be verified on that disk.
-
New #40
The estimate usually given is 5 hours for 1TB. By that calculation 5TB should take only about 25 hours.I would think if it passes Stage 1, the rest should go through quickly. In any case there is no going back now. Stopping CheckDisk will do more harm. As long as it shows it is progressing, the OP needs to wait. ( Whenever I give a go-ahead with checkdisk, I hold my breath till the OP comes back and reports success. This time I have been holding my breath for too long. )
Quote
Related Discussions
