chkdsk /r on a 14TB drive

[DCSeven]

I'm all Googled out on trying to find the answer so here I am.
Got a prompt to scan for possible errors on a 14TB drive in a USB-C dock. Clicked Scan with option to fix errors and it froze at about 16,000 files scanned in stage 4. Could stop it, didn't even see a process for it in Task Manager. So, I shut the machine down and rebooted to try the scan from a command prompt. I knew it would take forever but, some 6 hours later, I noticed the PC was starting to lag. Opened Task manager and it showed it was using almost 17,000,000K in memory and still climbing. Never seen anything even close to that!

Anyway, even though I know it's not the best practice, I exited CMD, shut the machine down and added the drive internally, hoping it might somehow make a difference. Not even close - Not even 1,000 files in and it's already showing 14,800,000K and going up.

SO... the big question is, is there anyway to finish a scan on a large drive that's not eventually going to lock up my computer?

 

[SIW2]

Housekeeping is a lot less stressful if the partitions are sensible sizes.

 

[DCSeven]

Housekeeping is a lot less stressful if the partitions are sensible sizes.

That almost sounds like a Chinese proverb. But I'm not sure what that means in regards to my question.

 

[samuria]

If windows has asked to check its likley the dirty bit is set when windows starts it write a dirty bit to the drive when shut down correct it clears it if its not shut down right and it finds dirty bit it asks to scan check if its set and you can clear it Dirty Bit: What Is It & How to Set/Clear/Reset It

 

[DCSeven]

If windows has asked to check its likley the dirty bit is set when windows starts it write a dirty bit to the drive when shut down correct it clears it if its not shut down right and it finds dirty bit it asks to scan check if its set and you can clear it Dirty Bit: What Is It & How to Set/Clear/Reset It

That looks promising, although I'll admit some of the information on that page is a little over my head. BUT - that's how I've learned what all I do know about computers - Read and try it, read and try it. Hopefully I'll be able to figure it out. Thanks for the info!

 

[file3456]

14 MASSIVE terabytes being read and written to via USB is going to not only be slow as molasses in the Antarctic, but prone to all kinds of errors. For a drive that size you want to use SATA - a direct SATA connection if at all possible. This is one reason why I never buy USB HDDs. I use my internal connections. It's fine for small drives, but still very slow and problematic. Especially if you don't use the safe to remove hardware icon and whatnot.

Having said that, I doubt it's a dirty bit. It's probably a USB mess up in Windows. You can try this USB drive in safe mode or use USBDeView and remove the device and reattach.

You also want to make sure Windows' power options don't limit the USB connection's performance. Also, go into Device Manager under the USB root hubs. Double click each one and change this option in the screenshot to off.

 

[DCSeven]

...USB is going to not only be slow as molasses in the Antarctic, but prone to all kinds of errors. For a drive that size you want to use SATA - a direct SATA connection if at all possible. .

The only reason I use the dock is to transfer files to drive I keep offline, for backup. As I said above, I did put the drive in my tower and tried scanning it again. There's no noticeable increase in speed if any at all (expected) but the memory useage is just as bad and I know it'll eventualy lock up my computer. I'm still trying to weed through the information that samuria posted. It might just be a dirty bit because I'd accidentally pulled the USB plug on the dock while it was writing to the drive.

 

[SIW2]

win10/11 chdsk is faster than the win7 version. You could boot win10/11 installation media or pe and run chkdsk from there against the partitions on the disk.

you can borrow mine 2261v7.iso or use hirens which is win10 based pe

Have you got just one giant partition?

you could try using disk management or diskgenius to shrink it, leaving the rest as unallocated space. Then run chkdsk against that now smaller partition.